Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Structured brainstorming process for exploring requirements and approaches before planning. Use when feature ideas are vague, multiple approaches exist, or trade-offs need exploration.
Capture solved problems as ADRs, specs, or knowledge docs in docs/ and specs/ for fast institutional lookup. Use after solving non-trivial problems to compound team knowledge.
Structured self-review process for brainstorm, plan, spec, or ADR documents. Use when a document exists and needs refinement before proceeding to the next workflow step.
Run DNS lookups via comma using doggo. Use this when lookups must be executed as `, doggo <name>` instead of calling doggo directly.
Search nixpkgs packages by keyword or regex using nix search. Use this when you need package names, attribute paths, and short descriptions from nixpkgs.