From c0ee4f3caca82e6c4db53df92f187eb38f6a1e78 Mon Sep 17 00:00:00 2001 From: Paul Bakaus Date: Tue, 21 Jul 2026 23:49:01 -0700 Subject: [PATCH] Build mandate: author the assets, generate the imagery The truth split already permits full-fidelity demonstration data, but permission at selection time was not holding at build time: models that would not author covers, names, or thumbnails compensated with chrome, which is the content-starved look the detector hunts. Two build rules make it a mandate: every blank the ask round left open is authored at production fidelity (content is authorable, claims are labelable, nothing is omittable; unanswered commercial claims ship as marked placeholders with a replacement list), and when image generation is available, generating the build's imagery is part of building rather than a nicety. Co-Authored-By: Claude Fable 5 --- skill/reference/new-work.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/skill/reference/new-work.md b/skill/reference/new-work.md index 67fa72d3c..3af1de93d 100644 --- a/skill/reference/new-work.md +++ b/skill/reference/new-work.md @@ -88,6 +88,8 @@ Build the assigned direction, not a safer interpretation of it. The form supplie - **The first viewport is a thesis, not a header.** Demonstrate the mechanism immediately, at the scale the form has in life; do not trap the concept inside a standard hero or card shell. The memory test: if someone left after one viewport, what would they describe an hour later? If the honest answer is a mood, the concept has not committed yet. - **Prove, don't claim.** Show the subject doing its job: the interface at work, the mechanism dramatized, specifics a competitor could not copy-paste. Sections that restate a claim in different words add length, not substance. Demonstration data is design material: author it at full fidelity and label it synthetic; never invent prices, customers, benchmarks, or capabilities. +- **Author the assets; never substitute chrome.** Great surfaces live on carefully made content: names, entries, titles, copy, covers, thumbnails, textures. In greenfield work every blank the ask round left open is yours to author at production fidelity; content is authorable, claims are labelable, and no section is omittable. When a commercial claim stayed unanswered, ship a clearly marked placeholder value and hand the user the replacement list; a section thinned or dropped for missing truth is the asset gap wearing honesty's clothes. Decoration compensating for missing content, gradients, glass, borders, icon tiles where an authored asset belongs, is the same gap wearing chrome's. +- **Generate the imagery the build needs.** When any image generation is available, a harness-native tool or the API fallback context.mjs reports, generating the design's imagery is part of building: heroes, covers, demonstration thumbnails, textures, marks. Gray boxes and stock-styled placeholders are not a fallback while generation is one command away; state the cost once before the first render and batch what the surface needs. - **Build the form's web leverage.** When the chosen world names a technique (canvas, WebGL, view transitions, generative motion), build the technique itself, not a static imitation of it; the graceful fallback serves constrained clients, it is not the default experience. - **Pace the scroll like a studio.** Vary density, scale, image, motion, and quiet inside one grammar; a dense passage earns a quiet one, and the page ends anchored by a real close. One spacing rhythm throughout, with more space above a heading than below it. - **Use real, verified imagery when the brief implies it.** Search for the subject's physical object rather than the category; one decisive photo beats five mediocre ones. Verify stock URLs resolve.