- Home
- Skills
- Steveclarke
- Dotfiles
- I Bolder
i-bolder_skill
- Shell
31
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill steveclarke/dotfiles --skill i-bolder- SKILL.md6.6 KB
Overview
This skill amplifies safe or bland interfaces to make them visually interesting and memorable while preserving usability and accessibility. It provides a repeatable audit and amplification plan across typography, color, space, texture, motion, and composition so designs become distinctive, not just louder. Follow the Context Gathering Protocol in the i-frontend-design skill before starting; if no context exists, run teach-impeccable first.
How this skill works
First, the skill inspects the current design to identify why it feels safe: generic choices, timid scale, low contrast, static layout, or flat hierarchy. It then produces a targeted amplification plan: choose one hero focal point, set a personality direction, establish a risk budget, and amplify hierarchy. Finally it applies concrete treatments across typography, color, spatial drama, visual effects, motion, and composition, with verification checks for usability, performance, and accessibility.
When to use it
- When a product feels generic or forgettable and needs personality without breaking usability
- When marketing or promotional pages must make a bold impression while staying coherent
- Before a visual refresh to guide purposeful, non-derivative changes
- When brand guidelines allow experimentation but need a controlled risk budget
- When prototypes must show a clear hero moment and stronger visual hierarchy
Best practices
- Always run the Context Gathering Protocol from i-frontend-design first; stop and ask clarifying questions if context is missing
- Pick one focal point to amplify—avoid making everything large or flashy
- Favor distinctive choices over trendy effects; avoid generic purple-to-blue gradients and glassmorphism
- Measure contrast, readability, and motion load to maintain accessibility and prevent fatigue
- Document a risk budget and test changes with real users to ensure function matches impact
Example use cases
- Revamping a corporate website that currently uses system fonts and muted colors to become more memorable for campaigns
- Turning a marketing landing page into a dramatic hero-led experience without sacrificing conversion funnels
- Refreshing a product dashboard by increasing typographic scale and visual hierarchy while keeping core tasks efficient
- Creating a bold campaign microsite that uses asymmetric layouts, textured backgrounds, and choreographed entrance animations
- Prototyping brand-forward UI treatments (large type, tinted neutrals, sharp accents) for stakeholder review
FAQ
'Bolder' means more intentional, distinctive design—dramatic scale, unique type, clearer hierarchy—not indiscriminate effects or motion overload.
How do I avoid making things inaccessible when increasing contrast or motion?
Use WCAG contrast checks, provide motion-reduced alternatives, keep body text readable, and test with assistive technologies.