菜单
Router for loom-interface-design — design a product's interface/interaction/UX in any modality (GUI/TUI/CLI). Routes to design-system (→ DESIGN.md) + interaction-flows (→ ui-flows.md). Use for 'design the UI/UX', screen flow, TUI/CLI layout.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | using-loom-interface-design |
| description | Router for loom-interface-design — design a product's interface/interaction/UX in any modality (GUI/TUI/CLI). Routes to design-system (→ DESIGN.md) + interaction-flows (→ ui-flows.md). Use for 'design the UI/UX', screen flow, TUI/CLI layout. |
| version | 0.3.0 |
Before routing to design work, walk these three steps in order. User-facing
narration during this routing follows loom-pipeline/hooks/family-relay.md §Family relay discipline
(the SSOT; do not copy its rollup-card body here).
loom-pipeline/hooks/family-reception.md — the SSOT; do not copy its
rows here). If the repo has no docs/loom/PRINCIPLES.md and the work is
product-shaped, recommend using-loom-product-principles first —
surface it once, then proceed either way per the reception's
recommend-once rule.using-loom-spec. If the ask is actually to write or change code,
redirect to using-loom-code.Three load-bearing rules:
DESIGN.md) and how interaction flows are expressed.PRINCIPLES.md (produced by loom-product-principles:product-principles) as the governing context. Every design decision is checked against it — the design must not contradict the North Star or any non-negotiable principle. If PRINCIPLES.md is absent, surface that gap; the principles layer comes first.design-system for the static design-system artifact and interaction-flows for the dynamic interaction/flow artifact. Both are governed by the recorded modality + PRINCIPLES.md.dev-workflow:brief-before-asking first instead of improvising the question.Skipping the modality step or the PRINCIPLES governance = violation. "It's obviously a GUI, skip asking" / "I don't need the principles" are rationalizations — record the modality (default GUI) and read PRINCIPLES.md first.
When instructions conflict, follow this order:
CLAUDE.md / project conventions — local rules always win.PRINCIPLES.md — the product constitution governs all design.| Modality | What it is | Design-system artifact |
|---|---|---|
| GUI (default) | Graphical screens — web / mobile / desktop | DESIGN.md |
| TUI | Terminal UI — panes, keybindings, in-terminal layout | design-system artifact (TUI shape) |
| CLI | Command-line surface — commands, flags, output format | design-system artifact (CLI shape) |
Ask the user once; if unspecified, default to GUI. Record the answer before routing. The modality is passed to both generate skills.
Walk through these stages in order. Skip a stage only when its precondition is already met.
| # | Stage | Skill (target) | Output |
|---|---|---|---|
| 0 | Modality | (this router — Step 0) | recorded modality (GUI / TUI / CLI) |
| 1 | Static design system | design-system | the design-system artifact (GUI → DESIGN.md) |
| 2 | Interaction / flows | interaction-flows | ui-flows.md |
| 3 | Review (writer≠judge gate) | design-critic | gap-hunted design + ## Blind spots |
Stages 1–2 read the product's PRINCIPLES.md as governing context.
Stage 3 — the design station's completeness gate. Once design-system +
interaction-flows have emitted their artifacts, route to design-critic for an
adversarial heuristic-evaluation pass (writer≠judge) that hunts SURFACE omissions —
undrawn empty/error/loading states, navigational dead-ends, unreachable screens,
missing entry/exit — before ui-flows.md is handed to loom-spec:spec-expansion.
It critiques the surface only; behavioral fan-out stays downstream.
Stage-3 resolution rule. design-critic ends with a two-valued verdict:
NEEDS_REVISION → route back to design-system / interaction-flows for the
flagged surfaces, then re-run the critic; PASS_WITH_NOTES → the change-folder
proceeds (ui-flows.md hands to loom-spec:spec-expansion). There is no bare
PASS — the critic never claims the surface is complete.
| Harness | Mechanism |
|---|---|
| Claude Code | Use the Skill tool, e.g. Skill(skill: "design-system"). |
| Codex CLI | Use the skill tool (Codex shape). |
If the user types /skill-name, that is an explicit invocation — load it via the Skill tool. Do not guess names that are not listed above.
| Agent says | Reality | Correct response |
|---|---|---|
| "It's clearly a GUI, no need to ask the modality." | Modality is load-bearing; assuming it skips the recorded contract. | Ask once; if no answer, default GUI and record it. |
| "I'll design without reading PRINCIPLES.md." | The design must be checked against the product constitution. | Read PRINCIPLES.md first; surface it if absent. |
| "Design system and flows are the same artifact." | Static system ≠ dynamic interaction. | Route design-system and interaction-flows separately. |
loom-product-principles:product-principles — produces the PRINCIPLES.md this toolkit reads as governing context. The principles layer comes before interface design; this toolkit consumes its output, never duplicates it.loom-spec:spec-expansion) consumes ui-flows.md; the code / frontend layer consumes the DESIGN.md tokens directly at implementation time (a human / code-level seam, not a loom-code skill).design-system and interaction-flows.PRINCIPLES.md — that belongs to loom-product-principles.Append-only bitemporal store for validated operational-KPI series-points (US SEC primary-source layer). Persists file-per-series JSON keyed by company+kpi_id under a durable DATA dir, keeping full history so a restatement appends a superseding record and a point-in-time query sees only what was known then. 営業 KPI 二時制追加専用ストア。營運 KPI 雙時態 唯附加儲存層。
Layer-1 unified data fetch across US/JP/TW/KR/CN equities + macro — one pack.py facade, auto market detection from ticker suffix (.TW/.KS/.SS/.T/ bare-4-digit), 7 pack types (snapshot / memo-fetch / comps-multiples / screener-batch / regime-pack / kpi-quarterly / kpi-topline-backfill). Emits a raw data pack（原始資料包，非渲染卡片）— structured JSON straight from source clients including SEC EDGAR, EDINET, TWSE, and FRED (+14 more) through a shared cache layer; use this for a 資料層 health check, verifying cache writes/hits (快取), or fetching by source name (EDINET/EDGAR/TWSE/etc). Pure I/O, no analysis — for regime classification/判斷 (e.g. an Investment Clock verdict), use analysis-macro-regime instead. Consolidates the per-country data-{us,jp,tw,kr,cn} client scripts behind one CLI + shared cache layer.
Deliver a Mental-Model-first briefing before asking the user to decide a non-trivial engineering fork — the default, not optional. Also fires reactively when they're lost on the question, the explanation, or the stakes — including a 2nd consecutive check-question, which trips the repeated-confusion guard back to the Mental Model.
Family entry router for loom-discovery, the loom problem-space station. Use when unsure which discovery skill applies, or when a product idea's target users are still unclear (說不清是給誰用的 / not sure who this is for / 誰のためかまだ不明) — comes BEFORE product-principles. Routes worth-doing asks (值不值得做 / worth my time budget) to business-value, and user-needs asks (需求研究 / user research / ユーザーインサイト) to user-insights. Non-discovery asks redirect to their family entries. Members share no artifact and no agent.
The loom-product-principles family entry: intake + routing. Start here on a new product/feature idea when 不確定從哪開始 / 'where do I start' — checks the on-ramp criteria, then hands off to the member skill.
Use when starting spec work and unsure which loom-spec skill applies. Family entry router — routes to spec-expansion (draft/expand a spec from a seed) or completeness-critic (critique an existing draft for omissions).