SweetClaude

Skills

122 in the Claude listing

• _featuresFeature configuration — shows all optional SweetClaude features with descriptions and current status, lets the user enable or disable them.
• _healthConsistency scan and version check.
• _migrateMigration orchestrator.
• _routeNatural language classifier — maps user text to the right internal skill.
• Behavioral regressionRun SweetClaude's behavioral regression test suite.
• Big pictureShow the full project at a glance — the roadmap pipeline with its milestones, epics and issues.
• bootstrapSession startup skill — pre-flight checks, drift/update offers, and initial routing.
• Claude config auditRedirects to sweetclaude:doctor.
• Code debtTech debt cleanup.
• Code featureBuild a new feature end-to-end.
• Code issueImplement a GitHub issue end-to-end.
• Code reviewCode, security, and compliance review.
• Code tddInternal TDD process skill — invoked by code-feature, code-issue, and code-debt.
• Code testingRun any combination of test suite, mutation testing, security review, and PR pre-check.
• Code verifyRun verification before claiming work is complete.
• Corpus consolidateScan source directories, deduplicate files, copy unique files into corpus/raw/inbox/.
• Corpus promoteFinalize approved documents from corpus/working/.
• Corpus rag reindexRebuild RAG collections from source files.
• Corpus rag setupConfigure and run local semantic search on project documents using mcp-local-rag.
• Corpus reconcileTake staged files and work with the user to produce approved canonical documents in corpus/working/.
• Corpus statusShow the current state of the document corpus pipeline — file counts in each stage, last-run timestamps per step, and recommended next action.
• Corpus triageClassify files in corpus/raw/inbox/ as keep-as-is, needs-reconciliation, discard, or defer.
• Course correctionCourse correction — document the pivot, triage in-flight work, and update project direction.
• dashboardLaunch a local web dashboard showing roadmap, releases, epics, backlog, dependencies, git history, and skill activity.
• Deploy shipSHIP phase skill.
• Design api designDesign API endpoints: routes, request/response shapes, authentication, pagination, error responses, and versioning strategy.
• Design architectureDefine system architecture — components, boundaries, communication patterns, data flow, and compliance requirements.
• Design change impact analysisRipple-effect analysis for changes to EXISTING code or specs — trace what is affected across code, tests, docs, APIs, and specs.
• Design data modelDesign the data model: entities, relationships, constraints, indexes, and migration strategy.
• Design manage decisionsRecord and track design and architecture decisions with context, options considered, decision made, and rationale.
• Design solutioning gateValidate the proposed solution before implementation.
• Design tech specTechnical specification — every decision a developer needs before writing the first line of code.
• Design user flowsConvert user stories into UX/UI flows — step-by-step paths through the interface.
• Design uxDefine the visual and interaction design of the product — look, feel, layout, and style.
• Design ux reviewVirtual UX review session.
• Design wireframesGenerate HTML/CSS wireframes from user flows.
• doctorDiagnostic scan, repair, and rollback.
• Document corpusManage the full document corpus pipeline — consolidate raw files, triage, reconcile into canonical documents, promote, set up semantic search (RAG), and reindex.
• Documents academic researchAcademic paper development — from first principles through submission.
• Documents narrative arcBuild and query a knowledge graph connecting strategic claims, proof points, objectives, and supporting/opposing evidence.
• Documents update docsUpdate documentation when implementation changes behavior.
• Epic designProduce a complete, ordered story list for an epic.
• epicsManage epics and objectives — add, review, link, status, complete.
• Feature setupDeploy local repo to installed locations and rebuild the project cache.
• Find skillFind and start the right skill for any work.
• Fix sweetclaudeRedirects to sweetclaude:doctor.
• goAssess what to work on next and propose it.
• Guardian offDisable the Protocol Guardian for the current session
• Guardian onEnable the Protocol Guardian — enforces skill invocations, TDD discipline, and artifact saves for the current session
• helpSweetClaude help and skill discovery.
• hibernateUse when hibernating or unhibernating a project managed by SweetClaude.
• Hook repairRedirects to sweetclaude:doctor.
• hotfixHotfix — minimal patch for a production issue with expedited review and mandatory post-mortem.
• initEntry point for onboarding a project to SweetClaude — reads current state and hands off to the skill that owns the work.
• John wickFully autonomous, resumable, multi-session SDLC pipeline.
• John wick checkinInternal John Wick phase check-in subagent.
• Large storyInternal bounded, evidence-gated large-story workflow.
• masterSweetClaude master skill — phase router, interaction model, and session entry point.
• Misc meeting prepPrepare for a specific meeting.
• Mockup extractPull an existing production component into the mockup sandbox as an accurate 'Current' baseline for design iteration.
• Mockup graduateMove an approved mockup from the sandbox into the main application.
• Mockup sandboxCreate and iterate on interactive UI mockups in an isolated Vite + React + Tailwind + shadcn/ui sandbox.
• Next stepsWalk through the pipeline step by step.
• offDeactivate SweetClaude for the current project.
• orchestratorOrchestrator main loop — executes tracked workflow steps via subagents.
• postmortemPost-mortem authoring — timeline, root cause analysis, contributing factors, and action items.
• Product briefWrite a product brief — a strategic document describing what is being built, for whom, why it matters, and what success looks like.
• Product competitionCompetitive analysis at three depth levels — from a quick company survey to feature-by-feature deep analysis.
• Product discoveryEstablish what is being built, for whom, and why — at the depth appropriate for the project type.
• Product manage scopeTrack scope changes when items move between in-scope and out-of-scope.
• Product market messagingCraft external messaging — how you describe the product, the problem, and the value to different audiences.
• Product milestone planningGuided milestone planning workshop.
• Product milestonesManage roadmap targets (milestones) that span strategy and product work.
• Product parking lotManage deferred work.
• Product positioning statementDefine how the product is positioned — for whom, what category, what differentiates it, and why that matters.
• Product prdWrite a Product Requirements Document — functional requirements, non-functional requirements, epics, and success metrics.
• Product researchSurvey the solution field — what exists commercially and open source — so the user understands what they're entering before building.
• Product roadmapManage the product roadmap — feature delivery targets, releases, and priority stack.
• Product roadmap analysisRICE scoring and stack-rank analysis for roadmap items.
• Product sprint planPlan a sprint by selecting stories from the backlog, estimating scope, and producing a sprint commitment.
• Product terminologyDefine and maintain a shared domain glossary.
• Product user focus groupSynthetic panel research using persona archetypes as parallel subagent respondents.
• Product user storiesWrite user stories for a defined scope — Gherkin or generic format, scoped to all personas, SLC, or MVP.
• Product user tdd testsTransition user stories into Gherkin .feature files.
• Project assess shapeInterview user and recommend a SweetClaude project mode (Flow, Kanban, Shape Up, or Agile)
• Project backlogView and manage the unscheduled issue backlog.
• Project backlog triageStructured backlog grooming session.
• Project epicsDEPRECATED — use /sweetclaude:epics instead.
• Project gh import issuesImport open GitHub Issues into the local issue store as v4 story files.
• Project gh sync issuesBidirectional status sync between local issue files and GitHub Issues.
• Project goalsManage project goals — binary business goals.
• Project issuesManage project issues — list, view, create, update, and close.
• Project modeAssess and shift project modes.
• Project scopeDefine and maintain project scope.
• Project sprintsSprint planning, activation, board view, and close.
• Project themesManage themes — optional domain-grouping labels on stories.
• purgeDelete all SweetClaude artifacts from the current project.
• recapProduce a concise 'where we are' summary: current phase, active work item, last 3 commits, checkpoint state, and any open flags.
• recoverRecover or unblock SweetClaude projects left in bad update, migration, doctor, or repair states.
• Report failureWrite one structured failure report and root cause analysis to .sweetclaude/failure/.
• retroReview and maintain the improvement register.
• Rollback revertRoll back or revert a deployment — identify the cause, execute the rollback, confirm recovery.
• Security patchSecurity patch — vulnerability fix with mandatory security review and disclosure tracking.
• Session exportExport a Claude.ai session as a complete, portable package.
• setupConsolidated onboarding skill.
• Small storyInternal bounded, evidence-gated small-story workflow.
• Something brokeReactive production incident skill.
• statusOrient to the current project.
• Sweetclaude behavioral regressionValidates that mode enforcement is working correctly across all four modes.
• sweetclaude:migrateMigrate legacy work items to unified ISSUE-NNN format.
• sweetclaude:migrate-diagnoseRedirects to sweetclaude:doctor.
• Testing accessibilityWCAG 2.1 Level AA audit.
• Testing complianceCompliance control testing and evidence collection.
• Testing performanceDefine load scenarios, establish performance baselines, set thresholds.
• Testing planDefine and maintain a test strategy for a feature or release.
• Testing securityStructured security review.
• Testing sessionRun a manual QA session.
• ultraplanPrepare a structured ultraplan prompt from current phase artifacts, launch ultraplan, and ingest the resulting plan as the DESIGN phase architecture artifact.
• updateUpdate SweetClaude to the latest version from GitHub.
• usageToggle and view local usage tracking.
• User personasDefine product users — who they are, what they need to do, and exactly what completing each task looks and feels like.
• Work item artifactsCo-locate all artifacts per story, epic, and milestone into .sweetclaude/work/<ID>/.