Browse the docs

Skills — Craft and build

/crisp-redesign

Redesign without regression.

Specialist extensionsuser-invoked

Redesign without regression. /crisp-redesign starts by detecting the mode — preserve or overhaul — because misclassifying that is the single biggest source of bad redesign output. It then audits the current state before touching anything: brand tokens, information architecture, SEO baseline, accessibility wins, and the analytics surface.

Modernisation is applied through six levers in strict priority order — typography first, full block replacement last — and the redesign is not done until the /crisp-review grade beats the audit baseline and every protected surface is confirmed intact.

Reach for it when the request contains the words modernise, refresh, or upgrade:

  • An established site needs a visual refresh without destroying brand equity
  • You inherited a surface with real SEO rankings and analytics history to protect
  • A rebrand is changing the visual language but content, IA, and URLs must survive
  • A previous quick refresh silently broke tracking or rankings and it must not happen again
  • Preserve-vs-overhaul decision
  • Modernisation levers in priority order
  • Current-state audit
  • SEO + analytics + a11y regression guard
Claude Code — /crisp-redesign
mode detected: preserve3 levers
LEVERHierarchy — collapse 18 nav items to 6 primary + overflow
LEVERDensity — tighten vertical rhythm to one 8px scale
Guarded: canonical URLs, GA events, focus order

Illustrative example output — not a real audit.

These require explicit approval in any mode. If the redesign would benefit from changing one, it is surfaced as a question with the trade-off stated — never folded into the diff:

  • URL structure and route slugs
  • Primary navigation labels
  • Form field names and order — breaks analytics and browser autofill
  • Brand logo or wordmark
  • Legal, consent, and cookie copy
How does it decide preserve versus overhaul?

From the language of the request and the state of the brand. Modernise or refresh with an established brand means preserve; rebrand or start fresh visually means overhaul. If it is ambiguous, it asks exactly one question rather than guessing.

Will it break my SEO?

Protecting SEO is a core design goal of the skill. The audit records ranking pages, meta titles, structured data, and OG cards before any change, and the quality gates confirm the whole baseline is intact before the redesign is declared done.

What are the six levers?

Typography, spacing and rhythm, colour recalibration, motion, hero recomposition, and full block replacement — each cheaper and safer than the next. The skill stops at the first lever that satisfies the brief; reaching for lever six when lever one would do is treated as over-delivery risk.

What if the surface genuinely needs a ground-up rebuild?

Then the mode is greenfield and this skill hands off to /feature-design. Redesign-without-regression logic only applies when there is something worth not regressing.

zsh
$ npx skills add @laith-wallace/crisp

Installs all fourteen CRISP skills and auto-detects your AI harness. Run /crisp-teach once per project first.

The CRISP Letter

Design evaluation, in writing.

Occasional letters on making AI agents produce work worth shipping. New skills announced here first. No noise.