By alexiolan
Provides structured, multi-agent development workflows: plan features with clarifying questions, dispatch parallel coding agents, run browser-based UI testing, enforce systematic debugging via root-cause investigation, and integrate work through git commits and PRs. Includes cost-optimized variants using local LLMs and visual regression audits.
Generate or verify the project's one-time AESTHETIC_DIRECTION.md — a design-language contract used by ux-brief and design-review. Invoked automatically by architect/craft when UI work is planned and .claude/aesthetic-direction.md does not yet exist. Auto-generates without blocking; user can refine the file later.
Use when the user needs to plan and architect a new feature before implementation begins. This includes analyzing requirements, asking clarifying questions, and creating a detailed implementation plan aligned with the project's architecture. Invoke BEFORE any coding work starts.
Loaded at session start. Establishes awareness of craft-skills so the assistant invokes relevant skills before acting. Not invoked directly.
Use when a feature has been built and needs browser-based UI testing. Plans test scenarios, groups them into parallel batches, and dispatches multiple browser-tester agents simultaneously.
Cost-optimized craft variant: Qwen3.6-35B-A3B handles implementation and reviews locally, Opus orchestrates, Sonnet as fallback. Requires LM Studio running. Targets ~45-60% API cost reduction vs base /craft.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin providing structured development skills for any project.
Replaces generic AI workflows with battle-tested, structured processes: collaborative brainstorming, planning, parallel agent development, testing, systematic debugging, and self-improvement. Works with any tech stack — frontend, backend, or full-stack.
/plugin marketplace add alexiolan/craft-skills
/plugin install craft-skills@craft-skills
/plugin update craft-skills@craft-skills
Note: Claude Code has a known bug where
plugin updatemay report "already at latest" even when a new version exists. If that happens, run this in your terminal first, then retry the update:git -C ~/.claude/plugins/marketplaces/craft-skills pull --ff-only
Once installed, craft-skills activates automatically. Just describe what you want to build:
/craft Add a user notifications system
What happens:
You approve or redirect at every phase — nothing runs without your sign-off.
Other entry points:
/craft-ace Add a user notifications system # Same pipeline, local Qwen3.6 implements + reviews
/implement Add a logout button # Skip brainstorm, go straight to plan → develop
/architect 03 # Plan only (reads .claude/prompts/03-*.md)
/finish # Integrate completed work — commit, PR, merge, or cleanup
/debug The API returns 500 on save # Investigate before fixing — no guessing
/simplify # Review recent changes for quality
/reflect project # Audit your Claude configs
Both craft variants share the same pipeline: Brainstorm → Plan → Develop → Test → Report. They differ in which model handles implementation and review:
| Skill | Who implements | Who reviews | Requirements |
|---|---|---|---|
| craft | Claude (Sonnet) | Claude (Opus/Sonnet) | None |
| craft-ace | Qwen3.6 (local LLM) | Qwen3.6 (per-file + whole-diff) | LM Studio |
See Choosing a Variant for detailed comparison with real benchmark data.
| Skill | Description |
|---|---|
| implement | Fast pipeline: architect → develop → test. For clear, well-understood requirements. |
| finalize | Post-plan pipeline: develop → test. Use when a plan already exists. |
| architect | Create an implementation plan. No code written. |
| develop | Execute an approved plan using parallel agents. |
| browser-test | Run parallel browser-based UI tests. |
| finish | Integrate completed work — commit, PR, merge, or clean up the branch. The final pipeline step (after develop/test/report). |
Deterministic UI-quality gates. Invoked automatically by architect/craft/implement when the feature involves UI (no ambient auto-triggering — explicit, gated).
| Skill | Description |
|---|---|
| aesthetic-direction | One-time-per-project design-language contract written to .claude/aesthetic-direction.md. Auto-generated on first UI feature, refineable by hand. Invokes frontend-design if installed; falls back to observed-tokens template if not. |
| ux-brief | Per-feature UX brief with diagnosis + prioritized patches + success criteria, written to .claude/plans/{feature}/ux-brief.md. Solo mode uses frontend-design alone; combined mode adds ui-ux-pro-max for complex UI (triggered by explicit complexity: frontmatter or inferred from keywords). |
| design-review | Post-develop visual regression + contract audit. Captures screenshots, dispatches Haiku-vision agent against the aesthetic direction and feature brief. Escalates to Sonnet only on MAJOR issues (Haiku-first cost model, ~15-20K tokens per audit). |
Optional external skills (auto-detected, silent skip if not installed):
frontend-design — required for quality briefs; falls back to template if missingui-ux-pro-max — optional for combined mode on complex UInpx claudepluginhub alexiolan/craft-skills --plugin craft-skillsStructured project planning and execution through brainstorm, spec, and build phases across three execution tiers: sequential, delegated sub-agents, and full agent teams
AI-powered development tools for code review, research, design, and workflow automation.
Personal Claude Code / Codex skills — spec-driven development, agent teams, browser automation, productivity, and setup helpers. Install with `npx skills add devstefancho/claude-plugins`.
Focused agentic engineering workflow: design-doc, spec, plan, implement, tdd, refactor, review, address-pr-feedback, browser-verify, explain-visually, compress, branch, and commit.
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
CodyMaster v7.5 — token-optimized AI agent skills (progressive disclosure, ~100 tok index → SKILL.md on demand) + slash commands + sub-agents + cm-context MCP server. Browse Hybrid Bridge, a11y snapshots, structured error collection, video recording, anti-slop design layer, and self-evolving skill hooks/monitors.