bolder

Overview

What is bolder?

bolder is a UI design skill focused on transforming safe, generic, or visually bland interfaces into more stimulating and memorable experiences. It helps designers and teams identify why a design feels underwhelming and provides a structured approach to amplify its visual impact and personality—without compromising usability or accessibility.

Who should use bolder?

This skill is ideal for UI/UX designers, product teams, and developers who receive feedback that their designs look too safe, lack character, or fail to stand out. If you want to inject more energy, distinctiveness, or brand personality into your digital products, bolder provides a practical workflow.

Problems bolder solves

• Designs that feel generic, predictable, or uninspired
• Interfaces lacking contrast, hierarchy, or visual drama
• Projects where stakeholders request more personality or impact
• Ensuring bold changes remain usable and accessible

How to Use

Installation Steps

1. Install bolder using the following command:

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

2. Begin by reading the SKILL.md file for a detailed workflow and context.

3. Review supporting files such as README.md, AGENTS.md, and metadata.json for additional guidance.

4. Explore any rules/, resources/, references/, or scripts/ directories for extra tools and examples.

Applying the bolder workflow

• Mandatory Preparation:
  • Invoke $frontend-design to gather design principles and context. If no design context exists, run $teach-impeccable first.
• Assess Current State:
  • Identify what makes the design feel bland (e.g., generic fonts, low contrast, flat hierarchy).
  • Understand brand, audience, and project constraints.
• Plan Amplification:
  • Decide where and how to add visual drama, contrast, or unique elements.
  • Ensure changes align with brand and accessibility requirements.
• Amplify the Design:
  • Apply bolder choices in typography, color, layout, motion, or hierarchy.
  • Iterate based on feedback and usability checks.

Recommended files to preview

• Start with SKILL.md for the main workflow and rationale.

FAQ

When should I use bolder?

Use bolder when your design is described as bland, too safe, or lacking personality, or when stakeholders request more visual impact.

Does bolder replace design fundamentals?

No. bolder builds on solid design principles and is intended to enhance, not override, best practices in usability and accessibility.

Where can I find more details?

Open the Files tab in the repository to explore the full file tree, including supporting references and scripts for deeper guidance.