Each page was built from the same brief, following one skill's instructions. Tap through both, then read what each skill pushed for.
| frontend-design | taste-skill | |
|---|---|---|
| What it is | One page of design guidance, about 1,500 words | Rules plus 20+ reference docs, an asset kit and Node scripts (dealers, checker, gate) |
| Where the look comes from | The subject's own world, chosen by the designer | A random deal from its palette and font library |
| Structure | Free. Plan in ASCII, then critique | Fixed per business kind; one section per screen |
| Motion | One orchestrated moment, little else | Hero entrance, hover and press on everything, card loops |
| Checking | Self-critique with screenshots | Automated browser gate (SHIP or HOLD) |
| Setup cost | Zero. Read and build | Node 22 + Chrome; heavy to run in full |
| Best for | Pages that need a distinct identity | Company sites that must look like a polished SaaS |
No Claude skill for Georgian exists yet (searched with Exa deep research). The closest, georgian-grammar-codex-skill, is a Codex skill in plain Markdown, so its rules were applied by hand: polite თქვენ-forms, case before postpositions, hyphenated suffixes on Latin names (Tipbook-ი, Chrome-ში), Georgian „quotes“, singular nouns after numerals.
Neither build's fonts (Archivo, Courier Prime, Mona Sans) contain Georgian letters, so both switch to Noto Sans Georgian. Build A keeps its condensed headlines through Noto's width axis. Georgian has no capitals, so nothing is uppercased. Numbers follow ka-GE: 11,60 ₾.
A native speaker should still read both before anything ships.
Both pages were built by the same model in one session, one after the other, so some taste carries over. A cleaner test runs each skill in a fresh session.
taste-skill's own scripts (random dealer, checker, gate) were blocked from running here because they are downloaded third-party code. Its deal was reproduced from its own palette and font data files, and its rules were followed by hand. Its gate never ran.