init-prototype
This skill bootstraps a new prototype monorepo with the standard package structure: core, api, ui, mcp, and types packages — all wired up with Bun workspaces. It should be used when the user wants to start a new prototype, create a new project, scaffold a monorepo, or says anything like "new prototype", "new project", "let's start fresh", "set up the repo", "init", or "bootstrap."
What this skill does
# Prototype Bootstrapper
Set up a new prototype monorepo using **Bun workspaces** with the following
standard package structure. Follow this exactly — do not improvise the structure.
## Monorepo Structure
```
[project-name]/
├── package.json # Root workspace config
├── bunfig.toml # Bun configuration
├── biome.json # Biome linting + formatting config
├── tsconfig.json # Base tsconfig
├── justfile # Quick setup and dev actions
├── CLAUDE.md # Project-specific context for Claude Code
├── .github/
│ └── workflows/
│ └── ci.yml # GitHub Actions CI
├── .claude/
│ └── settings.json # Project-level Claude Code settings
├── packages/
│ ├── core/ # Core business logic (variable tech)
│ │ ├── src/
│ │ │ └── index.ts
│ │ ├── package.json
│ │ └── tsconfig.json
│ ├── types/ # Shared TypeScript types + Zod schemas
│ │ ├── src/
│ │ │ └── index.ts
│ │ ├── package.json
│ │ └── tsconfig.json
│ ├── api/ # Hono API (follows prototyping-skills:generate-api conventions)
│ │ ├── CLAUDE.md
│ │ ├── src/
│ │ │ ├── index.ts
│ │ │ └── routes/
│ │ │ └── health.ts
│ │ ├── package.json
│ │ └── tsconfig.json
│ ├── ui/ # Next.js dashboard (follows prototyping-skills:generate-ui conventions)
│ │ ├── CLAUDE.md
│ │ ├── src/
│ │ │ └── app/
│ │ │ ├── layout.tsx
│ │ │ ├── page.tsx
│ │ │ └── globals.css
│ │ ├── components.json
│ │ ├── next.config.ts
│ │ ├── postcss.config.mjs
│ │ ├── package.json
│ │ └── tsconfig.json
│ └── mcp/ # MCP server (follows prototyping-skills:generate-mcp conventions)
│ ├── CLAUDE.md
│ ├── src/
│ │ ├── index.ts
│ │ └── tools/
│ ├── package.json
│ └── tsconfig.json
```
## Step-by-Step Bootstrap Process
### 1. Root workspace configuration
**package.json:**
```json
{
"name": "[project-name]",
"private": true,
"workspaces": ["packages/*"],
"scripts": {
"dev": "bun --filter '*' dev",
"dev:api": "bun --filter api dev",
"dev:ui": "bun --filter ui dev",
"dev:mcp": "bun --filter mcp dev",
"check": "bunx @biomejs/biome check .",
"fix": "bunx @biomejs/biome check --write .",
"test": "bun test"
},
"devDependencies": {
"@biomejs/biome": "^1.9"
}
}
```
**bunfig.toml:**
```toml
[install]
peer = false
```
**tsconfig.json** (base config):
```json
{
"compilerOptions": {
"target": "ESNext",
"module": "ESNext",
"moduleResolution": "bundler",
"esModuleInterop": true,
"strict": true,
"skipLibCheck": true,
"declaration": true,
"declarationMap": true,
"sourceMap": true,
"composite": true,
"paths": {
"@repo/*": ["./packages/*/src"]
}
}
}
```
**biome.json:**
```json
{
"$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
"organizeImports": { "enabled": true },
"linter": {
"enabled": true,
"rules": { "recommended": true }
},
"formatter": {
"enabled": true,
"indentStyle": "tab",
"lineWidth": 100
},
"javascript": {
"formatter": {
"quoteStyle": "double",
"semicolons": "always"
}
}
}
```
**justfile:**
```makefile
# Default: list available recipes
default:
@just --list
# Install all dependencies
setup:
bun install
# Run all packages in dev mode
dev:
bun run dev
# Run only the API
dev-api:
bun run dev:api
# Run only the UI
dev-ui:
bun run dev:ui
# Lint and format with Biome
check:
bunx @biomejs/biome check .
# Lint and format with auto-fix
fix:
bunx @biomejs/biome check --write .
# Run all tests
test:
bun test
# Run tests in watch mode
test-watch:
bun test --watch
```
**.github/workflows/ci.yml:**
```yaml
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: oven-sh/setup-bun@v2
- run: bun install
- run: bunx @biomejs/biome check .
- run: bun test
```
Add `@biomejs/biome` as a root dev dependency in **package.json:**
```json
{
"devDependencies": {
"@biomejs/biome": "^1.9"
}
}
```
### 2. Types package (create first — others depend on it)
Hold all shared TypeScript types AND Zod schemas used across packages.
```json
{
"name": "@repo/types",
"version": "0.1.0",
"type": "module",
"exports": { ".": "./src/index.ts" },
"dependencies": {
"zod": "^3"
}
}
```
Starter `src/index.ts`:
```typescript
import { z } from "zod";
// Entity modeling: use Schema.org property names where a relevant type exists.
// See https://schema.org/CreativeWork — only include fields you actually need.
export const ItemSchema = z.object({
id: z.string(),
name: z.string(),
dateCreated: z.string().datetime(),
});
export type Item = z.infer<typeof ItemSchema>;
```
### 3. Core package
The core package is where the prototype's unique functionality lives. Its tech stack
varies per prototype. Set up the shell and let the user define what goes here.
```json
{
"name": "@repo/core",
"version": "0.1.0",
"type": "module",
"exports": { ".": "./src/index.ts" },
"dependencies": {
"@repo/types": "workspace:*"
}
}
```
### 4. API, UI, MCP packages
Set these up following the conventions in the `prototyping-skills:generate-api`,
`prototyping-skills:generate-ui`, and `prototyping-skills:generate-mcp` skills
respectively. Create minimal working starters:
- **API**: Health check route, CORS middleware, Swagger UI mounted
- **UI**: Root layout with sidebar, home page with placeholder content, shadcn/ui initialised
- **MCP**: Server entry point with stdio transport, one placeholder tool
### 5. Generate the project CLAUDE.md
After scaffolding, create a `CLAUDE.md` at the project root. Ask the user what the
prototype is about and fill in this template:
```markdown
# [Project Name]
## What This Prototype Does
[Description from user]
## Monorepo Structure
- `packages/core` — Core logic: [what the core does + any special tech]
- `packages/types` — Shared TypeScript types and Zod schemas
- `packages/api` — Hono API with @hono/zod-openapi (port 3001)
- `packages/ui` — Next.js dashboard with shadcn/ui (port 3000)
- `packages/mcp` — MCP server using @modelcontextprotocol/sdk
## Stack & Conventions
- **Runtime**: Bun
- **Monorepo**: Bun workspaces
- **Linting + Formatting**: Biome (not ESLint/Prettier)
- **Testing**: bun:test
- **CI**: GitHub Actions (.github/workflows/ci.yml)
- **Task runner**: justfile
- **API**: Hono + @hono/zod-openapi — all routes use `createRoute` + `app.openapi()`, JSON:API spec paths
- **UI**: Next.js 16 App Router + shadcn/ui — Server Components by default, Server Actions for mutations
- **MCP**: @modelcontextprotocol/sdk with stdio transport
- **Database**: bun:sqlite when persistence is needed
- **Types**: Shared via @repo/types, never duplicate across packages
## Team
Multiple people work on this prototype. Follow the global skill conventions unless
a deviation is documented below.
## Deviations from Team Defaults
<!-- Document any approved deviations here so all team members understand why -->
<!-- Format: what was changed, why, who approved it, what to watch out for -->
_None yet._
## Core Package — Prototype-Specific Tech
<!-- This section is for tech unique to THIS prototype's core package -->
[Libraries, patterns, or approaches specific to this prototype's core functionality]
## Commands
- `bun install` — Install all dependencies
- `bun run dev` — Run all packages in dev mode
- `bun run dev:api` — API only
- `bun run dev:ui` — UI only
- `bun run check` — Lint and format check (Biome)
- `bun run fix` — Lint and format with auto-fix (Biome)
- `bun test` — Run all tests (bun:test)
- `just` — List all available tasks (justfiRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.