Epsilondelta-ai

Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil DNA codes to .pen frames, exporting .pen designs to React/Tailwind code, or choosing design-to-code workflows. Supports design fetching (Figma), visual rendering (Pencil MCP), and code generation (React/Tailwind).

Documentation generation patterns for technical specs, API docs, user guides, and knowledge bases using real tools like Sphinx, MkDocs, TypeDoc, and Nextra. Use when creating docs from code, building doc sites, or automating documentation workflows.

Backend development specialist covering API design, database integration, microservices architecture, and modern backend patterns. Use when user asks about API design, REST or GraphQL endpoints, server implementation, authentication, authorization, middleware, or backend service architecture. Do NOT use for database-specific schema design or query optimization (use moai-domain-database instead) or frontend implementation (use moai-domain-frontend instead).

Database specialist covering PostgreSQL, MongoDB, Redis, Oracle, and advanced data patterns for modern applications. Use when user asks about database schema design, query optimization, indexing strategies, data modeling, migrations, ORM configuration, or database performance tuning. Do NOT use for API design or server-side business logic (use moai-domain-backend instead).

Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.

UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when user asks about design systems, WCAG accessibility compliance, ARIA patterns, icon libraries, dark mode theming, design tokens, or user experience research. Do NOT use for React component coding or frontend implementation (use moai-domain-frontend instead) or shadcn/ui specifics (use moai-library-shadcn instead).

Canonical Claude Code authoring kit covering Skills, sub-agents, plugins, slash commands, hooks, memory, settings, sandboxing, headless mode, and advanced agent patterns. Use when creating Claude Code extensions or configuring Claude Code features.

Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use when dealing with token budget management, context window limits, session handoff, state persistence across agents, or /clear strategies. Do NOT use for agent orchestration patterns (use moai-foundation-core instead).

Initialize a repository for Re:ZERO Loop. Use for `/rezero init` in Pi, `/rezero:run init` in Claude Code, or `$rezero:run init` in Codex: detect project type, set up witch evaluation tools, create memory ignore rules, and record unavailable tools.

Orchestrate the Re:ZERO Loop. Use for /rezero requests in Pi: split large work, let Subaru implement, call Seven Witches, send warnings to Rem, reset on fail, and commit on pass.

Run the Re:ZERO Loop. Use for `/rezero:run` in Claude Code or `$rezero:run` in Codex: initialize if needed, plan tasks, let Subaru implement, run Seven Witches review, remember warnings, reset on failures, and commit on pass.

Run the Seven Witches evaluation for a Re:ZERO attempt. Use after Subaru implements and verifies a task to get independent pass/warning/fail verdicts.

Subaru's single-task Re:ZERO implementation loop. Use inside rezero after task splitting: implement, verify, survive witches, reset on fail, commit on pass.

Manage Re:ZERO warning memory. Use when witch warnings pass, when processing .rezero/memory/rem.md, or when resolved warnings should be removed.

Split a large Re:ZERO request into small ordered tasks with clear done criteria. Use before implementation when the request spans multiple features, files, or risks.

Render visual design mockups directly inside pi-web transcript. Use when the user asks to show UI/design options, mockups, or design directions in pi-web instead of opening an external design_deck browser window.