committed-aesthetic
FeaturedHow to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when starting a new brand surface with no reference, or when authoring a house style you want executed the same way twice.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- avelikiy
- Repository
- avelikiy/great_cto
- Created
- 5 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
aesthetic-instrument
great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.
frontend-aesthetics
Raises the visual quality of agent-generated UI so it stops reading as AI slop, and audits existing UI against a catalog of tells. Use BEFORE writing the first line of markup for any user-facing surface (landing page, marketing site, dashboard, app screen, docs site) - not after, when the defaults are already baked in. Also use whenever a UI is described as looking generic, templated, "AI-generated", soulless, or "like every other site", when asked to make something look better/more premium/less default, when redesigning or critiquing an existing interface, or when reviewing UI a model produced. Ships a deterministic linter (scripts/slop_check.py) for the countable tells; the judgment calls stay human. Not for chart/data-viz design, and not for layout BUGS (that is debugging, not taste).
frontend-aesthetics
Raises the visual quality of agent-generated UI so it stops reading as AI slop, and audits existing UI against a catalog of tells. Use BEFORE writing the first line of markup for any user-facing surface (landing page, marketing site, dashboard, app screen, docs site) - not after, when the defaults are already baked in. Also use whenever a UI is described as looking generic, templated, "AI-generated", soulless, or "like every other site", when asked to make something look better/more premium/less default, when redesigning or critiquing an existing interface, or when reviewing UI a model produced. Ships a deterministic linter (scripts/slop_check.py) for the countable tells; the judgment calls stay human. Not for chart/data-viz design, and not for layout BUGS (that is debugging, not taste).