ワンクリックで
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 職業分類に基づく
Builds or restructures a Sapphire harness. Use when a task needs a strict multi-agent workflow, reusable project skills, or a stronger orchestration design for non-trivial work.
Design and implement production-grade backend systems with strict contracts, clear boundaries, strong validation, disciplined testing, observability, resilience, and maintainable architecture across languages and frameworks.
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
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`).
| name | bolder |
| description | Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. |
| args | [{"name":"target","description":"The feature or component to make bolder (optional)","required":false}] |
| user-invocable | true |
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 learn-frontend-context first.
Analyze what makes the design feel too safe or boring:
Identify weakness sources:
Understand the context:
If any of these are unclear from the codebase, {{ask_instruction}}
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."
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.