By jaebit
Architecture compliance enforcement for layered projects — config-driven layer boundary checks, contract-first development, and design decision records
This skill should be used when the user asks "create ADR", "document design decision", "adr", "record architecture decision", "why did we decide this", or wants to create an Architecture Decision Record documenting a design choice with context, rationale, alternatives, and consequences.
This skill should be used when the user asks "check architecture", "layer violations", "arch-check", "reference rule violations", "cross-layer reference check", "architecture scan", or wants to detect layer boundary violations by analyzing source references against arch-guard.json rules.
This skill should be used when the user asks "do contracts exist?", "can I start implementing?", "contract-first check", "are interfaces defined?", "define interfaces", "suggest interfaces", "fill contracts", or wants to verify that the layer's Contracts project exists and required interfaces are defined before writing implementation code. Can also design and generate interfaces interactively.
This skill should be used when the user asks "review implementation", "check design compliance", "impl-review", "does this code match the architecture?", "responsibility boundary check", or wants to verify implementation code against architecture docs — checking component responsibility boundaries, interface contract compliance, and reference rule compliance.
This skill should be used when the user asks "generate implementation", "implement interface", "create stubs", "implement", "generate class from interface", or wants to generate implementation classes and unit test stubs from Contracts interfaces following the architecture rules in arch-guard.json. Creates sealed classes with constructor injection and empty test methods.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
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.
Claude Code plugin marketplace — automate, orchestrate, and extend AI-powered development workflows.
| Plugin | Version | Description |
|---|---|---|
| crew | 4.1.1 | Agent-orchestrated development — 9-stage pipeline, 8 adaptive agents, parallel execution, research, review |
| autopilot | 0.4.0 | End-to-end autonomous pipeline — wraps crew + debate + arch-guard into a single /autopilot command (research → design → build → review → report) |
| multi-model-debate | 1.0.0 | Multi-agent debates using Claude, Codex, and Gemini for decision-making |
| arch-guard | 0.2.2 | Architecture compliance — layer boundary checks, contract-first development, ADRs |
| gemini-cli | 1.0.0 | Gemini CLI integration — code review, commit messages, documentation |
| worktree | 0.1.0 | Git worktree lifecycle management — create, merge, cleanup |
# Add marketplace
claude plugins add github:jaebit/claudemate
# Install plugins
claude plugins install crew
claude plugins install autopilot
claude plugins install arch-guard
Single command from idea to working code:
/autopilot "build a notification system"
Chains crew, multi-model-debate, and arch-guard into a 5-phase autonomous pipeline with one user confirmation gate after design.
Agent-orchestrated development:
/crew:go "Add JWT authentication" # Full 9-stage pipeline
/crew:explore --arch "microservice" # Architecture design
/crew:review --all # Unified code review
Cross-model evaluation for design decisions:
/multi-model-debate:debate-orchestration "REST vs GraphQL"
Architecture compliance for layered projects:
/arch-guard:arch-check # Verify layer boundaries
/arch-guard:contract-first # Define interfaces first
/arch-guard:scaffold # Generate module structure
plugins/.claude-plugin/plugin.json (only name, version, description)skills/*/SKILL.md), hooks (hooks/hooks.json), agents, or commands.claude-plugin/marketplace.jsonMIT License
npx claudepluginhub jaebit/claudemate --plugin arch-guardAgent-orchestrated development pipeline — 9-stage automation with 8 adaptive agents, parallel execution, research, and review
Git worktree lifecycle management — create, merge, cleanup
Google Gemini CLI integration for code review, commit messages, and documentation
Orchestrate structured multi-agent debates using Claude, Codex, and Gemini for software engineering decision-making
End-to-end autonomous coding pipeline — orchestrates cw, multi-model-debate, codex CLI, and arch-guard into a single /autopilot command
AI-powered architecture documentation framework with ADRs, reviews, and pragmatic mode
Make your AI agent code with your project's architecture, rules, and decisions.
[Beta] 6つの専門エージェントチームでコードベースのアーキテクチャを多角的に分析するスキル
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions. For example: user: 'I need to add a user authentication system to my app' -> assistant: 'I'll use the code-architect agent to design the architecture and folder structure for your authentication system' -> <uses agent>. Another example: user: 'How should I organize my e-commerce product catalog feature?' -> assistant: 'Let me use the code-architect agent to design a scalable structure for your product catalog' -> <uses agent>.
Architecture Deep Research — scan a repo, draft a PRD, run live deep research, get a cited handoff. Use when picking a topology, retrieval architecture, event bus, storage engine, auth pattern, or any system-design decision before code lands.
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions. For example: user: 'I need to add a user authentication system to my app' -> assistant: 'I'll use the code-architect agent to design the architecture and folder structure for your authentication system' -> <uses agent>. Another example: user: 'How should I organize my e-commerce product catalog feature?' -> assistant: 'Let me use the code-architect agent to design a scalable structure for your product catalog' -> <uses agent>.