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
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
vercel-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.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
shader-dev
Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.
remotion-best-practices
Best practices for Remotion - Video creation in React
prompt-engineering-patterns
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing production prompt templates.
pptx-generator
Generate, edit, and read PowerPoint presentations. Create from scratch with PptxGenJS (cover, TOC, content, section divider, summary slides), edit existing PPTX via XML workflows, or extract text with markitdown. Triggers: PPT, PPTX, PowerPoint, presentation, slide, deck, slides.
planning-with-files
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
pinchtab
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, log into sites with a persistent profile, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API when the CLI is unavailable. Prefer this skill for token-efficient browser work driven by stable accessibility refs such as `e5` and `e12`.
opencli
OpenCLI — Make any website or Electron App your CLI. Zero risk, AI-powered, reuse Chrome login.