[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQKJSDRD5T2KKWTZ2278VR":3,"skill-same:01M7CQKJSDRD5T2KKWTZ2278VR":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CQKJSDRD5T2KKWTZ2278VR","product-principles",null,"Ratify PRINCIPLES.md. Use when a product needs principles or someone asks what should govern product, design, or engineering trade-offs.","kouko\u002Floom-plugins","kouko","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1480254?v=4","01M7CQCPAJR9C92XDGR0QDCQ98","01M7CQCPB8FTVY1BT26ENK1YP4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fproduct-principles\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: product-principles\ndescription: |\n  Ratify PRINCIPLES.md. Use when a product needs principles or someone asks what should govern product, design, or engineering trade-offs.\nversion: 1.0.0\n---\n\n## What this tool does\n\nWhen an outcome priority depends on a consequential evidence gap, identify\nthat decision and use `loom-design:design-research` as needed. Reuse adequate\nevidence directly; return findings or uncertainty to this task while preserving\nthe user's preferences, authorization and authority to confirm principles.\n\nRelative paths in this document are relative to this skill's own directory.\n\nDeliver local documents with actual absolute paths from the active worktree or\nexternal location, including in copyable instructions. For known local Markdown\nsupport, use the document's project-relative path as link text (external files:\nbasename) and absolute targets; otherwise show full absolute paths. Enclose\ntargets with spaces in angle brackets: `[doc.md](\u003C\u002Fworktree name\u002Fdoc.md>)`. Preserve bundled references, stored\nrelative paths, quoted examples and incidental filenames.\n\nThe user names a product idea. You run one short interview, write\n`PRINCIPLES.md` at the consumer project's root, restate it, and — on\n\"yes\" — write the `ratified-by:` line that makes it the repo's standing\nconstitution. You never invent a principle the user did not confirm, and\nyou never ask them to judge anything but their own answers.\n\nMost of the time you are not invoked directly: `capture-intent` (or, when\n`loom-design` is absent, `loom-code`'s `write-plan`) runs this same\ninterview inline, in the same conversation as decision point ①, the first\ntime a `kind: product` change meets a repo with no ratified\n`PRINCIPLES.md`. **The interview is the same one `loom-code`'s\n`write-plan` runs when `loom-design` is absent** — this tool exists so a\nuser can also run it stand-alone, on request, before any change is in\nflight.\n\n## Step 1 — Run the interview\n\nRead `..\u002Fcapture-intent\u002Ftemplates\u002FPRINCIPLES-interview.md` and ask\nexactly its five questions, in the user's own words, until each answer is\nclear. One line each on their intent:\n\n1. **Who** it is for, and how they solve this today without it.\n2. **The one thing** that cannot be compromised (fast, accurate, cheap,\n   private, offline, good-looking) — ranked.\n3. **What it explicitly will not do.**\n4. **The worst failure**, and who it hurts.\n5. **What is already fixed** and cannot change (platform, language, a\n   paid service, a data format).\n\nPush until each answer is falsifiable — a later decision can be checked\nagainst it, not just admired.\n\n## Step 2 — Write PRINCIPLES.md\n\nEmit `PRINCIPLES.md` at the consumer project's root (not per-feature),\nwith exactly these five `##` sections, in this order:\n\n```\n# Product principles\n## Who\n## Non-negotiables (ordered)\n## Won't do\n## Failure we must avoid\n## Fixed choices\n```\n\n`## Non-negotiables` is an ordered list of **at least three** entries,\neach **falsifiable**: state the choice and a concrete pair that would\ntell a stranger it held or broke. For example — good: \"offline-first: the\napp must complete a save with the network off (bad: 'the app should feel\nfast').\" A non-negotiable with no such pair is a slogan, not a principle;\npush back and ask again rather than write it down.\n\n## Step 3 — Restate and ratify\n\nRead the whole file back to the user in their own words — not a diff, the\nactual sections. On a correction, fix it and read back again; there is no\nround limit. On \"yes\", write one line at the top of the file, directly\nunder the title:\n\n```\nratified-by: \u003Cname> \u003Cdate>\n```\n\n`\u003Cname>` is the user's own name or handle; `\u003Cdate>` is today,\n`YYYY-MM-DD`. A file with no `ratified-by:` line, or one whose\n`## Non-negotiables` has fewer than three entries, is not ratified —\n`capture-intent` checks both conditions itself and runs the interview\nbefore a `kind: product` change goes on against an unratified file;\nnothing here can talk it out of that.\n\n## Step 4 — Commit\n\n```\ngit add PRINCIPLES.md\ngit commit -m \"docs(loom): PRINCIPLES.md ratified\"\n```\n\n## Downstream — how the rest of the flow uses it\n\n`PRINCIPLES.md` is the standing, always-on constraint every later station\nreads: `write-spec` loads it before drafting `Requirements`; a product\nchange with no ratified copy is refused there\n(`standing.product-principles-reject`), never silently allowed through.\nAt `closing-review`, the `principles-conformance` dimension scores the diff\nagainst these Non-negotiables; when nothing in the file speaks to a given\nfinding, the dimension is scored **N\u002FA with a one-line reason**, never\nforced to a number it cannot support. Engineering-only changes are never\nblocked by a missing or unratified file — the reject rule fires only on\n`kind: product`.\n\n\u003C!-- gate: product-principles.ratified-requires-user-yes -->\n**No `ratified-by:` line is ever written without the user having said\nyes to the restatement in Step 3.** Writing it on an assumed confirmation\nmakes a constitution nobody actually agreed to.\n","## What this tool does\n\nWhen an outcome priority depends on a consequential evidence gap, identify\nthat decision and use `loom-design:design-research` as needed. Reuse adequate\nevidence directly; return findings or uncertainty to this task while preserving\nthe user's preferences, authorization and authority to confirm principles.\n\nRelative paths in this document are relative to this skill's own directory.\n\nDeliver local documents with actual absolute paths from the active worktree or\nexternal location, including in copyable instructions. For known local Markdown\nsupport, use the document's project-relative path as link text (external files:\nbasename) and absolute targets; otherwise show full absolute paths. Enclose\ntargets with spaces in angle brackets: `[doc.md](\u003C\u002Fworktree name\u002Fdoc.md>)`. Preserve bundled references, stored\nrelative paths, quoted examples and incidental filenames.\n\nThe user names a product idea. You run one short interview, write\n`PRINCIPLES.md` at the consumer project's root, restate it, and — on\n\"yes\" — write the `ratified-by:` line that makes it the repo's standing\nconstitution. You never invent a principle the user did not confirm, and\nyou never ask them to judge anything but their own answers.\n\nMost of the time you are not invoked directly: `capture-intent` (or, when\n`loom-design` is absent, `loom-code`'s `write-plan`) runs this same\ninterview inline, in the same conversation as decision point ①, the first\ntime a `kind: product` change meets a repo with no ratified\n`PRINCIPLES.md`. **The interview is the same one `loom-code`'s\n`write-plan` runs when `loom-design` is absent** — this tool exists so a\nuser can also run it stand-alone, on request, before any change is in\nflight.\n\n## Step 1 — Run the interview\n\nRead `..\u002Fcapture-intent\u002Ftemplates\u002FPRINCIPLES-interview.md` and ask\nexactly its five questions, in the user's own words, until each answer is\nclear. One line each on their intent:\n\n1. **Who** it is for, and how they solve this today without it.\n2. **The one thing** that cannot be compromised (fast, accurate, cheap,\n   private, offline, good-looking) — ranked.\n3. **What it explicitly will not do.**\n4. **The worst failure**, and who it hurts.\n5. **What is already fixed** and cannot change (platform, language, a\n   paid service, a data format).\n\nPush until each answer is falsifiable — a later decision can be checked\nagainst it, not just admired.\n\n## Step 2 — Write PRINCIPLES.md\n\nEmit `PRINCIPLES.md` at the consumer project's root (not per-feature),\nwith exactly these five `##` sections, in this order:\n\n```\n# Product principles\n## Who\n## Non-negotiables (ordered)\n## Won't do\n## Failure we must avoid\n## Fixed choices\n```\n\n`## Non-negotiables` is an ordered list of **at least three** entries,\neach **falsifiable**: state the choice and a concrete pair that would\ntell a stranger it held or broke. For example — good: \"offline-first: the\napp must complete a save with the network off (bad: 'the app should feel\nfast').\" A non-negotiable with no such pair is a slogan, not a principle;\npush back and ask again rather than write it down.\n\n## Step 3 — Restate and ratify\n\nRead the whole file back to the user in their own words — not a diff, the\nactual sections. On a correction, fix it and read back again; there is no\nround limit. On \"yes\", write one line at the top of the file, directly\nunder the title:\n\n```\nratified-by: \u003Cname> \u003Cdate>\n```\n\n`\u003Cname>` is the user's own name or handle; `\u003Cdate>` is today,\n`YYYY-MM-DD`. A file with no `ratified-by:` line, or one whose\n`## Non-negotiables` has fewer than three entries, is not ratified —\n`capture-intent` checks both conditions itself and runs the interview\nbefore a `kind: product` change goes on against an unratified file;\nnothing here can talk it out of that.\n\n## Step 4 — Commit\n\n```\ngit add PRINCIPLES.md\ngit commit -m \"docs(loom): PRINCIPLES.md ratified\"\n```\n\n## Downstream — how the rest of the flow uses it\n\n`PRINCIPLES.md` is the standing, always-on constraint every later station\nreads: `write-spec` loads it before drafting `Requirements`; a product\nchange with no ratified copy is refused there\n(`standing.product-principles-reject`), never silently allowed through.\nAt `closing-review`, the `principles-conformance` dimension scores the diff\nagainst these Non-negotiables; when nothing in the file speaks to a given\nfinding, the dimension is scored **N\u002FA with a one-line reason**, never\nforced to a number it cannot support. Engineering-only changes are never\nblocked by a missing or unratified file — the reject rule fires only on\n`kind: product`.\n\n\u003C!-- gate: product-principles.ratified-requires-user-yes -->\n**No `ratified-by:` line is ever written without the user having said\nyes to the restatement in Step 3.** Writing it on an assumed confirmation\nmakes a constitution nobody actually agreed to.\n",{"name":5,"version":23,"description":24},"1.0.0","Ratify PRINCIPLES.md. Use when a product needs principles or someone asks what should govern product, design, or engineering trade-offs.\n","main","3b1a9972644517911454530dc1876f88525b1f37","loom-design\u002Fskills\u002Fproduct-principles","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins","https:\u002F\u002Fgithub.com\u002Fkouko","2026-11-15 00:45:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add kouko\u002Floom-plugins --skill product-principles",{"tool":37,"command":38},"bunx","bunx skills add kouko\u002Floom-plugins --skill product-principles",{"tool":40,"command":41},"pnpm","pnpm dlx skills add kouko\u002Floom-plugins --skill product-principles","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fproduct-principles\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",1419,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fproduct-principles\u002FREADME.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7CQNVD2W5MP7PKX3MD0YSQE","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.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fusing-loom-workflow\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7CQNNTPVG52CS2C6Q9HJ2E2","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.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fskill-retro\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7CQNHR1BDKJ63CC4R1RY9GE","recap-state","Give an in-session recap of current progress for 'where were we', '我們剛剛在幹嘛', '剛剛講到哪', '我跟丟了', 'ちょっと振り返って', '今どこだっけ', or '振り返り'. The built-in \u002Frecap is an away-summary.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Frecap-state\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7CQNE1A9272WPRE1MM3JRFK","project-retro","Review one current or specified coding session for source-backed project\ndevelopment improvements. Use for a requested retrospective, including\n振り返り seeking improvements; not for current-progress recaps or recurring skill mining.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fproject-retro\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7CQNACJB36T0A039HT89P38","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.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-visualization\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7CQN7TVS0XF44JXQBWA32Z1","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.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-memory\u002FSKILL.md",[],[]]