Opinionated Claude Code configuration: 30 skills, 11 agents, 14 commands, 7 hooks, spec-driven workflows. Captures the scaffolding.tool orchestration patterns.
npx claudepluginhub komluk/scaffolding --plugin scaffoldingAnalyze and optimize Claude Code's context configuration.
Implement a feature using using the PRP file.
Generate a complete PRP for general feature implementation with thorough research. Ensure context is passed to the AI agent to enable self-validation and iterative refinement. Read the feature file first to understand what needs to be created, how the examples provided help, and any other considerations.
Initialize OpenSpec in a project directory with the scaffolding-workflow schema.
Bootstrap a new project with the scaffolding CLAUDE.md, settings.json, and `.scaffolding/` directory structure.
Implement tasks from a conversation's specs (Experimental)
Archive a completed change in the experimental workflow
Archive multiple completed changes at once
Continue working on a change - create the next artifact (Experimental)
Enter explore mode - think through ideas, investigate problems, clarify requirements
Create a change and generate all artifacts needed for implementation in one go
Start a new change using the experimental artifact workflow
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
Sync design specs from a conversation to main specs
Verify implementation matches change artifacts before archiving
Requirements analyst. MUST BE USED for ambiguous requests, requirements gathering, scope assessment, feasibility checks, and proposal writing. PROACTIVELY interprets user intent and produces proposal.md specs.
Technical architect. MUST BE USED for system design, API design, implementation planning, multi-file refactoring, and agent orchestration. Receives proposal.md from analyst and produces design.md + tasks.md.
Analyzes tasks and decomposes them into a sequence of agent steps for execution.
Bug investigation specialist. MUST BE USED for bug reports, unexpected behavior, error diagnosis. PROACTIVELY performs systematic root cause analysis using progressive debugging techniques.
Expert software engineer. Use proactively to implement features, fix bugs, write tests, style UI, and make code changes. MUST BE USED for all development tasks.
Infrastructure specialist. MUST BE USED for CI/CD, Docker, deployment, infrastructure. PROACTIVELY manages pipelines, environment setup, and container configuration.
Git operations specialist. MUST BE USED for branch management, conflict resolution, git history analysis, worktree recovery, commit, merge, push. Owns ALL git operations — other agents do NOT commit.
Performance specialist. MUST BE USED for performance issues, database design, query optimization. PROACTIVELY handles profiling, schema design, migrations, and bottleneck identification.
Documentation researcher. MUST BE USED for new API integration, library questions, best practices. PROACTIVELY gathers version-specific documentation and produces ResearchPacks with citations.
Senior code reviewer, security specialist, and quality assurance expert. Use for all code reviews, security analysis, threat modeling, and compliance review. MUST BE USED for all reviews.
Documentation owner. MUST BE USED for README, CHANGELOG, docs/ updates. PROACTIVELY manages all markdown files as sole authority for documentation.
3-tier persistent memory protocol for cross-session knowledge accumulation. Use when agents need to read, write, or manage memory files.
RESTful API design standards for this project. Use when designing new API endpoints, creating error responses, or implementing pagination.
Optimize Claude Code context window usage for better performance. Use when managing context limits, prompt engineering, or improving agent accuracy.
Schema design principles, index strategy, migration safety, and query analysis patterns
Knowledge distillation methodology -- extraction patterns, confidence scoring, and tier routing rules for the /distill command.
Docker multi-stage build templates, security best practices, and docker-compose patterns for this project
Consistent error handling patterns across frontend and Python backend. Use when implementing error boundaries, exception handlers, or error responses.
Git command patterns, branching strategies, and safety protocols. Use for branch management, conflict resolution, or worktree operations.
GitHub Actions CI pipeline templates and workflow patterns for this project
Structured logging standards using structlog and Seq. Use when adding log statements, configuring logging, or reviewing log output.
MCP tool decision tree and plugin reference. Agents follow MCP-first strategy: attempt MCP tools before falling back to built-in alternatives.
Monitoring, metrics, alerting, and observability standards. Use when implementing health checks, metrics collection, or alerting rules.
Material-UI styling standards with the project's neon cyberpunk theme. Use when styling React components, creating theme tokens, or applying componentStyles.
Identify and apply existing codebase patterns for consistency. Use when writing new code to match established conventions in a project.
Systematic approach for creating minimal, reversible implementation plans. Use after research phase before writing code.
Python backend patterns with FastAPI, async SQLAlchemy, and Pydantic. Use when creating routes, models, schemas, or services.
Validate ResearchPacks and Implementation Plans meet quality thresholds. Use when scoring research (>=80) or plans (>=85) before implementation.
React 18 + TypeScript component standards and hook patterns. Use when creating components, custom hooks, or reviewing React code.
Systematic approach for gathering accurate, version-specific documentation. Use when researching new APIs, libraries, or best practices before implementation.
OWASP Top 10, STRIDE threat modeling, auth/compliance review checklists for code review
Directives for proactive use of semantic memory MCP tools (semantic_search, semantic_store, semantic_recall). Ensures agents actively leverage vector-similarity memory during tasks.
How to write OpenSpec design.md and tasks.md artifacts
How to execute OpenSpec tasks.md during implementation
How to write OpenSpec proposal.md artifacts
How to verify implementation against OpenSpec artifacts
OpenSpec lifecycle orchestration for /workflow chains
Zustand-based state management standards. Use when creating stores, managing global state, or choosing between local and global state.
Test pyramid, coverage targets, and testing patterns for pytest and vitest. Use when planning tests, writing test code, or reviewing test coverage.
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
Scaffolding.tool worktree lifecycle management, diagnostics, and recovery. Use when debugging worktree issues or managing task isolation.
Give Claude Code 11 specialized agents, 30 skills, safety hooks, and auto-routing — in one install.
Instead of Claude answering everything directly, it routes your messages to the right specialist:
You say "fix the login bug" → Claude auto-routes to debugger → debugger investigates → developer fixes it.
No special commands. Just talk normally.
Requirements: Claude Code CLI only
First, add the marketplace (one-time setup):
/plugin marketplace add komluk/scaffolding
Then install the plugin:
/plugin install scaffolding@komluk-scaffolding
After install, initialize the project:
/scaffolding:init-scaffolding
This creates the .scaffolding/ directory, copies CLAUDE.md and settings.json to your project. This step is required — the plugin cannot auto-initialize due to Claude Code plugin system limitations.
Then restart Claude Code (close and reopen) to load the new CLAUDE.md and settings.
That's it. Start talking — Claude will auto-route to the right agent.
Requirements: git, python3, Claude Code CLI
git clone https://github.com/komluk/scaffolding
cd scaffolding
./install.sh --target /path/to/your/project/.claude
The installer auto-detects your test commands, project name, and other settings. Hit Enter to accept defaults, or customize anything. Your choices are saved to ~/.scaffolding.env and can be changed later.
/plugin update scaffolding@komluk-scaffolding
Or full reinstall:
/plugin uninstall scaffolding@komluk-scaffolding
/plugin install scaffolding@komluk-scaffolding
cd scaffolding
git pull
./install.sh --refresh
11 agents analyst, architect, researcher, developer, debugger,
reviewer, optimizer, tech-writer, devops,
gitops, coordinator
30 skills api-design, error-handling, pattern-recognition,
testing-strategy, python-patterns, mui-styling, ...
14 commands /workflow, /init-openspec, /context, and more
7 hooks pre-commit validation, block destructive commands,
block env file writes, ...
2 workflows workflow — full 8-step pipeline (analyst → architect → developer → reviewer → ...)
coordinate — LLM-planned minimal pipeline for everything else
| Agent | What it handles |
|---|---|
| analyst | Requirements, feasibility, proposals |
| architect | System design, API design, multi-file planning |
| researcher | External APIs, libraries, best practices |
| developer | Code, bug fixes, features, tests, UI |
| debugger | Errors, unexpected behavior |
| reviewer | Code review, security analysis |
| optimizer | Performance, database, queries |
| tech-writer | README, CHANGELOG, docs |
| devops | CI/CD, deployment, infrastructure |
| gitops | Git operations, commits, merges, push |
| coordinator | Decomposes complex tasks into agent sequences |
These features need a running backend and are not part of this plugin:
Skills that reference these features degrade gracefully — they skip the unavailable section instead of failing. See docs/locked-to-project/ for details.
Make sure you ran /scaffolding:init-scaffolding after installing the plugin. This copies CLAUDE.md to your project — without it, Claude doesn't know about the agents.
Plugin agents are namespaced. Use scaffolding:developer not developer. The CLAUDE.md copied by /scaffolding:init-scaffolding already handles this — if you see this error, re-run /scaffolding:init-scaffolding.
Re-add the marketplace first:
/plugin marketplace add komluk/scaffolding
Run /scaffolding:init-scaffolding — it creates the full directory structure.
MIT
AI-supervised issue tracker for coding workflows. Manage tasks, discover work, and maintain context with simple CLI commands.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Multi-LLM orchestration for Claude Code with Double Diamond workflows, provider routing, safety gates, and automation. Use '/octo:auto' or just describe what you need. Run /octo:setup.
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Real-time statusline HUD for Claude Code - context health, tool activity, agent tracking, and todo progress
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation