bolder
Skill4 starsChanged 6 months agoMITView on GitHub
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
34 other projects use a version of this, 27 of them edited.
Adopted by
Most recently taken up by
- theexperiencecompany/gaiaedited, first seen Nov 3, 2026
- vijaysuperpositionist/skillsedited, first seen Nov 1, 2026
- nexmoe/DayBeeedited, first seen Nov 1, 2026
- davidanthonyn/claude-skillsedited, first seen Oct 20, 2026
- The-Utopia-Studio/skillsedited, first seen Oct 13, 2026
- excatt/superclaude-plusplusedited, first seen Oct 13, 2026
Used with
Projects with it also use layout, shape and 1 more.
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
HAR5HA-7663Skillshape
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
Also in 12 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 · 5
- talesofai/cohub★ 585100% same
- HK-hub/AgentSkills★ 6100% same
- huangzida/skills★ 2100% same
- freshpomelo/agent_skills★ 0100% same
- lucaszb-orla/claude-skills★ 0100% same
Edited · 27
- nexmoe/DayBee★ 42498% same
- nexmoe/eve★ 42498% same
- Southclaws/storyden★ 34898% same
- 10xChengTu/Mux0★ 33797% same
- theexperiencecompany/gaia★ 32597% same
- AkaraChen/aghub★ 271100% same
- zacharyfmarion/openscad-studio★ 23895% same
- jagrat7/linux-wallpaper-engine★ 22798% same
- owshq-mec/semana-ai-data-engineer★ 12295% same
- rwliebs/Dossier★ 8898% same
17 more not listed
Wrote their own version · 2
- educlopez/ui-craft★ 441same name
- Zack-Grogan/agentos-foundation★ 0same name
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 repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adaptSkill
- animateSkill
- arrangeSkill
- auditSkill
- clarifySkill
- code-refactorSkill
- colorizeSkill
- critiqueSkill
- delightSkill
- distillSkill
- extractSkill
- frontend-designSkill
- gitlab-integrationSkill
- git-operationsSkill
- hardenSkill
- industrial-ai-researchSkill
- latex-paper-enSkill
- latex-thesis-zhSkill
- mermaid-diagramsSkill
- normalizeSkill
- onboardSkill
- optimizeSkill
- overdriveSkill
- paper-auditSkill
- polishSkill
- pydanticSkill
- python-best-practicesSkill
- python-docsSkill
- pytorch-lightningSkill
- quieterSkill
- remotion-best-practicesSkill
- research-paper-writingSkill
- skill-creatorSkill
- teach-impeccableSkill
- typesetSkill
- typst-paperSkill
The file
We split this skill into the rules it gives an agent
11 rules. 10 are common, 1 is distinctive, and 0 are very specific to this project.
10
Common
Most of the 28 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
- Common: line 24
Static: No motion, no energy, no life
- Distinctive: line 34
If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.
- Common: line 42
Create a strategy to increase impact while maintaining coherence:
- Common: line 57
Extreme scale: Create dramatic size jumps (3x-5x differences, not 1.5x)
- Common: line 73
Generous space: Use white space dramatically (100-200px gaps, not 20-40px)
- Common: line 90
Hero moments: Create clear focal points with dramatic treatment
- Common: line 92
Full-bleed elements: Use full viewport width/height for impact
- Common: line 96
Add effects randomly without purpose (chaos ≠ bold)
- Common: line 105
Ensure amplification maintains usability and coherence:
- Common: line 111
Performant: Do all these effects run smoothly?
- Common: line 114
The test: If you showed this to someone and said "AI made this bolder," would they believe you immediately?
“Common” is measured: kept by at least 6 in 10 of the 28 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
Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences.
MANDATORY PREPARATION
Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.
Assess Current State
Analyze what makes the design feel too safe or boring:
- Identify weakness sources:
- Generic choices: System fonts, basic colors, standard layouts
- Timid scale: Everything is medium-sized with no drama
- Low contrast: Everything has similar visual weight
- Static: No motion, no energy, no life
- Predictable: Standard patterns with no surprises
- Flat hierarchy: Nothing stands out or commands attention
- Understand the context:
- What's the brand personality? (How far can we push?)
- What's the purpose? (Marketing can be bolder than financial dashboards)
- Who's the audience? (What will resonate?)
- What are the constraints? (Brand guidelines, accessibility, performance)
If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.
CRITICAL: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos.
WARNING - AI SLOP TRAP: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the frontend-design skill before proceeding. Bold means distinctive, not "more effects."
Plan Amplification
Create a strategy to increase impact while maintaining coherence:
- Focal point: What should be the hero moment? (Pick ONE, make it amazing)
- Personality direction: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane.
- Risk budget: How experimental can we be? Push boundaries within constraints.
- Hierarchy amplification: Make big things BIGGER, small things smaller (increase contrast)
IMPORTANT: Bold design must still be usable. Impact without function is just decoration.
Amplify the Design
Systematically increase impact across these dimensions:
Typography Amplification
- Replace generic fonts: Swap system fonts for distinctive choices (see frontend-design skill for inspiration)
- Extreme scale: Create dramatic size jumps (3x-5x differences, not 1.5x)
- Weight contrast: Pair 900 weights with 200 weights, not 600 with 400
- Unexpected choices: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default)
Color Intensification
- Increase saturation: Shift to more vibrant, energetic colors (but not neon)
- Bold palette: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop
- Dominant color strategy: Let one bold color own 60% of the design
- Sharp accents: High-contrast accent colors that pop
- Tinted neutrals: Replace pure grays with tinted grays that harmonize with your palette
- Rich gradients: Intentional multi-stop gradients (not generic purple-to-blue)
Spatial Drama
- Extreme scale jumps: Make important elements 3-5x larger than surroundings
- Break the grid: Let hero elements escape containers and cross boundaries
- Asymmetric layouts: Replace centered, balanced layouts with tension-filled asymmetry
- Generous space: Use white space dramatically (100-200px gaps, not 20-40px)
- Overlap: Layer elements intentionally for depth
Visual Effects
- Dramatic shadows: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles)
- Background treatments: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue)
- Texture & depth: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop)
- Borders & frames: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side)
- Custom elements: Illustrative elements, custom icons, decorative details that reinforce brand
Motion & Animation
- Entrance choreography: Staggered, dramatic page load animations with 50-100ms delays
- Scroll effects: Parallax, reveal animations, scroll-triggered sequences
- Micro-interactions: Satisfying hover effects, click feedback, state changes
- Transitions: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect)
Composition Boldness
- Hero moments: Create clear focal points with dramatic treatment
- Diagonal flows: Escape horizontal/vertical rigidity with diagonal arrangements
- Full-bleed elements: Use full viewport width/height for impact
- Unexpected proportions: Golden ratio? Throw it out. Try 70/30, 80/20 splits
NEVER:
- Add effects randomly without purpose (chaos ≠ bold)
- Sacrifice readability for aesthetics (body text must be readable)
- Make everything bold (then nothing is bold - need contrast)
- Ignore accessibility (bold design must still meet WCAG standards)
- Overwhelm with motion (animation fatigue is real)
- Copy trendy aesthetics blindly (bold means distinctive, not derivative)
Verify Quality
Ensure amplification maintains usability and coherence:
- NOT AI slop: Does this look like every other AI-generated "bold" design? If yes, start over.
- Still functional: Can users accomplish tasks without distraction?
- Coherent: Does everything feel intentional and unified?
- Memorable: Will users remember this experience?
- Performant: Do all these effects run smoothly?
- Accessible: Does it still meet accessibility standards?
The test: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects."
Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable.
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.

