[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVKWSB6399WQZW6GA2HTD7":3,"skill-same:01M7EVKWSB6399WQZW6GA2HTD7":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},"01M7EVKWSB6399WQZW6GA2HTD7","lean-project",null,"Use when adding Lean formalization to a repository or locating the workspace for a Lean task.","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\u002Flean-project\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lean-project\ndescription: Use when adding Lean formalization to a repository or locating the workspace for a Lean task.\n---\n\n# Select or establish the Lean workspace\n\nInput: repository, authorized deliverable, local instructions and layout.\nOutput: workspace path, library\u002Fmodule roots, pinned dependencies, scratch path,\nthe registry-manifest path, and the command that verifies setup.\n\n1. Read the nearest instructions and `LAYOUT.md` when present. Locate existing\n   lakefiles and toolchains before creating anything. Reuse the relevant project;\n   do not upgrade it, overwrite its manifests or move it to satisfy a default.\n2. For a new workspace, default to repository-root `lean\u002F` beside `latex\u002F`.\n   Honor a declared alternative. If a binding layout must change, route that\n   amendment through installed `new-repo-layout-policy`, carrying existing user\n   authorization; otherwise report the exact unresolved layout choice.\n3. Read [tool recipes](..\u002Flean-workflow\u002Freferences\u002Ftools.md). Select a concrete\n   Lean\u002FMathlib-compatible pin. Create the smallest library workspace needed;\n   record its toolchain, lakefile and dependency lockfile. Add source modules to\n   actual build targets. Core-only mathematics need not acquire Mathlib.\n4. Ignore `.lake\u002F` and generated build output in the workspace. Put experiments,\n   logs and source maps under the declared scratch root, default dated `ai\u002F` at\n   repository root. Keep reusable formalization sources in the Lean workspace.\n5. Declare the workspace's documentation paths, all inside it beside the library\n   root: an assumption census, a statement-to-declaration map, and — when the\n   project may be registered — a **Palomar manifest at `\u003Cworkspace>\u002FPALOMAR.md`**.\n   A registry entry describes a Lean workspace at an exact commit, so its manifest\n   belongs with that workspace, never in a separate repository-root directory.\n   Report the path at setup even when the file does not yet exist, so later work\n   does not invent a location. Preparing a manifest and submitting it are separate\n   acts, and submission needs its own explicit authorization; a manifest states\n   which has occurred. Per entry it records the declaration name, its elaborated\n   type quoted verbatim from Lean, an informal claim rendered from that type rather\n   than from memory, the axioms, and an explicit *does not claim* block — registries\n   check informal-against-formal agreement, and an absent claim is not visible to a\n   reviewer unless it is written down.\n6. Invoke `lean-doctor`; return its evidence and any setup blocker. An unavailable\n   compiler still permits source analysis but cannot produce a checked result.\n\nExample: a repo already using `formal\u002FAlgebra\u002F` keeps that project; a manuscript\nrepo with only `latex\u002F` normally gains `lean\u002F`, with run evidence under `ai\u002F`.\n","# Select or establish the Lean workspace\n\nInput: repository, authorized deliverable, local instructions and layout.\nOutput: workspace path, library\u002Fmodule roots, pinned dependencies, scratch path,\nthe registry-manifest path, and the command that verifies setup.\n\n1. Read the nearest instructions and `LAYOUT.md` when present. Locate existing\n   lakefiles and toolchains before creating anything. Reuse the relevant project;\n   do not upgrade it, overwrite its manifests or move it to satisfy a default.\n2. For a new workspace, default to repository-root `lean\u002F` beside `latex\u002F`.\n   Honor a declared alternative. If a binding layout must change, route that\n   amendment through installed `new-repo-layout-policy`, carrying existing user\n   authorization; otherwise report the exact unresolved layout choice.\n3. Read [tool recipes](..\u002Flean-workflow\u002Freferences\u002Ftools.md). Select a concrete\n   Lean\u002FMathlib-compatible pin. Create the smallest library workspace needed;\n   record its toolchain, lakefile and dependency lockfile. Add source modules to\n   actual build targets. Core-only mathematics need not acquire Mathlib.\n4. Ignore `.lake\u002F` and generated build output in the workspace. Put experiments,\n   logs and source maps under the declared scratch root, default dated `ai\u002F` at\n   repository root. Keep reusable formalization sources in the Lean workspace.\n5. Declare the workspace's documentation paths, all inside it beside the library\n   root: an assumption census, a statement-to-declaration map, and — when the\n   project may be registered — a **Palomar manifest at `\u003Cworkspace>\u002FPALOMAR.md`**.\n   A registry entry describes a Lean workspace at an exact commit, so its manifest\n   belongs with that workspace, never in a separate repository-root directory.\n   Report the path at setup even when the file does not yet exist, so later work\n   does not invent a location. Preparing a manifest and submitting it are separate\n   acts, and submission needs its own explicit authorization; a manifest states\n   which has occurred. Per entry it records the declaration name, its elaborated\n   type quoted verbatim from Lean, an informal claim rendered from that type rather\n   than from memory, the axioms, and an explicit *does not claim* block — registries\n   check informal-against-formal agreement, and an absent claim is not visible to a\n   reviewer unless it is written down.\n6. Invoke `lean-doctor`; return its evidence and any setup blocker. An unavailable\n   compiler still permits source analysis but cannot produce a checked result.\n\nExample: a repo already using `formal\u002FAlgebra\u002F` keeps that project; a manuscript\nrepo with only `latex\u002F` normally gains `lean\u002F`, with run evidence under `ai\u002F`.\n",{"name":5,"description":7},"main","8d13efb5e66306aeae6e3b948bc463e7e2db1b65","skills\u002Flean-project","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 lean-project",{"tool":38,"command":39},"bunx","bunx skills add tdupu\u002Fagent-skills-public --skill lean-project",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tdupu\u002Fagent-skills-public --skill lean-project","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Flean-project\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",[],[]]