菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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).
| name | using-loom-product-principles |
| description | 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. |
| version | 0.1.0 |
This is the loom-product-principles family entry — a thin router, not the skill that writes the constitution. It does intake + routing, then hands off.
User-facing narration in this intake follows
loom-pipeline/hooks/family-relay.md §Family relay discipline — reference it, do not copy its rules here.
Check the target repo against the loom family reception's on-ramp criteria
table — the single source of truth lives in
loom-pipeline/hooks/family-reception.md. Reference it, do not copy its
rows here. If docs/loom/PRINCIPLES.md already exists in the target repo,
confirm with the user whether this station's work is already done before
proceeding.
If the user's actual ask belongs to a different family entry, redirect instead of proceeding here:
using-loom-interface-designusing-loom-specusing-loom-codeusing-loom-discovery first; resume here with its output as seedBrief before you ask a complex product/principle fork. Before you ask the user a product/principle fork this complex — ≥3 trade-offs, ≥2 implementation paths, or architectural blast radius — run dev-workflow:brief-before-asking first instead of improvising the question.
Once intake confirms this is the right station, hand off to
product-principles — the member skill that elicits the idea, drafts the
## North Star, and derives the 3–7 falsifiable principles into
PRINCIPLES.md. This entry does not do that work itself.
PRINCIPLES.md itself — that is product-principles's job.loom-pipeline/hooks/family-reception.md as the single source of truth.product-principles — the harness invokes it
once intake and routing confirm this is the right station.