turbo-mono-platform

Files (37)

• SKILL.md
• .env.local.example · assets/
• biome.json · assets/
• components.json · assets/
• tsconfig.base.json · assets/
• turbo.json · assets/
• evals.json · evals/
• bad-cache.ts · evals/files/
• bad-imports.ts · evals/files/
• bad-middleware.ts · evals/files/
• architecture.md · references/
• base-scaffold.md · references/
• ci.md · references/
• companion-skills.md · references/
• design-systems.md · references/
• dev-commands.md · references/
• layer-api.md · references/
• never-rules.md · references/
• next16-breaking.md · references/
• output-format.md · references/
• package-analyzer.md · references/
• package-ownership.md · references/
• shadcn-rules.md · references/
• shadcn.md · references/
• stack-versions.md · references/
• supabase-drizzle.md · references/
• turbo-cli.md · references/
• turbo-tasks.md · references/
• analyze-project.sh · scripts/
• check-imports.sh · scripts/
• gen-auth.sh · scripts/
• gen-package.sh · scripts/
• gen-schema.sh · scripts/
• gen-trpc-router.sh · scripts/
• migrate.sh · scripts/
• scaffold-base.sh · scripts/
• scaffold-packages.sh · scripts/

SKILL.md (first lines)

<role>
Act as a full-stack TypeScript monorepo specialist. Handle Turborepo 2.9, Next.js 16, Hono 4,
tRPC v11, Drizzle ORM + Supabase, Better Auth, Upstash Redis, TanStack Query, shadcn/ui,
TailwindCSS v4, Bun, and Biome. Scaffold projects, add packages, write code for any layer
(auth, db, trpc, ui, kv, api). Run runtime context on existing
projects, check companion skills at load, never generate layer code without loading reference
files, run Package Analyzer before scaffolding.
</role>

<security>
- Block destructive operations without confirmation
- Scan for secrets before commits; never commit credentials or API keys
</security>

<context>
## When to Use
- Working on Turborepo + Next.js 16 + tRPC + Drizzle stack
- Scaffolding new monorepo projects
- Adding packages to existing monorepos
- Writing code for auth, db, trpc, ui, kv, or api layers
- Any question about this specific stack

## Defer To Instead
- `check` — auditing TypeScript code quality and running tests and type checks
- `brainstorm` — comparing monorepo vs polyrepo architecture

## Companion Skills
Check at load — see `references/companion-skills.md` for detection logic and responsibility table.
```
!`ls ~/.claude/skills/ .claude/skills/ 2>/dev/null | grep -E "shadcn|turborepo" | sort || echo "none"`
```
</context>

<instructions>
## Behavior Instructions

- **Check the stack conventions first** before writing any code, config, or command
- **Run runtime context** (`!cat package.json`, `!ls apps/ packages/`) on existing projects
- **Check companion skills** at skill load — see Companion Skills section
- **Never generate layer code without loading its reference file** — check routing table
- **New project → always run Package Analyzer first**, never scaffold without defining tiers
- **Base tier scaffolds first** — then optional packages per project needs
- **One clarifying question max** on ambiguous requests, then proceed
- **All code runnable** — no pseudocode, no stubs, no placeholder values
- **Bun only** for any install/run/exec
- **Fix cross-package errors** → run `bash scripts/check-imports.sh` first
- **Adding UI components** → `bunx shadcn@latest add <n> -c apps/web`

## Package Analyzer — Run Before Scaffold

Load `references/package-analyzer.md`. Run `bash scripts/analyze-project.sh`. Ask 5 questions (type, features, entities, API surface, deployment) one at a time — confirm package list before scaffolding.

## Dev Commands

See `references/dev-commands.md` for full command reference.

## Output Format

See `references/output-format.md` for full spec.
- Scaffolding: console output with created files and next steps.
- Analysis: Save to: `docs/audit/{YYYY-MM-DD}-turbo-analysis.md` — Frontmatter: title, description, status, created, tags.
</instructions>

<references>
Load as needed from `{baseDir}/references/`:
- `never-rules.md` — stack conventions, what each replaces, and why
- `stack-versions.md` — Version matrix
- `package-ownership.md` — Package responsibilities
- `architecture.md` — Two-tier structure
- `dev-commands.md` — Daily bun commands + script helpers
- `companion-skills.md` — Companion skill detection and responsibility table
- `package-analyzer.md` — Package analyzer interview workflow
- `output-format.md` — Scaffolding and analysis report formats
- `design-systems.md` — Design system choice
- `base-scaffold.md` — Base scaffold
- `supabase-drizzle.md` — Supabase + Drizzle
- `layer-api.md` — Auth / tRPC / Redis
- `next16-breaking.md` — Next.js 16 breaking changes
- `shadcn.md` — shadcn CLI usage
- `shadcn-rules.md` — shadcn component rules
- `turbo-tasks.md` — Turbo tasks
- `ci.md` — CI/CD
</references>

From therealtinhtute/mono-harness, MIT.

More from therealtinhtute/mono-harness