Name: detail
Author: RebelliousSmile

Imported from RebelliousSmile/my-claude-marketplace (plugins/design/skills/detail/SKILL.md). Install upstream with npx skills add RebelliousSmile/my-claude-marketplace --skill detail. Copyright stays with the author.

Detail

flowchart LR
  describe([descriptive question]) --> explain --> stop([stop])
  plan([workflow question]) --> route --> stop

Read only the next action selected by the user's question.

Action	Does
explain	explain one capability or the complete map
route	route an explicit workflow request from observed project state

Routing

"explain the design plugin or one capability" → explain
"which complete workflow should I run" → route

Transversal rules

Resolve the plugin root using host-portability.md before loading bundled tools or references.
Stay read-only and never invoke the capabilities being described.
A precise production, critique, freeze, audit, or rendering request belongs directly to that capability; do not intercept it here.
Emit the full five-capability recipe only when the user explicitly asks for a complete design-system lifecycle.
Keep wireframes and harness outside that lifecycle. Name the optional wireframes → review → harness prerequisite only when an interface still needs exploration.
Read funnel-map.md for capability boundaries and workflow-classes.md for complete lifecycle routes.

{ "ocm": "1", "id": "rebellioussmile-my-claude-marketplace-detail", "kind": "skill", "name": "detail", "description": "Explains the design capabilities or routes an explicit end-to-end design-system request without executing it. Use when the user asks what to run, how the workflow fits together, or which path matches the project state.", "publisher": "RebelliousSmile", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "ui", "contract", "design-system", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Explains the design capabilities or routes an explicit end-to-end design-system request without executing it. Use when the user asks what to run, how the workflow fits together, or which path matches the project state." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/RebelliousSmile/my-claude-marketplace", "path": "plugins/design/skills/detail/SKILL.md", "ref": "c9bc2fdc1c3e5c9d8d7e6c2525b611c035e9d274", "url": "https://github.com/RebelliousSmile/my-claude-marketplace/blob/c9bc2fdc1c3e5c9d8d7e6c2525b611c035e9d274/plugins/design/skills/detail/SKILL.md", "key": "RebelliousSmile/my-claude-marketplace/plugins/design/skills/detail/SKILL.md" } }, "instructions": "# Detail\n\n```mermaid\nflowchart LR\n describe([descriptive question]) --> explain --> stop([stop])\n plan([workflow question]) --> route --> stop\n```\n\nRead only the next action selected by the user's question.\n\n| Action | Does |\n| --- | --- |\n| explain | explain one capability or the complete map |\n| route | route an explicit workflow request from observed project state |\n\n## Routing\n\n- \"explain the design plugin or one capability\" → `explain`\n- \"which complete workflow should I run\" → `route`\n\n## Transversal rules\n\n- Resolve the plugin root using [host-portability.md](../../references/host-por", "cost": { "context_tokens": 326 } }

detail

About

Detail

Routing

Transversal rules

Use it

Manifest

Reviews