ワンクリックで
colorize
Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
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 | colorize |
| description | Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive. |
| args | [{"name":"target","description":"The feature or component to colorize (optional)","required":false}] |
| user-invocable | true |
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.
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. Additionally gather: existing brand colors.
Analyze the current state and identify opportunities:
Understand current state:
Identify where color adds value:
If any of these are unclear from the codebase, {{ask_instruction}}
CRITICAL: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose.
Create a purposeful color introduction plan:
IMPORTANT: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more.
Add color systematically across these dimensions:
State indicators:
Status badges: Colored backgrounds or borders for states (active, pending, completed, etc.)
Progress indicators: Colored bars, rings, or charts showing completion or health
#f5f5f5) with warm neutrals (oklch(97% 0.01 60)) or cool tints (oklch(97% 0.01 250))Use OKLCH for color: It's perceptually uniform, meaning equal steps in lightness look equal. Great for generating harmonious scales.
Ensure color addition improves rather than overwhelms:
NEVER:
#000) or pure white (#fff) for large areasTest that colorization improves the experience:
Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional.