Revise wireframe

---
name: revise-wireframe
description: Offline wireframe order/presentation revise using package handoffs only.
license: PolyForm-Noncommercial-1.0.0
---

> Frezpo free tool — open for learning and paid client work. May not be sold or productized as a competing skill pack. Built by Frezpo (https://frezpo.com).

# Skill: revise-wireframe

**Package-native skill** — run in the user's local LLM or coding agent.
**Do not re-run the ads-landing pipeline** or the product UX agent. This skill burns
**their** tokens.

## When to use

- Reorder landing sections or change `position` (above-fold / early-scroll / mid-scroll / bottom).
- Change **presentation** (`ui_component`, `layout_mobile`, `layout_desktop`).
- Soften or drop a section the brief cannot support (e.g. unearned proof).
- Prepare structure before / while generating the site with design tokens or tools like
  ui-ux-pro-max.

## Inputs (read first)

1. `machine/build_context.json` — **SSoT** for `sections[]` (order, position, ui_component,
   layouts, content_fields, cta, developer_notes).
2. `02_ux.md` — human narrative of the same wireframe.
3. `01_content.md` — copy + hooks + message-match (locked story).
4. Optional user notes: brand tokens, Figma kit, preferred stack, revise intent.

## Locked vs editable

| Locked (without explicit user override) | Editable offline |
|-----------------------------------------|------------------|
| `content_fields[].text` (copy is sacred) | `sections` **order** |
| Message-match: winning ad H1 ↔ hero H1 intent | `position` per section |
| Dominant angle / disqualifiers from content | `ui_component` |
| Invented proof, stats, testimonials, prices | `layout_mobile` / `layout_desktop` |
| Re-running the product pipeline | Dropping a section the brief cannot support (state why) |
| Inventing a full design system when tokens absent | `developer_notes` (clarify only) |

## Procedure

1. Restate the user's revise intent in one sentence.
2. Load `sections` from `build_context.json` in array order (= page order).
3. Apply only structural / presentation edits. Keep every `content_fields[].text` **verbatim**
   unless the user explicitly asked for copy changes (then use skill `rewrite-copy`).
4. Preserve `section_id` when the section remains; if removing a section, drop it from
   `sections` and note why in a short changelog.
5. Do not invent design tokens or stock imagery. User-supplied tokens → record as assumptions.
6. Emit outputs below. Do not implement the full site unless the user also invokes
   `build-landing-page`.

## Output contract

1. **Updated** `machine/build_context.json` — same schema; revised `sections` order /
   presentation fields only (unless user requested more).
2. Optional **changelog** (bullets): moves, presentation changes, drops + why.
3. Optional sync of `02_ux.md` section order if human docs should match.

## Examples

- *"Put proof above the fold"* → move proof-like `section_id` earlier; set `position`;
  keep copy fields unchanged.
- *"Pain as accordion"* → change that section's `ui_component` / layout notes only.
- *"We have no real testimonials"* → drop or demote proof; do not invent quotes.

## Success criteria

- [ ] Page order matches the revised `sections` array.
- [ ] Remaining sections still have valid `section_id`, `position`, `ui_component`, layouts.
- [ ] All `content_fields[].text` still verbatim (unless user asked for copy rewrite).
- [ ] No pipeline re-run; no invented proof or design system.
- [ ] Changelog states assumptions.

## Notes

- Soft-fill (`Not produced in this run.`) is not invent-license.
- After revise, implement with skill `build-landing-page` against the **updated** context.