codebase-adapter

Pre-injected project snapshot (verify in phase 2 — do not skip discovery):

Working directory: !pwd

Lockfile detected: !ls bun.lock pnpm-lock.yaml yarn.lock package-lock.json 2>/dev/null | head -1 || echo "none"

Agents installed: !ls .claude/agents/ 2>/dev/null | tr '\n' ' ' || ls agents/ 2>/dev/null | tr '\n' ' ' || echo "(not found)"

MCP servers configured: !python3 -c "import json; s=json.load(open('.claude/settings.json')); print(', '.join(s.get('mcpServers',{}).keys()) or '(none)')" 2>/dev/null || echo "(not found)"

package.json: !cat package.json 2>/dev/null || echo "(not found)"

You MUST NOT change:

• Any <phase_*> logic or step sequences
• Dispatch protocols, decomposition rules, execution mode decisions
• Core agent principles, role descriptions, or behavior narratives
• Output template formats or section headers
• Skill descriptions or their trigger conditions
• XML tag structures (<workflow>, <domain_areas>, <skill_map>, etc.)

<phase_1_locate_plugin> Find the plugin root. Try in order:

1. skills/execute-task/SKILL.md exists in current directory → user is inside the ts-dev-kit repo.
2. node_modules/@jgamaraalv/ts-dev-kit/ → installed via npm.
3. Search upward and in siblings for a directory containing plugin.json with "name": "ts-dev-kit".

Store the resolved plugin root. All edits in phases 3–5 use paths relative to it. </phase_1_locate_plugin>

<phase_2_project_discovery> Determine the target project root ($ARGUMENTS if provided, otherwise current working directory).

Discover with Read, Glob, Grep — verify everything, assume nothing.

Package manager — detect from lockfile: bun.lock → bun, pnpm-lock.yaml → pnpm, yarn.lock → yarn, package-lock.json → npm.

Monorepo — check for workspaces in package.json, pnpm-workspace.yaml, or turbo.json. Record workspace names and their paths.

Tech stack — read package.json dependencies in root and each workspace:

• HTTP framework: Fastify, Express, Hono, Elysia, or none
• ORM/DB: Drizzle, Prisma, Kysely + database type (PostgreSQL, MySQL, SQLite)
• Frontend: Next.js (detect App Router via app/ directory), Vite + React, or none
• Validation: Zod (check version — v3 imports from "zod", v4 imports from "zod/v4"), Valibot
• Queue: BullMQ, or none
• Cache: ioredis, @upstash/redis, or none
• Testing: Vitest or Jest; Playwright or Cypress
• Docker: check for Dockerfile or docker-compose.yml

Project paths (verify with Glob — record exact paths):

• Backend source root (e.g., apps/api/src/, src/)
• Routes/handlers directory
• DB schema + migrations directory
• DB client file (search for database connection setup)
• Redis client file (search for Redis instantiation)
• Frontend source root (e.g., apps/web/, src/)
• Shared package: directory path and package name (e.g., packages/shared/, @acme/shared)