Loading...
Loading...
Found 431 Skills
Scaffold a new planning output format adapter. Creates a format directory with all required files implementing the output format contract.
This skill should be used when the user asks to "create a new FastAPI project", "setup a fastapi api", "new fastapi project", "scaffold a fastapi app", "initialize a fastapi backend", or "start a new python api". Scaffolds a complete production-ready FastAPI project with SQLAlchemy, PostgreSQL, JWT auth, Pydantic v2 settings, and uv package management.
Recommend the next roadmap-backed change, then after explicit confirmation scaffold it as a normal spec-driven change.
End-to-end Claude Design handoff to pull request: imports a handoff bundle from claude.ai/design, generates Storybook stories and Playwright tests, runs diff-aware browser verification, and opens a PR with the bundle URL, before/after screenshots, and coverage delta embedded in the body. The one-shot 'design URL in, reviewable PR out' workflow. Use when a designer or PM hands you a Claude Design URL and you want a PR back without intermediate steps.
Generates complete, production-ready SaaS project boilerplate including authentication, database schemas, billing integration, API routes, and a working dashboard using Next.js 14+ App Router, TypeScript, Tailwind CSS, shadcn/ui, Drizzle ORM, and Stripe. Use when the user wants to create a new SaaS app, start a subscription-based web project, scaffold a Next.js application, or mentions terms like starter template, boilerplate, new project, or wiring up auth and payments.
Scaffold and maintain a reusable research → design → plan → orchestrate → act folder for any non-trivial work — software features, marketing campaigns, org changes. Drops a domain-agnostic spine (00-README · 01-plan · 02/03 research · 04-discussion newest-first · 05-tracking · 09-orchestration · artifact/board.html plan-board) plus stateless action-skills that augment the docs in place without clobbering hand-written prose. Composes ikenga-artifact-builder, huashu-design, frontend-design, ikenga-pkg-builder when present; degrades gracefully when not. Profile-driven: `software` (rich default, code work), `general` (lean, non-code — campaigns, org changes), and `content` (editorial/marketing with key art). TRIGGER when the user asks to start a real plan for non-trivial work ("plan a feature," "scaffold a plan folder," "set up groundwork for…"), references an existing plans/ folder by groundwork structure, or runs any of these actions: groundwork init / research / design / review / clarify / orchestrate / refresh-board / refresh-living-spec / status. DO NOT TRIGGER for one-off code changes, single-document writeups, ADRs, or content that fits in a single markdown file — those don't need a multi-doc plan folder. If the user just wants a single artifact (dashboard, mockup), route to ikenga-artifact-builder instead.
Scaffold a design iteration notebook for exploring UI concepts through rapid, intent-driven variation. Use when a user wants to explore multiple directions for a UI, track design decisions, or compare variations side-by-side.
Scaffold a new project with Next.js, GSD, skills, Linear integration, and MCP config
Build a new app or add Stream products (Chat, Video, Feeds, Moderation) to an existing app. Scaffold Next.js + Tailwind + Shadcn + Stream SDKs end-to-end with Steps 0–7. Add Chat/Video/Feeds/Moderation to an existing project (enhance flow). Triggers on 'build me a … app', 'scaffold', 'create a new …', 'add Chat to this app', 'integrate Video', 'drop Feeds into …'. Covers livestreaming, video conferencing, team messaging, direct messaging, social feed use cases.
Scaffold an aggregate root with entity, value objects, repository interface, domain events, and test stubs
Scaffold the Mimas agent instruction file tree for any repository — AGENTS.md at root, subdomain CONTEXT.md files, and the full agents-docs/ hierarchy (a sibling of any existing docs/, kept separate so human-maintained project docs stay untouched). Every file is tailored to the repo's actual tech stack, git platform, and conventions. Use this skill whenever someone wants to set up agent instructions, onboard a repo for AI-assisted development, add AGENTS.md / CONTEXT.md files, create engineering docs for agents, or mentions "set up agentic repository" or "mimas template". Even if they just say "set up this repo for agents" or "add agent docs", this is the skill to use.
Create the first .NET test project. USE FOR: "solution has no tests", xUnit tests, Tests.csproj/ProjectReference, add an omitted test project to .sln/.slnx/.slnf, central packages, or tests missing from CI. DO NOT USE FOR: a suitable project already registered in the requested build entry point (stop) or migration.