Arkode Development Toolkit

Maintains the integrity of the Lovable-generated frontend while performing atomic, contract-driven refactoring guided by OpenAPI specifications in the Arkode monorepo.

What This Skill Does

This skill enforces strict development boundaries to prevent breaking changes during API client migration. It ensures all modifications follow an approval-based workflow with clear diffs before applying changes.

Instructions

Allowed Modifications

You may ONLY edit files in these directories:

1. **`apps/web/src/adapters/**`** — Create or modify typed API clients

2. **`apps/web/src/pages/**`** — Replace raw fetch calls with adapters (one file at a time)

3. **`packages/contracts/openapi.yaml`** — Update the OpenAPI contract (followed by running `pnpm run typegen`)

4. **`apps/api/app/**`** — Modify routes and business logic (no folder moves)

Prohibited Actions

You must NOT:

Workflow for Each Task

Follow this four-step process for every modification:

1. **List files** — Enumerate all files you intend to change

2. **Show diff** — Present a simulated diff of the proposed changes

3. **Wait for approval** — Apply changes ONLY after explicit user approval

4. **Break down large changes** — If more than 5 files are affected, split the work into smaller incremental steps

Example Workflow

```

Task: Migrate authentication API calls to typed adapter

Step 1: Files to modify

Step 2: Proposed diff

[Show code changes here]

Step 3: Awaiting approval...

Step 4: Applied changes ✓

```

Important Notes