Sponsored by

Find leads on Reddit on auto pilot

Agent skills
claude-code

Topic: claude-code

35,830 skills in this topic.

cavekit-writing How to write Cavekit-quality kits that AI agents can consume effectively. Covers implementation-agnostic cavekit design, testable acceptance criteria, hierarchical structure, cross-referencing, cavekit templates, greenfield and rewrite patterns, cavekit compaction, and gap analysis. Trigger phrases: "write kits", "create kits", "cavekit this out", "define requirements for agents", "how to write kits for AI"
JuliusBrussee/cavekit 256
brownfield-adoption Step-by-step process for adopting Cavekit on an existing codebase. Covers the 6-step brownfield process, bootstrap prompt design, spec validation against existing behavior, and the decision between brownfield adoption vs deliberate rewrite. Trigger phrases: "brownfield", "existing codebase", "add Cavekit to existing project", "adopt Cavekit", "layer kits on code", "retrofit kits"
JuliusBrussee/cavekit 256
validation-first Validation-first design for AI agent output — every spec requirement must be automatically verifiable. Covers the 6-gate validation pipeline, phase gates between Hunt phases, merge protocol, completion signals, and acceptance criteria design patterns. Trigger phrases: "validation gates", "quality gates", "validation-first design", "how to validate agent output", "acceptance criteria design"
JuliusBrussee/cavekit 256
ui-craft Authoritative guide for implementing stunning, accessible, performant UI. Synthesizes design engineering philosophy, accessibility standards, animation principles, spatial design, typography, color systems, and component craft into a single actionable reference. Complements the design-system skill (which covers DESIGN.md spec writing) by covering the HOW of implementation. Trigger phrases: "build UI", "create component", "landing page", "make it look good", "frontend", "design", "polish UI", "implement design", "make it beautiful", "UI implementation", "component styling", "animation", "accessibility"
JuliusBrussee/cavekit 256
rewind List and restore to a named checkpoint from the current session. Use when the agent has gone off track and you need to recover to a previous good state.
juanandresgs/claude-ctrl 173
reckoning Analyze a project's MASTER_PLAN.md to assess coherence, evolution trajectory, and intent alignment. Modes: default (full analysis), compare (delta between reckonings), operationalize (convert findings to actionable work via /decide), steer (strategic brainstorming grounded in findings).
juanandresgs/claude-ctrl 173
prd Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics. Use when describing a problem space, developing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.
juanandresgs/claude-ctrl 173
observatory Self-improving flywheel that analyzes agent traces, surfaces improvement signals, and proposes targeted system enhancements.
juanandresgs/claude-ctrl 173
diagnose Validate hook integrity, state file consistency, and system health for the ~/.claude configuration.
juanandresgs/claude-ctrl 173
deep-research Multi-model deep research with comparative assessment (OpenAI + Perplexity + Gemini). Queries 3 deep research providers in parallel and produces a comparative synthesis.
juanandresgs/claude-ctrl 173
decide Generate an interactive decision configurator from research or plan analysis. Presents options as explorable cards with trade-offs, costs, and filtering. Integrates with Planner to collect DEC-ID decisions.
juanandresgs/claude-ctrl 173
context-preservation Generate structured context summaries for session continuity across compaction
juanandresgs/claude-ctrl 173
consume-content Produce a faithful content-snapshot of any source material (article, report, PDF, advisory) with verbatim quotes, structural transparency, and labeled editorial.
juanandresgs/claude-ctrl 173
compound Document what you learned during this sprint. Reads artifacts, writes structured solutions to know-how/solutions/. Run after /ship or after fixing a significant bug. Triggers on /compound.
garagon/nanostack 173
think Use before planning when you need strategic clarity — product discovery, scope decisions, premise validation. Applies YC-grade product thinking to challenge assumptions and find the narrowest valuable wedge. Supports --autopilot to run the full sprint automatically after approval. Triggers on /think, /office-hours, /ceo-review.
garagon/nanostack 173
nano-run First-time setup and guided sprint. Configures stack, permissions, and work preferences conversationally. Run once after installing nanostack. Triggers on /nano-run.
garagon/nanostack 173
ship Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.
garagon/nanostack 173
security Use before shipping to production. Performs OWASP Top 10 audit and STRIDE threat modeling against the codebase. Supports --quick, --standard, --thorough modes. Also use when the user asks to check security, audit code, or review for vulnerabilities. Triggers on /security.
garagon/nanostack 173
review Use after writing code to get a thorough code review. Runs two passes — structural correctness then adversarial edge-case hunting. Scales depth by diff size. Supports --quick, --standard, --thorough modes. Triggers on /review.
garagon/nanostack 173
qa Use to verify that code works correctly — browser-based testing with Playwright, native app testing with computer use, CLI testing, API testing, or root-cause debugging. Supports --quick, --standard, --thorough modes. Triggers on /qa.
garagon/nanostack 173
nano Use when starting non-trivial work (touching 3+ files, new features, refactors, bug investigations). Produces a scoped, actionable implementation plan before any code is written. Triggers on /nano.
garagon/nanostack 173
nano-help Quick reference for all nanostack commands. Shows available skills, what each one does, and how to use them. Triggers on /nano-help.
garagon/nanostack 173
guard Use when working near production, sensitive systems, or destructive operations. Activates on-demand safety hooks that block dangerous commands. Supports modes — careful (warn), freeze (block writes outside scope), unfreeze (remove restrictions). Triggers on /guard, /careful, /freeze, /unfreeze.
garagon/nanostack 173
feature Add a feature to an existing project with a full sprint. Skips /think diagnostic, goes straight to planning. Use when the user knows what they want and the project already exists. Triggers on /feature.
garagon/nanostack 173