frontend-skills
claudeFrontend skill pack for React 19 + Next.js 15 (App Router): code architecture/placement, React best practices, and Next.js patterns.
3 skills
Spec-Driven Development workflow (spec -> plan -> implement -> test -> verify -> retro) with slash commands. Depends on research-tools, code-agents and frontend-skills.
Plugin sdd-workflow from marketplace ai-demo-marketplace in burnjohn/ai-demo-marketplace. Commands read from the repo's manifest — 1 month ago.
workflow-retroPost-mortem / retrospective for a multi-agent run. Run it AFTER a workflow finishes (/run-plan, the spec → plan → implement chain, a Workflow() fan-out, or any batch of sub-agents) to collect how the run actually went and turn it into actionable change. Gathers cost & resource metrics (tokens, cache
/sdd-workflow:planSDD step 2 — turn an agreed spec or set of requirements into a phased implementation plan (HOW).
/sdd-workflow:run-planSDD step 3 — execute an implementation plan by dispatching implementer agents, respecting its dependency DAG.
/sdd-workflow:sdd-retroSDD step 5 — retrospective on the multi-agent run that just finished: cost, friction, waste, and what to change.
/sdd-workflow:specSDD step 1 — write a spec (WHAT/WHY) for a feature before any plan or code exists.
/sdd-workflow:verifySDD step 4 — check that every plan item / acceptance criterion is actually implemented, with evidence.
implementation-plannerUse proactively when an agreed set of requirements (a spec, ticket, or clear request) needs a structured Implementation Plan before any code is written. Read-only architect that verifies the incoming requirements, flags gaps, recommends a better approach where it sees one, and maps the work onto the
plan-verifierRead-only requirements-completion checker. Use after a feature is claimed done to verify every plan item / acceptance criterion is actually implemented — focus on completeness and traceability, not code quality.
spec-creatorUse proactively when a feature or change needs a written specification before any plan or code exists. Read-only-except-specs author for Spec-Driven Development — turns a request plus design sources (text, Figma links, screenshots, generated design skeletons, existing docs/plans, repo code) into a s
Frontend skill pack for React 19 + Next.js 15 (App Router): code architecture/placement, React best practices, and Next.js patterns.
3 skills
Execution agents usable with or without a spec-driven workflow: `implementer` and `test-writer`.
2 agents
Read-only research agent that gathers and fact-checks information from the codebase or the public web.
1 agent
Testing skill pack: React Testing Library conventions for component and hook tests with Vitest.
1 skill
Language-level TypeScript skill pack: type-level programming, strictness settings, utility types, and a diagnostic script.
1 skill
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.