[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79A9D4WM4JE8BANDH4ARNT8":3,"skill-same:01M79A9D4WM4JE8BANDH4ARNT8":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79A9D4WM4JE8BANDH4ARNT8","matrize-brief",null,"Use to synthesise a design-system derivation into the approval artefact a human signs: target taxonomy, chosen direction, what is deliberately NOT adopted and why, and falsification criteria stating what would show the system does not hold. Trigger on 'write the design brief', 'what are we actually proposing', 'put this in front of the decision-maker', 'matrize brief'. Stops outright if any discovery artefact is missing, warns when the state-of-the-art survey is past its expiry, and writes nothing further until the approval block is signed — no objection is not approval.","Anselmoo\u002Fwerkstoff","Anselmoo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13209783?v=4","01M799YTB3D7RZ4P3B8CSR2X85","Anselm Hahn","01M799YTBRAM6719D9V0NRGB4R",1,"MIT","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Fplugins\u002Fmatrize\u002Fskills\u002Fmatrize-brief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: matrize-brief\ndescription: \"Use to synthesise a design-system derivation into the approval artefact a human signs: target taxonomy, chosen direction, what is deliberately NOT adopted and why, and falsification criteria stating what would show the system does not hold. Trigger on 'write the design brief', 'what are we actually proposing', 'put this in front of the decision-maker', 'matrize brief'. Stops outright if any discovery artefact is missing, warns when the state-of-the-art survey is past its expiry, and writes nothing further until the approval block is signed — no objection is not approval.\"\nargument-hint: \"\u003Csystem> [direction]\"\n---\n\nSynthesise discovery into a document a human can approve or reject. This is the\nhuman-in-the-loop gate, and it is the reason an n-proposal portfolio is a decision aid\nrather than a procrastination machine.\n\n## Hard input gate\n\nRead `\u003Croot>\u002Fsystem\u002FDECODE.md` and `\u003Croot>\u002Fsystem\u002FLEXIKON.md` first. **If either is\nmissing, say so and stop.** They come from `matrize-decode` and `matrize-name`; run\nthose. Do not synthesise around an absent input — a brief assembled from a missing\nmeasurement is the one artefact nobody can audit later.\n\nIf `\u003Croot>\u002Fsystem\u002FSTATE-OF-THE-ART.md` exists and is past its stated expiry, **warn and\nname the claim that forced it**. The style of a design system does not go stale; its\ndelivery chain does.\n\n## What the brief contains\n\n1. **Target taxonomy** — the named elements this system will carry, from `LEXIKON.md`.\n2. **Chosen direction**, stated in one paragraph a non-technical reader can hold.\n3. **What is deliberately not adopted, and why.** This section is not optional and not\n   decorative. A brief that only says yes has recorded no decision.\n4. **Falsification criteria** — what would show this system does not hold. Write these\n   as things that could actually be observed: \"a view needs two dominant action colours\n   and neither can be demoted\", \"the spacing scale cannot express the densest table we\n   ship\". A criterion nobody could ever observe is not a criterion.\n5. **Open questions**, carried verbatim from every grade-C-only finding and every\n   unanswered `preflight` question.\n6. **Coverage** — state explicitly which of the six required areas (states, contrast,\n   motion, inverse mode, content rules, provenance) the system covers and which it does\n   not. A system missing any of them is incomplete, and this is where that is said.\n   Check the asset classes too, against\n   `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fvocabulary\u002Fvisual-asset-taxonomy.md` — three are\n   missing from almost every design system and almost always needed: **empty state**,\n   **error state**, and **Open Graph image**. Treat them as mandatory coverage.\n\n## Phase entry criteria are gates, not aspirations\n\nThe three build methods — `echo`, `spread`, `retrofit` — read this brief and treat its\nentry criteria as binding. So write them as **checkable preconditions**: \"`tokens.json`\nvalidates against the DTCG profile\", \"every colour role has a computed contrast figure\",\nnot \"colours are finalised\".\n\nTell the approver plainly that they steer execution by editing this file. **An edited\nentry criterion is honoured; a note in a chat is not.**\n\n## The approval block\n\nEnd with it, and enter plan mode if the session supports it:\n\n```\nThis is a discussion basis, not a finished rulebook.\n\nDecision-maker: ______________________\nGate criteria:  feedback on \u003Cthe specific things> before production\nApproved by: ________________  Date: __________\nApproval covers: \u003Cdirection only> | \u003Cdirection and taxonomy> | \u003Cthe whole system>\n```\n\nThen **stop — write nothing further until the user explicitly approves.** \"No objection\"\nis not approval. `matrize-status` reads this block and reports whether it is signed.\n\n## This brief is a hypothesis\n\nSay so in the document. What the first real emit surfaces — a token the taxonomy cannot\nexpress, a role that turns out to be two roles, a reference that contradicts another —\nis *expected* to revise this brief. A regenerated brief after the first build is the\nnormal path, not a correction.\n\n## Staleness\n\nCompare modification times. If any input is newer than an existing `BRIEF.md`, the brief\nis being justifiably regenerated. If the brief is newer than every input and it is being\nre-run anyway, ask what changed. Either way, record the input timestamps in the header so\na reviewer can see what it was built from.\n","Synthesise discovery into a document a human can approve or reject. This is the\nhuman-in-the-loop gate, and it is the reason an n-proposal portfolio is a decision aid\nrather than a procrastination machine.\n\n## Hard input gate\n\nRead `\u003Croot>\u002Fsystem\u002FDECODE.md` and `\u003Croot>\u002Fsystem\u002FLEXIKON.md` first. **If either is\nmissing, say so and stop.** They come from `matrize-decode` and `matrize-name`; run\nthose. Do not synthesise around an absent input — a brief assembled from a missing\nmeasurement is the one artefact nobody can audit later.\n\nIf `\u003Croot>\u002Fsystem\u002FSTATE-OF-THE-ART.md` exists and is past its stated expiry, **warn and\nname the claim that forced it**. The style of a design system does not go stale; its\ndelivery chain does.\n\n## What the brief contains\n\n1. **Target taxonomy** — the named elements this system will carry, from `LEXIKON.md`.\n2. **Chosen direction**, stated in one paragraph a non-technical reader can hold.\n3. **What is deliberately not adopted, and why.** This section is not optional and not\n   decorative. A brief that only says yes has recorded no decision.\n4. **Falsification criteria** — what would show this system does not hold. Write these\n   as things that could actually be observed: \"a view needs two dominant action colours\n   and neither can be demoted\", \"the spacing scale cannot express the densest table we\n   ship\". A criterion nobody could ever observe is not a criterion.\n5. **Open questions**, carried verbatim from every grade-C-only finding and every\n   unanswered `preflight` question.\n6. **Coverage** — state explicitly which of the six required areas (states, contrast,\n   motion, inverse mode, content rules, provenance) the system covers and which it does\n   not. A system missing any of them is incomplete, and this is where that is said.\n   Check the asset classes too, against\n   `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fvocabulary\u002Fvisual-asset-taxonomy.md` — three are\n   missing from almost every design system and almost always needed: **empty state**,\n   **error state**, and **Open Graph image**. Treat them as mandatory coverage.\n\n## Phase entry criteria are gates, not aspirations\n\nThe three build methods — `echo`, `spread`, `retrofit` — read this brief and treat its\nentry criteria as binding. So write them as **checkable preconditions**: \"`tokens.json`\nvalidates against the DTCG profile\", \"every colour role has a computed contrast figure\",\nnot \"colours are finalised\".\n\nTell the approver plainly that they steer execution by editing this file. **An edited\nentry criterion is honoured; a note in a chat is not.**\n\n## The approval block\n\nEnd with it, and enter plan mode if the session supports it:\n\n```\nThis is a discussion basis, not a finished rulebook.\n\nDecision-maker: ______________________\nGate criteria:  feedback on \u003Cthe specific things> before production\nApproved by: ________________  Date: __________\nApproval covers: \u003Cdirection only> | \u003Cdirection and taxonomy> | \u003Cthe whole system>\n```\n\nThen **stop — write nothing further until the user explicitly approves.** \"No objection\"\nis not approval. `matrize-status` reads this block and reports whether it is signed.\n\n## This brief is a hypothesis\n\nSay so in the document. What the first real emit surfaces — a token the taxonomy cannot\nexpress, a role that turns out to be two roles, a reference that contradicts another —\nis *expected* to revise this brief. A regenerated brief after the first build is the\nnormal path, not a correction.\n\n## Staleness\n\nCompare modification times. If any input is newer than an existing `BRIEF.md`, the brief\nis being justifiably regenerated. If the brief is newer than every input and it is being\nre-run anyway, ask what changed. Either way, record the input timestamps in the header so\na reviewer can see what it was built from.\n",{"name":5,"description":7,"argument-hint":24},"\u003Csystem> [direction]","main","6158c1e4e112c06af2c7ac01b13b2ed7214c0fcf","plugins\u002Fmatrize\u002Fskills\u002Fmatrize-brief",0,"https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff","https:\u002F\u002Fanselmoo.github.io\u002Fwerkstoff\u002F","https:\u002F\u002Fgithub.com\u002FAnselmoo","Likes to Develop","2026-11-02 04:20:59",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Anselmoo\u002Fwerkstoff --skill matrize-brief",{"tool":40,"command":41},"bunx","bunx skills add Anselmoo\u002Fwerkstoff --skill matrize-brief",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Anselmoo\u002Fwerkstoff --skill matrize-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Fplugins\u002Fmatrize\u002Fskills\u002Fmatrize-brief\u002FSKILL.md",true,[],[49,56,63,68,73,78],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M79AJTRBNBX03WWKYJ8ENM45","toy-check","A skill that checks things in the repository and reports what it finds.","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fworkflows\u002Ffixtures\u002Ftoy-plugin\u002Fskills\u002Ftoy-check\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79AJS292F3HTDRXWZVRSN5B","demo-check","Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-uncompleted-run\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":64,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79AJP4TFQXKT1AAK1WC1JYK","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-stale-lock\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":69,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79AJM6Y50WP3G2BR4H0M60Z","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-preflight-mixed\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":74,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AJGR6DMT8KCCK071V78XM","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-hooks-shape\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AJBJ4CHC4PZVWKERWF3HF","zirkel-verify-assumptions","Checks exactly ONE named assumption against real evidence in at most 3 steps and reports one outcome: confidence raised (>=90), reading changed, or still unresolved. Use to resolve a single load-bearing uncertainty — typically a blocking entry surfaced by zirkel-clarify-scope: \"verify this one assumption\", \"is it actually true that X\", \"check this before we rely on it\". For multiple uncertainties, invoke once per uncertainty — the step budget is never shared.","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Fplugins\u002Fzirkel\u002Fskills\u002Fzirkel-verify-assumptions\u002FSKILL.md",[],[]]