원클릭으로
bolder
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | bolder |
| description | Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. |
| user-invocable | true |
| args | [{"name":"target","description":"The feature or component to make bolder (optional)","required":false}] |
Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences.
Use the frontend-design skill: 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.
Analyze what makes the design feel too safe or boring:
If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify.
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 are generic. Review ALL the DON'T guidelines in the frontend-design skill before proceeding. Bold means distinctive, not "more effects."
Create a strategy to increase impact while maintaining coherence:
IMPORTANT: Bold design must still be usable. Impact without function is just decoration.
Systematically increase impact across these dimensions:
NEVER:
Ensure amplification maintains usability and coherence:
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.
Runs and scopes automated tests for this Turborepo (unit, package filters, Medusa stress, E2E, release gate). Use when the user asks to run tests, verify CI locally, debug failing tests, or choose the right test command for a changed package.
Plug-and-play orchestration skill. User states a goal in natural language; the model runs commands/agent-hub.md (dispatcher), classifies work via agent/operating-model.md, then opens only the matching command or architecture doc (map, architect, memory, recovery, verify, next-pass, or one NN-layer). Layered docs for intent, policy, context, planning, routing, delegation, execution, MCP/tool boundaries, verification, memory, recovery, observability, human gates, release. Use for repo orchestration reviews, boundary work, memory/recovery design, permission-sensitive refactors.
CO-STAR UI Creator for React/Next.js: structured prompting to build or integrate UI (components, pages, design systems) or to create custom CO-STAR prompts. Use when the user wants to add hero sections, dashboards, design tokens, shadcn/Magic UI/Aceternity integration, Newsprint design system, or to draft their own CO-STAR prompt (Context, Objective, Style, Tone, Audience, Response). Always run discovery questions first, then plan, then implementation.
Context Engineering patterns for AI development and prompting. Use when the user wants to reduce tokens, avoid lost-in-the-middle, and structure prompts using Skeleton-of-Thought, token-efficient diff updates, XML tagging, symbolic variables, negative constraints, or LLMBundle-style context packaging.
Object-oriented design and Core Engineering principles for AI agents and developers. Use when the user asks about OOP (four pillars), SOLID, encapsulation, abstraction, inheritance, polymorphism, Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion, composition over inheritance, DRY, KISS, YAGNI, Law of Demeter, or association vs aggregation vs composition. Includes how each principle looks and example code.
Apply the "Family Values" design philosophy to every UI you build. Use this skill whenever creating frontends, components, apps, landing pages, dashboards, or any user-facing interface. Enforces three core principles (Simplicity, gradual revelation; Fluidity, seamless transitions; Delight, selective emphasis) so that every output feels crafted, intentional, and alive. Prevents generic, static, lifeless UI. Works alongside other skills like frontend-design, web-animation-design, and more.