heimdall-agent 1.2.0 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +99 -29
- package/README.pt-BR.md +100 -30
- package/agents/frontend-designer.md +6 -1
- package/agents/modernizer.md +4 -1
- package/agents/orchestrator.md +2 -1
- package/agents/reviewer.md +1 -1
- package/config/agents.json +166 -4
- package/config/mcp.resolved.json +74 -0
- package/config/mcp.template.json +85 -0
- package/config/models.json +70 -0
- package/config/profiles.json +4 -3
- package/config/skills.json +911 -762
- package/docs/SKILLS.md +82 -21
- package/docs/designs/old/2026-11-16 upstream-skill-sync-and-provenance-links.md +60 -0
- package/doctrine/AGENTS.md +3 -3
- package/hooks/heimdall-hook.cjs +16 -1
- package/hooks/hooks.json +11 -0
- package/lib/model-context.cjs +50 -1
- package/lib/model-router.cjs +294 -0
- package/package.json +1 -1
- package/playbooks/05-canonical-plan-template.md +5 -12
- package/playbooks/06-model-registry-matrix.md +27 -19
- package/readme.html +1006 -0
- package/setup.mjs +317 -206
- package/skills/communication-doctrine/SKILL.md +2 -2
- package/skills/handoff/SKILL.md +13 -0
- package/skills/mcp-cleanup/SKILL.md +61 -0
- package/skills/mcp-sync/SKILL.md +58 -0
- package/skills/modern-web-guidance/SKILL.md +90 -0
- package/skills/ruminate/SKILL.md +140 -0
- package/skills/taste-skill/SKILL.md +367 -534
- package/skills/upstream-skill-sync/SKILL.md +46 -0
- package/skills/writing-plans/SKILL.md +1 -1
|
@@ -1,542 +1,375 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: design-taste-frontend
|
|
3
3
|
description: >-
|
|
4
|
-
tasteskill
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
4
|
+
tasteskill 2.5.1, the anti-slop frontend skill. Builds professional company websites at the level
|
|
5
|
+
of figma.com and x.ai: plain copy in a voice of its own, one system, one section per screen,
|
|
6
|
+
equal edges, real photographs and real product UI (licensed stand-in photographs when the client
|
|
7
|
+
has none; a product render only when the brief asks for 3D), a hero entrance and one or two dealt
|
|
8
|
+
moments on every page, shader effects and scenes only on tech, gaming and software pages, quiet
|
|
9
|
+
micro-interactions, and a checker and finish gate that enforce it in a real browser. Use this
|
|
10
|
+
whenever you build, design, redesign, restyle, polish or review a landing page, company,
|
|
11
|
+
product, shop, cafe, hotel, studio, SaaS, AI, developer-tool or game site, as static HTML/CSS or
|
|
12
|
+
inside an existing React, Next.js, Vue, Svelte, Astro or Tailwind project, or when the user says
|
|
13
|
+
a page looks generic, templated or "AI-made".
|
|
14
14
|
---
|
|
15
15
|
|
|
16
|
-
# tasteskill
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
1. **A script deals the directions, you choose among them.** Asked to invent a look, a model picks
|
|
25
|
-
the category default every time. `scripts/draw.mjs` deals three of twenty researched directions;
|
|
26
|
-
you choose the one that carries the subject's idea, and the script then deals its type system,
|
|
27
|
-
palette, hero and section compositions from a library distilled from 247 real sites.
|
|
28
|
-
2. **The idea comes from the subject.** In the study, what separated the best sites from the forgettable
|
|
29
|
-
ones was a concept taken from the thing itself, not the styling.
|
|
30
|
-
3. **A house style with no ornaments,** measured in a real browser by `scripts/inspect.mjs`, so the
|
|
31
|
-
rules are checked rather than hoped for.
|
|
32
|
-
4. **You look at what you made.** Screenshots at three widths, a juror's rubric, fix, look again.
|
|
33
|
-
|
|
34
|
-
One warning learned in testing. Taking the ornaments away is only half the job; a page that has lost its
|
|
35
|
-
labels, rules and cards and gained nothing in their place reads as thin, and blind jurors rightly prefer
|
|
36
|
-
a richer page with tells over an empty page without them. The other half is substance: type set
|
|
37
|
-
larger, whole fields of colour, real pictures of this subject's world (found or drawn), and every
|
|
38
|
-
section carrying its full content. The skill is built to give you that; do not trade it for restraint.
|
|
39
|
-
|
|
40
|
-
In the commands below `<skill>` is this skill's folder. Run them from the project's root, so the
|
|
41
|
-
working files land in `.taste-skill/` there. The scripts need Node 22+ and an installed Chrome, Edge
|
|
42
|
-
or Chromium, and install nothing. `assets.mjs` also needs network access; it uses no API keys.
|
|
43
|
-
|
|
44
|
-
## Page or app screen
|
|
45
|
-
|
|
46
|
-
Decide first which of two kinds of work this is.
|
|
47
|
-
|
|
48
|
-
- **A page** is read and scrolled: a landing page, a marketing or product site, a portfolio, an
|
|
49
|
-
event, a restaurant, a one-pager. It follows **the run** below.
|
|
50
|
-
- **An app screen** is worked in: a dashboard, an admin or analytics view, settings, billing, an inbox
|
|
51
|
-
or queue to work through, a wallet, a list with filters, an editor or builder. It follows
|
|
52
|
-
**`references/app-screens.md`**: its own run, its own draw (`draw.mjs --app`), its own house rules
|
|
53
|
-
(quiet borders, small labels and repeated panels are normal there; gradients, glows, icons in tinted
|
|
54
|
-
squares, rainbow charts and invented vanity numbers are not) and `inspect.mjs --app`. Read that file
|
|
55
|
-
whole before you start; the page run below does not apply.
|
|
56
|
-
|
|
57
|
-
A product site that shows its app is a page; the interface fragments on it follow the app-screen
|
|
58
|
-
rules for their insides. Deal the product's app style once, in its own folder, with the page's colours
|
|
59
|
-
and type kept:
|
|
60
|
-
|
|
61
|
-
```bash
|
|
62
|
-
node <skill>/scripts/draw.mjs --app --kind <kind> --brief "<the product>" --keep palette,type --out .taste-skill/app
|
|
63
|
-
```
|
|
64
|
-
|
|
65
|
-
and build every fragment the page shows (the hero's live screen, a feature's crop, a chart) as a real
|
|
66
|
-
piece of that app: `assets/app.css` for its panels, tables and controls, `assets/charts.js` for its
|
|
67
|
-
charts, real data that adds up, one finding stated, cropped and scaled the way the page's blueprint
|
|
68
|
-
treats a picture. A fragment that looks like a working product is the strongest picture a software page
|
|
69
|
-
has; grey bars and lorem numbers are the weakest. When a request mixes both (a landing page and the
|
|
70
|
-
dashboard behind it), build each with its own run and one shared palette and typeface.
|
|
71
|
-
|
|
72
|
-
## The run
|
|
73
|
-
|
|
74
|
-
Do these in order. Steps 1–5 take a few minutes and decide whether the page is any good.
|
|
75
|
-
|
|
76
|
-
### 1. Read the brief and the project
|
|
77
|
-
|
|
78
|
-
Find out what is real: the subject, the audience, the one thing the page must get someone to do, the
|
|
79
|
-
stack, any existing brand (colours, fonts, logo), and above all **what imagery truly exists**: the
|
|
80
|
-
project's own photographs or product shots, a real interface that can be shown, an image generation
|
|
81
|
-
tool you can call, or nothing. Do not plan around pictures you do not have. Nothing of its own is
|
|
82
|
-
rarely nothing at all: the subject's city, street, materials and history are in open archives and
|
|
83
|
-
museums, free to use with a credit (step 6, `scripts/assets.mjs`).
|
|
84
|
-
|
|
85
|
-
If the request is vague, decide and state your reading in one line instead of asking. Ask only when a
|
|
86
|
-
missing fact blocks the work (for example, no product name).
|
|
87
|
-
|
|
88
|
-
Then **inventory the subject** in your notes: eight to twelve things that belong to this client and to
|
|
89
|
-
no competitor. Look for its name and what the name means; its address, door number, street and
|
|
90
|
-
neighbourhood, and what that place looks like (its tiles, signs, paint colours, typefaces on its shop
|
|
91
|
-
fronts, its light, its weather); the numbers in the brief (seats, rooms, minutes to the sea, the
|
|
92
|
-
price, the year); the constraint it lives with (only one batch a month, closed in winter, by
|
|
93
|
-
appointment); its materials and colours; its rituals and hours (the oven lit at five, the ferry at
|
|
94
|
-
seven); the printed things of its world (a timetable, a label, a ticket, a sign). This list is where
|
|
95
|
-
the idea comes from in step 4. In blind tests, the page that won each brief was built from an item on
|
|
96
|
-
such a list (the client's name and what it means, the street it stands in, the one constraint that
|
|
97
|
-
makes it what it is), and the pages that lost had a good composition with a category idea. The list
|
|
98
|
-
is also your picture search: each place, material and printed thing on it is a query for step 6.
|
|
99
|
-
|
|
100
|
-
### 2. Write the argument
|
|
101
|
-
|
|
102
|
-
Before any design, list the page as claims with their proof, one line per section, the way
|
|
103
|
-
`references/copy.md` §1 shows. The claims decide which sections exist and in what order. Delete any
|
|
104
|
-
section that has no claim. This is how you avoid the stock sequence of hero, logos, three features,
|
|
105
|
-
testimonial, pricing, call to action.
|
|
106
|
-
|
|
107
|
-
### 3. Draw the direction
|
|
108
|
-
|
|
109
|
-
```bash
|
|
110
|
-
node <skill>/scripts/draw.mjs --sector <sector> --brief "<one line about the subject>" \
|
|
111
|
-
--sections <roles in the order of your argument> [--tone <tone>] [--have <assets>] [--keep palette,type] \
|
|
112
|
-
--options 3
|
|
113
|
-
```
|
|
114
|
-
|
|
115
|
-
This deals three directions and prints a short summary of each. Hold each one against your inventory:
|
|
116
|
-
which way of composing can carry something only this client has? Choose that one, not the most
|
|
117
|
-
familiar, and write one line in your notes on why. In testing, a single random direction that did not
|
|
118
|
-
suit the subject was the commonest cause of a weak page. Then deal the full sheet:
|
|
119
|
-
|
|
120
|
-
```bash
|
|
121
|
-
node <skill>/scripts/draw.mjs <the same arguments, without --options> --direction <chosen id>
|
|
122
|
-
```
|
|
123
|
-
|
|
124
|
-
- `--sector`: `node <skill>/scripts/draw.mjs --list sectors`. Pick the closest.
|
|
125
|
-
- `--sections`: roles from `--list roles` (features, showcase, how-it-works, testimonial, proof, stats,
|
|
126
|
-
pricing, faq, cta, footer, intro, about, work, gallery, list, contact). The hero is implied.
|
|
127
|
-
- `--tone` (optional): quiet, bold, warm, technical, playful, luxury, editorial. Only pass it when the
|
|
128
|
-
brief clearly asks for one.
|
|
129
|
-
- `--have`: assets that really exist, comma-separated: `photography` (the project's own photographs of
|
|
130
|
-
the place, people or work), `product-photo` (photographs of the specific product, or an image tool
|
|
131
|
-
that can make them), `product-ui` (real screenshots), `illustration`, `video`. Leave it out if you
|
|
132
|
-
have none: the draw then avoids compositions that depend on them and the sheet says how to fill
|
|
133
|
-
picture slots honestly (software shows its own interface built in HTML; a product with no photographs
|
|
134
|
-
is drawn and set among real pictures of its world, never a fake product shot). Pictures you will
|
|
135
|
-
find in the open collections are not the project's own; leave them out of `--have`.
|
|
136
|
-
- `--keep palette,type`: when the brand already fixes colours or typefaces. The draw then deals only
|
|
137
|
-
the composition, and you map the brand's values onto the roles.
|
|
138
|
-
|
|
139
|
-
The command prints a **direction sheet**. It is the art direction for this build:
|
|
140
|
-
|
|
141
|
-
- **Adopt it.** Do not blend it with the layout you would have made anyway. If it feels unfamiliar,
|
|
142
|
-
good: the familiar layout is the one this skill exists to prevent.
|
|
143
|
-
- Redraw one slot (`--redraw hero | type | palette | photos | scenes | section:<role> | direction`) only for a
|
|
144
|
-
reason you can state: it contradicts a stated brand constraint, needs an asset that does not exist,
|
|
145
|
-
or is a section that cannot hold the real content (next point). Never redraw to get something more
|
|
146
|
-
comfortable. Record every redraw in your report.
|
|
147
|
-
- When a dealt section cannot hold the real content (it compares three plans and there is one price;
|
|
148
|
-
it wants five quotations and there are none), do not bend the content to fit. List the others with
|
|
149
|
-
`--alternatives <role>`, pick the one whose assumptions match the content, and take it with
|
|
150
|
-
`--redraw section:<role>=<id>`.
|
|
151
|
-
- **Check the palette against the subject.** A dealt palette is a set of proportions (one ground, one
|
|
152
|
-
ink, one accent, fields) as much as a set of colours. If its colours fight the subject's own material
|
|
153
|
-
(candy pastels for a peat whisky, neon for a mountain hut), redraw the palette once; if the subject
|
|
154
|
-
has unmistakable colours of its own (its material, the paint of its street, the landscape outside
|
|
155
|
-
its windows), keep the dealt proportions and take the colours from the subject instead, and say so
|
|
156
|
-
in the report.
|
|
157
|
-
- Reprint it any time with `node <skill>/scripts/draw.mjs --show`. In a long session, re-read it before each
|
|
158
|
-
section you build.
|
|
159
|
-
|
|
160
|
-
### 4. Find the idea
|
|
161
|
-
|
|
162
|
-
The direction is a way of composing. The idea is what makes the page belong to this subject and no
|
|
163
|
-
other. Write this sentence in your notes and do not start building until both blanks are filled from
|
|
164
|
-
the subject itself:
|
|
165
|
-
|
|
166
|
-
> On this page, **[something that belongs to the subject]** becomes **[the device the direction calls for]**.
|
|
167
|
-
|
|
168
|
-
Places to look for the first blank:
|
|
169
|
-
|
|
170
|
-
- **Its output.** What does the thing produce? Put the real output on the page as material. (A camera
|
|
171
|
-
that prints poems delivered its copy as paper slips.)
|
|
172
|
-
- **Its object or shape.** What does it physically look like, in cross-section, in silhouette?
|
|
173
|
-
Enlarge it, crop it, make it the frame or the one motif.
|
|
174
|
-
- **Its name.** Can the letters hold a photograph, stack into a wall, split to two corners?
|
|
175
|
-
- **Its place.** Is there one view that makes someone want to be there?
|
|
176
|
-
- **Its ritual.** Is there a sequence the page can perform as it scrolls?
|
|
177
|
-
- **Its artefact.** What printed thing already exists in its world: ticket, menu, label, receipt,
|
|
178
|
-
invitation, folder, manual?
|
|
179
|
-
- **Its opposite.** Which other category owns the feeling this one lacks?
|
|
180
|
-
|
|
181
|
-
Fill the first blank from your inventory (step 1), not from the category. **The competitor test:** put
|
|
182
|
-
the nearest real competitor in the sentence (the bakery two streets away, another oak furniture maker,
|
|
183
|
-
another hut on the same mountain). If the sentence still works, the idea belongs to the category: a
|
|
184
|
-
loaf of bread is every bakery; the seven doors of the street this one is named after are only this one.
|
|
185
|
-
"Clean and modern" is not an idea. The sites the study's panel scored lowest were the ones whose idea
|
|
186
|
-
was recorded as "none beyond the standard formula".
|
|
187
|
-
|
|
188
|
-
**One live thing.** Give the page one thing the visitor can do, or that is different for each visit,
|
|
189
|
-
made from the idea: pick a wood and see the chair in it; type your name and see it cut in the
|
|
190
|
-
foundry's letters; set the loan and read the real monthly figure; see whether the hut's stove is lit
|
|
191
|
-
right now and how long until the last ferry; choose a size and see it against the room. In blind tests every winning page had one and the jurors named it first. Rules: it uses the subject's real content, it works on a phone with a thumb, it has a plain
|
|
192
|
-
fallback without script, it never blocks reading, and it is one thing, not a playground. It is
|
|
193
|
-
built in step 6 as part of the page, not added as motion in step 9.
|
|
194
|
-
|
|
195
|
-
**The scenes carry the idea too.** The scroll scenes on the sheet are devices waiting for a subject.
|
|
196
|
-
Decide what each one shows from your inventory before building: the fly-through passes through this
|
|
197
|
-
studio's own title cards, the route is the road this shipment really takes, the picture that opens to
|
|
198
|
-
the whole screen is the room the guest will wake up in. A scene filled with pictures that could belong
|
|
199
|
-
to anyone is a screensaver.
|
|
200
|
-
|
|
201
|
-
### 5. Write the words
|
|
202
|
-
|
|
203
|
-
Write the whole page as a copy deck (plain text) before markup, following `references/copy.md`:
|
|
204
|
-
|
|
205
|
-
- **Every headline fits in two lines or fewer at every width.** Do the arithmetic in copy.md §2 before
|
|
206
|
-
committing to a sentence: about 32 characters is safe everywhere at a confident size. The studied
|
|
207
|
-
gallery heroes have a median of 5 words and 32 characters.
|
|
208
|
-
- One supporting sentence, directly under the headline (32–48px below it) and shown with it, never
|
|
209
|
-
docked at the foot of the first screen or held back by an animation. When the headline is a name or
|
|
210
|
-
a figure of speech, this sentence says plainly what the thing is. One primary action, named for what
|
|
211
|
-
it does, as a real button on the first screen.
|
|
212
|
-
- **The first screen answers the visitor's first question in large type.** For an event: what it is,
|
|
213
|
-
when and where (the dates belong in the headline or at the second size, never only in small text).
|
|
214
|
-
For a product: what it is and what it costs or does. For a person: who and what they do. Every
|
|
215
|
-
section the visitor came for (the line-up, the menu, the rooms, the price) has its own heading and
|
|
216
|
-
its own place in the navigation.
|
|
217
|
-
- **Write the full content.** Every section the brief asks for delivers its information completely:
|
|
218
|
-
the whole menu with prices, each room with its own details, every speaker and talk, the price with
|
|
219
|
-
what it includes, an answer for each real question. Thin sections are the commonest reason a clean
|
|
220
|
-
page loses to a busier one.
|
|
221
|
-
- Sample details are expected where the brief leaves gaps (dish names, room names and rates, project
|
|
222
|
-
titles) so the design is seen at full density; list them in the report for the client to confirm.
|
|
223
|
-
Proof is never invented: no customers, quotes, reviews, press, logos or business statistics.
|
|
224
|
-
|
|
225
|
-
### 6. Build it, still
|
|
226
|
-
|
|
227
|
-
Build the page with motion switched off in your head; a page that needs animation to look finished is
|
|
228
|
-
not finished. Order of work:
|
|
229
|
-
|
|
230
|
-
1. **Tokens.** Colour and type roles from the sheet as CSS custom properties. Everything downstream
|
|
231
|
-
references tokens only. `<skill>/assets/base.css` is a neutral foundation you may start from (reset, token
|
|
232
|
-
names, fluid type steps, grid, focus and selection styles, the motion helpers); it has no look of
|
|
233
|
-
its own.
|
|
234
|
-
2. **The hero, exactly as the blueprint describes it,** at desktop and at phone width. Get the big
|
|
235
|
-
thing big and the small things small before anything else exists.
|
|
236
|
-
3. **Each section from its blueprint,** with this project's content. Keep the geometry, change the
|
|
237
|
-
subject. Neighbouring sections must not share a layout. **Carry the idea into every section,**
|
|
238
|
-
pricing, FAQ and footer included: the commonest failure in the study, even among good sites, is a
|
|
239
|
-
distinctive first screen followed by stock blocks.
|
|
240
|
-
4. **Imagery,** in this order of preference:
|
|
241
|
-
1. the project's own;
|
|
242
|
-
2. generated, if you have an image tool;
|
|
243
|
-
3. **real pictures of the subject's world from the open collections,** whenever an honest one
|
|
244
|
-
exists. Search them with `node <skill>/scripts/assets.mjs "<query>"` (Openverse, Wikimedia
|
|
245
|
-
Commons, the Art Institute of Chicago and the Met; only licences that allow commercial use, by
|
|
246
|
-
default). Search the inventory, not the category: its street in old postcards, an old map of the
|
|
247
|
-
neighbourhood, its material up close, its trade in engravings, a museum object of its kind, a
|
|
248
|
-
botanical plate, a star chart. Use them large and with intent: one archival photograph as the
|
|
249
|
-
hero, an engraving enlarged into the page's motif, the real map of the street as the contact
|
|
250
|
-
section. Look at each before choosing; `--get <ref>` downloads it into `assets/` and records
|
|
251
|
-
its source and licence, and `--credits` prints the credit line for the footer. A found picture
|
|
252
|
-
shows the world around the client and is never presented as the client's own product, room,
|
|
253
|
-
dish, person or team;
|
|
254
|
-
4. **drawn in code from the subject itself,** for what no honest picture exists of (its objects,
|
|
255
|
-
its tiles, its windows, its product's interface, made as one consistent flat graphic language in
|
|
256
|
-
the palette's real colours);
|
|
257
|
-
5. the photographs dealt on the sheet, only where an honestly generic picture fits (the sea for a
|
|
258
|
-
sea house), never as a stand-in for the subject;
|
|
259
|
-
6. type and colour alone.
|
|
260
|
-
|
|
261
|
-
When the project has footage or a real picture of its own process or product, the first screen
|
|
262
|
-
shows it, large (about 40% of the screen or more). Never write a sentence on the page about where
|
|
263
|
-
the pictures come from or what they are not ("none of these shows our bar"): a caption says what
|
|
264
|
-
the picture is, and the credit line sits small in the footer. A portfolio whose work is invented
|
|
265
|
-
for the brief draws each piece as a finished still of that work (its title card with its own type,
|
|
266
|
-
an end frame, a poster), with real detail, never as a pictogram of the client's product.
|
|
267
|
-
|
|
268
|
-
**The floor, which the inspector checks:** at least four real pictures on the page, usually six to
|
|
269
|
-
twelve (photographs, archival images, maps, engravings, footage, raster artwork; for software, its
|
|
270
|
-
cropped interface fragments count too). SVG drawings do not count toward the floor: draw what no
|
|
271
|
-
picture exists of, and still carry real pictures. Add one moving picture wherever an honest clip
|
|
272
|
-
exists: search it with `assets.mjs --video "<query>"` and use it as a muted loop with a poster
|
|
273
|
-
frame. Models skip pictures and footage because finding them is work; the page fails without them.
|
|
274
|
-
|
|
275
|
-
`references/imagery.md` covers searching, licences and credits, video, drawing, crops and treatments.
|
|
276
|
-
5. **The live thing** from step 4, built into the section where it proves the claim (often the hero
|
|
277
|
-
or the booking), with real content, a thumb-sized phone version and a plain fallback.
|
|
278
|
-
6. **The scroll scenes,** when the sheet deals them (section 9), each with the section it carries: the page's big
|
|
279
|
-
moments, the camera that flies through the work, the picture that opens to the whole screen, the
|
|
280
|
-
word that buckles under the scroll. Copy the shared stage and the scene's files from
|
|
281
|
-
`<skill>/assets/scenes/`, fill the scene with this project's own pictures and words, and set the
|
|
282
|
-
page's tokens so it takes the page's look. A scene is composition: it decides how long the page is
|
|
283
|
-
and what each screen shows, so it is built now and seen in every look round, not added at the end.
|
|
284
|
-
`references/scenes.md` says how to put one on a page, fill it, fit it and check it;
|
|
285
|
-
`assets/scenes/demo/<id>.html` is a working example of each.
|
|
286
|
-
7. **Fullness.** Look at each desktop screen as a poster: one dominant thing and the content it
|
|
287
|
-
carries. A screen that is mostly empty ground is an underbuilt section, not a rest; one deliberate
|
|
288
|
-
rest per page is the limit, and the inspector fails a page with two or more near-empty screens.
|
|
289
|
-
Running text is in the full ink at 16px or more; grey is for secondary notes.
|
|
290
|
-
8. **The frame.** The page has one pair of equal outer margins at every width, and every section uses
|
|
291
|
-
the width the page has set up: when its text sits in the left half, the right half holds its
|
|
292
|
-
picture, its second column, its list or its figure, never nothing. Asymmetry lives inside the grid,
|
|
293
|
-
never in the frame: a void is placed only when something closes it on the far side. No stretch of
|
|
294
|
-
the page taller than about half a screen holds nothing at all; sections are 120–240px apart on
|
|
295
|
-
desktop. Every section the visitor came for opens with a heading that names it, and the first
|
|
296
|
-
screen carries the page's title in an `h1`. These are what readers name first when a page looks
|
|
297
|
-
wrong ("no clear title", "random empty space", "everything is pushed to one side"), and the
|
|
298
|
-
inspector measures each of them.
|
|
299
|
-
9. **States and semantics.** Real links and buttons, visible focus, alt text, a phone layout that is
|
|
300
|
-
its own composition. Every control, the live thing included, works from the keyboard alone in
|
|
301
|
-
reading order and has an accessible name: its visible label, or `aria-label` when it shows only an
|
|
302
|
-
icon.
|
|
303
|
-
|
|
304
|
-
Read `references/type.md`, `references/colour.md` and `references/layout.md` when you need the detail
|
|
305
|
-
behind a decision; the laws below are the short form.
|
|
306
|
-
|
|
307
|
-
### 7. Gate
|
|
308
|
-
|
|
309
|
-
```bash
|
|
310
|
-
node <skill>/scripts/lint.mjs <source files or folder>
|
|
311
|
-
node <skill>/scripts/inspect.mjs <url or path/to/index.html>
|
|
312
|
-
node <skill>/scripts/scenes.mjs <url or path/to/index.html> # when the page has scroll scenes
|
|
313
|
-
```
|
|
314
|
-
|
|
315
|
-
`scenes.mjs` photographs every scroll scene at 0, 10 … 100% of its hold, on desktop and on a phone,
|
|
316
|
-
and the reduced-motion page; with scenes on the sheet, `inspect.mjs` also films the whole scroll
|
|
317
|
-
(`desktop-film-NN.jpg`). A scene that never started or rests on desktop is a `FAIL`.
|
|
318
|
-
|
|
319
|
-
`lint.mjs` scans source for banned patterns and stock phrases. `inspect.mjs` opens the page in a real
|
|
320
|
-
browser at 1440, 768 and 390 pixels, measures it (headline line counts, type sizes, fonts actually
|
|
321
|
-
loaded, colours, rules, shadows, gradients, contrast, overflow, and the frame: equal margins, sections
|
|
322
|
-
huddled on one side, blank stretches, the title, untitled sections, text against the screen edge) and
|
|
323
|
-
saves screenshots to `.taste-skill/inspect/`. Fix every `FAIL`. Treat each `WARN` as wrong unless you can defend it to a
|
|
324
|
-
designer in one sentence. Re-run until there are no `FAIL`s. Do not argue with the meter and do not
|
|
325
|
-
hide things from it. The inspector serves local files over a throwaway local server; if the page must
|
|
326
|
-
also open straight from the file system, open `index.html` that way once before you finish.
|
|
327
|
-
|
|
328
|
-
Inspect what the visitor receives. With a build step, run the last gate on the production build
|
|
329
|
-
(`vite build && vite preview`, `next build && next start`, or the built `index.html`), not only on the
|
|
330
|
-
dev server: minifiers and bundlers change what ships (one dropped a `backdrop-filter` that the dev
|
|
331
|
-
server showed). The inspector warns when it is looking at a dev server.
|
|
332
|
-
|
|
333
|
-
### 8. Look
|
|
334
|
-
|
|
335
|
-
Passing the gate means nothing banned was measured. It does not mean the page is good. Open the
|
|
336
|
-
screenshots the inspector lists (every viewport, with your image viewer or Read tool) and critique them
|
|
337
|
-
with `references/critique.md`: the fourteen passes, the Awwwards-weighted score, the caps. Write the critique
|
|
338
|
-
down in its format, fix the top three problems, run the inspector again, look again. Three rounds at
|
|
339
|
-
most.
|
|
340
|
-
|
|
341
|
-
Judge only the pictures. If a problem is visible in a screenshot, it is real, whatever the code says.
|
|
342
|
-
|
|
343
|
-
### 9. Move
|
|
344
|
-
|
|
345
|
-
Now build the motion layer. It is required, and it is more than one fade: the inspector counts the
|
|
346
|
-
elements that really move while the page loads and is scrolled, and fails a page under eight (it warns
|
|
347
|
-
under sixteen). Any scroll scenes are already built (step 6); around them the layer has four parts:
|
|
348
|
-
|
|
349
|
-
1. **The signature move** named on the sheet: one, done well (a dealt scene can be it).
|
|
350
|
-
2. **An entrance for the parts of every section:** the heading, then the text, then the picture,
|
|
351
|
-
staggered by 60–90ms, rising 16–32px with opacity, triggered once as the section enters. Not one
|
|
352
|
-
fade for the whole block, and never content that stays hidden if the script fails.
|
|
353
|
-
3. **Feedback on every control:** press, hover and focus on buttons, links, cards and the live thing.
|
|
354
|
-
4. **One moving picture:** a found clip as a muted loop, a slow scale or drift on a photograph, or a
|
|
355
|
-
scroll-linked move on the hero picture.
|
|
356
|
-
|
|
357
|
-
Transform and opacity only; every move has a `prefers-reduced-motion` fallback that keeps the content
|
|
358
|
-
and drops the travel. A move that changes the colour or the layout of whole screens (colour by
|
|
359
|
-
chapter, a pinned story) is part of the composition, so build it in step 6 and let every look round see
|
|
360
|
-
it. `references/motion.md` has the tokens and tested recipes. Then run the inspector once more and check
|
|
361
|
-
every screenshot for content that failed to appear.
|
|
362
|
-
|
|
363
|
-
### 10. Report
|
|
364
|
-
|
|
365
|
-
Do not report until all of these are true; each one was skipped in a test run that came out badly:
|
|
366
|
-
|
|
367
|
-
- `inspect.mjs` shows **0 FAIL** at 1440, 768 and 390, on the final version of the page.
|
|
368
|
-
- You opened every screenshot it listed after the last change, not only the first screen.
|
|
369
|
-
- With scroll scenes: `scenes.mjs` ran on the final page with no problems, and you read every sheet
|
|
370
|
-
(desktop, phone, reduced motion).
|
|
371
|
-
- A stranger reading the first screen for five seconds can say what this is and what to do.
|
|
372
|
-
- Every section has a heading; the margins match on both sides; no stretch of the page is empty.
|
|
373
|
-
- The critique of your last round is written down in the shape of `references/critique.md` §4.
|
|
374
|
-
|
|
375
|
-
Tell the user, briefly: the direction dealt (name and seed) and any redraws with reasons; the idea
|
|
376
|
-
sentence and the live thing; the final scores from your last critique round and what still falls short;
|
|
377
|
-
every found picture and clip with its title, creator, licence and source page (`assets.mjs --credits` prints
|
|
378
|
-
the list) and where its credit sits on the page; which bundled photographs and which drawings stand in
|
|
379
|
-
for photography (so they can be replaced); and any sample content that must be swapped before launch.
|
|
380
|
-
Do not claim a check you did not run.
|
|
16
|
+
# tasteskill 2.5
|
|
17
|
+
|
|
18
|
+
Build the website a good company would ship: it says plainly what is sold, shows the real thing on
|
|
19
|
+
every screen, and looks made for this client, not from a template and not like an art piece.
|
|
20
|
+
figma.com and x.ai are the bar (in words: `layout-v4.md` section 1).
|
|
21
|
+
|
|
22
|
+
`<skill>` is this folder. It needs Node 22+ and Chrome, Edge or Chromium (ffmpeg optional).
|
|
381
23
|
|
|
382
24
|
## House rules
|
|
383
25
|
|
|
384
|
-
These
|
|
385
|
-
|
|
386
|
-
|
|
387
|
-
|
|
388
|
-
|
|
389
|
-
|
|
390
|
-
|
|
391
|
-
|
|
392
|
-
|
|
393
|
-
|
|
394
|
-
|
|
395
|
-
|
|
396
|
-
|
|
397
|
-
|
|
398
|
-
|
|
399
|
-
|
|
400
|
-
|
|
401
|
-
|
|
402
|
-
|
|
403
|
-
|
|
404
|
-
|
|
405
|
-
|
|
406
|
-
|
|
407
|
-
|
|
408
|
-
|
|
409
|
-
|
|
410
|
-
|
|
411
|
-
|
|
412
|
-
|
|
413
|
-
|
|
414
|
-
|
|
415
|
-
|
|
416
|
-
|
|
417
|
-
|
|
418
|
-
|
|
419
|
-
|
|
420
|
-
|
|
421
|
-
|
|
422
|
-
|
|
423
|
-
|
|
424
|
-
|
|
425
|
-
|
|
426
|
-
|
|
427
|
-
|
|
428
|
-
**
|
|
429
|
-
|
|
430
|
-
|
|
431
|
-
|
|
432
|
-
|
|
433
|
-
|
|
434
|
-
|
|
435
|
-
|
|
436
|
-
|
|
437
|
-
|
|
438
|
-
|
|
439
|
-
-
|
|
440
|
-
|
|
441
|
-
|
|
442
|
-
|
|
443
|
-
|
|
444
|
-
|
|
445
|
-
|
|
446
|
-
|
|
447
|
-
|
|
448
|
-
-
|
|
449
|
-
|
|
450
|
-
|
|
451
|
-
|
|
452
|
-
|
|
453
|
-
|
|
454
|
-
the
|
|
455
|
-
|
|
456
|
-
|
|
457
|
-
|
|
458
|
-
|
|
459
|
-
|
|
460
|
-
|
|
461
|
-
|
|
462
|
-
-
|
|
463
|
-
|
|
464
|
-
|
|
465
|
-
|
|
466
|
-
|
|
467
|
-
|
|
468
|
-
|
|
469
|
-
|
|
470
|
-
|
|
471
|
-
|
|
472
|
-
|
|
473
|
-
|
|
474
|
-
|
|
475
|
-
|
|
476
|
-
|
|
477
|
-
|
|
478
|
-
|
|
479
|
-
|
|
480
|
-
|
|
481
|
-
|
|
482
|
-
|
|
483
|
-
|
|
484
|
-
|
|
485
|
-
|
|
486
|
-
|
|
487
|
-
|
|
488
|
-
|
|
489
|
-
|
|
490
|
-
|
|
491
|
-
|
|
492
|
-
|
|
493
|
-
|
|
494
|
-
|
|
495
|
-
|
|
496
|
-
|
|
497
|
-
|
|
498
|
-
|
|
499
|
-
|
|
500
|
-
|
|
501
|
-
|
|
502
|
-
|
|
503
|
-
|
|
504
|
-
|
|
505
|
-
|
|
506
|
-
|
|
507
|
-
|
|
508
|
-
|
|
509
|
-
|
|
510
|
-
|
|
511
|
-
|
|
512
|
-
|
|
513
|
-
|
|
514
|
-
|
|
515
|
-
|
|
516
|
-
|
|
517
|
-
|
|
518
|
-
|
|
519
|
-
|
|
520
|
-
|
|
521
|
-
|
|
522
|
-
|
|
523
|
-
|
|
524
|
-
|
|
525
|
-
|
|
526
|
-
|
|
527
|
-
|
|
528
|
-
|
|
529
|
-
|
|
530
|
-
|
|
531
|
-
|
|
532
|
-
|
|
533
|
-
|
|
534
|
-
|
|
535
|
-
|
|
536
|
-
|
|
537
|
-
|
|
538
|
-
|
|
539
|
-
|
|
540
|
-
|
|
541
|
-
|
|
542
|
-
|
|
26
|
+
These nine win over everything else in this skill.
|
|
27
|
+
|
|
28
|
+
1. **No caption or description under any image, render or visual.** Licence credits go in one
|
|
29
|
+
footer line.
|
|
30
|
+
2. **Every visual renders, never an empty ground,** at 1440, 1024, 768 and 390.
|
|
31
|
+
3. **One section per screen:** the hero alone on the first screen, every section exactly one or
|
|
32
|
+
two screens tall at 1440x900, no second section heading peeking in. The one exception is a
|
|
33
|
+
live `photo-chapters` section, three or four screens, set by the moment.
|
|
34
|
+
4. **Equal left and right content edges.**
|
|
35
|
+
5. **Hover micro-animations:** a linked card lifts 2px, a photo zooms 1.02-1.03 inside its frame,
|
|
36
|
+
buttons step on hover and press on click, underlines draw, card loops cycle in 2.5-4 s, repeat
|
|
37
|
+
and restart on hover. The motion layer does it; never strip or override it. No tilt, carousels
|
|
38
|
+
or timed tabs. Every hero enters once on load (`data-enter`), and every page carries one dealt
|
|
39
|
+
moment, two on a long page (the gate holds both).
|
|
40
|
+
6. **More and better real photographs where they fit;** nicer backgrounds; better heroes, layouts
|
|
41
|
+
and fonts.
|
|
42
|
+
7. **Real full-colour icons** (a known product's real icon, never a drawn one); small diagram
|
|
43
|
+
visuals in cards (a hub with branches; one input, a main processor, three parallel lanes;
|
|
44
|
+
pulses running along the lines).
|
|
45
|
+
8. **The big award-site scenes and creative moments are part of the skill:** every page deals its
|
|
46
|
+
moments (photo- and type-led off tech), but shader effects and scenes only where the trade has a
|
|
47
|
+
technical subject (tech, AI, developer tools, gaming, fintech, hardware), never on a local cafe,
|
|
48
|
+
bakery, guesthouse or shop: those get photographs.
|
|
49
|
+
9. **Addresses:** street and district only (no street given: the district), no house number, postcode or coordinates; no register
|
|
50
|
+
or VAT numbers; no phone in a real format; contacts on `.example`.
|
|
51
|
+
|
|
52
|
+
## 1. The kind of business decides everything
|
|
53
|
+
|
|
54
|
+
Write the kind on the plan's first line and declare it on the page: the page type on
|
|
55
|
+
`<html data-type>` and `<meta name="page-type">` (the same value), and `<meta name="site-kind">`;
|
|
56
|
+
a place adds `<meta name="page-kind" content="place">`. The dealers take the last column
|
|
57
|
+
(`start.mjs --page`, `moments.mjs --page`), the hero dealer the page type; `consistency.mjs` reads
|
|
58
|
+
the metas.
|
|
59
|
+
|
|
60
|
+
| Brief | page type | site-kind | kind |
|
|
61
|
+
|---|---|---|---|
|
|
62
|
+
| App, SaaS, AI, developer tool, fintech or banking app, a studio selling its own software | software | software | software |
|
|
63
|
+
| A game, a studio launching its game | software | gaming | gaming |
|
|
64
|
+
| Hardware or a tech device (a drone, a robot arm, a keyboard) | product | tech | tech |
|
|
65
|
+
| Any other physical product or brand (a chair, a bike, coffee beans sold online) | product | other | product |
|
|
66
|
+
| People are hired: clinic, law firm, agency, creative studio, trade | service | other | service |
|
|
67
|
+
| People come to it: cafe, bar, bakery, restaurant, guesthouse, small hotel, shop, florist, bike shop, gym, local studio | place | other | place |
|
|
68
|
+
|
|
69
|
+
A maker that also opens its door or teaches (a ceramics studio, a bakery with a web shop) is a
|
|
70
|
+
**place**; its web shop becomes the goods section. It is a product only when nothing happens at the door.
|
|
71
|
+
|
|
72
|
+
"Tech" below means site-kind software, gaming or tech; "other" is everything else. Effects,
|
|
73
|
+
scenes, loops, counts, CSS grounds, dark pages and dark heroes are tech only. An other page is
|
|
74
|
+
photographs, flat colour, type, real icons, the hero's entrance, its dealt moment (photo- or
|
|
75
|
+
type-led, `moments.md`) and the hover layer.
|
|
76
|
+
|
|
77
|
+
## 2. The page plan by kind
|
|
78
|
+
|
|
79
|
+
The full plans, deal lists and section order: `references/sections.md`.
|
|
80
|
+
|
|
81
|
+
- **Place** (a cafe, bakery, guesthouse, shop). Photographs lead: 12 to 20 on the full page, 8 to
|
|
82
|
+
12 compact, under 8 frames the 3-screen short page, whatever the trade; no client photographs:
|
|
83
|
+
the draft path and a live search (`photos.md`), then count; the palette dealt by trade. The hero
|
|
84
|
+
a photograph whenever a frame fits (a remote place: its region's landscape), the visit block on
|
|
85
|
+
screen two, the offer, the place, orders or booking.
|
|
86
|
+
**Variety without effects** (`sections.md` section 4): the offer and the place deal different
|
|
87
|
+
compositions, never two sections round one picture; one type moment (the address or name set large); one main action a screen; list text 16px. Flat grounds, square
|
|
88
|
+
photographs, one button style, the phone bar, the dealt moments; no effect, ground, loop,
|
|
89
|
+
fragment, diagram or tab.
|
|
90
|
+
- **Product and service** (site-kind other). Photographs lead: the product, the people, the rooms,
|
|
91
|
+
the work, two or more a screen on a product page. Real icons for the tools a studio uses; one
|
|
92
|
+
still diagram at most; flat grounds and one brand band. No shader effect, print, grain, gradient,
|
|
93
|
+
scene or loop (the dealt moments only); WebGL only for a product render the brief asks for. **A
|
|
94
|
+
physical product with no photographs is shown in photographs:** stand-ins of the same kind of
|
|
95
|
+
thing from `photos.mjs search`, each listed in the report, on the full product page; a render
|
|
96
|
+
(`assets/objects/product-render`, stills) only when the brief asks for 3D or a render; never a
|
|
97
|
+
drawing, mood stock or a set of props (`sections.md`, Product).
|
|
98
|
+
- **Every product page** (photographed, in stand-ins or rendered on a 3D ask, hardware too; the bar is Figure and 1X;
|
|
99
|
+
`sections.md`, Product): the product **big** where it stands
|
|
100
|
+
whole (most of its frame, or on the ground at anchor scale), never mid-size in a grey rounded
|
|
101
|
+
panel on a grey ground; **a different picture each section**, never one view twice; **every headline promise pictured** (a family bike shows the child bench); dealt
|
|
102
|
+
compositions, no structure twice, one contrasting ground; the **swatch changes the picture**,
|
|
103
|
+
every colour shown once; **no fact twice**; buttons step and press (rule 5).
|
|
104
|
+
- **Tech** (software, gaming, hardware). The client's own subject leads at true size. Software: its
|
|
105
|
+
own UI as live HTML showing what it works on (a code-review tool: a red and green diff with its
|
|
106
|
+
Accept action) in one `app-frame`, never a generic dashboard or only fragments on panels; cards:
|
|
107
|
+
fragments on lit panels, pulsing diagrams, real icons. Hardware: its photographs, else stand-in
|
|
108
|
+
photographs of its kind (a render only when the brief asks for 3D), never a split hero of only
|
|
109
|
+
an order form or a drawn SVG. A game: its name in the h1, a launch line, its world as full-bleed
|
|
110
|
+
key art (else its name set large over stand-in photographs of its setting), an effect never in
|
|
111
|
+
its place (`sections.md`, Gaming). **60 to 80 words a screen** outside UI mocks (`copy.md`). By
|
|
112
|
+
deal: **one effect** (a shader ground in the hero or the one `[data-visual]` frame, a WebGL
|
|
113
|
+
part, an object or one big scene) and **one or two moments** in their own sections; four live
|
|
114
|
+
WebGL contexts at most; no card moves with the scroll (`effects-usage.md`).
|
|
115
|
+
- **One object never carries the page.** The product or hero object whole leads the hero and **two more sections at
|
|
116
|
+
most**; another kind of visual the brief supports carries the rest (`sections.md` section 1,
|
|
117
|
+
its table): a game's world and crew; hardware's use at the bench, its parts close up; a still
|
|
118
|
+
diagram card, a type moment, a context photograph where the trade allows.
|
|
119
|
+
- **The client's own assets get slots.** A trailer, key art, screenshots, CAD renders or a motion
|
|
120
|
+
video the brief names each get a frame that reads finished now (a real `<video>` with a stand-in
|
|
121
|
+
poster, a play control only when there is a page or file to play, three to five stand-in
|
|
122
|
+
photographs of the world, a CAD frame), named in a comment for the client's file, never empty
|
|
123
|
+
(`sections-library.md`, client-slots).
|
|
124
|
+
|
|
125
|
+
## 3. What serves which page
|
|
126
|
+
|
|
127
|
+
Open the reference of every asset family the page uses first. A dash means never.
|
|
128
|
+
|
|
129
|
+
| Need | Asset | Software, gaming | Hardware | Product, service | Place | Reference |
|
|
130
|
+
|---|---|---|---|---|---|---|
|
|
131
|
+
| Heights, edges, heroes, type | `system.css`, `assets/layout` | dealt hero | dealt hero | dealt hero | place hero | `layout-v4.md` |
|
|
132
|
+
| Sections and recipes | `starter.html` | its plan | product plan | its plan | place plan | `sections.md`, `sections-library.md` |
|
|
133
|
+
| Tokens, grid, buttons, nav, footer, colour | `system.css`, `system.js` | yes | yes | yes | place tokens | `system.md` |
|
|
134
|
+
| Forms, keyboard, head and share tags | `starter.html`, `system.css`, `system.js` | yes | yes | yes | yes | `system.md` |
|
|
135
|
+
| Copy, contacts, credits | `scripts/copy-lint.mjs` | yes | yes | yes | yes | `copy.md`, `copy-voice.md` |
|
|
136
|
+
| Hero entrance, hover, press, focus, nav, tabs | `assets/motion` | yes | yes | yes | yes | `motion.md` |
|
|
137
|
+
| Card loops, a count | `assets/motion`, `assets/ui` | yes | yes | - | - | `motion.md`, `cards.md` |
|
|
138
|
+
| Photographs | `scripts/photos.mjs` | people, customers; a game's art, else stand-ins of its setting | lead | lead | lead, 12-20 | `photos.md` |
|
|
139
|
+
| Real tool, app and file icons | `scripts/icons.mjs` | yes | yes | tools really used | - | `icons.md` |
|
|
140
|
+
| Feature cards, UI fragments | `assets/ui` | lead (gaming: none) | its app | an app the client runs | - | `cards.md` |
|
|
141
|
+
| Diagram cards (hub, lanes, pulses) | `assets/diagrams` | 0-2, pulsing | 0-2, pulsing | 0-1, still | - | `diagrams.md` |
|
|
142
|
+
| CSS grounds | `assets/backgrounds` | 0-2 dealt | 0-2 dealt | flat tokens | flat tokens | `backgrounds.md` |
|
|
143
|
+
| Shader grounds | `assets/effects` | the one effect | the one effect | - | - | `effects-usage.md` |
|
|
144
|
+
| Creative parts (`fx-*`) | `assets/components` | yes | yes | `fx-photo` plain, `fx-map` still | `fx-map` still | `effects-creative.md` |
|
|
145
|
+
| Objects and prints | `assets/objects` | one, as the effect; a render when the brief asks for 3D | its render when the brief asks for 3D | its render when the brief asks for 3D | - | `effects-objects.md` |
|
|
146
|
+
| Award-site moments | `assets/moments` | 1-2 | 1-2 | 1-2 (photo, type) | 1-2 (photo, type) | `moments.md` |
|
|
147
|
+
| Big scenes | `assets/scenes` | 0-1 | 0-1 | - | - | `scenes.md` |
|
|
148
|
+
| Speed and weight | `scripts/perf.mjs` | yes | yes | yes | yes | `perf.md` |
|
|
149
|
+
|
|
150
|
+
Read `copy.md`, `copy-voice.md`, `system.md`, `layout-v4.md` and `sections.md` in full before the first page.
|
|
151
|
+
|
|
152
|
+
## 4. The run
|
|
153
|
+
|
|
154
|
+
0. **The stack.** An empty folder builds a static page: copy `<skill>/assets` into `assets` and
|
|
155
|
+
start from `assets/starter.html`. An existing project builds in its own stack, its components
|
|
156
|
+
taking the starter's markup and classes, with the kit copied into its public folder
|
|
157
|
+
(`public/assets`) and loaded from there as plain files. A brief that asks for Next.js builds a
|
|
158
|
+
static export (`output: 'export'`), checked on its built page (`--root out`).
|
|
159
|
+
|
|
160
|
+
1. **Read the brief.** Write down the kind (section 1), what is sold, who buys it, the one main
|
|
161
|
+
action (the transaction: Book a room, Order a cake, Start a free trial; a place with neither:
|
|
162
|
+
Get directions) and the real material: logo, screens, photographs, prices, address, hours.
|
|
163
|
+
Then arm the finish gate, before any page exists:
|
|
164
|
+
|
|
165
|
+
```bash
|
|
166
|
+
node <skill>/scripts/gate.mjs --start index.html --kind <kind> --category "<what is sold>" --primary "<main action>"
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
A framework build names its dev server's URL (`--start http://localhost:5173/`) or its built page
|
|
170
|
+
(`--start dist/index.html --root dist`; a Next.js export: `out`) in place of `index.html`, and
|
|
171
|
+
rebuilds before every gate run.
|
|
172
|
+
|
|
173
|
+
2. **Write all the copy first,** with the copy layer (`copy-voice.md`: the fact sheet, the voice
|
|
174
|
+
card on the plan, the page's shape, the device budget; a register from `copy-registers.md`, the
|
|
175
|
+
moves of `copy-moves.md`) within the rules of `copy.md`: the h1 names the category and the buyer or the place (a game: its name and genre),
|
|
176
|
+
one hard fact on the first screen, a noun in every heading, buttons as a verb and an object.
|
|
177
|
+
Nothing is invented but a coined brand name (searched first, the result kept in `names.json`
|
|
178
|
+
beside the page) and, on a place, plausible hours and prices, each marked `data-assumed`
|
|
179
|
+
(`copy.md`, What may be assumed). A draft kept in a `.md` file lints the same way as the page
|
|
180
|
+
(the voice card and part labels are skipped).
|
|
181
|
+
|
|
182
|
+
3. **Plan the page as screens.** Line 1: the kind. Line 2: the deal (step 4), with one sentence on
|
|
183
|
+
why the palette fits the trade. Then one line per
|
|
184
|
+
section: its id, its one idea, its picture and its kind (object, use, parts, world, slot, diagram, type; three object lines at most), its
|
|
185
|
+
screens (1 or 2, from its content height, `layout-v4.md` section 2), which section holds a
|
|
186
|
+
moment and why it moves (on tech also the effect or the scene). Pick the photographs now (`photos.md`); their count,
|
|
187
|
+
stand-ins included, sets a place's length (section 2). Then read `cards.md` and the recipe of
|
|
188
|
+
every id you use in `sections-library.md`.
|
|
189
|
+
|
|
190
|
+
4. **Deal, never choose by taste.** Each command keeps a history, so pages differ:
|
|
191
|
+
|
|
192
|
+
```bash
|
|
193
|
+
node <skill>/assets/layout/deal.mjs --type <page type> --has <photo,ui,film,object,setting> --history .taste-skill/layout-history.json # the hero; a game adds --kind gaming, hardware --kind tech
|
|
194
|
+
node <skill>/scripts/start.mjs deal --page <kind> --trade <trade> --history .taste-skill/history.json # three palettes made for the trade, three pairings: take the first; add --axis after a word or editorial hero
|
|
195
|
+
node <skill>/scripts/start.mjs css --page <kind> --palette <id> --type <id> --radius soft --history .taste-skill/history.json
|
|
196
|
+
node <skill>/scripts/start.mjs brand --page place --bg "#.." --ink "#.." --accent "#.." [--surface "#.."] [--muted "#.."] --type <id> --radius soft # the client's own colours (a logo, a painted shopfront), in place of css
|
|
197
|
+
node <skill>/scripts/moments.mjs pick --page <kind> --count 1|2 --fits section,statement --photo --history .taste-skill/history.json # every kind
|
|
198
|
+
node -e "for(const l of process.argv.slice(1)){const o=l.split('|');console.log(o[Math.floor(Math.random()*o.length)])}" <the kind's lists, below>
|
|
199
|
+
```
|
|
200
|
+
|
|
201
|
+
Run every command from the project folder (the deal arms the gate in the folder it runs in, or
|
|
202
|
+
joins the build already open one or two folders up). The
|
|
203
|
+
lists, in order nav, footer, close, rhythm, buttons, mark (`sections.md` sections 2 and 3):
|
|
204
|
+
- software: `"nav-mega|nav-cards|nav-centre" "footer-dark|footer-statement|footer-columns" "close-type|close-word" "dark-band|surface-pairs|space" "solid|pill|tonal|arrow" "wordmark|initial|arc|ring|stack|dots"`
|
|
205
|
+
- gaming: `"nav-mega|nav-centre|nav-cards" "footer-dark|footer-statement" "close-word|close-type" "dark-band|media-band|space" "solid|pill|block" "wordmark|initial|arc|ring|stack|dots"`
|
|
206
|
+
- product and hardware: `"nav-cards|nav-split|nav-mega" "footer-columns|footer-dark" "close-photo|close-type|close-word" "dark-band|brand-band" "arrow|solid|block|pill" "wordmark|initial|arc|ring|stack|dots"`
|
|
207
|
+
- service: `"nav-mega|nav-split|nav-centre" "footer-visit|footer-dark|footer-columns" "close-type|close-photo" "surface-pairs|dark-band|space" "solid|tonal|block|arrow" "wordmark|initial|arc|ring|stack|dots"`
|
|
208
|
+
- place: the whole line in `sections.md` section 4, Place (The deal), read in its order.
|
|
209
|
+
|
|
210
|
+
A product or hardware with no photographs deals with `--has photo` for its stand-ins;
|
|
211
|
+
`--has object` only for a cut-out or a render the brief asks for (always the `product` hero, its
|
|
212
|
+
widest view across the wrap, no box); a game without art files passes `--has setting` (the
|
|
213
|
+
`photo` hero, its name over a stand-in of its setting; a game always passes `--has`). A product
|
|
214
|
+
page is dealt only the product, photo and film heroes. A place's hero is printed, never dealt (`--type
|
|
215
|
+
place`). A dealt part that needs a photograph the page lacks is dealt again (`sections.md` section 2). Take the
|
|
216
|
+
first palette and the first pairing printed (the next only when the first clashes with the
|
|
217
|
+
client's own logo or photographs, or the pairing fails `hero-lines`, said on plan line 2); the client's own colours go through
|
|
218
|
+
`start.mjs brand` instead (`sections.md` section 4, Look); never violet: deal again. Keep the `:root` block as printed. Radius: `sharp` for fintech and developer tools, `soft` by default,
|
|
219
|
+
`round` for consumer apps, square on a place. On tech only: the lit ground (`<html data-ground>`:
|
|
220
|
+
`sand|sky|sage` through the one-liner), the CSS grounds (`backgrounds.md`) and the one effect
|
|
221
|
+
(`effects-usage.md`). Write every result on plan line 2 and in
|
|
222
|
+
the comment at the top of `<body>`, and build exactly that (a short page drops what it has no section for: `sections.md` section 4).
|
|
223
|
+
|
|
224
|
+
5. **Build.** In `starter.html`: set `<html lang data-type data-radius data-buttons data-motion>`
|
|
225
|
+
(lang: the brief's language), the three metas, the head block (title, description, og, icon,
|
|
226
|
+
theme-color: `system.md`, Head) and the nav class; keep the skip link and the `m-enter` head
|
|
227
|
+
line; copy only the `<section class="hero …" data-enter>` of
|
|
228
|
+
`assets/layout/hero-<id>.html` (never its nav, other sections, footer or credit line; every word
|
|
229
|
+
and picture becomes the client's); move the dealt close and footer out of their `<template>`s
|
|
230
|
+
and delete the rest. Every section is `main > section` with
|
|
231
|
+
one `.wrap`, its h2 first, `--h: 1` or `2`. Build each to its recipe with the system's classes
|
|
232
|
+
and tokens; write page CSS only where a reference says page CSS (inside a visual, `--p-h`,
|
|
233
|
+
`.wall`, `.rail`, `.device`). Paste UI from `assets/ui/<name>/fragment.html` and rewrite every
|
|
234
|
+
name, number and logo to the client's (kit icons become `data-icon`, `cards.md`); a diagram card is `data-diagram="<preset>"`
|
|
235
|
+
with the client's labels; run `icons.mjs scan index.html --out assets/icons --colour` last, so every icon
|
|
236
|
+
the page names is a local file. Mount an effect, object, moment or scene exactly as its
|
|
237
|
+
reference says, never from your own script. A moment's section is copied from
|
|
238
|
+
`assets/moments/_demo/in-page.html` (place: photo-chapters, word-highlight) or
|
|
239
|
+
`in-page-service.html` (pinned-chapters, picture-develops film); a moment's own `demo.html` shows
|
|
240
|
+
it alone and is not a page model. A form is the starter's `booking-form` (`system.md`,
|
|
241
|
+
Forms). Credits: the one footer line from `photos.mjs credits`, once the markup uses the
|
|
242
|
+
photographs (it reads the page). Copy the hero's tile from `shoot.mjs` beside the page as `share.jpg`.
|
|
243
|
+
|
|
244
|
+
6. **Check and look.** Only the skill's scripts, each running one headless Chrome with WebGL on the
|
|
245
|
+
CPU, closed by its own PID, one at a time in the foreground with a 10-minute timeout; never in
|
|
246
|
+
the background, a windowed browser or a browser tool.
|
|
247
|
+
Each serves the page file itself over http on 127.0.0.1 (never `file://`), so no server is needed;
|
|
248
|
+
for a built page whose links start at the site root (`/_astro/page.css`), pass `--root` with the build folder (`dist`).
|
|
249
|
+
`--profile <dir>` is the Chrome profile: a folder of its own in the OS temp folder or in the
|
|
250
|
+
project's `.taste-skill` folder (`.taste-skill/chrome-check`), never outside the project (no
|
|
251
|
+
`../`); a relative one that leads out of it is replaced by `.taste-skill/chrome-<script>`. Then:
|
|
252
|
+
|
|
253
|
+
```bash
|
|
254
|
+
node <skill>/scripts/copy-lint.mjs index.html --kind <kind>
|
|
255
|
+
node <skill>/scripts/consistency.mjs index.html --widths 1440,1024,820,768,390 --rhythm-widths 1440,820,768,390 --profile <dir> --page <kind> --category "<what is sold>" --primary "<main action>"
|
|
256
|
+
node <skill>/assets/layout/check.mjs --url index.html --profile <dir> --sizes 1440x900,1024x768,820x1180,768x1024,390x844 --shots shots/layout
|
|
257
|
+
node <skill>/scripts/shoot.mjs --url index.html --w 1440 --out shots/1440.png --profile <dir>
|
|
258
|
+
node <skill>/scripts/perf.mjs index.html --profile <dir>
|
|
259
|
+
```
|
|
260
|
+
|
|
261
|
+
Shoot 1024, 820x1180, 768x1024 and 390 as well. Every `check.mjs` finding fails the page (no `--no-stress`).
|
|
262
|
+
copy-lint opens no browser and takes under a second. Fix every FAIL (a copy-lint WARN too, or say
|
|
263
|
+
why it stays) and read the copy aloud (`copy-voice.md` section 6); shoot again and read every
|
|
264
|
+
screenshot against the checklist. In the fix rounds run `consistency.mjs --quick --widths
|
|
265
|
+
1440,390`. Then the gate, which runs the checker at 1440 and 390 every time, walks the page at 320
|
|
266
|
+
for overflow, collide and tap-size, and runs copy-lint, whose FAILs block like the checker's:
|
|
267
|
+
|
|
268
|
+
```bash
|
|
269
|
+
node <skill>/scripts/gate.mjs index.html
|
|
270
|
+
```
|
|
271
|
+
|
|
272
|
+
Fix what it lists and run it again until its last line is `GATE: PASS` or `GATE: OPEN`, three
|
|
273
|
+
rounds at most (in Claude Code it also runs when you finish; a stop before your first gate run is
|
|
274
|
+
no round, and to ask the user something after a block, just stop again). When the user tells you
|
|
275
|
+
to stop, or to ship the page as it is, run `gate.mjs --done "<what they said>"` (`GATE: DONE`)
|
|
276
|
+
and report the open FAILs.
|
|
277
|
+
`GATE: SETUP` (no page yet, a framework's source shell, a page that is not local): arm what a
|
|
278
|
+
browser can open (step 1) and run it again. `GATE: ERROR` (the checks could not run) or
|
|
279
|
+
`GATE: OFF`: put the line in the report and finish; do not rerun. Never edit
|
|
280
|
+
the kit's files or hide anything from the checker. A FAIL you judge false is waived in
|
|
281
|
+
`.taste-skill/waivers.json` with its reason, never fixed by gaming the check (`references/gate.md`);
|
|
282
|
+
a word from the client's own copy that copy-lint FAILs is waived hit by hit, the brief as the reason
|
|
283
|
+
(a word inside the client's name, as the logo or the title writes it, is not counted: one WARN).
|
|
284
|
+
|
|
285
|
+
7. **Report:** the `GATE:` line first, then every waiver with its reason and every open FAIL; the
|
|
286
|
+
kind, the deal (palette and why it fits, pairing, hero, grounds, effect, moments, scene); the
|
|
287
|
+
voice card in one line and every copy-lint WARN kept, with why; the checker, layout and perf
|
|
288
|
+
results; what you could not check; every assumed fact (the checker's `assumed` list) and the
|
|
289
|
+
coined name's search; the form's `.example` stand-in and the canonical domain still to come; the photographs and art the client must supply, every
|
|
290
|
+
stand-in frame among them (library and live search); every client slot, its file and its stand-in.
|
|
291
|
+
|
|
292
|
+
## 5. Checklist
|
|
293
|
+
|
|
294
|
+
Each line names its checks: `consistency.mjs` ids in brackets, `check.mjs` findings in braces,
|
|
295
|
+
`perf.mjs` rows. The last line is for your eyes.
|
|
296
|
+
|
|
297
|
+
- **First screen:** says what is sold, for whom or where, with one hard fact [copy-headline,
|
|
298
|
+
copy-fact]; the hero fills it alone at every width, its main button inside it [hero-screen,
|
|
299
|
+
hero-fill, fold-action, fold-cut] {hero-fold}.
|
|
300
|
+
- **One section per screen:** every section 1 or 2 screens, its h2 first and top-aligned, no
|
|
301
|
+
neighbour's heading or picture in its tile, nothing sparse, no section half empty [section-height, one-section,
|
|
302
|
+
one-heading, section-air, one-screen, section-gaps, empty-area] {screen-short, screen-height, sparse,
|
|
303
|
+
neighbour, neighbour-ground}.
|
|
304
|
+
- **Equal edges:** every block on the `.wrap` lines or the grid's columns, nothing out to one side,
|
|
305
|
+
no sideways scroll [container-edges, row-lines, split-pair, off-grid, right-edge, col-edge,
|
|
306
|
+
spill, off-viewport, stagger, top-stagger] {edge-left, edge-right, spill, bleed-one-side,
|
|
307
|
+
one-sided, lines}.
|
|
308
|
+
- **Every visual draws** at 1440, 1024, 768 and 390; a refused effect shows its still fallback
|
|
309
|
+
[visual-empty, empty-visual, gl-fallback, shader-lint, no-visual, photo-weight].
|
|
310
|
+
- **No caption** explains, apologises for or labels a picture; credits in one footer line
|
|
311
|
+
[visual-caption, caption, credit-wall, photo-credit]; no placeholder, sample note or printed
|
|
312
|
+
`.example` address [placeholder, sample-label].
|
|
313
|
+
- **The right things for the kind:** outside tech no effect ground, print or scene, only the
|
|
314
|
+
dealt photo- or type-led moments (WebGL only for a product render the brief asked for)
|
|
315
|
+
[effect-kind, effects-fit, photo-print]; the subject itself
|
|
316
|
+
shows: the product big, whole in three sections at most, a new picture each [product-shown,
|
|
317
|
+
same-object, photo-repeat]; each asset the brief names in its slot; a game's name and its world as key art,
|
|
318
|
+
the diff of a code-review tool, software's `app-frame`;
|
|
319
|
+
real photographs where they fit, none twice [photo-set, photo-repeat, photo-upscale]; real icons in their own
|
|
320
|
+
colours; flat grounds on other [grounds]; a place deals two different compositions and one type
|
|
321
|
+
moment.
|
|
322
|
+
- **Motion:** every button, link, linked card and linked photograph visibly answers the pointer,
|
|
323
|
+
nothing tilts [motion-layer, hover, hover-move, tilt]; the hero enters once on load
|
|
324
|
+
[hero-enter]; one or two dealt moments [moment-none]; card loops cycle in 2.5-4 s [loop-cycle]; nothing moves because the page scrolled
|
|
325
|
+
except a dealt moment inside its own section (every kind) or the big scene (tech)
|
|
326
|
+
[scroll-linked, scroll-reveal, pinned: expected only there]; anything
|
|
327
|
+
moving past 5 s has a pause button [loop-pause]; under reduced motion everything rests and nothing
|
|
328
|
+
stays hidden [reduced-motion, hidden-content]; at most four live contexts [webgl].
|
|
329
|
+
- **Contacts** as rule 9 [street-number, postcode, coordinates, company-number, phone-number];
|
|
330
|
+
Get directions only with a street, "See the area" with a district, no map link with a town only [map-link].
|
|
331
|
+
- **Keyboard and head:** every control named, alt on pictures, labels you can see, headings one
|
|
332
|
+
level at a time, no tabindex above 0; Tab reaches the skip link first, its ring shows at once and
|
|
333
|
+
never under the header; the menu button says its state; lang, title, description and share tags
|
|
334
|
+
[a11y-name, img-alt, field-label, heading-order, tabindex, skip-link, focus-ring, focus-visible,
|
|
335
|
+
focus-hidden, menu-toggle, lang, page-meta, share-meta].
|
|
336
|
+
- **One system:** one button pair, one card style, one radius scale, one link look [button-styles,
|
|
337
|
+
button-shape, card-family, card-layout, link-styles]; two boxes deep at most [nesting]; one
|
|
338
|
+
heading scale, its faces loaded [heading-scale, font-load]; text contrast [text-contrast,
|
|
339
|
+
contrast].
|
|
340
|
+
- **Copy and links:** headings name things, buttons a verb and an object, at most two hero actions
|
|
341
|
+
[copy-headings, copy-buttons, copy-actions, action-count]; one action twice a screen at most
|
|
342
|
+
[action-repeat]; a heading's grey half is its own sentence [run-on]; one fact, one wording
|
|
343
|
+
[fact-agree]; assumed facts marked, never an open-now line from them [assumed, open-now]; every
|
|
344
|
+
link lands, forms send, a confirmation only after a real send, each error under its own field
|
|
345
|
+
[links, forms, form-send, form-fields]; no slop word, stock line, leftover or device used as a
|
|
346
|
+
tic, a voice of its own (copy-lint's ids: copy-residue, copy-slop-word, copy-stock-phrase,
|
|
347
|
+
copy-two-fragment, copy-virtue, ...; `copy-voice.md`).
|
|
348
|
+
- **Fast:** no FAIL row in `perf.mjs` (image weight, contexts, layout shift).
|
|
349
|
+
- **820, 768, 390 and 320:** sections on their screens [section-height]; on a phone a section is at
|
|
350
|
+
least its screens and grows with what it holds, so nothing lies on anything else or under a fixed
|
|
351
|
+
bar [collide]; every link and control outside running text 44px tall [tap-size] (a FAIL when
|
|
352
|
+
another target is under 8px away); nothing past the screen at 320 [off-viewport], and nothing
|
|
353
|
+
lies on anything else there either [collide]; the first screen ending whole or on a clear bleed [fold-card]
|
|
354
|
+
(`layout-v4.md`); splits stack text first, no row half empty; one column at 390, buttons full
|
|
355
|
+
width, a full-screen menu; the place action bar.
|
|
356
|
+
- **Your eyes:** beside the figma.com and x.ai frames it reads as a professional company site;
|
|
357
|
+
nothing tilted, staggered, cut or overlapping; the hero is the work, not a mood.
|
|
358
|
+
|
|
359
|
+
## 6. Never
|
|
360
|
+
|
|
361
|
+
- A card, row or tile that fades in on scroll; a fade-in on every section; parallax on text;
|
|
362
|
+
scroll-jacking; random blinking.
|
|
363
|
+
- Stock photographs passed off as the client's product, people or place (a stand-in is listed in
|
|
364
|
+
the report as one, never shown with another maker's name or logo); a product page that never
|
|
365
|
+
shows the product.
|
|
366
|
+
- A drawn look-alike of a real logo; invented reviews, quotes, customers or figures.
|
|
367
|
+
- Violet or lavender in the page's own design: accent, ground, gradient, effect colour or tint (a
|
|
368
|
+
real third-party logo keeps its own colours, `icons.md`).
|
|
369
|
+
- Copying a reference site's code, copy, pictures or signature effect.
|
|
370
|
+
- Deleting or editing the kit's own files (`assets/`, `scripts/`) to clear a check: a check that
|
|
371
|
+
flags a kit file is reported, and the page is checked again after any change.
|
|
372
|
+
|
|
373
|
+
## References
|
|
374
|
+
|
|
375
|
+
All in `references/`; section 3 names the one each asset needs.
|