pb-redesign-app
Overhaul one app's UI against an audit: UX audit and UI review of the running app, current versus proposed design tokens, a before/after visual plan, a startcycle build, point fixes, accessibility and
SKILL.mdskills/playbooks/pb-redesign-app/SKILL.md
GitHubRedesign one app
What you get: one app's UI overhauled against a written audit, new design tokens and a before/after plan, delivered as a pull request after your GO.
Inputs
- repo — the app's checkout, default the current directory
- app_url — the running local dev URL (not a remote or production site)
- scope — the screens or flows to redesign, asked once
Steps
- ui-ux-pro-max review (plus ux-audit and ui-review if the optional StyleSeed package is installed) —
app_urlopened and screenshotted per screen in scope with chrome-devtools (puppeteer_navigate,puppeteer_screenshot) →production_artifacts/pb-redesign-app-<date>/audit.mdwith numbered findings — app_url unreachable or chrome-devtools unavailable → log it and stop; every finding has a screenshot or a file reference - Token diff (godmode-ui-ux DTCG rules; ui-tokens if the optional StyleSeed package is installed) — current tokens read from the repo versus proposed DTCG tokens →
tokens-diff.mdin the same folder — diff written, nothing applied yet - plan-canvas (Plan Builder mode) — before/after per screen in scope → plan link or file in the run log — stops for approval
- startcycle (architect, techlead, reviewer) — the approved plan and audit → build on a new branch; godmode-ui-ux rules apply to the UI work — reviewer reports no open
blockingfinding - bdb-visual-edit — point fixes the human annotates in the running app via
aos-plan-canvas annotate, each after its diff plan is approved → edited files in the run log — only the picked files change - wcag-audit-patterns and webapp-testing — accessibility pass plus a browser test of the changed screens, then the repo's lint and test scripts → results in the run log — all exit 0; each audit finding marked fixed or deferred
- [GO] git push -u origin <branch> and gh pr create — one combined GO; the WAITING FOR GO line names the branch, base branch, PR title and the head SHA. The run stops here until the human types GO. Where the hook runs, it covers
git push;gh pr createis not hooked, so this GO is its only guard. Afterwardsgh pr view <branch> --json state -q .stateequalsOPENand the PR URL is logged.
Run log: production_artifacts/pb-redesign-app-<date>.md in the start directory, never committed
Rules
- Anything other than the literal GO (case-insensitive) is not a GO; a GO covers only that one step, one time.
- GO is by contract in every harness. The go-gate hook is only a backstop on Claude Code, OpenCode and agy (Codex: unverified; Cursor, Kimi: none). A missing hook is never permission to proceed.
- A failed check stops the run: write the failure into the run log and report. No silent retries.
- Write one run-log line per step as it completes (
N. done|skipped|failed — artifact — check result) andWAITING FOR GO: <step>at each gate.