القائمة
The feature or component to colorize (optional)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Single owner for everything related to a specific Disney Lorcana card in `packages/lorcana/lorcana-cards` — authoring, debugging, triaging, generating, and any bounded engine or types extension required to make the printed text work. Use whenever the unit of work is "this card".
Explain and cite Disney Lorcana rules using indexed references, and produce implementation-ready behavior constraints for card development. Use when answering mechanic questions, resolving card interactions, or deriving test/implementation constraints from official rules.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
| name | colorize |
| description | The feature or component to colorize (optional) |
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.
You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and especially existing brand colors.
Attempt to gather these from the current thread or codebase.
Do NOT proceed until you have answers. Guessing leads to generic AI slop colors.
Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts.
Analyze the current state and identify opportunities:
Understand current state:
Identify where color adds value:
If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
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.