claude-structure

claude-structure

A stack-agnostic Claude Code plugin/template that turns the chat into a disciplined, spec-driven development pipeline: Spec Writer → Architect → Implementer, plus auto-invoked skills for bug fixing, frontend design, security/architecture/performance audits, and a meta skill to create new skills.

What you get:

• 3 specialized subagents (spec-writer, architect, implementer) with clear roles and STOP protocols.
• 13 skills that auto-invoke when their context fits.
• 4 deterministic quality-gate hooks (bash) that enforce structure on specs, audits, plans, and implementations.
• One real human-approval gate (plan approval). AUTO_MODE=1 skips even that.
• A workflow document describing the end-to-end pipeline (WORKFLOW.md).

The skill set is curated based on hard usage data — bugfix, frontend-design, and skill-creator made it in because they got used week after week, not because they sound nice.

---

Install

Option A — as a Claude Code plugin (recommended)

Inside Claude Code:

/plugin marketplace add Valdemird/claude-structure
/plugin install claude-structure@claude-structure

The plugin auto-discovers agents/, skills/, and hooks/ (via hooks/hooks.json). Nothing else to wire up.

Option B — copy-paste into your project

git clone https://github.com/Valdemird/claude-structure.git
cd claude-structure

# Copy plugin components into your project's .claude/
mkdir -p /path/to/your/project/.claude
cp -r agents skills hooks /path/to/your/project/.claude/

# Copy the project-level templates
cp templates/settings.json /path/to/your/project/.claude/settings.json
cp templates/CLAUDE.md.template /path/to/your/project/CLAUDE.md
$EDITOR /path/to/your/project/CLAUDE.md   # describe your stack & commands

Configure the toolchain (any stack)

export TEST_CMD="pytest"          # or "npx vitest run", "go test", etc.
export TEST_ALL_CMD="pytest"
export TYPECHECK_CMD="mypy"
export LINT_CMD="ruff check"
export FORMAT_CMD="black"
export AUTO_MODE=1                # optional: autonomous multi-phase runs

Open Claude Code in your project and the skills activate automatically based on the conversation.

---

Repository layout

claude-structure/                ← this is the plugin root
├── .claude-plugin/
│   ├── plugin.json              ← plugin manifest
│   └── marketplace.json         ← marketplace entry for /plugin marketplace add
├── agents/                      ← plugin auto-discovers these
│   ├── architect.md
│   ├── implementer.md
│   └── spec-writer.md
├── skills/                      ← plugin auto-discovers these
│   ├── spec-create/
│   ├── spec-audit/
│   ├── spec-review/
│   ├── spec-plan/
│   ├── spec-implement/
│   ├── spec-orchestrator/
│   ├── architecture/
│   ├── security-audit/
│   ├── performance/
│   ├── mobile-audit/
│   ├── bugfix/
│   ├── frontend-design/
│   └── skill-creator/
├── hooks/                       ← plugin reads hooks.json + scripts
│   ├── hooks.json               ← plugin hook config (uses ${CLAUDE_PLUGIN_ROOT})
│   ├── validate-spec-structure.sh
│   ├── validate-audit.sh
│   ├── validate-plan.sh
│   └── validate-implementation.sh
├── templates/                   ← for copy-paste users only
│   ├── CLAUDE.md.template
│   └── settings.json
├── .github/workflows/validate.yml  ← CI: shell, JSON, manifest, frontmatter
├── README.md
├── WORKFLOW.md
└── LICENSE

---

When does each skill fire?

Skill	Fires when you say…
spec-create	"I want a spec for X", "create a spec for Y"
spec-audit	"audit the spec for X"
spec-review	"review the spec for X"
spec-plan	"generate the plan for X", "plan the implementation"
spec-implement	"implement phase N of X" (or end-to-end in AUTO_MODE=1)
spec-orchestrator	"take this idea end-to-end as a spec"
architecture	"do an architecture review", "audit the structure of this module"
security-audit	"is this secure?", "check for XSS / SQLi / SSRF / auth issues"
performance	"audit performance", "find bottlenecks"
mobile-audit	"audit the mobile experience", "this is broken on iOS Safari"
bugfix	"fix the bug where…", "X is broken / not working / regressed"
frontend-design	"build me a landing page", "design this component"
skill-creator	"create a new skill for…", "improve the X skill"