Redesign

Selectively redesign one or more of the 5 landing page variations generated by design-gallery. Avoids repeating previously used design directions and respects user-approved ones.

When to Use This Skill

• User ran /design-gallery and is not happy with one or more of the variations
• User says "redesign page 3", "redo all of them", "none of these work, try again", or runs /redesign
• Always used after design-gallery has already generated pages

Workflow

Step 1 — Resolve the Session ID

See lib/session.md — Session ID Resolution

The user may provide the session ID explicitly (e.g. "redesign page 3 from session a3f9k2") or it may be implicit from context.

Step 2 — Load Directions from File

See lib/directions.md — Read Rules

Read {output_root}/gallery/{id}/directions.json. This is the authoritative record of what has been designed. Do not rely on session memory alone.

Use the loaded data to build the current state of the gallery.

Step 3 — Show Existing Pages

List all existing gallery pages with their current design directions. Format:

Here are your current design variations (session: {id}):

1. /gallery/{id}/1 — Dark & Bold (high contrast, split-screen hero)
2. /gallery/{id}/2 — Minimal Clean (whitespace-heavy, single-column)
3. /gallery/{id}/3 — Glassmorphism (frosted blur, asymmetric cards)
4. /gallery/{id}/4 — Corporate Pro (muted palette, grid-based)
5. /gallery/{id}/5 — Vibrant Playful (expressive gradients, full-bleed)

Which ones would you like to redesign? (e.g. "1 and 3", "all", "just 5")

Wait for the user's answer before proceeding.

Step 4 — Confirm What to Keep

After the user specifies which pages to redesign:

• Pages NOT selected → keep exactly as-is, do not touch them
• Pages selected → will be fully replaced with a new design direction

If the user mentioned any direction they liked (e.g. "I like the vibe of page 2 but want the rest redone"), note that explicitly:

"Got it — keeping page 2 (Minimal Clean) as-is and redesigning pages 1, 3, 4, 5."

Step 5 — Recall Used Directions

Before proposing new directions, review all directions recorded in directions.json — these are off-limits for new proposals.

Also note any directions the user has explicitly said they like — those must not be replaced even if their page is being redesigned.

Step 6 — Propose New Directions (WAIT FOR APPROVAL)

For each page being redesigned, propose a new direction that:

• Has not been used before (check directions.json)
• Differs in both visual style and layout from all other current and previous directions
• Is genuinely distinct from the directions being kept

Format:

Here are the new directions I'm planning:

- Page 1: **[New Direction Name]** — [One sentence: visual style + layout]
- Page 3: **[New Direction Name]** — [One sentence: visual style + layout]

Shall I proceed, or would you like to adjust?

Do not write any code until the user approves. If the user requests changes, revise and re-present.

Step 7 — Update directions.json

See lib/directions.md — Update Rules

Immediately after approval, update directions.json to replace the entries for pages being redesigned with the newly approved directions. This keeps the file as the single source of truth before any code is written.

Step 8 — Rebuild Selected Pages

After updating directions.json, fully replace each selected page with its new design. The implementation rules are identical to design-gallery:

• UI-only — no business logic, no API calls, placeholder copy is fine
• Follow the same routing convention already in use (/gallery/{id}/1–/gallery/{id}/5)
• Overwrite the existing file for that route completely — do not preserve any old styles
• Each page must be visually distinct from all others currently in the gallery

Tell the user as you complete each page:

"Page 1 (Neo Brutalist) — done."

Step 9 — Update the Gallery Page

After all redesigned pages are complete, update the /gallery/{id} navigation page to reflect the new direction names and descriptions from directions.json.

• Keep entries for unchanged pages exactly as they were
• Update only the changed entries with the new direction name and description

Finish with:

"Done! Updated pages and gallery:

• Redesigned: [list]
• Unchanged: [list]

Run /redesign again if you'd like to iterate further."

Design Direction Memory Rules

• directions.json is the authoritative history — always read it before proposing new directions
• Never propose a direction that appears anywhere in directions.json, even if that page was later redesigned
• If the user says "I liked the dark direction, keep something like that" — note it as a soft preference and factor it into new proposals without repeating the exact same direction
• If you run out of genuinely distinct directions (unlikely with 5 pages), inform the user and ask how they'd like to proceed

Notes

• This skill only operates on pages previously created by design-gallery — do not create new routes
• Do not modify any pages the user did not select for redesign
• Do not modify any project files outside the gallery routes
• The gallery page itself is always updated at the end to stay in sync