update-the-design-page

Synchronizes a Claude Design page with the actual poster drawings rendered by code.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/oleg-vasilyev/FoolProof --skill update-the-design-page-oleg-vasilyev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-the-design-page
Source: https://github.com/oleg-vasilyev/FoolProof/tree/main/.claude/skills/update-the-design-page
Command: npx skills add https://github.com/oleg-vasilyev/FoolProof --skill update-the-design-page-oleg-vasilyev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design documentation pages drift out of sync with what the code actually renders, leaving mockups that show intentions instead of real output. This Skill pulls the Durak Stats Poster System page from Claude Design, splices in the current renderer output, fixes stale prose, and pushes the page back with byte-level verification. ## Core Features & Use Cases - Splice-based updates: Runs node scripts/tools/tools.ts design-page to replace poster <div> bodies matched by name, never regenerating the page or touching surrounding markup. - Prose correction: Detects sentences made false by the change (renamed awards, new colors, changed sizes) and bumps the Rev. marker in header and footer together. - Byte-checked push: Uploads via finalize_plan and write_files, then reads the page back and requires byte-identical match before committing the docs/posters/design-page.sync fingerprint. - Use Case: After refresh-the-pictures redrew the poster mockups, run this Skill so the design page shows the real drawings and docs-check stops failing on the stale sync fingerprint. ## Quick Start Update the design page so it matches what the poster renderer currently draws, then push it back and verify the bytes match.

Frequently Asked Questions about update-the-design-page

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a Claude Design page to match rendered mockups?▼

Pull the page with DesignSync get_file, run the design-page splice script to replace poster div bodies matched by name, fix any prose the change made false, then push with write_files and verify the read-back is byte-identical.

When should the design page be updated after code changes?▼

Update it after the design changed mid-phase, after a new chart was drawn on the page, or after the picture-refresh step redrew the poster mockups. It is stage 5 of the change-to-release flow, run once the drawings are final.

Does the splice script reorder or regenerate the design page?▼

No. The script only replaces the body of each poster div matched by name and touches nothing else. Reordering the page cannot swap drawings, and slots naming unknown posters or holding nested markup are refused by name.

Why does docs-check fail after updating the design page?▼

docs-check fails while the fingerprint in docs/posters/design-page.sync disagrees with the English posters. Commit the sync file only after the push step passed, because before that it claims a sync that did not happen.

Can I use Design System features like register_assets on this page?▼

No. The project is PROJECT_TYPE_PROJECT, not PROJECT_TYPE_DESIGN_SYSTEM, and the type is fixed at creation. The Design System pane, @dsCard markers, and register_assets do not apply.