genie

Activate Architect genie to bootstrap architecture artifacts (ADR-000 and C4 diagrams) for an existing project.

Activate Architect genie for interactive architecture workshops — approach comparison, technical decisions, interface design, and risk prioritization.

Generate a brand-consistent image using AI, with cost-tiered model routing and graceful degradation.

Review a design artifact (wireframe, mockup, screenshot, or generated image) against brand guidelines and universal UX heuristics, producing a persistent Design Review Report.

Generate W3C Design Tokens JSON from an existing brand guide.

Activate Designer genie to create, evolve, or activate a brand guide via an interactive design workshop.

Quick bug fix workflow: light shape → deliver → discern.

Debt reduction workflow: diagnose → tidy (batched).

Create a conventional commit for completed work after review approval.

Initialize session with project context. Run at the start of every session.

Find past work on a specific topic. Use before starting work that might duplicate previous effort.

Update context documents from current codebase state. Use when context docs are stale.

Create a handoff summary of current work state. Run at end of session or before switching genies.

Activate Shaper genie to define problem boundaries and create a shaped work contract.

Write implementation to pass existing tests (TDD Green phase). Tests must already exist.

Write failing tests only (TDD Red phase). Use this for human-in-the-loop TDD workflow.

Activate Crafter genie to implement the technical design with TDD discipline.

Activate Architect genie to create technical design within shaped boundaries.

Activate Architect genie to perform codebase health scan and identify cleanup needs.

Activate Critic genie to review implementation against acceptance criteria.

Activate Scout genie to explore opportunities and surface assumptions.

Mark completed work as done and archive artifacts.

Orchestrate full feature lifecycle: discover → define → design → deliver → discern.

Display available Genie Team commands and current project status.

Show current work status and recent document trail.

Explicit transition between lifecycle phases with context summarization.

Orchestrate autonomous PDLC lifecycle: discover → define → design → deliver → discern → done → commit.

Activate Scout genie to produce rich capability specifications from an existing project's source code, tests, and documentation.

Technical investigation workflow: discover → design (feasibility only).

Activate Tidier genie to execute cleanup in safe, tested batches.

Technical designer for system architecture, pattern enforcement, and feasibility assessment. Use for design exploration and technical spikes that benefit from context isolation.

TDD implementation engineer for building software with test-first discipline. Use for delivering designs with red-green-refactor, minimal code, and strict scope discipline.

Code review specialist for acceptance criteria verification, pattern compliance, and quality assessment. Use when reviewing implementations against specs and designs.

Brand strategist for visual identity, design systems, and AI-assisted asset generation. Use for brand workshops, image prompt optimization, and brand guide analysis.

Discovery specialist for problem exploration, assumption surfacing, and opportunity mapping. Use for research-heavy discovery using Teresa Torres, JTBD, and evidence-based product thinking.

Problem framing specialist. Proactively activates when the user describes a feature request, solution-loaded problem, or says 'we should add' or 'let's build'. Reframes solutions as problems and produces Shaped Work Contracts with appetite boundaries.

Code cleanup specialist for safe, incremental refactoring using Kent Beck's Tidy First approach. Use for codebase analysis and cleanup execution.

Ensures ADR and C4 diagram behaviors during all workflows. Use when loading context, discussing architecture, creating designs, or when "ADR", "architecture decision", "C4", "coupling", "cohesion", or "boundary" are mentioned. Activates during /arch:init, /context:load, /context:refresh, /spec:init, /define, /design, /deliver, /discern, /handoff, /diagnose, and /discover.

Ensures brand-consistent behavior during workflows. Auto-activates when brand guide exists and "brand", "brand spec", "design tokens", "brand consistent", or "visual identity" are mentioned. Activates during /brand, /brand:image, /brand:tokens, /design, /deliver, /discern, /handoff, /context:load, and /context:refresh.

Enforces code quality standards when writing or editing code. Use when implementing features, fixing bugs, or refactoring. Ensures error handling, no hardcoded values, proper patterns, and security considerations.

Creates conventional commit messages following commitlint standards. Use when committing code, creating git commits, or when the user says commit, push, or save changes.

Structured root cause investigation when tests fail unexpectedly or fixes don't resolve the issue. Use when a test fails that you expected to pass, when a previous fix attempt didn't work, or when an error occurs during implementation.

Enforces project patterns and architecture conventions. Use when designing systems, implementing features, or reviewing code structure. Ensures consistency with established patterns.

Ensures problem-first framing before solutioning. Use when defining work, discussing features, handling requests that sound like solutions, or when someone says "we should add" or "let's build".

Ensures spec-driven behavior during all workflows. Use when loading context, discussing project structure, starting features, or when "spec", "specification", "acceptance criteria", or "bootstrap" are mentioned. Activates during /context:load, /context:refresh, /spec:init, /define, /design, /deliver, /discern, /handoff, /done, and /discover.

Ensures tech-stack-aware behavior during workflows. Auto-activates when stack profile rules exist in .claude/rules/stack-*.md. Activates during /arch:init, /context:load, /context:refresh, /deliver, /discern, /diagnose, and /handoff.

Enforces test-driven development with Red-Green-Refactor cycle. Use when writing new code, implementing features, fixing bugs, or when tests are mentioned. Ensures tests are written before implementation.

3 hooks across 3 events