craft

Plugin craft from marketplace data-wise in Data-Wise/claude-plugins. Commands read from the repo's manifest — 8 days ago.

Skills (44)

• craft-do

  Carry out a coding or documentation task in the current repository. Use when the user asks to implement, fix, update, or otherwise do project work.

• craft-finish

  Capture progress when wrapping up a coding session. Use when the user asks to finish, wrap up, save progress, or end the session.

• craft-restore

  Restore project context after a break. Use when the user asks where they left off, requests a repository recap, or wants the current status and next action.

• system-architect

  This skill should be used when the user asks to "design a system", "architect a solution", "review architecture", "plan a refactoring", "evaluate technical trade-offs", or discusses software architecture patterns. Provides expert guidance on system design, architecture patterns, and technical decisi

• project-detector

  This skill should be used when the user asks to "detect project type", "what kind of project is this", "generate CI workflow", "set up CI", or needs to identify build tools, test frameworks, and CI requirements. Smart detection of project types, build tools, and CI requirements for automated workflo

• sync-features

  This skill should be used when the user asks to "sync features", "check for new Claude features", "update craft for latest Claude", "what's new in Claude Code", or wants to ensure craft is up-to-date with Claude Code/Desktop capabilities. Chains command-audit and unified release-watch into a priorit

• audit-router

  This skill should be used when the user asks to "audit commands", "check command frontmatter", "audit skills", "check skill standards", "validate command/skill health", or invokes `/craft:code:command-audit` or `/craft:code:skill-standards`. Shared vocabulary + reference bodies for craft's two schem

• command-skill-token-efficiency

  This skill should be used when the user is writing, editing, resizing, or reviewing a craft command (commands/**/*.md), skill (skills/**/SKILL.md), or agent (agents/*.md) file — including "add a new command for X", "this command is getting long", "should this be a skill instead", "make /craft:do lea

• plugin-audit

  This skill should be used when the user asks to "audit my plugins", "check for plugin duplicates", "plugin collision check", "find duplicate skills across plugins", "which plugins overlap", or wants to know if an installed Claude Code plugin duplicates or shadows another plugin's commands/skills. Di

• backend-designer

  This skill should be used when the user asks to "design an API", "plan database schema", "set up authentication", "design backend architecture", or discusses backend patterns and infrastructure. Provides pragmatic backend design guidance following "solid indie" principles.

• devops-helper

  This skill should be used when the user asks to "set up deployment", "configure CI/CD", "create a Dockerfile", "choose a hosting platform", or discusses deployment and infrastructure decisions. Provides pragmatic DevOps guidance for indie developers.

• frontend-designer

  This skill should be used when the user asks to "design a UI", "plan component architecture", "improve accessibility", "optimize frontend performance", or discusses UI/UX patterns. Provides pragmatic frontend design guidance with ADHD-friendly patterns.

• git-workflow

  This skill should be used when the user asks to "init a repo", "set up git", "manage branches", "switch branch", "create a worktree", "list worktrees", "clean merged branches", "sync with remote", "git activity", "git recap", "protect main", "apply branch protection", "bypass protection", "undo a co

• dist-extras

  This skill should be used when the user asks to "publish to PyPI", "generate an install script", "curl install", "publish to Claude Code marketplace", "create marketplace.json", "PyPI trusted publishing", "private plugin", "plugin drift", "pin refresh", or needs help with non-Homebrew distribution c

• distribution-strategist

  This skill should be used when the user asks to "plan distribution", "how should I distribute this", "choose a package manager", "distribution strategy", or needs to select and prioritize distribution channels for a software project. Recommends optimal distribution channels based on project type and

• homebrew-formula-expert

  This skill should be used when the user asks to "create a Homebrew formula", "fix brew audit errors", "write a formula", "Homebrew best practices", or needs help with Homebrew formula syntax, dependencies, and troubleshooting. Expert knowledge of Homebrew formula creation and maintenance.

• homebrew-multi-formula

  This skill should be used when the user asks to "release multiple formulas", "batch Homebrew update", "coordinate formula releases", "formula dependencies", or needs to manage releases across multiple Homebrew formulas with dependency ordering.

• homebrew-setup-wizard

  This skill should be used when the user asks to "set up Homebrew automation", "homebrew setup", "automate formula updates", "configure Homebrew workflow", or needs end-to-end Homebrew formula automation from detection through workflow generation.

• homebrew-workflow-expert

  This skill should be used when the user asks to "create Homebrew release workflow", "automate formula updates with GitHub Actions", "configure tap CI", or needs GitHub Actions workflows for automated Homebrew formula updates and releases.

• architecture-decision-records

  Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

• changelog-automation

  Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

• claude-md-lifecycle

  This skill should be used when the user asks to "create CLAUDE.md", "scaffold CLAUDE.md", "sync CLAUDE.md", "update CLAUDE.md", "audit CLAUDE.md", "fix CLAUDE.md", "optimize CLAUDE.md", "edit CLAUDE.md sections", or otherwise wants to manage the CLAUDE.md lifecycle (init, sync, edit). Covers project

• guard-audit

  This skill should be used when the user asks to "audit guard", "guard friction", "tune guard", "guard false positives", "fix guard blocking", or mentions branch guard configuration issues. Analyzes branch-guard.sh rules; proposes JSON branch-policy config changes for policy-level false positives, an

• hooks

  Common PostToolUse/PreToolUse hook templates for quality gates. Provides ready-to-install JSON blocks for MkDocs strict mode, linting, and other automated checks, with setup instructions for each.

• insights-apply

  This skill should be used when the user asks to "apply insights", "insights to rules", "update rules from insights", "apply suggestions", or mentions updating CLAUDE.md from insights data. Extracts suggestions from the /insights report and applies them to the global CLAUDE.md via the sync pipeline.

• mode-controller

  This skill should be used when the user asks to "switch mode", "use debug mode", "optimize mode", "release mode", or mentions execution modes for craft commands. Manages craft plugin execution modes (default, debug, optimize, release) for different use cases.

• drive-engine

  This skill should be used when driving an approved SPEC to completion — "drive this spec to done", "run the orchestrate drive loop", "implement the spec autonomously until tests pass". Owns the reusable body behind /craft:orch:drive — parse-or-derive ORCHESTRATE phases, dispatch file-scoped subagent

• plan-orchestrator

  This skill should be used when the user asks to "generate an ORCHESTRATE file", "turn a spec into a plan", "scaffold a feature breakdown", "scaffold a sprint backlog", "plan a sprint" (when a committed backlog/artifact is wanted, not just strategy advice), "generate roadmap artifacts", "create an im

• repo-triage

  This skill should be used when the user asks to "triage the repo", "clean up open issues and stale branches", "what needs attention in this repo", or wants a batch pass over open GitHub issues plus stale worktrees/branches, grounded against current repo state, with confirmed (never automatic) deleti

• session-state

  This skill should be used when the user asks to "save session", "resume session", "continue where I left off", "session history", or needs orchestrator session state persistence including save, load, resume, and history management.

• task-analyzer

  This skill should be used when the user asks to "analyze a task", "route a command", "what craft command should I use", or describes a development task that needs routing to the appropriate craft workflow. Analyzes natural language task descriptions and maps them to optimal craft command sequences.

• workflow-engine

  This skill should be used when executing a coded, fixed-control-flow workflow — "run the workflow engine", "execute this WORKFLOW yaml", "run the coded orchestration", decompose→cover→verify→synthesize shapes. Owns the reusable body behind /craft:orch:workflow — compile a WORKFLOW definition to a de

• orchestrator-resilience
• planning
• preflight-check
• release
• test-generator
• test-strategist
• adhd-workflow
• brainstorm-insights
• brainstorm
• grill
• prompt-refiner
• task-management

Slash commands (46)

• /craft:arch:analyze

  Analyze codebase architecture with mode support

• /craft:arch:diagram

  Architecture Diagrams

• /craft:arch:plan

  Architecture Planning

• /craft:arch:review

  Architecture Review

• /craft:brainstorm

  Enhanced brainstorming with smart detection, design modes, time budgets, context-aware questions, and spec capture

• /craft:brief

  Generate a 3-line action block (Next step / Watch out for / Connects to) with optional planning expansion

• /craft:check

  Universal pre-flight check that validates project readiness

• /craft:ci:detect

  Smart detection of project type, build tools, test frameworks, and CI requirements

• /craft:ci:fix

  Fix CI Failures

• /craft:ci:generate

  Generate GitHub Actions CI workflow from project detection

• /craft:ci:local

  Run CI checks locally before pushing (lint, test, coverage, security)

• /craft:ci:status

  Cross-repo CI status dashboard showing all workflow runs

• /craft:ci:triage

  Triage a failing CI check: classify as diff-caused vs pre-existing/infra and recommend re-run / --admin / fix with evidence

• /craft:ci:validate

  Validate existing CI workflow against project configuration

• /craft:ci:watch

  Poll a CI run to completion, then route the next action: merge if green, triage if red

• /craft:code:command-audit

  Validate command frontmatter, find deprecated patterns, report health score

• /craft:code:debug

  Debug Assistance

• /craft:code:demo

  Code Demonstration

• /craft:code:deps-audit

  Security audit of dependencies for known vulnerabilities

• /craft:code:deps-check

  Dependency Check

• /craft:code:docs-check

  Documentation & Website Pre-flight Check

• /craft:code:fewer-prompts

  Install curated read-only Bash allowlist to eliminate permission prompts

• /craft:code:lint

  Code style and quality checks with mode support

• /craft:code:refactor

  Refactoring Guidance

• /craft:code:release-watch

  Track Claude Code + Desktop releases and identify plugin-relevant changes

• /craft:code:release

  Release Workflow

• /craft:code:skill-standards

  Audit skills/**/SKILL.md against Anthropic authoring standards; report gaps, apply safe fixes, refresh vendored checklist

• /craft:code:test-gen

  Generate Tests

• /craft:do

  Universal command that intelligently routes to appropriate craft commands

• /craft:docs:changelog

  Auto-update CHANGELOG.md based on git commits

• /craft:docs:update

  Smart documentation generator with interactive category-level updates

• /craft:finish

  /finish - Session Completion & Context Capture

• /craft:git:issue-check

  Check whether an open GitHub issue's premise still holds against current code, before implementing a fix it requests

• /craft:grill

  Adversarially interrogate a plan, spec, or topic one question at a time — convergent counterpart to brainstorm

• /craft:hub

  /craft:hub - Command Discovery Hub

• /craft:next

  /next - Decision Support

• /craft:orch

  Launch orchestrator mode with subagent delegation, monitoring, mode-aware execution, and chat compression

• /craft:orch:drive

  Drive an approved SPEC to completion via the native /goal turn-loop, with a real verify gate; stops at verified green and prints the PR command

• /craft:orch:workflow

  Execute a coded, fixed-control-flow workflow (parallel/pipeline/loop/verify) with schema-gated agents, data-driven fan-out, and cached/resumable replay

• /craft:plan

  Universal planning entry point — routes to the right deliberation tier (brainstorm/grill/plan-orchestrator/project-planner) via deterministic repo-state detection, never phrase matching

• /craft:plan:feature

  Feature Planning

• /craft:refine

  /refine - Prompt Optimizer

• /craft:restore

  /restore - Restore Git & Session Context

• /craft:site:deploy

  Deploy documentation site to GitHub Pages

• /craft:smart-help

  Context-aware help that suggests relevant commands

• /craft:test

  Unified test runner with category filtering and modes

Subagents (2)

• orchestrator-v2

  Enhanced orchestrator with subagent monitoring, mode-aware execution, resilient error handling, and ADHD-optimized status tracking. Use proactively for complex multi-step tasks requiring parallel agent delegation.

• workflow-orchestrator

  Manages background agent delegation, task parallelization, and result synthesis for workflow automation

MCP servers (1)

• mcp-mermaid

  runs: npx -y [email protected]

Similar plugins