القائمة
Audit Gundam AGENTS, skills, and living documentation against current code after package moves or architectural changes. Use for semantic drift that deterministic link checks cannot prove.
التثبيت باستخدام 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 | doc-gardening |
| description | Audit Gundam AGENTS, skills, and living documentation against current code after package moves or architectural changes. Use for semantic drift that deterministic link checks cannot prove. |
Run deterministic checks first:
pnpm run check:harness
pnpm run check:doc-drift
Then inspect only the living docs affected by recent code changes:
docs/architecture.md and docs/design-docs/core-beliefs.md.AGENTS.md owns current instructions; adjacent CLAUDE.md is its alias. Do
not add divergent guidance to the alias. Keep completed execution plans as
historical records unless they claim to be current.
Report each finding with file and line, current evidence, proposed action, and whether it was fixed or needs owner input.