jtenner

Guided wizard workflow for installing Metidos in Docker or Podman, configuring runtime access through a reverse proxy or Tailscale, importing Codex, selecting core plugins, creating model-provider plugins, wiring env secrets, and enabling Telegram/Gmail integrations.

Use for accessibility implementation, audits, remediation, validation, WCAG-oriented reviews, keyboard and screen-reader support, inclusive UI decisions, or when the user mentions a11y.

Follow the canonical Metidos repository commit workflow, including atomic commits, validation policy, documentation sync, and detailed commit messages. Use when committing changes, preparing a commit, validating a change before commit, or updating repository workflow guidance.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Use when running or reviewing accessibility tests, validating WCAG conformance, checking keyboard/screen-reader/mobile usability, or verifying that fixes work in practice.

Use when documenting accessibility issues, writing remediation guidance, prioritizing fixes, or translating audit findings into actionable engineering/design work.

Use when evaluating or improving screen reader support, checking announcements, landmarks, labels, reading order, or dynamic updates for blind and low-vision users.

Use when designing or reviewing touch interactions, gesture-based controls, swipe patterns, or alternatives for users who cannot perform complex gestures.

Implement, port, or sign off Starshine optimizer passes with the repo-standard TDD, registry, Binaryen semantic parity, performance, validity, and documentation workflow. Use when working on pass creation, pass porting, pass parity, pass fuzz compare failures, optimizer registry wiring, preset changes, or pass signoff.

Commit current work using Starshine's commit policy. Use when the user asks to commit, create commits, save changes to git history, or prepare a commit from the current worktree.

Create a continuation thread with default thread parameters and a comprehensive handoff of the current task. Use when the user says "/handoff", asks to hand off the current work, continue in another thread, or wants a fresh thread with full context.

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.