ottonomous

Build React components, implement responsive layouts, and handle client-side state management. Optimizes frontend performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.

Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.

Reviews code changes for architectural consistency and patterns. Use PROACTIVELY after any structural changes, new services, or API modifications. Ensures SOLID principles, proper layering, and maintainability.

Reviews code changes for bugs, security issues, and code quality. Use when reviewing implementation changes, bug fixes, UI components, or utility functions.

Writes unit tests for pure functions. Identifies testable code, skips I/O-heavy files, and ensures comprehensive coverage with happy path, edge cases, and error handling.

Verifies running apps against acceptance criteria using agent-browser CLI. Returns structured pass/fail with ARIA/screenshot evidence. Use when verifying a built app works as specified.

Diagnoses and fixes app verification failures using screenshot/ARIA evidence from smoke-tester. Use when a built app fails visual verification and needs debugging.

Browser automation for web apps and Electron desktop apps. Supports navigation, screenshots, ARIA snapshots, forms, data extraction, and visual verification. Use when inspecting UI, verifying frontend behavior, or automating browser/desktop workflows.

Pick or implement the next task or session. Use when continuing work, picking the next task, or implementing tasks from a task list.

Autonomous product development. Takes an idea and builds it end-to-end with subagents. Write a product spec, generate tasks from spec, implement each task while testing/reviewing changes, with final verification. Use when you want to build something from scratch.

Generates manual and automated verification checklists from specs. Creates structured QA plans with human and test verification steps. Use when preparing for QA, creating test plans, or validating completeness.

Resets workflow artifacts (.otto/ directory). Removes sessions, tasks, and specs. Use when starting over. Destructive - requires confirmation.

Reviews code changes for bugs with P0-P2 prioritized feedback. Uses parallel subagents for thorough analysis, then creates fix plans. Use when reviewing code, finding bugs, checking quality, or before merging. Use /review fix to implement fixes.

Writes product specifications through collaborative interview with web research. Use when planning, gathering requirements, designing new features, or creating a spec/PRD.

Synthesizes code docs into user-facing HTML summary. Creates semantic narrative explaining what changed and why it matters. Use when creating PR summaries, release notes, or change overviews.

Generates parallelizable task lists from specs. Breaks specs into atomic, prioritized tasks with dependencies. Use when you have a spec and need tasks, implementation breakdown, or a work plan.

Runs lint, type check, tests, and visual verification. Auto-detects tools. Use when running tests, linting, type checking, or writing tests.

Launches a built app and verifies it against the spec using browser/electron automation. Includes fix loop. Use after implementation to verify the app works as specified.