[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EW0P2RN2SPYA4QSE2H6PXZ":3,"skill-same:01M7EW0P2RN2SPYA4QSE2H6PXZ":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EW0P2RN2SPYA4QSE2H6PXZ","write-definition",null,"Draft ONE definition into the repo's canonical tex file, consistent with the repo's standing notation. Use when the user says \"add a definition\", \"define X in the notes\", or when resolve-dependencies reports a missing definition. NOT for claims (write-proposition) or remarks (write-remark). Refuses on notation collision with the repo's declared conventions.","tdupu\u002Fagent-skills-public","tdupu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3440403?v=4","01M7EV32X9J0EFE5T4P8TKQTCQ","Taylor Dupuy","01M7EV32XZ1Z4MDBYAFRCJD3BP",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-definition\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-definition\ndescription: Draft ONE definition into the repo's canonical tex file, consistent with the repo's standing notation. Use when the user says \"add a definition\", \"define X in the notes\", or when resolve-dependencies reports a missing definition. NOT for claims (write-proposition) or remarks (write-remark). Refuses on notation collision with the repo's declared conventions.\n---\n\n# write-definition\n\nRuns `subdomains\u002Flatex\u002FWRITERS.md` preamble and postamble in full. This leaf's middle:\n\n## Definition separation\n\nPlace the definition before the first theorem-class statement that uses\nit (LX10), never inside that statement. When extracting an existing\ndefinition, retain its parameter conditions and keep every hypothesis\nneeded by the subsequent result explicit. Do not promote a claim of\nexistence or well-definedness into an assumption of the definition.\n\n### One-concept rule\n\nOne `definition` environment defines exactly one mathematical object,\nconstruction, or term. A paired construction (for example, a jet functor and\na Greenberg functor) must use separate adjacent definitions with separate\nsignatures and parameter domains. Comparisons, non-identification warnings,\nrepresentability caveats, and equivalence claims belong in a following\n`remark`, proposition, or theorem, never appended to the preceding\ndefinition. Do not write a sentence such as “the corresponding ... is” inside\nthe first definition when it introduces a second object; start a new\ndefinition environment instead.\n\nBefore writing, make a definition inventory with one row per concept:\n\n| Concept | Domain\u002Ftest category | Defining formula | Name of representing object |\n|---|---|---|---|\n\nThe inventory must have one row for every displayed construction. The writer\nmust then check that each row has exactly one definition environment and that\nall comparison prose has been moved to a separate remark. If two rows would\nshare an environment, stop and split the draft before editing the canonical\nfile.\n\n### Mechanical check before closing the environment\n\nThe one-concept rule is violated far more often than it is invoked,\nincluding by reviewers looking straight at the violation, because\nnothing catches it: a consequence sentence inside a `definition`\ncompiles exactly as well as one outside it. Check it by hand, every\ntime, on the draft you are about to write:\n\n- read the body from `\\end{enumerate}` — or from the last defining\n  sentence — to `\\end{definition}`;\n- every sentence in that span is a defect unless it is itself a\n  definition. \"Equivalently, ...\", \"We identify ... with ...\", \"Thus $X$\n  is source-side while $Y$ is target-side\", \"It follows that ...\" are\n  consequences, conventions and observations; all of them belong after\n  `\\end{definition}`;\n- a convention ranging wider than this one definition belongs to the\n  Conventions section, not to either side of this environment.\n\nWhen editing an existing definition for any reason, run the same check\nover what is already there, and report violations you do not fix.\n\n### Competing notions each get a definition\n\nWhen a claim proves false because it conflated several inequivalent\nnotions, the repair is structural and it starts here: define each\ncandidate notion, with its own environment and label, placed *before*\nthe statement that adjudicates them (LX10). The theorem then says under\nwhat hypotheses they agree, and examples show the hypotheses cannot be\ndropped.\n\nDo not record the conflation as a remark about a previous draft — see\nwrite-remark. The definitions and the theorem are the record.\n\n## Drafting\n\n- Scan for notation collisions FIRST: the document's own preamble and\n  existing definitions, plus STYLE.md's \"Repo-specific standing\n  conventions\" section where the repo declares one. A symbol already\n  taken → refuse and propose alternatives; never silently overload.\n- Insert at the location the human named, or ask — never guess (D5).\n- Definition environment; term bold\u002Femphasized per document practice;\n  every symbol in the definiens already defined or standard for the\n  declared audience.\n- A definition environment may state notation for a representing object only\n  conditionally (“when representable, write ...”); it may not assert the\n  representability theorem or an identification with another construction.\n- Imported definition: provenance per track-down-reference (opened\n  source), cited at the definition.\n- Cross-reference: list sites already using the term undefined, for\n  the human — do not edit them.\n\n## Red flags\n\n| Thought | Reality |\n|---|---|\n| \"This notation is standard, no need to check\" | The repo's conventions outrank the literature's (floor tightening). |\n| \"I'll also fix the places that use it informally\" | List the sites; touching them is separate, gated work. |\n","# write-definition\n\nRuns `subdomains\u002Flatex\u002FWRITERS.md` preamble and postamble in full. This leaf's middle:\n\n## Definition separation\n\nPlace the definition before the first theorem-class statement that uses\nit (LX10), never inside that statement. When extracting an existing\ndefinition, retain its parameter conditions and keep every hypothesis\nneeded by the subsequent result explicit. Do not promote a claim of\nexistence or well-definedness into an assumption of the definition.\n\n### One-concept rule\n\nOne `definition` environment defines exactly one mathematical object,\nconstruction, or term. A paired construction (for example, a jet functor and\na Greenberg functor) must use separate adjacent definitions with separate\nsignatures and parameter domains. Comparisons, non-identification warnings,\nrepresentability caveats, and equivalence claims belong in a following\n`remark`, proposition, or theorem, never appended to the preceding\ndefinition. Do not write a sentence such as “the corresponding ... is” inside\nthe first definition when it introduces a second object; start a new\ndefinition environment instead.\n\nBefore writing, make a definition inventory with one row per concept:\n\n| Concept | Domain\u002Ftest category | Defining formula | Name of representing object |\n|---|---|---|---|\n\nThe inventory must have one row for every displayed construction. The writer\nmust then check that each row has exactly one definition environment and that\nall comparison prose has been moved to a separate remark. If two rows would\nshare an environment, stop and split the draft before editing the canonical\nfile.\n\n### Mechanical check before closing the environment\n\nThe one-concept rule is violated far more often than it is invoked,\nincluding by reviewers looking straight at the violation, because\nnothing catches it: a consequence sentence inside a `definition`\ncompiles exactly as well as one outside it. Check it by hand, every\ntime, on the draft you are about to write:\n\n- read the body from `\\end{enumerate}` — or from the last defining\n  sentence — to `\\end{definition}`;\n- every sentence in that span is a defect unless it is itself a\n  definition. \"Equivalently, ...\", \"We identify ... with ...\", \"Thus $X$\n  is source-side while $Y$ is target-side\", \"It follows that ...\" are\n  consequences, conventions and observations; all of them belong after\n  `\\end{definition}`;\n- a convention ranging wider than this one definition belongs to the\n  Conventions section, not to either side of this environment.\n\nWhen editing an existing definition for any reason, run the same check\nover what is already there, and report violations you do not fix.\n\n### Competing notions each get a definition\n\nWhen a claim proves false because it conflated several inequivalent\nnotions, the repair is structural and it starts here: define each\ncandidate notion, with its own environment and label, placed *before*\nthe statement that adjudicates them (LX10). The theorem then says under\nwhat hypotheses they agree, and examples show the hypotheses cannot be\ndropped.\n\nDo not record the conflation as a remark about a previous draft — see\nwrite-remark. The definitions and the theorem are the record.\n\n## Drafting\n\n- Scan for notation collisions FIRST: the document's own preamble and\n  existing definitions, plus STYLE.md's \"Repo-specific standing\n  conventions\" section where the repo declares one. A symbol already\n  taken → refuse and propose alternatives; never silently overload.\n- Insert at the location the human named, or ask — never guess (D5).\n- Definition environment; term bold\u002Femphasized per document practice;\n  every symbol in the definiens already defined or standard for the\n  declared audience.\n- A definition environment may state notation for a representing object only\n  conditionally (“when representable, write ...”); it may not assert the\n  representability theorem or an identification with another construction.\n- Imported definition: provenance per track-down-reference (opened\n  source), cited at the definition.\n- Cross-reference: list sites already using the term undefined, for\n  the human — do not edit them.\n\n## Red flags\n\n| Thought | Reality |\n|---|---|\n| \"This notation is standard, no need to check\" | The repo's conventions outrank the literature's (floor tightening). |\n| \"I'll also fix the places that use it informally\" | List the sites; touching them is separate, gated work. |\n",{"name":5,"description":7},"main","8d13efb5e66306aeae6e3b948bc463e7e2db1b65","skills\u002Fwrite-definition","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public","https:\u002F\u002Fgithub.com\u002Ftdupu","https:\u002F\u002Ftdupu.github.io\u002Findex.html","Associate Professor, Department of Mathematics and Statistics, University of Vermont --- last updated Fall 2019","2026-11-13 09:07:19",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tdupu\u002Fagent-skills-public --skill write-definition",{"tool":38,"command":39},"bunx","bunx skills add tdupu\u002Fagent-skills-public --skill write-definition",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tdupu\u002Fagent-skills-public --skill write-definition","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-definition\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EW4PT586KKE7VRCAD80Z9K","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7EW4HV5V74AF3PTV8N4T0PS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"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},"01M7EW4DNKGP5CR1RAJP2J9PHA","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"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":74,"publishedAt":19},"01M7EW4BA2QP88VBFVXDVJM7XQ","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EW47F2JG5FBESDJNP3PKMV","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EW44N8556Y556NX9HJT4KP","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]