bolder
Skill441 starsChanged 3 months agoMITView on GitHub
Amplify personality — raises layout variance and motion, strengthens typography and one signature detail, without slop. Use when the UI works but feels safe, flat, or \"template-y\", or when the user says \"bolder\", \"more personality\", \"more creative\", or \"make it pop\" (still professional). Invoke when the user asks for bolder on their UI, or mentions 'bolder' alongside design / UI / frontend work.
34 other projects use a version of this.
Adopted by
Most recently taken up by
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- nexmoe/DayBeetheir own version, first seen Nov 1, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
- excatt/superclaude-plusplustheir own version, first seen Oct 13, 2026
Used with
Projects with it also use layout and vercel-react-best-practices.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
VercelSkillvercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Also in 3 projects that use this
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- talesofai/cohub★ 585same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
- Southclaws/storyden★ 348same name
- 10xChengTu/Mux0★ 337same name
- theexperiencecompany/gaia★ 327same name
- AkaraChen/aghub★ 271same name
- zacharyfmarion/openscad-studio★ 238same name
- jagrat7/linux-wallpaper-engine★ 227same name
- owshq-mec/semana-ai-data-engineer★ 122same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/ui-craft/references/agents.mdAGENTS.md
- adaptSkill
- animateSkill
- auditSkill
- briefSkill
- clarifySkill
- colorizeSkill
- craftSkill
- critiqueSkill
- delightSkill
- distillSkill
- extractSkill
- finalizeSkill
- hardenSkill
- heuristicSkill
- polishSkill
- quieterSkill
- redesignSkill
- rememberSkill
- sddesignSkill
- shapeSkill
- startSkill
- tokensSkill
- typesetSkill
- ui-craft-dense-dashboardSkill
- ui-craft-editorialSkill
- ui-craft-minimalSkill
- ui-craftSkill
- unhappySkill
- friction-logSkill
- friction-logSkill
- ui-craft-dense-dashboardSkill
- ui-craft-editorialSkill
- ui-craft-minimalSkill
- ui-craftSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Knob gating: if already at variance ≥9 or MOTION ≥9, strengthen signature and typography instead of pushing further.
“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- HARNESS MIRROR — do not edit here. Canonical source: commands/bolder.md. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.
Make the UI at $ARGUMENTS bolder. Load the ui-craft skill and read references/craft-intent.md.
This is amplitude, not decoration. Increase editorial confidence while staying anti-slop clean.
Apply in order (edit code directly):
- Declare an updated Craft Read — one line: what changed (variance, motion, signature).
- Raise DESIGN_VARIANCE by +1–2 (cap 10). Product surfaces: asymmetric offset, stronger metric hierarchy, or display moment in shell. Marketing: stronger hero composition, section rhythm break, or typographic scale — per
references/craft-intent.mdvariance table. - Raise MOTION_INTENSITY by +1 (cap 10) if below 8 — add one purposeful entrance or hover choreography on the focal element only. Honor
prefers-reduced-motion. - Typography — increase display weight or size one step; tighten tracking on headlines; ensure numbers stay
tabular-nums. - Accent — strengthen focal accent placement (within 3–5 viewport budget); tint primary card or CTA — never add a second accent hue.
- Signature — add or strengthen the one signature bet if missing or weak (see craft-intent §3).
Never add: purple-cyan gradients, bounce easing, glassmorphism stacks, emoji, ALL CAPS headings, three equal icon-card grids, confetti.
Knob gating: if already at variance ≥9 or MOTION ≥9, strengthen signature and typography instead of pushing further.
Output: edit code. Print Review Format table. End with the updated Craft Read line.
Next step: /critique — confirm the added personality did not cost hierarchy or become slop (rung 1).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

