[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV4BCMYNHT3M1JQNE4NTSF":3,"skill-same:01M7EV4BCMYNHT3M1JQNE4NTSF":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},"01M7EV4BCMYNHT3M1JQNE4NTSF","break-up-proposition",null,"Break an existing proposition, theorem, or corollary into a labelled enumerate with separately signposted proofs while preserving its mathematics. Use for a style-driven decomposition; adding new items is optional and must be evidence-backed.","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\u002Fbreak-up-proposition\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: break-up-proposition\ndescription: Break an existing proposition, theorem, or corollary into a labelled enumerate with separately signposted proofs while preserving its mathematics. Use for a style-driven decomposition; adding new items is optional and must be evidence-backed.\n---\n\n# break-up-proposition\n\nUse this leaf after `using-latexpowers` has resolved the canonical manuscript\nand target region. It rewrites one existing theorem-class statement into an\nenumerated interface and keeps the proof readable and traceable. It is a\nrefactoring skill: it does not turn an unproved idea into a result and does\nnot require new items when the existing statement already contains the right\nclaims.\n\n## Scope and stop conditions\n\n- Work on one proposition at a time in the declared canonical `.tex` file.\n- Preserve the proposition's hypotheses, conclusions, theorem label, proof,\n  citations, human markers, and surrounding order unless the user explicitly\n  changes them.\n- Add an item only when the user requests it or the evidence and surrounding\n  manuscript establish a genuinely separate conclusion. Record its source and\n  proof obligation before editing.\n- Stop and route to `using-mathpowers` or `write-proposition` if a proposed\n  item needs a new proof, changes the quantifiers, or is not supported by the\n  existing argument. Do not silently strengthen or weaken the result.\n- Stop if the statement's parts are actually separate named theorems. Split\n  those into separate theorem-class environments instead of manufacturing an\n  enumeration.\n\n## Before editing\n\n1. Read the repository's `WRITERS.md`, `STYLE.md`, `LATEX.md`, and any local\n   powers policy through `using-latexpowers`. Resolve the canonical file and\n   the exact proposition region; do not edit a generated or sibling variant.\n2. Read the complete proposition and proof, then search the manuscript for\n   its theorem label, every existing part reference, and nearby labels. Run\n   the repository's label\u002Freference checker before the edit when available.\n3. Make an item map: one semantic conclusion per item, the evidence or proof\n   paragraph that establishes it, and every site that will cite it. Preserve\n   the original order unless there is a stated reason to reorder it.\n4. Choose stable semantic item labels such as\n   `item:pc-invariance` or `item:branch-control`; never use labels whose only\n   meaning is an ordinal. Check that every new label is unique.\n\n## Statement transformation\n\nKeep the theorem-class environment limited to the hypotheses and the\nconclusion. When the proposition has multiple conclusions, use an explicit\nenumerate:\n\n```tex\n\\begin{proposition}\\label{prop:example}\nAssume ... . Then:\n\\begin{enumerate}\n  \\item ... .\\label{item:first-conclusion}\n  \\item ... .\\label{item:second-conclusion}\n\\end{enumerate}\n\\end{proposition}\n```\n\nEach item must be independently meaningful and must state a conclusion, not\nmotivation, unpacking, or a proof step. Keep explanatory consequences outside\nthe theorem-class environment unless they are themselves part of the claimed\nresult. If there is only one conclusion after the refactor, do not enumerate\nmerely to create an item number.\n\nItem labels are an interface. Update every consumer in the same change to use\n`\\eqref{item:\u003Cslug>}`. Never cite a part by a literal `(1)`, `(2)`, or by an\nunstable ordinal. Preserve the proposition's top-level label and update any\nold part labels deliberately; do not leave aliases or duplicate labels behind.\n\n## Proof transformation\n\nUse one `proof` environment for the proposition unless the repository's style\ncontract requires another form. Inside it, give a signpost and proof for each\nenumerated item, in item order:\n\n```tex\n\\begin{proof}\n\\noindent\\emph{Proof of \\eqref{item:first-conclusion}.}\n...\n\n\\noindent\\emph{Proof of \\eqref{item:second-conclusion}.}\n...\n\\end{proof}\n```\n\nThe `\\eqref` renders the current item number while keeping the proof tied to\nthe stable label. Each signposted block must discharge exactly its item. A\nlater block may cite an earlier item with `\\eqref{item:\u003Cslug>}`; state that\ndependency rather than repeating an unproved assertion. Give a short proof\nfor an immediate item or move it out of the proposition; never leave an\nenumerated item without a corresponding proof signpost.\n\n## After editing\n\nReview the diff item by item: the enumerated statement is mathematically\nequivalent to the original unless an explicitly authorized, evidence-backed\nitem was added; every item has a proof block; no proof paragraph or negative\nresult was dropped; and all part references use the new labels. Re-run the\nlabel\u002Freference checker, the repository's LaTeX\u002Fstyle checks, and the\ncanonical build. Inspect the source as well as the PDF because compilation\ncannot detect an omitted conclusion or a proof attached to the wrong item.\n\nReport the target file, the item-to-proof map, any added items and their\nevidence, references updated, and the validation results. Do not commit or\nsync as part of this leaf unless the user separately authorizes that action.\n","# break-up-proposition\n\nUse this leaf after `using-latexpowers` has resolved the canonical manuscript\nand target region. It rewrites one existing theorem-class statement into an\nenumerated interface and keeps the proof readable and traceable. It is a\nrefactoring skill: it does not turn an unproved idea into a result and does\nnot require new items when the existing statement already contains the right\nclaims.\n\n## Scope and stop conditions\n\n- Work on one proposition at a time in the declared canonical `.tex` file.\n- Preserve the proposition's hypotheses, conclusions, theorem label, proof,\n  citations, human markers, and surrounding order unless the user explicitly\n  changes them.\n- Add an item only when the user requests it or the evidence and surrounding\n  manuscript establish a genuinely separate conclusion. Record its source and\n  proof obligation before editing.\n- Stop and route to `using-mathpowers` or `write-proposition` if a proposed\n  item needs a new proof, changes the quantifiers, or is not supported by the\n  existing argument. Do not silently strengthen or weaken the result.\n- Stop if the statement's parts are actually separate named theorems. Split\n  those into separate theorem-class environments instead of manufacturing an\n  enumeration.\n\n## Before editing\n\n1. Read the repository's `WRITERS.md`, `STYLE.md`, `LATEX.md`, and any local\n   powers policy through `using-latexpowers`. Resolve the canonical file and\n   the exact proposition region; do not edit a generated or sibling variant.\n2. Read the complete proposition and proof, then search the manuscript for\n   its theorem label, every existing part reference, and nearby labels. Run\n   the repository's label\u002Freference checker before the edit when available.\n3. Make an item map: one semantic conclusion per item, the evidence or proof\n   paragraph that establishes it, and every site that will cite it. Preserve\n   the original order unless there is a stated reason to reorder it.\n4. Choose stable semantic item labels such as\n   `item:pc-invariance` or `item:branch-control`; never use labels whose only\n   meaning is an ordinal. Check that every new label is unique.\n\n## Statement transformation\n\nKeep the theorem-class environment limited to the hypotheses and the\nconclusion. When the proposition has multiple conclusions, use an explicit\nenumerate:\n\n```tex\n\\begin{proposition}\\label{prop:example}\nAssume ... . Then:\n\\begin{enumerate}\n  \\item ... .\\label{item:first-conclusion}\n  \\item ... .\\label{item:second-conclusion}\n\\end{enumerate}\n\\end{proposition}\n```\n\nEach item must be independently meaningful and must state a conclusion, not\nmotivation, unpacking, or a proof step. Keep explanatory consequences outside\nthe theorem-class environment unless they are themselves part of the claimed\nresult. If there is only one conclusion after the refactor, do not enumerate\nmerely to create an item number.\n\nItem labels are an interface. Update every consumer in the same change to use\n`\\eqref{item:\u003Cslug>}`. Never cite a part by a literal `(1)`, `(2)`, or by an\nunstable ordinal. Preserve the proposition's top-level label and update any\nold part labels deliberately; do not leave aliases or duplicate labels behind.\n\n## Proof transformation\n\nUse one `proof` environment for the proposition unless the repository's style\ncontract requires another form. Inside it, give a signpost and proof for each\nenumerated item, in item order:\n\n```tex\n\\begin{proof}\n\\noindent\\emph{Proof of \\eqref{item:first-conclusion}.}\n...\n\n\\noindent\\emph{Proof of \\eqref{item:second-conclusion}.}\n...\n\\end{proof}\n```\n\nThe `\\eqref` renders the current item number while keeping the proof tied to\nthe stable label. Each signposted block must discharge exactly its item. A\nlater block may cite an earlier item with `\\eqref{item:\u003Cslug>}`; state that\ndependency rather than repeating an unproved assertion. Give a short proof\nfor an immediate item or move it out of the proposition; never leave an\nenumerated item without a corresponding proof signpost.\n\n## After editing\n\nReview the diff item by item: the enumerated statement is mathematically\nequivalent to the original unless an explicitly authorized, evidence-backed\nitem was added; every item has a proof block; no proof paragraph or negative\nresult was dropped; and all part references use the new labels. Re-run the\nlabel\u002Freference checker, the repository's LaTeX\u002Fstyle checks, and the\ncanonical build. Inspect the source as well as the PDF because compilation\ncannot detect an omitted conclusion or a proof attached to the wrong item.\n\nReport the target file, the item-to-proof map, any added items and their\nevidence, references updated, and the validation results. Do not commit or\nsync as part of this leaf unless the user separately authorizes that action.\n",{"name":5,"description":7},"main","8d13efb5e66306aeae6e3b948bc463e7e2db1b65","skills\u002Fbreak-up-proposition","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 break-up-proposition",{"tool":38,"command":39},"bunx","bunx skills add tdupu\u002Fagent-skills-public --skill break-up-proposition",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tdupu\u002Fagent-skills-public --skill break-up-proposition","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fbreak-up-proposition\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",[],[]]