bolder
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.
Best use case
bolder is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using bolder should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/bolder/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How bolder Compares
| Feature / Agent | bolder | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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: 1. **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 2. **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.
Related Skills
workos-convex-debug
Debug and troubleshoot WorkOS AuthKit authentication issues with Convex. Use when authentication fails, JWT validation errors occur, user identity returns null, email claims are missing, admin access checks fail, or sign in button does not work. Supports Netlify deployment.
workos-convex-auth
Set up and configure WorkOS AuthKit authentication with Convex backend. Use when integrating AuthKit, configuring JWT providers, setting up environment variables, or implementing sign in and sign out flows with React and Vite. Supports Netlify deployment.
convex-scale-optimization
Patterns for scaling read-heavy Convex apps to millions of users. Use when optimizing bandwidth, reducing query costs, fixing slow queries, creating digest tables, replacing reactive subscriptions with one-shot fetches, adding compound indexes, debouncing writes, rate-controlling backfills, or running npx convex insights. Trigger when users mention "scale", "bandwidth", "performance", "optimize", "slow queries", "expensive queries", "digest table", "denormalize", or "thundering herd" in the context of Convex.
convex-design-system
Convex UI component patterns from the live Storybook preview. Use when building React components, forms, modals, navigation, feedback states, or app layouts that should match the current Convex design system. Applies to both shared primitives and dashboard style product UI.
Update project docs
Sync project tracking files after completing work, then provide a ready to use git commit message.
typeset
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
robel-auth
Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation. Use when adding auth setup, updating auth wiring, migrating between upstream patterns, or troubleshooting @robelest/convex-auth behavior across projects.
quieter
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
polish
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
overdrive
Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.
optimize
Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.