القائمة
Apply the Reality Reprojection design system — auto-detects whether to generate new components, convert existing code, or review compliance. Single entry point that routes to the correct sub-skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | apply |
| description | Apply the Reality Reprojection design system — auto-detects whether to generate new components, convert existing code, or review compliance. Single entry point that routes to the correct sub-skill. |
| argument-hint | ["describe what you need"] |
You are the entry point for the Reality Reprojection design system plugin. Your job is to determine what the user needs and route to the correct skill.
Analyze $ARGUMENTS and classify the user's intent:
| Intent | Signal Words | Route To |
|---|---|---|
| Setup | "setup", "bootstrap", "install", "init", "add to project", "get started" | reality-reprojection:setup |
| Generate | "create", "build", "make", "add", "I need", "generate", "new", "component", "page", "form", "card", "button" | reality-reprojection:generate |
| Convert | "convert", "transform", "migrate", "apply to", "make it match", "rewrite", "update to", "refactor to" + file path references | reality-reprojection:convert |
| Review | "check", "audit", "review", "compliance", "does this follow", "validate", "inspect", "scan" | reality-reprojection:review |
$ARGUMENTS throughWhen you cannot determine intent, ask:
I can help you with the Reality Reprojection design system in four ways:
- Setup — Bootstrap the design system into your project (CSS + fonts)
- Generate — Create new components from a description
- Convert — Transform existing code to use the design system
- Review — Audit code for design system compliance
Which would you like?
reality-reprojection:setupreality-reprojection:generatereality-reprojection:convertreality-reprojection:reviewreality-reprojection:generatereality-reprojection:convertreality-reprojection:reviewreality-reprojection:setupUse the Skill tool to invoke the target skill:
Skill: reality-reprojection:generate
Args: [pass through the user's original arguments]
Do NOT attempt to generate, convert, or review code yourself. Always route to the specialized skill.
Run quality checks on a task's implementation before it closes to done. Triggers: 'is this ready?', 'run the review gate', 'check my work', 'I think this is done'. Reviews code + spec adherence, runs tests/build. Design review uses taskmaster:spec-review.
Log a lightweight idea into .taskmaster/ideas/. Triggers: '/add-idea', 'save this as an idea', 'remember this idea', 'log this idea', or something worth keeping, not yet a task. Only way - not backlog_idea_create directly.
Log/update/close project bugs in .taskmaster/bugs/. Triggers: 'log a bug', 'this is a bug', 'track this defect', 'I found a bug', 'shelve this for later', 'list open bugs', 'promote B-XX', 'close B-XX'. Also for ambiguous 'issue' phrasing lacking recurring/systemic/outstanding evidence - falls back here. Only correct way to transition a project Bug.
Scan the codebase for TODO/FIXME/HACK/XXX and cross-reference the backlog. Triggers: 'check todos', 'are my todos tracked', 'scan for todos', 'todo audit', 'what's untracked'.
Write/resolve/drop project decisions in .taskmaster/decisions/. Invoke when about to write an inline option menu - route here, not Options: in chat. Also 'choose between', 'pick an option', 'decide on', 'open question', 'resolve DEC-X', 'drop DEC-X'. Only correct way - do not call backlog_decision_create directly.
Close out a work session. Triggers: 'end session', 'I'm done for today', 'let's wrap up', 'mark this task done', 'save progress'. ONLY correct way to mark tasks done/in-review with a session record.