Pace
← All cookbooks Design cookbook

Design

Design audits on every PR. Brand-voice enforcement on shipped content. Defers to impeccable for the frontend craft Pace doesn't own.

Marquee recipe

Per-PR design audit before review

Design regressions caught before a reviewer ever clicks "request changes".

Every PR touching CSS / JSX / Vue templates runs /impeccable audit against the changed files. Findings (contrast issues, anti-pattern hits from impeccable's 50+ detection rules, layout regressions) post as inline comments. Reviewers see the design diff alongside the code diff.

Trigger
Routine, GitHub trigger on pull_request.opened against frontend repos
Skills
/impeccable audit, /impeccable critique
Features
Routines (GitHub trigger), inline PR comments, plan mode for fixes

Brand-voice enforcement on every PR

Voice drift caught before it ships, not after the campaign runs.

Any PR that touches landing pages, blog posts, or email templates auto-runs brand-voice-enforcement from the brand-voice plugin and posts inline comments with concrete fixes. Pairs with the marketing plugin's draft-content when a section needs a rewrite from scratch.

Trigger
Routine, GitHub trigger on pull_request.opened for content/CMS repos
Skills
brand-voice-enforcement, draft-content
Features
Routines (GitHub trigger), inline PR comments, plan mode

How to set it up

  1. 1
    Create the scheduled routine in Cowork

    In Cowork, open Routines → New routine → Schedule. Match the cadence described in the trigger above.

  2. 2
    Paste this as the routine prompt
    Brand-voice PR prompt 
    When a PR opens touching landing pages, blog templates, or email templates, run brand-voice-enforcement against the changed text. For each violation (off-tone, restricted term, structural deviation), post an inline comment with the concrete fix.

Where a section needs a rewrite from scratch rather than a tweak, draft the replacement using draft-content from the marketing plugin. Park rewrites in plan mode.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.

Polish pass on a feature branch

Trigger
Interactive, before merging a feature
Skills
/impeccable polish, /impeccable typeset, /impeccable layout
Features
Multi-skill chain, plan mode

Before merging, run /impeccable polish on the branch. The router orchestrates typography, color, layout, and motion sub-commands; plan mode shows the diff before anything ships. The polish pass is what turns a working feature into one that feels intentional.

Cross-tool design system sync

Trigger
Interactive, when tokens or components change
Skills
design-system (Pace), /impeccable colorize + /impeccable typeset (impeccable)
Features
Cross-plugin chain, MCP connector to Figma

Pace's /design plugin manages the system at the spec level (Figma tokens, contribution model, dev handoff). Impeccable's /colorize and /typeset apply those tokens in code with full understanding of how they look on screen. Use both: the design plugin sets the rules, impeccable enforces them in the codebase.

Visit impeccable.style Read the impeccable docs
When to use Pace's /design plugin vs impeccable

Different layers of the same craft:

  • Pace /design covers UX research, design system management, accessibility audits at the policy level, dev handoff, and research synthesis. Use it for the work a design team does.
  • Impeccable covers the visual + interaction craft of writing the UI code itself: typography choices, color tokens, spatial rhythm, motion design, responsive layout. Use it for the work a designer would obsess over when looking at the rendered pixels.

Most teams want both. Install impeccable alongside Pace; the Pace CLI (npx pace skills install) offers it during setup.

Accessibility audit before every release

Before merging the release branch, a routine runs an accessibility sweep across the changed pages: WCAG 2.1 AA checks, keyboard-navigation flow, color contrast against the design tokens, screen-reader labeling. Findings post as a single triaged issue per release: P0 must-fix, P1 should-fix, P2 worth-noting.

Trigger
Routine, GitHub trigger on release-branch creation
Skills
accessibility-audit, /impeccable audit
Features
Routines (GitHub trigger), GitHub Issues integration, axe-core via MCP

How to set it up

  1. 1
    Create the GitHub-triggered routine

    In Cowork, open Routines → New routine → GitHub event. Pick the repo and event described in the trigger above. The Claude GitHub App is offered as part of setup; install it on the relevant repo.

  2. 2
    Paste this as the routine prompt
    Release a11y audit prompt 
    When a release branch is created, run an accessibility audit across the pages changed in the release:

- WCAG 2.1 AA checks via axe-core.
- Keyboard-navigation walk on every interactive surface.
- Color contrast verified against design tokens.
- Screen-reader labeling and ARIA roles.

Post a single triaged issue per release: P0 must-fix, P1 should-fix, P2 worth-noting. Block the release on P0 only.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.