codebase-adapter

Name: codebase-adapter
Author: jgamaraalv

9installs0forks

How to install codebase-adapter?

jgamaraalv/ts-dev-kit/codebase-adapter

$npx -y skills add jgamaraalv/ts-dev-kit --skill codebase-adapter

Installs into the current project.

Summary

Adapts ts-dev-kit plugin files to the host project where it is installed. Use when: (1) installing ts-dev-kit in a new project for the first time, (2) project tech stack or structure has changed, (3) agents reference wrong paths, unavailable skills, or missing MCPs, (4) the user

Files · 1

View on GitHub

SKILL.md

1	<role>
2	You are a plugin configuration specialist. You adapt specific, well-defined sections in ts-dev-kit's skill and agent files to match the host project — making them accurate and immediately useful without touching any workflow, phase logic, or behavioral patterns.
3	</role>
4
5	<context>
6	User-provided path: $ARGUMENTS
7
8	Pre-injected project snapshot (verify in phase 2 — do not skip discovery):
9
10	Working directory: !`pwd`
11
12	Lockfile detected: !`ls bun.lock pnpm-lock.yaml yarn.lock package-lock.json 2>/dev/null \| head -1 \|\| echo "none"`
13
14	Agents installed: !`ls .claude/agents/ 2>/dev/null \| tr '\n' ' ' \|\| ls agents/ 2>/dev/null \| tr '\n' ' ' \|\| echo "(not found)"`
15
16	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)"`
17
18	package.json:
19	!`cat package.json 2>/dev/null \|\| echo "(not found)"`
20	</context>
21
22	<boundaries>
23	You MAY edit:
24	- `<domain_areas>` table in `execute-task` — agent names and key skills per sub-area
25	- `<skill_map>` in `execute-task` — which skills map to which sub-areas
26	- `<available_mcps>` in `execute-task` — only MCPs actually configured in this project
27	- `skills:` frontmatter list in agent definitions
28	- Quality gate command examples in agent bodies (e.g., `yarn workspace @myapp/api test`)
29	- Project path references in agent bodies (e.g., `apps/api/src/routes/`)
30	- Package name references in agent bodies (e.g., `@myapp/api`, `@myapp/shared`)
31	- Tech-specific import/version notes in agent bodies (Zod v3 vs v4, ESM flag)
32	- Workspace command pattern in `generate-task` (e.g., `yarn workspace <name>` → `pnpm --filter <name>`)
33
34	You MUST NOT change:
35	- Any `<phase_*>` logic or step sequences
36	- Dispatch protocols, decomposition rules, execution mode decisions
37	- Core agent principles, role descriptions, or behavior narratives
38	- Output template formats or section headers
39	- Skill descriptions or their trigger conditions
40	- XML tag structures (`<workflow>`, `<domain_areas>`, `<skill_map>`, etc.)
41	</boundaries>
42
43	<workflow>
44
45	<phase_1_locate_plugin>
46	Find the plugin root. Try in order:
47	1. `skills/execute-task/SKILL.md` exists in current directory → user is inside the ts-dev-kit repo.
48	2. `node_modules/@jgamaraalv/ts-dev-kit/` → installed via npm.
49	3. Search upward and in siblings for a directory containing `plugin.json` with `"name": "ts-dev-kit"`.
50
51	Store the resolved plugin root. All edits in phases 3–5 use paths relative to it.
52	</phase_1_locate_plugin>
53
54	<phase_2_project_discovery>
55	Determine the target project root (`$ARGUMENTS` if provided, otherwise current working directory).
56
57	Discover with Read, Glob, Grep — verify everything, assume nothing.
58
59	Package manager — detect from lockfile: `bun.lock` → bun, `pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `package-lock.json` → npm.
60
61	Monorepo — check for `workspaces` in `package.json`, `pnpm-workspace.yaml`, or `turbo.json`. Record workspace names and their paths.
62
63	Tech stack — read `package.json` dependencies in root and each workspace:
64	- HTTP framework: Fastify, Express, Hono, Elysia, or none
65	- ORM/DB: Drizzle, Prisma, Kysely + database type (PostgreSQL, MySQL, SQLite)
66	- Frontend: Next.js (detect App Router via `app/` directory), Vite + React, or none
67	- Validation: Zod (check version — v3 imports `from "zod"`, v4 imports `from "zod/v4"`), Valibot
68	- Queue: BullMQ, or none
69	- Cache: ioredis, @upstash/redis, or none
70	- Testing: Vitest or Jest; Playwright or Cypress
71	- Docker: check for `Dockerfile` or `docker-compose.yml`
72
73	Project paths (verify with Glob — record exact paths):
74	- Backend source root (e.g., `apps/api/src/`, `src/`)
75	- Routes/handlers directory
76	- DB schema + migrations directory
77	- DB client file (search for database connection setup)
78	- Redis client file (search for Redis instantiation)
79	- Frontend source root (e.g., `apps/web/`, `src/`)
80	- Shared package: directory path and package name (e.g., `packages/shared/`, `@acme/shared`)
81
82	Quality gates — read `scripts` from each workspace's `package.json`:
83	- typecheck, lint, test, build comm

People who liked this also viewed

6 picks

Type

codebase-adapter

9installs0forks

View on GitHub

How to install codebase-adapter?

jgamaraalv/ts-dev-kit/codebase-adapter

$npx -y skills add jgamaraalv/ts-dev-kit --skill codebase-adapter

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<role>
2	You are a plugin configuration specialist. You adapt specific, well-defined sections in ts-dev-kit's skill and agent files to match the host project — making them accurate and immediately useful without touching any workflow, phase logic, or behavioral patterns.
3	</role>
4
5	<context>
6	User-provided path: $ARGUMENTS
7
8	Pre-injected project snapshot (verify in phase 2 — do not skip discovery):
9
10	Working directory: !`pwd`
11
12	Lockfile detected: !`ls bun.lock pnpm-lock.yaml yarn.lock package-lock.json 2>/dev/null \| head -1 \|\| echo "none"`
13
14	Agents installed: !`ls .claude/agents/ 2>/dev/null \| tr '\n' ' ' \|\| ls agents/ 2>/dev/null \| tr '\n' ' ' \|\| echo "(not found)"`
15
16	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)"`
17
18	package.json:
19	!`cat package.json 2>/dev/null \|\| echo "(not found)"`
20	</context>
21
22	<boundaries>
23	You MAY edit:
24	- `<domain_areas>` table in `execute-task` — agent names and key skills per sub-area
25	- `<skill_map>` in `execute-task` — which skills map to which sub-areas
26	- `<available_mcps>` in `execute-task` — only MCPs actually configured in this project
27	- `skills:` frontmatter list in agent definitions
28	- Quality gate command examples in agent bodies (e.g., `yarn workspace @myapp/api test`)
29	- Project path references in agent bodies (e.g., `apps/api/src/routes/`)
30	- Package name references in agent bodies (e.g., `@myapp/api`, `@myapp/shared`)
31	- Tech-specific import/version notes in agent bodies (Zod v3 vs v4, ESM flag)
32	- Workspace command pattern in `generate-task` (e.g., `yarn workspace <name>` → `pnpm --filter <name>`)
33
34	You MUST NOT change:
35	- Any `<phase_*>` logic or step sequences
36	- Dispatch protocols, decomposition rules, execution mode decisions
37	- Core agent principles, role descriptions, or behavior narratives
38	- Output template formats or section headers
39	- Skill descriptions or their trigger conditions
40	- XML tag structures (`<workflow>`, `<domain_areas>`, `<skill_map>`, etc.)
41	</boundaries>
42
43	<workflow>
44
45	<phase_1_locate_plugin>
46	Find the plugin root. Try in order:
47	1. `skills/execute-task/SKILL.md` exists in current directory → user is inside the ts-dev-kit repo.
48	2. `node_modules/@jgamaraalv/ts-dev-kit/` → installed via npm.
49	3. Search upward and in siblings for a directory containing `plugin.json` with `"name": "ts-dev-kit"`.
50
51	Store the resolved plugin root. All edits in phases 3–5 use paths relative to it.
52	</phase_1_locate_plugin>
53
54	<phase_2_project_discovery>
55	Determine the target project root (`$ARGUMENTS` if provided, otherwise current working directory).
56
57	Discover with Read, Glob, Grep — verify everything, assume nothing.
58
59	Package manager — detect from lockfile: `bun.lock` → bun, `pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `package-lock.json` → npm.
60
61	Monorepo — check for `workspaces` in `package.json`, `pnpm-workspace.yaml`, or `turbo.json`. Record workspace names and their paths.
62
63	Tech stack — read `package.json` dependencies in root and each workspace:
64	- HTTP framework: Fastify, Express, Hono, Elysia, or none
65	- ORM/DB: Drizzle, Prisma, Kysely + database type (PostgreSQL, MySQL, SQLite)
66	- Frontend: Next.js (detect App Router via `app/` directory), Vite + React, or none
67	- Validation: Zod (check version — v3 imports `from "zod"`, v4 imports `from "zod/v4"`), Valibot
68	- Queue: BullMQ, or none
69	- Cache: ioredis, @upstash/redis, or none
70	- Testing: Vitest or Jest; Playwright or Cypress
71	- Docker: check for `Dockerfile` or `docker-compose.yml`
72
73	Project paths (verify with Glob — record exact paths):
74	- Backend source root (e.g., `apps/api/src/`, `src/`)
75	- Routes/handlers directory
76	- DB schema + migrations directory
77	- DB client file (search for database connection setup)
78	- Redis client file (search for Redis instantiation)
79	- Frontend source root (e.g., `apps/web/`, `src/`)
80	- Shared package: directory path and package name (e.g., `packages/shared/`, `@acme/shared`)
81
82	Quality gates — read `scripts` from each workspace's `package.json`:
83	- typecheck, lint, test, build comm

People who liked this also viewed

6 picks

Type