“design”

Design and build reactive, type-safe, production-grade backends on Convex.

Visual design law for the generated app — screen structure, colour tokens, typography, icons, spacing, and the states every screen owes the user.

Design and refine context-fit user interfaces, then verify the rendered result.

Generates and maintains a design manifest for visual consistency.

Apply Odin's visual design, interaction, animation, and responsive UX principles when explicitly requested.

Design interfaces and domain models.

Think a design through before coding it, or stress-test one you already have.

Designs or redesigns user interfaces with a coherent visual system, appropriate component sources, motion, responsive behavior, and rendered-browser…

Use when designing or improving a module's interface, deciding where a seam goes, making code more testable or navigable, or pinning down domain terminology.

Design a feature or change into a reviewed system spec (plus a slim ADR only when the decision threshold is met).

Writes a clear design for a proposed feature or system change.

Design the implementation for an approved software specification, including architecture, module boundaries, data flow, APIs, state management, error…

Design or redesign a web interface with deliberate taste instead of the model's default look.

Design an LLM Rail workflow — analyze intent, validate requirements, and generate optimized YAML

Grill the user relentlessly about a plan or technical design until reaching shared understanding, challenging it against the existing domain model, sharpening…

Use for frontend UI design review and refinement tasks: audit, critique, polish, harden, layout, typeset, colorize, clarify, or distill pages, components…

Interactive requirements clarification and test plan design.

Design/architecture/API + planning seat — produce clean design docs, architecture decisions, and API shapes that fit the existing codebase; hand…

Use for standard or complex new work before coding or planning.

Clarify a user problem and visualize the experience before deriving features or tickets.

Decide the shape of code before it's built — modules, interfaces, function signatures, data shapes, and the seams tests will live at.

Create distinctive frontend interfaces, review UI against web guidelines, and build brand identities.

Design phase.

Use when in ARCH_REVIEW to produce a concrete design doc with tradeoffs, constraints, and decision rationale.