bolder

Overview

What is bolder?

bolder is a UI design skill that helps you transform safe, generic, or visually bland interfaces into more stimulating and memorable experiences. It is designed for designers and teams who want to add personality, energy, and stronger visual direction to their products without sacrificing usability.

Who should use bolder?

• UI/UX designers seeking to break out of generic or uninspired design patterns
• Teams receiving feedback that their product looks too safe, bland, or lacks character
• Projects where increased visual impact and brand personality are desired

Problems bolder solves

• Designs that feel generic, predictable, or lack visual hierarchy
• Interfaces with low contrast, timid scale, or static layouts
• Products that need to stand out and create a lasting impression

How to Use

Installation Steps

1. Add the skill to your project:
   Run the following command in your project directory:

   npx skills add https://github.com/pbakaus/impeccable --skill bolder
   

2. Review the main documentation:
   Start with the SKILL.md file for a detailed workflow and context. Additional context may be found in README.md, AGENTS.md, or related folders if available.

Getting Started

• Mandatory Preparation:
  • Before using bolder, invoke /frontend-design to gather design principles and context. If your project lacks design context, run /teach-impeccable first as instructed in the skill's documentation.
• Assess Your Current Design:
  • Identify what makes your design feel too safe or bland (e.g., generic fonts, low contrast, static layouts).
  • Understand your brand personality, audience, and any constraints.
• Plan and Apply Amplification:
  • Use bolder's guidance to introduce stronger hierarchy, contrast, motion, and unique elements while respecting usability and accessibility.

File Structure

• Key file to review: SKILL.md (primary workflow and instructions)
• Other helpful files: README.md, AGENTS.md, and any supporting folders if present

FAQ

When should I use bolder?

Use bolder when your design is described as bland, generic, too safe, or lacking in personality. It is especially useful after receiving stakeholder or user feedback requesting more visual impact or uniqueness.

Does bolder replace my existing design process?

No, bolder is intended to enhance your current workflow by providing targeted strategies to amplify visual impact. It works best when integrated with your existing design tools and processes.

What preparation is required before using bolder?

You must gather design context by invoking /frontend-design as outlined in the skill's documentation. If no context exists, run /teach-impeccable first.

Where can I find more details?

Open the Files tab in the repository to explore the full file tree, including SKILL.md and any additional references or scripts that support the bolder workflow.