From prototyping-skills
This skill should be used when the user is working on a prototype monorepo with the standard Bun workspace structure (core, types, api, ui, mcp packages), mentions "team defaults", "deviation protocol", "our conventions", "standard stack", asks about anti-patterns, or references @repo/types, @repo/core, Bun workspaces, or any of the stable packages. It also applies when the user mentions "plan mode" in the context of suggesting alternatives to established patterns.
npx claudepluginhub kjgarza/marketplace-claude --plugin prototyping-skillsThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
These conventions apply to all prototypes built with this team's standard monorepo structure. Multiple people work on each prototype, so consistency matters.
When working in execution mode, follow the defaults below without question.
When working in Plan mode and an alternative to a default is worth considering, follow this protocol:
packages/core (the variable package)@repo/typesWhen a deviation is approved, add it to the project's CLAUDE.md under "Deviations from Team Defaults" with: what was changed, why, who approved it, and what other team members should watch out for.
The core package is expected to change tech per prototype — that is low risk by design. API, UI, and MCP stacks changing is medium-to-high risk because it creates inconsistency across prototypes and requires the team to context-switch.
bun:test (not Jest, Vitest, etc.).github/workflows/ci.yml)createRoute() + app.openapi(). Paths follow JSON:API spec.bun:sqlite when persistence is needed. Not better-sqlite3, Prisma, or Drizzle unless deviation approved.@repo/types package. Types and Zod schemas defined once.headline not title, datePublished not publishedAt, text not body). Only include fields actually needed; enforce strict types.When introducing new technologies to the stack (libraries, frameworks, tools not already
in the defaults above), use the /context7 MCP to fetch up-to-date documentation and examples
before writing code. This prevents hallucinated APIs and outdated patterns.
@repo/core — All business logic. Variable tech stack per prototype.@repo/types — All shared types and Zod schemas. Single source of truth.packages/api — Thin HTTP wrapper around core. Hono + OpenAPI.packages/ui — Dashboard visualisation. Next.js + shadcn/ui.packages/mcp — Thin MCP wrapper around core. Official SDK.superpowers:test-driven-development for new featuresbun test before merge/generate-tests after scaffolding to set up test directories, helpers, and example testssrc/routes/items.ts → tests/routes/items.test.tsWhen introducing a new approach, delete the old code in the same PR. Do not layer new code on top of old code and leave both in place.
Deviation protocol addition — when evaluating an alternative approach, add this step:
Replacement Check — Does this replace existing functionality? If yes, identify and remove the old implementation in the same PR. Do not leave dead code.
Anti-patterns:
// TODO: remove old implementation commentsEnforcement:
/simplify to catch accumulated layerssuperpowers:requesting-code-review) should flag layered codereq, res, next) instead of Hono contextgetServerSideProps) instead of App RouteruseEffect + fetch, Tanstack Query) instead of RSC@repo/types@repo/coreprocess.env instead of Bun.envbun:testprovide() callback.passthrough() on Zod schemas for external API dataprovide() in actor pattern/items/create) instead of JSON:API resource paths (POST /items)title, publishedAt, body) when a relevant Schema.org type exists (headline, datePublished, text)For package-specific patterns, consult the corresponding skill:
prototyping-skills:generate-api — Hono + @hono/zod-openapi route patternsprototyping-skills:generate-ui — Next.js + shadcn/ui dashboard patternsprototyping-skills:generate-mcp — MCP server tool patternsprototyping-skills:init-prototype — Bootstrap a new monorepoprototyping-skills:generate-tests — Scaffold test infrastructure per packageprototyping-skills:development-workflow — Bridge scaffolding to development with skill chaining