Design Actions

Required only for Design Actions. Ordinary Waypoint Annotations do not require Impeccable.

Install Impeccable first

Design Actions are powered by the external Impeccable skill. Install Impeccable for the coding agent that will claim the Annotation, following its current agent-specific instructions.

Waypoint does not install Impeccable or detect whether an agent can load it. Waypoint does not currently certify a particular agent installation path, so confirm the skill is available in the same environment where the agent connects to Waypoint through MCP.

Write one brief, then choose the discipline

Describe the desired outcome in the normal Annotation comment, then turn on Design Actions. Leave the action unselected for Design Actions · Freeform, or choose one named discipline: Bolder, Quieter, Distill, Polish, Typeset, Colorize, Layout, Animate, Delight, or Overdrive.

Each Annotation carries at most one primary Design Action. The comment remains the only brief, so constraints and context stay together instead of drifting across two prompt fields.

Choose a discipline by the result you want

Use a brief such as “Make the main action easier to notice without adding more color,” then choose the discipline that matches your goal. Bolder asks for stronger expression; Quieter asks for restraint; Typeset focuses on typography; Layout focuses on arrangement. Freeform lets the brief guide the approach without naming a discipline.

Include constraints the agent cannot infer from a screenshot: preserve the wording, keep the mobile layout, or avoid changing shared components. After implementation, inspect the result and the Resolution Record, which captures the Design Action’s completion summary and verification evidence.

Request Variants separately

A Design Action describes how the agent should approach the interface. Request Variants asks for multiple named candidates. You can use either feature alone or combine them on the same Annotation.

When Variants are requested, Waypoint owns the Active Variant, discard and Keep decisions, and final cleanup. Finalize the chosen candidate before resolving the Annotation so the coding agent can reconcile temporary source Scaffold safely.

Recover when the skill is unavailable

If the executing agent cannot load Impeccable, it should not silently replace the requested discipline with generic design work. The Annotation returns to Pending with a workflow_unavailable Work Notice.

Install or repair Impeccable in that agent environment, then claim the same Annotation again. The original brief and Design Intent remain in the Queue for the next attempt.

Keep one workflow authority

Impeccable supplies the design methodology. Waypoint remains responsible for the Annotation, Queue, Claim and Watch state, Work Notices, retained results, Variant selection, and cleanup decisions. The coding agent remains responsible for source changes.

Waypoint does not embed Impeccable Live or adopt its separate picker, polling, preview, or acceptance workflow. That boundary keeps one authoritative lifecycle and makes interrupted work recoverable through the normal Queue.