[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DKBZ1KZKZQQAVB89YSCV7S":3,"skill-same:01M7DKBZ1KZKZQQAVB89YSCV7S":45},{"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":6,"updatedAt":30,"install":31,"resources":44},"01M7DKBZ1KZKZQQAVB89YSCV7S","split-markdown",null,"Split a Markdown file that reached the size limit (50 KiB) into a folder of its subjects — one file per top-level section, a README.md index, every inbound link updated — the way the rules prescribe. Use when check-md-size or the pre-commit hook refuses a file, or when the developer asks to split a Markdown file that grew too large. Shows the plan and writes nothing until the developer agrees.","TheHefty\u002Fjvsl.env.agents.container","TheHefty","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165610515?v=4","01M7CE9QCF7JH950RN330BKCF4","João Lima","01M7DK9BR7HVQK0TMTRFPY7MC8",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fsplit-markdown\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: split-markdown\ndescription: Split a Markdown file that reached the size limit (50 KiB) into a folder of its subjects — one file per top-level section, a README.md index, every inbound link updated — the way the rules prescribe. Use when check-md-size or the pre-commit hook refuses a file, or when the developer asks to split a Markdown file that grew too large. Shows the plan and writes nothing until the developer agrees.\n---\n\n# Splitting a Markdown file that grew past the limit\n\nThe rules hold every Markdown file under 50 KiB (RULES.md, \"Documentation\"), and say how a file that reaches the limit is split: **into a folder named for its subject, one file per top-level section, with a `README.md` inside that indexes them.** This skill does that. The arithmetic — where each section starts and ends, how big each file will be, which links point at what — is done by a script, so no prose passes through your hands to be retyped.\n\n## 1. Which file\n\nThe file `check-md-size` or the pre-commit hook named, or the one the developer names. Two are special:\n\n- **`CHANGELOG.md` is exempt.** It only grows and release-please writes it. Say so and stop.\n- **`CLAUDE.md` stays the file that is loaded.** It is split into files it imports with `@path`, never into a folder that replaces it. Ask the developer which sections must stay in its own body — the mode, the gates and the instruction to stop and say so, at least: what has to survive the imports failing.\n\n## 2. Plan, and show the plan\n\nFrom the repository's root:\n\n```bash\n${CLAUDE_PLUGIN_ROOT}\u002Fbin\u002Fmd-split-plan \u003Cfile>\n```\n\nFor `CLAUDE.md`, add `--keep \"\u003Cheading>\"` once for each section that stays in its body.\n\nIt prints the plan as JSON and writes nothing. Show the developer, in words:\n\n- the folder and the files it will create, one per section, with each one's size;\n- the index (`README.md`), which keeps the file's preamble and lists the sections;\n- every file whose links will be rewritten, because they point at the old file or at one of its sections;\n- that the old path becomes a one-line pointer to the index — never a second copy.\n\n**If `oversized` is not empty**, a section is over the limit on its own, and its file would be too. Say which, and propose splitting that section by its own subsections first: the same rule, one level down. Do not cut a section at a byte count — the rules forbid it, because it leaves half an argument in each piece.\n\n**Never compress the prose to make it fit.** The length was the signal. Deleting the explanations that made it long throws away the part worth keeping.\n\n## 3. Apply, only on the developer's word\n\nWhen the developer agrees:\n\n```bash\n${CLAUDE_PLUGIN_ROOT}\u002Fbin\u002Fmd-split-plan --apply \u003Cfile>   # with the same --keep options\n```\n\nIt writes the section files as exact slices of the original, with only their links rewritten. It writes the index and the pointer, rewrites the inbound links, and prints what it did. It refuses, writing nothing, if a section is still over the limit.\n\nThen run `check-md-size` and show its line. **Nothing is committed**: leave the change for the developer to review and commit, as one change — the split and every link it updated together.\n","# Splitting a Markdown file that grew past the limit\n\nThe rules hold every Markdown file under 50 KiB (RULES.md, \"Documentation\"), and say how a file that reaches the limit is split: **into a folder named for its subject, one file per top-level section, with a `README.md` inside that indexes them.** This skill does that. The arithmetic — where each section starts and ends, how big each file will be, which links point at what — is done by a script, so no prose passes through your hands to be retyped.\n\n## 1. Which file\n\nThe file `check-md-size` or the pre-commit hook named, or the one the developer names. Two are special:\n\n- **`CHANGELOG.md` is exempt.** It only grows and release-please writes it. Say so and stop.\n- **`CLAUDE.md` stays the file that is loaded.** It is split into files it imports with `@path`, never into a folder that replaces it. Ask the developer which sections must stay in its own body — the mode, the gates and the instruction to stop and say so, at least: what has to survive the imports failing.\n\n## 2. Plan, and show the plan\n\nFrom the repository's root:\n\n```bash\n${CLAUDE_PLUGIN_ROOT}\u002Fbin\u002Fmd-split-plan \u003Cfile>\n```\n\nFor `CLAUDE.md`, add `--keep \"\u003Cheading>\"` once for each section that stays in its body.\n\nIt prints the plan as JSON and writes nothing. Show the developer, in words:\n\n- the folder and the files it will create, one per section, with each one's size;\n- the index (`README.md`), which keeps the file's preamble and lists the sections;\n- every file whose links will be rewritten, because they point at the old file or at one of its sections;\n- that the old path becomes a one-line pointer to the index — never a second copy.\n\n**If `oversized` is not empty**, a section is over the limit on its own, and its file would be too. Say which, and propose splitting that section by its own subsections first: the same rule, one level down. Do not cut a section at a byte count — the rules forbid it, because it leaves half an argument in each piece.\n\n**Never compress the prose to make it fit.** The length was the signal. Deleting the explanations that made it long throws away the part worth keeping.\n\n## 3. Apply, only on the developer's word\n\nWhen the developer agrees:\n\n```bash\n${CLAUDE_PLUGIN_ROOT}\u002Fbin\u002Fmd-split-plan --apply \u003Cfile>   # with the same --keep options\n```\n\nIt writes the section files as exact slices of the original, with only their links rewritten. It writes the index and the pointer, rewrites the inbound links, and prints what it did. It refuses, writing nothing, if a section is still over the limit.\n\nThen run `check-md-size` and show its line. **Nothing is committed**: leave the change for the developer to review and commit, as one change — the split and every link it updated together.\n",{"name":5,"description":7},"master","e4865519cb1c8f3e0af4852ab91d612413d70117","core\u002Fplugin\u002Fagent-container\u002Fskills\u002Fsplit-markdown","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container","https:\u002F\u002Fgithub.com\u002FTheHefty","https:\u002F\u002Fwww.fahrenheit404.com.br","2026-11-04 14:42:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TheHefty\u002Fjvsl.env.agents.container --skill split-markdown",{"tool":37,"command":38},"bunx","bunx skills add TheHefty\u002Fjvsl.env.agents.container --skill split-markdown",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TheHefty\u002Fjvsl.env.agents.container --skill split-markdown","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fsplit-markdown\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7DKC53FSDENMQ30AAR4022D","study","Build study material for a topic the developer wants to understand before writing about it — a guide in docs\u002Fstudy\u002F\u003Cslug>\u002F, tracked as a study task. Use when the developer asks to study a topic, to turn a blog candidate or a report topic into study material, or to prepare before writing a post. Never writes the post.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fstudy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7DKBTQG1Y99AA8KNM3VSS6F","review","End-of-day review with the developer — show each task worked today against its done criterion, and record the developer's acceptance or reopen it with what is missing. Use when the developer asks to review the day or close out today's work, or as the first part of the end-of-day block.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DKBNCKYKA9HXG84JY1ZMV4","retro","The day's retrospective with the developer — report what was discovered, what surprised, what went wrong and what was decided without asking, take the developer's own \"what I want to learn\" line and elaborate on it, grounded in the day's work, and write the day's journal entry. Use after the review at the end of the day, or when the developer asks for the retro. Never skipped.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fretro\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DKBGG57AZR87EG60MQBNA4","refine","Refinement with the developer — grill the next candidate items or a new idea, propose stories and tasks in the tracker, and agree or reject them on the developer's word, so tomorrow's planning has agreed tasks to pick. Use after the retro at the end of the day, or when the developer asks to refine or plan the next work.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Frefine\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DKBBBFQC5ETAK11F45JCME","project-report","A read-only report on the project — overview, decisions documented and implicit, critical areas, quality and tests, a study list by risk, and topics worth writing about — written to docs\u002FREPORT.md, which git ignores. Use when the developer asks for a project report, an overview of the codebase, what to study, or what is worth writing about.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fproject-report\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DKB7A8D7KSV8YAWMA92SVS","planning","Start the working day with the developer — read the tracker and yesterday's journal, propose today's tasks, and claim only what the developer confirms. Use when the developer asks to start the day, plan the day, or plan today's work. Writes no code.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fplanning\u002FSKILL.md",[],[]]