[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4HGKJWQVMJYSTA5TRPWNK":3,"skill-same:01M6C4HGKJWQVMJYSTA5TRPWNK":67},{"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":28,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6C4HGKJWQVMJYSTA5TRPWNK","wtf",null,"WHEN the immediately previous LLM response was unclear, too dense, or hard to follow; NOT for doing the work that response describes, and NOT for writing a new document from it; returns a plain UK English re-explanation that keeps every detail that changes how the response should be understood.","mintuz\u002Fskills","mintuz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F447031?v=4","01M6BVWJYSVR4XQC9AQCEMWQRG","Adam Bulmer","01M6C4DCXKNYZB281YB3PZDJJG",35,"MIT","https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fcore\u002Fskills\u002Fwtf\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[5,29,30,31,32],"writing","how","returns","work","2026-11-10 10:12:30",false,"---\nname: wtf\ndescription: >\n  WHEN the immediately previous LLM response was unclear, too dense, or hard to\n  follow; NOT for doing the work that response describes, and NOT for writing a\n  new document from it; returns a plain UK English re-explanation that keeps\n  every detail that changes how the response should be understood.\n---\n\n# WTF\n\n## Procedure\n\n1. Read the immediately previous LLM response.\n2. If no previous LLM response exists, say there is nothing to re-explain, ask which response or text to explain, and stop. Do not invent, quote, or guess a previous response.\n3. If the response uses domain terms, look in the current project for `CONTEXT.md`, `GLOSSARY.md`, `UBIQUITOUS_LANGUAGE.md`, and `*.glossary.yml` files. Take canonical terms and meanings from them, but add no information from them that the previous response did not contain.\n4. Re-explain the previous response with clearer structure and simpler wording.\n5. Preserve every detail that changes how the response should be understood: each condition, causal link, uncertainty, constraint, exception, dependency, example, technical identifier, value, unit, warning, scope, conclusion, and relationship.\n6. Attribute operational actions to the previous response so the explanation cannot read as a new task. Do not perform a new task.\n\n## Writing Rules\n\nWrite in a style inspired by ASD-STE100 Simplified Technical English.\n\n- Use active voice and plain UK English.\n- Write for a reading level between Key Stage 4 and Further Education.\n- Use the same term for the same concept throughout.\n- Use precise, technically accurate wording; when clarity and brevity conflict, prioritise accuracy and unambiguous meaning.\n- Use short sentences where possible; put one main action in each sentence.\n- Use the imperative for direct instructions.\n- Define an uncommon abbreviation or specialist term at first use.\n\n## Clarity Controls\n\n- Put each prerequisite, condition, warning, or limitation before the action it governs.\n- Replace a prose noun with the canonical term when a terminology file gives one; otherwise use the previous response's own nouns.\n- Keep every literal identifier, path, command, and value exactly as the previous response wrote it.\n- Replace vague pronouns with the specific subject.\n- Remove idioms, unnecessary synonyms, ambiguous references, and complex noun clusters.\n- Add no information absent from the previous response.\n- State uncertainty where the previous response was uncertain.\n- Report a contradiction in the previous response as a contradiction. Do not resolve it, choose a side, or state what the previous response intended. State that the previous response does not establish which statement is correct.\n- Keep the scope of an absolute word such as `only`, `never`, `all`, or `always`; never weaken it to `usually` or `mostly`.\n\n## Completion Criterion\n\nThe explanation is complete when it re-explains the immediately previous LLM response in clearer plain language, preserves every detail that changes its meaning, and starts no new work.\n\nWith no previous LLM response, the reply is complete when it says there is nothing to re-explain and asks which response or text to explain.\n","# WTF\n\n## Procedure\n\n1. Read the immediately previous LLM response.\n2. If no previous LLM response exists, say there is nothing to re-explain, ask which response or text to explain, and stop. Do not invent, quote, or guess a previous response.\n3. If the response uses domain terms, look in the current project for `CONTEXT.md`, `GLOSSARY.md`, `UBIQUITOUS_LANGUAGE.md`, and `*.glossary.yml` files. Take canonical terms and meanings from them, but add no information from them that the previous response did not contain.\n4. Re-explain the previous response with clearer structure and simpler wording.\n5. Preserve every detail that changes how the response should be understood: each condition, causal link, uncertainty, constraint, exception, dependency, example, technical identifier, value, unit, warning, scope, conclusion, and relationship.\n6. Attribute operational actions to the previous response so the explanation cannot read as a new task. Do not perform a new task.\n\n## Writing Rules\n\nWrite in a style inspired by ASD-STE100 Simplified Technical English.\n\n- Use active voice and plain UK English.\n- Write for a reading level between Key Stage 4 and Further Education.\n- Use the same term for the same concept throughout.\n- Use precise, technically accurate wording; when clarity and brevity conflict, prioritise accuracy and unambiguous meaning.\n- Use short sentences where possible; put one main action in each sentence.\n- Use the imperative for direct instructions.\n- Define an uncommon abbreviation or specialist term at first use.\n\n## Clarity Controls\n\n- Put each prerequisite, condition, warning, or limitation before the action it governs.\n- Replace a prose noun with the canonical term when a terminology file gives one; otherwise use the previous response's own nouns.\n- Keep every literal identifier, path, command, and value exactly as the previous response wrote it.\n- Replace vague pronouns with the specific subject.\n- Remove idioms, unnecessary synonyms, ambiguous references, and complex noun clusters.\n- Add no information absent from the previous response.\n- State uncertainty where the previous response was uncertain.\n- Report a contradiction in the previous response as a contradiction. Do not resolve it, choose a side, or state what the previous response intended. State that the previous response does not establish which statement is correct.\n- Keep the scope of an absolute word such as `only`, `never`, `all`, or `always`; never weaken it to `usually` or `mostly`.\n\n## Completion Criterion\n\nThe explanation is complete when it re-explains the immediately previous LLM response in clearer plain language, preserves every detail that changes its meaning, and starts no new work.\n\nWith no previous LLM response, the reply is complete when it says there is nothing to re-explain and asks which response or text to explain.\n",{"name":5,"description":7},"main","4e0a12b5048eac78a3ace4feee657873cdd530ef","src\u002Fcore\u002Fskills\u002Fwtf",7,"https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills","https:\u002F\u002Fgithub.com\u002Fmintuz","http:\u002F\u002Fwww.mintuz.com","Working at @monzo, Previously worked at Moonpig, @booking and @bbc","2026-11-13 19:21:11",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add mintuz\u002Fskills --skill wtf",{"tool":53,"command":54},"bunx","bunx skills add mintuz\u002Fskills --skill wtf",{"tool":56,"command":57},"pnpm","pnpm dlx skills add mintuz\u002Fskills --skill wtf","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fcore\u002Fskills\u002Fwtf\u002FSKILL.md",true,[61],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"agents\u002Fopenai.yaml","REFERENCE","参考文档",214,"https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fcore\u002Fskills\u002Fwtf\u002Fagents\u002Fopenai.yaml",[68,89,110,123,144,161],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":80,"publishedAt":33},"01M6C4PDGB6ZZWBS35N3DF7PZZ","xstate","WHEN React state changes in response to an external answer — async submit, in-flight or loading flags, retries, cancellation, polling, optimistic updates, stale responses — or to an interaction with an interruptible middle, such as a drag or a gesture; or WHEN building, reviewing, testing, or visualising XState 5 actors and @xstate\u002Freact integrations; NOT for a value one event sets completely, such as a text draft, a focus flag, or a plain open and closed toggle; models typed lifecycles and renders legal Mermaid stateDiagram-v2 charts.","https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fweb\u002Fskills\u002Fxstate\u002FSKILL.md",[74,77],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[70,81,82,83,84,85,86,87,88],"react","text","state","integrations","Charts","mermaid","testing","open",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":101,"publishedAt":33},"01M6C4PB6VVC2X19B63B7YNH0T","web-design","WHEN refining UI layout, typography, color, or polish; NOT code implementation; provides concise principles for intentional, legible design.","https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fweb\u002Fskills\u002Fweb-design\u002FSKILL.md",[95,98],{"categoryNo":96,"categoryName":97,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[102,103,104,105,106,107,108,109],"web","design","web design","code implementation","polish","ui","typography","code",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":33},"01M6C4P8D92GJDA49V7X1CZXEV","tailwind","USE WHEN writing, fixing or reviewing styling in a project that uses Tailwind CSS, even a one-class change or a request that does not name Tailwind: colours, focus rings, spacing, class names chosen by a prop, map or CVA variants, theme tokens and dark mode in the Tailwind stylesheet or tailwind.config, setup or upgrades (if unsure whether the project uses Tailwind, check package.json or the main stylesheet first); NOT WHEN writing plain CSS or Sass in a project without Tailwind; produces class names Tailwind can find, syntax for the installed major version, visible focus indicators, and no unrequested dependency or invented brand value.","https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fweb\u002Fskills\u002Ftailwind\u002FSKILL.md",[116],{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},[118,119,120,121,103,122],"Tailwind","libraries","component","css","design systems",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":33},"01M6C4P5VWQ69Q32DA0634GDJY","refactoring","WHEN you need a plan to refactor, restructure, or clean up working code and the test result is known, either green or a recorded failing set; NOT for new feature delivery or any behavior change; reversible-baseline safety with prioritized improvements.","https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fweb\u002Fskills\u002Frefactoring\u002FSKILL.md",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",[125,133,134,135,136,137,138,139,140,141,109,142,143],"Safety","baseline","refactor","behavior","change","plan","new feature","SET","up","feature delivery","test",{"skillNo":145,"name":81,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":151,"publishedAt":33},"01M6C4P345APEFEX00J8T7QMXQ","USE WHEN changing the logic, data, props, state, Effects or rendered text of a React component, hook or page, even a one-line change; NOT WHEN the request is styling only (class names, Tailwind, CSS, dark mode, spacing, shadows) or tests only, or when it models submit, in-flight, loading, retry or failure states, even for a named React form (xstate covers that, including its React wiring); applies React 19 composition, state, Effect, structure, API and performance rules with only the project's installed libraries.","https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fweb\u002Fskills\u002Freact\u002FSKILL.md",[149,150],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[81,109,121,118,152,87,153,154,155,156,157,83,143,158,159,160],"performance","hooks","components","architecture","api","react components","state management","styling","management",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":169,"publishedAt":33},"01M6C4P0DK385QBG3B3S86TQV2","react-testing","USE WHEN writing, fixing or reviewing a React Testing Library test for a component, hook or context provider, even one small test, or when asked for an end-to-end journey inside a Vitest or React Testing Library suite; NOT WHEN changing the component itself (react), testing XState actors or @xstate\u002Freact (xstate), or writing a Playwright or Cypress test; covers renderHook, providers, async results, forms and false-pass anti-patterns, and declines end-to-end journeys with the testable slices.","https:\u002F\u002Fgithub.com\u002Fmintuz\u002Fskills\u002Fblob\u002Fmain\u002Fsrc\u002Fweb\u002Fskills\u002Freact-testing\u002FSKILL.md",[167,168],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[170,87,81,171,153,172,173,174,154,175,176,157],"react testing","anti-patterns","e2e","library","testing library","Providers","context"]