- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Leonxlnx/taste-skill --skill taste-skill -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Leonxlnx/taste-skill --skill taste-skill -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Leonxlnx/taste-skill --skill taste-skill -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Leonxlnx/taste-skill --skill taste-skill -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/Leonxlnx/taste-skill/tree/HEAD/skills/taste-skillVom Herausgeber
Build the website a good company would ship: it says plainly what is sold, shows the real thing on
every screen, and looks made for this client, not from a template and not like an art piece.
figma.com and x.ai are the bar (in words: layout-v4.md section 1).
<skill> is this folder. It needs Node 22+ and Chrome, Edge or Chromium (ffmpeg optional).
These nine win over everything else in this skill.
photo-chapters section, three or four screens, set by the moment.data-enter), and every page carries one dealt
moment, two on a long page (the gate holds both)..example.Write the kind on the plan's first line and declare it on the page: the page type on
<html data-type> and <meta name="page-type"> (the same value), and <meta name="site-kind">;
a place adds <meta name="page-kind" content="place">. The dealers take the last column
(start.mjs --page, moments.mjs --page), the hero dealer the page type; consistency.mjs reads
the metas.
A maker that also opens its door or teaches (a ceramics studio, a bakery with a web shop) is a place; its web shop becomes the goods section. It is a product only when nothing happens at the door.
"Tech" below means site-kind software, gaming or tech; "other" is everything else. Effects,
scenes, loops, counts, CSS grounds, dark pages and dark heroes are tech only. An other page is
photographs, flat colour, type, real icons, the hero's entrance, its dealt moment (photo- or
type-led, moments.md) and the hover layer.
The full plans, deal lists and section order: references/sections.md.
photos.md), then count; the palette dealt by trade. The hero
a photograph whenever a frame fits (a remote place: its region's landscape), the visit block on
screen two, the offer, the place, orders or booking.
Variety without effects (sections.md section 4): the offer and the place deal different
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
photographs, one button style, the phone bar, the dealt moments; no effect, ground, loop,
fragment, diagram or tab.photos.mjs search, each listed in the report, on the full product page; a render
(assets/objects/product-render, stills) only when the brief asks for 3D or a render; never a
drawing, mood stock or a set of props (sections.md, Product).sections.md, Product): the product big where it stands
whole (most of its frame, or on the ground at anchor scale), never mid-size in a grey rounded
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
compositions, no structure twice, one contrasting ground; the swatch changes the picture,
every colour shown once; no fact twice; buttons step and press (rule 5).app-frame, never a generic dashboard or only fragments on panels; cards:
fragments on lit panels, pulsing diagrams, real icons. Hardware: its photographs, else stand-in
photographs of its kind (a render only when the brief asks for 3D), never a split hero of only
an order form or a drawn SVG. A game: its name in the h1, a launch line, its world as full-bleed
key art (else its name set large over stand-in photographs of its setting), an effect never in
its place (, Gaming). outside UI mocks (). By
deal: (a shader ground in the hero or the one frame, a WebGL
part, an object or one big scene) and in their own sections; four live
WebGL contexts at most; no card moves with the scroll ().Open the reference of every asset family the page uses first. A dash means never.
Read copy.md, copy-voice.md, system.md, layout-v4.md and sections.md in full before the first page.
The stack. An empty folder builds a static page: copy <skill>/assets into assets and
start from assets/starter.html. An existing project builds in its own stack, its components
taking the starter's markup and classes, with the kit copied into its public folder
(public/assets) and loaded from there as plain files. A brief that asks for Next.js builds a
static export (output: 'export'), checked on its built page (--root out).
Read the brief. Write down the kind (section 1), what is sold, who buys it, the one main action (the transaction: Book a room, Order a cake, Start a free trial; a place with neither: Get directions) and the real material: logo, screens, photographs, prices, address, hours. Then arm the finish gate, before any page exists:
node <skill>/scripts/gate.mjs --start index.html --kind <kind> --category "<what is sold>" --primary "<main action>"
A framework build names its dev server's URL (--start http://localhost:5173/) or its built page
(--start dist/index.html --root dist; a Next.js export: out) in place of index.html, and
rebuilds before every gate run.
Write all the copy first, with the copy layer (copy-voice.md: the fact sheet, the voice
card on the plan, the page's shape, the device budget; a register from copy-registers.md, the
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),
one hard fact on the first screen, a noun in every heading, buttons as a verb and an object.
Nothing is invented but a coined brand name (searched first, the result kept in names.json
beside the page) and, on a place, plausible hours and prices, each marked data-assumed
(copy.md, What may be assumed). A draft kept in a .md file lints the same way as the page
(the voice card and part labels are skipped).
Plan the page as screens. Line 1: the kind. Line 2: the deal (step 4), with one sentence on
why the palette fits the trade. Then one line per
section: its id, its one idea, its picture and its kind (object, use, parts, world, slot, diagram, type; three object lines at most), its
screens (1 or 2, from its content height, layout-v4.md section 2), which section holds a
moment and why it moves (on tech also the effect or the scene). Pick the photographs now (photos.md); their count,
stand-ins included, sets a place's length (section 2). Then read and the recipe of
every id you use in .
Each line names its checks: consistency.mjs ids in brackets, check.mjs findings in braces,
perf.mjs rows. The last line is for your eyes.
.wrap lines or the grid's columns, nothing out to one side,
no sideways scroll [container-edges, row-lines, split-pair, off-grid, right-edge, col-edge,
spill, off-viewport, stagger, top-stagger] {edge-left, edge-right, spill, bleed-one-side,
one-sided, lines}..example address [placeholder, sample-label].app-frame;
real photographs where they fit, none twice [photo-set, photo-repeat, photo-upscale]; real icons in their own
colours; flat grounds on other [grounds]; a place deals two different compositions and one type
moment.icons.md).assets/, scripts/) to clear a check: a check that
flags a kit file is reported, and the page is checked again after any change.All in references/; section 3 names the one each asset needs.
>-
---name: design-taste-frontenddescription: >----# skills/taste-skill/SKILL.mdFAQ
Laden Sie skills/taste-skill/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/Leonxlnx/taste-skill.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.
sections.mdcopy.md[data-visual]effects-usage.mdsections.md section 1,
its table): a game's world and crew; hardware's use at the bench, its parts close up; a still
diagram card, a type moment, a context photograph where the trade allows.<video> with a stand-in
poster, a play control only when there is a page or file to play, three to five stand-in
photographs of the world, a CAD frame), named in a comment for the client's file, never empty
(sections-library.md, client-slots).| Feature cards, UI fragments | assets/ui | lead (gaming: none) | its app | an app the client runs | - | cards.md |
| Diagram cards (hub, lanes, pulses) | assets/diagrams | 0-2, pulsing | 0-2, pulsing | 0-1, still | - | diagrams.md |
| CSS grounds | assets/backgrounds | 0-2 dealt | 0-2 dealt | flat tokens | flat tokens | backgrounds.md |
| Shader grounds | assets/effects | the one effect | the one effect | - | - | effects-usage.md |
Creative parts (fx-*) | assets/components | yes | yes | fx-photo plain, fx-map still | fx-map still | effects-creative.md |
| 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 |
| Award-site moments | assets/moments | 1-2 | 1-2 | 1-2 (photo, type) | 1-2 (photo, type) | moments.md |
| Big scenes | assets/scenes | 0-1 | 0-1 | - | - | scenes.md |
| Speed and weight | scripts/perf.mjs | yes | yes | yes | yes | perf.md |
cards.mdsections-library.mdDeal, never choose by taste. Each command keeps a history, so pages differ:
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
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
node <skill>/scripts/start.mjs css --page <kind> --palette <id> --type <id> --radius soft --history .taste-skill/history.json
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
node <skill>/scripts/moments.mjs pick --page <kind> --count 1|2 --fits section,statement --photo --history .taste-skill/history.json # every kind
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>
Run every command from the project folder (the deal arms the gate in the folder it runs in, or
joins the build already open one or two folders up). The
lists, in order nav, footer, close, rhythm, buttons, mark (sections.md sections 2 and 3):
"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""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""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""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"sections.md section 4, Place (The deal), read in its order.A product or hardware with no photographs deals with --has photo for its stand-ins;
--has object only for a cut-out or a render the brief asks for (always the product hero, its
widest view across the wrap, no box); a game without art files passes --has setting (the
photo hero, its name over a stand-in of its setting; a game always passes --has). A product
page is dealt only the product, photo and film heroes. A place's hero is printed, never dealt (--type place). A dealt part that needs a photograph the page lacks is dealt again (sections.md section 2). Take the
first palette and the first pairing printed (the next only when the first clashes with the
client's own logo or photographs, or the pairing fails hero-lines, said on plan line 2); the client's own colours go through
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,
round for consumer apps, square on a place. On tech only: the lit ground (<html data-ground>:
sand|sky|sage through the one-liner), the CSS grounds (backgrounds.md) and the one effect
(effects-usage.md). Write every result on plan line 2 and in
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).
Build. In starter.html: set <html lang data-type data-radius data-buttons data-motion>
(lang: the brief's language), the three metas, the head block (title, description, og, icon,
theme-color: system.md, Head) and the nav class; keep the skip link and the m-enter head
line; copy only the <section class="hero …" data-enter> of
assets/layout/hero-<id>.html (never its nav, other sections, footer or credit line; every word
and picture becomes the client's); move the dealt close and footer out of their <template>s
and delete the rest. Every section is main > section with
one .wrap, its h2 first, --h: 1 or 2. Build each to its recipe with the system's classes
and tokens; write page CSS only where a reference says page CSS (inside a visual, --p-h,
.wall, .rail, .device). Paste UI from assets/ui/<name>/fragment.html and rewrite every
name, number and logo to the client's (kit icons become data-icon, cards.md); a diagram card is data-diagram="<preset>"
with the client's labels; run icons.mjs scan index.html --out assets/icons --colour last, so every icon
the page names is a local file. Mount an effect, object, moment or scene exactly as its
reference says, never from your own script. A moment's section is copied from
assets/moments/_demo/in-page.html (place: photo-chapters, word-highlight) or
in-page-service.html (pinned-chapters, picture-develops film); a moment's own demo.html shows
it alone and is not a page model. A form is the starter's booking-form (system.md,
Forms). Credits: the one footer line from photos.mjs credits, once the markup uses the
photographs (it reads the page). Copy the hero's tile from shoot.mjs beside the page as share.jpg.
Check and look. Only the skill's scripts, each running one headless Chrome with WebGL on the
CPU, closed by its own PID, one at a time in the foreground with a 10-minute timeout; never in
the background, a windowed browser or a browser tool.
Each serves the page file itself over http on 127.0.0.1 (never file://), so no server is needed;
for a built page whose links start at the site root (/_astro/page.css), pass --root with the build folder (dist).
--profile <dir> is the Chrome profile: a folder of its own in the OS temp folder or in the
project's .taste-skill folder (.taste-skill/chrome-check), never outside the project (no
../); a relative one that leads out of it is replaced by .taste-skill/chrome-<script>. Then:
node <skill>/scripts/copy-lint.mjs index.html --kind <kind>
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>"
node <skill>/assets/layout/check.mjs --url index.html --profile <dir> --sizes 1440x900,1024x768,820x1180,768x1024,390x844 --shots shots/layout
node <skill>/scripts/shoot.mjs --url index.html --w 1440 --out shots/1440.png --profile <dir>
node <skill>/scripts/perf.mjs index.html --profile <dir>
Shoot 1024, 820x1180, 768x1024 and 390 as well. Every check.mjs finding fails the page (no --no-stress).
copy-lint opens no browser and takes under a second. Fix every FAIL (a copy-lint WARN too, or say
why it stays) and read the copy aloud (copy-voice.md section 6); shoot again and read every
screenshot against the checklist. In the fix rounds run consistency.mjs --quick --widths 1440,390. Then the gate, which runs the checker at 1440 and 390 every time, walks the page at 320
for overflow, collide and tap-size, and runs copy-lint, whose FAILs block like the checker's:
node <skill>/scripts/gate.mjs index.html
Fix what it lists and run it again until its last line is GATE: PASS or GATE: OPEN, three
rounds at most (in Claude Code it also runs when you finish; a stop before your first gate run is
no round, and to ask the user something after a block, just stop again). When the user tells you
to stop, or to ship the page as it is, run gate.mjs --done "<what they said>" (GATE: DONE)
and report the open FAILs.
GATE: SETUP (no page yet, a framework's source shell, a page that is not local): arm what a
browser can open (step 1) and run it again. GATE: ERROR (the checks could not run) or
GATE: OFF: put the line in the report and finish; do not rerun. Never edit
the kit's files or hide anything from the checker. A FAIL you judge false is waived in
.taste-skill/waivers.json with its reason, never fixed by gaming the check (references/gate.md);
a word from the client's own copy that copy-lint FAILs is waived hit by hit, the brief as the reason
(a word inside the client's name, as the logo or the title writes it, is not counted: one WARN).
Report: the GATE: line first, then every waiver with its reason and every open FAIL; the
kind, the deal (palette and why it fits, pairing, hero, grounds, effect, moments, scene); the
voice card in one line and every copy-lint WARN kept, with why; the checker, layout and perf
results; what you could not check; every assumed fact (the checker's assumed list) and the
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
stand-in frame among them (library and live search); every client slot, its file and its stand-in.
copy-voice.md).perf.mjs (image weight, contexts, layout shift).layout-v4.md); splits stack text first, no row half empty; one column at 390, buttons full
width, a full-screen menu; the place action bar.