SKILL·055ACF

committed-aesthetic

avelikiy
Updated 16 days ago
4 views
93
13
93
View on GitHub
Metaaidesign

About

The `committed-aesthetic` skill defines a single, precise design style for consistent agent execution, unlike a catalogue of options. It's used to enforce a specific house style from scratch, prevent generic outputs, and ensure repeatable results. Apply it when starting a new brand surface without existing references or when you need an agent to reliably implement a defined aesthetic.

Quick Install

Claude Code

Recommended
Primary
npx skills add avelikiy/great_cto -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/avelikiy/great_cto
Git CloneAlternative
git clone https://github.com/avelikiy/great_cto.git ~/.claude/skills/committed-aesthetic

Copy and paste this command in Claude Code to install this skill

Documentation

A committed aesthetic beats a catalogue

The problem this exists for

ui-ux-pro-max ships 84 styles, 161 palettes and 57 font pairings, and design-advisor is wired to all of it. The catalogue is not the bottleneck.

The bottleneck is that a catalogue lets a model pick, and an unconstrained pick is the modal one. Asked for a landing page with no brand, any model reaches for the same safe centre: a soft gradient, a large sans heading, three rounded cards with a left accent border, generous neutral grey. Every input in the training distribution votes for it. Nothing in a catalogue entry saying "Swiss minimalism — clean, grid-based, generous whitespace" is specific enough to override that, because that sentence describes the safe centre too.

Compare a rule from a committed aesthetic:

every dimension is calc(fraction * 100vw) against a baseline width, so one page at 1024px reads as a perfect scaled-down of the same page at 1920px

You can check that. A design either obeys it or does not. That is the whole difference: a catalogue entry is a label, a committed aesthetic is a constraint.

The form

A committed-aesthetic skill has five parts. The first is the one that does the work.

1. Transferable DNA — numbered, specific, falsifiable

Between 8 and 14 rules. Each must be checkable by someone who was not in the room. Test every rule against this: could two designers disagree about whether a page obeys it? If yes, it is a vibe, rewrite it.

Vibe (useless)Constraint (usable)
"thin, elegant type""weights 100 or 300 only, never 400+"
"lots of whitespace""~60% of any above-the-fold area is empty"
"restrained motion""no shadows, no gradients, no bounce; one shadow exists in the system, on toasts"
"technical feel""product codes use en-dash U+2013, never hyphen"
"dark and dense""five surface steps, each ~5% apart; depth is a surface step, never a shadow"

2. What this does NOT do — the IP boundary, as a table

An aesthetic is inspired-by, not cloned. Name the specific assets that belong to whoever you are borrowing from — wordmark, icon set, information architecture, product names, copy — and for each give the reason and what to do instead. This is not a legal disclaimer at the bottom; it is a working table an agent reads while building, and it is the difference between an homage and a trademark problem. Where the source is a real company, default to inspired-but-distinct and ask before taking the clone path.

3. A component library that runs

One HTML file the agent can open, with every component rendered and its own CSS inline, copy-pasteable. A token table in prose is read and paraphrased; a rendered gallery is copied exactly. This is why the form works at all.

4. Templates for the signature patterns

The two or three moves nobody would reconstruct from the DNA list alone — the navigation shape, the section header, the hero. With swap these for your own brand marked in comments.

5. Reference captures, marked "study, do not pixel-copy"

Screenshots are for understanding the patterns. Building FROM a screenshot rather than from the rules produces a bad tracing of one page instead of a design in the family.

The banned list, and why we needed one

ui-ux-pro-max's anti-pattern tables are about accessibility, touch targets and performance. They are good and they are not about taste. Nothing in this repository told an agent what cliché looks like, so the only defence against slop was one sentence in design-advisor: "no generic clean modern minimal filler".

Banned by default on any surface without an existing system that calls for them:

  • A gradient as the page ground. Especially purple-to-blue, especially at 135°.
  • The card triplet: three equal cards, rounded corners, a coloured left border, an icon in a tinted circle.
  • Inter, Roboto, Arial, Open Sans, Fraunces, Poppins as the display face. Not because they are bad — because they are the default vote.
  • Emoji as iconography. Draw the icon. (Emoji are fine if the brand uses them.)
  • The hero that describes a category rather than taking a position. "The modern platform for X" is the sentence a model writes when it has not been told what to believe.
  • Glassmorphism, neumorphism, and a mesh-gradient blob unless the brief names one of them.
  • Symmetric three-column feature grids as the default second section.

A banned list is not a style. It removes the centre so a choice has to be made.

Using one

  1. If a system already governs, this skill does not apply — match what exists.
  2. If nothing governs and you can ask: offer 2–4 genuinely different directions, each an axis you can name, before building. Not five shades of one aesthetic — that is not a choice.
  3. If nothing governs and you cannot ask: commit to ONE, state the assumption in a line at handover, and put 1–2 low-fi alternates beside the deliverable, never instead of it.
  4. Once a direction is chosen, load its committed-aesthetic skill and execute the DNA rules literally. Cite the rule number for each choice, the way design-advisor already cites a ui-ux-pro-max rule.

Instances in this repository

Related: skills/ui-ux-pro-max/SKILL.md is the catalogue this stands beside, not a replacement for it — the catalogue is where you look when you need to KNOW something; this is what you load once you have DECIDED something.

GitHub Repository

avelikiy/great_cto
Path: skills/committed-aesthetic
0
agentic-codingai-agentsclaude-codeclaude-code-pluginclaude-code-skillsclaude-code-subagents
FAQ

Frequently asked questions

What is the committed-aesthetic skill?

committed-aesthetic is a Claude Skill by avelikiy. Skills package instructions and resources that Claude loads on demand, so Claude can perform committed-aesthetic-related tasks without extra prompting.

How do I install committed-aesthetic?

Use the install commands on this page: add committed-aesthetic to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does committed-aesthetic belong to?

committed-aesthetic is in the Meta category, tagged ai and design.

Is committed-aesthetic free to use?

Yes. committed-aesthetic is listed on AIMCP and free to install.

Related Skills

content-collections
Meta

This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.

View skill
polymarket
Meta

This skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.

View skill
creating-opencode-plugins
Meta

This skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.

View skill
sglang
Meta

SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.

View skill