using-loom-design
Route Loom product-definition requests to intent, specification, principles, visual design, architecture or design research skills when the needed skill is unclear.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- using-loom-design
- description
- Route Loom product-definition requests to intent, specification, principles, visual design, architecture or design research skills when the needed skill is unclear.
- user-invocable
- true
02 资源文件 1
- 参考文档README.md1.4 KB
03 SKILL.md 正文
Using Loom Design
Select the matching skill below and read its full SKILL.md before proceeding. An explicit leaf invocation goes directly to that skill; this router is not a prerequisite. Use the request and existing project artifacts to distinguish intent capture from specification.
| Request and artifact state | Load |
|---|---|
| A consequential evidence gap about users, outcomes, behavior options or design-owned architecture | design-research |
| A feature or change idea with no intent file yet | capture-intent |
A requested spec, or a confirmed intent marked needs-design: yes without a spec |
write-spec |
| Product principles are needed, or the user asks what governs a product, design, or engineering trade-off | product-principles |
| A visual design system: colors, type, layout, or component tokens | design-system |
| A project's architecture: module boundaries, tech choices, folder layout, or CI stages | architecture-design |
For implementation, delivery, or general toolbox requests, none of these routes applies. Leave the request to the host's skill selection. The selected skill owns its workflow, decisions, and output contract.
04 同仓库更多 Skills
using-loom-workflow
Route broad Loom workflow-tool requests to the right skill. Use when the request spans tools or the right workflow skill is unclear.
skill-retro
Review selected past or current Claude Code or Codex sessions against readable target skill sources and related integration. Produce source-linked proposals without applying changes.
recap-state
Give an in-session recap of current progress for 'where were we', '我們剛剛在幹嘛', '剛剛講到哪', '我跟丟了', 'ちょっと振り返って', '今どこだっけ', or '振り返り'. The built-in /recap is an away-summary.
project-retro
Review one current or specified coding session for source-backed project development improvements. Use for a requested retrospective, including 振り返り seeking improvements; not for current-progress recaps or recurring skill mining.
loom-visualization
Show comparisons, flows, decisions, states or reasoning chains as tables, ASCII or Mermaid in coding chat, including when a Loom station reports to the user (intent restatement, choices, acceptance test results); not Obsidian notes.
loom-memory
Record repo-wide lessons when saving to your own memory or asked to remember; recall, reconcile, or forget them when a task needs it.