[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FC4AAKES837K30MSN0DM2A":3,"skill-same:01M7FC4AAKES837K30MSN0DM2A":68},{"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":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7FC4AAKES837K30MSN0DM2A","docs",null,"Writes and updates project documentation (README, project spec, ADRs, CHANGELOG, code comments) so it stays short, true and in sync with the code. Use when creating or changing docs, recording an architecture decision, preparing a release, describing what a project is, or when a change alters behavior that docs describe.","gustavoSaboia97\u002Fcasulo","gustavoSaboia97","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28377961?v=4","01M7FC3VEPZE3BH2DBWD0MJ57A","Gustavo Dutra Domingues Saboia","01M7FC3VF9DYHTHHVXZ0GZ630A",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fdocs\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: docs\ndescription: Writes and updates project documentation (README, project spec, ADRs, CHANGELOG, code comments) so it stays short, true and in sync with the code. Use when creating or changing docs, recording an architecture decision, preparing a release, describing what a project is, or when a change alters behavior that docs describe.\n---\n\n# Docs\n\nGoal: a reader (person or agent) understands the project from the docs alone,\nand every line is still true. Wrong docs are worse than none: agents trust them.\n\n## Rules for every document\n\n- Write for the reader: what they need to use or change the project, in that\n  order.\n- One source of truth: each fact lives in one place; elsewhere, link to it.\n- Examples must run: copy them from a real run or a test, never from memory.\n- Docs change with the code, in the same pull request.\n- Describe **what** and **why**. The **how** lives in the code.\n\nBefore writing, read `references\u002Fstyle.md` (how to write: words, sentences,\nstructure).\n\n## Where each thing lives\n\n| Document | Says | Template |\n|---|---|---|\n| `README.md` | What it is (short), install, quick start, links | `assets\u002Freadme.md` |\n| `docs\u002Fspec.md` | The whole project: purpose, concepts, behavior, constraints | `assets\u002Fspec.md` |\n| `docs\u002Fadr\u002FNNNN-\u003Ctitle>.md` | Why one decision was made | `assets\u002Fadr.md` |\n| `CHANGELOG.md` | What changed for users, per release | `assets\u002Fchangelog.md` |\n| Code comments | Why the code is the way it is | (below) |\n\nPer-feature documents come from other skills: `docs\u002Frequirements\u002F` from the\n`requirements` skill, `docs\u002Fplans\u002F` from the `implementation-plan` skill.\nFollow the project's own layout if it already has one.\n\n## README\n\nStart with **What it is**: 2 to 4 sentences on what, for whom and which\nproblem, then **Non-goals**. Then install, a quick start that works when\ncopied, and links to the spec and other docs. Keep details out; link instead.\n\n## Spec\n\nThe full description of the project, precise enough that someone could\nrebuild a project that behaves the same without seeing the code.\n- Describe behavior from the outside: commands or endpoints, inputs, outputs,\n  errors. No function or file names: they go stale at every refactor.\n- Name the constraints that must never break (security, trust, platforms).\n- Link ADRs for the reasons; do not repeat them.\n- When a change alters behavior, update the spec in the same pull request.\n  The tests prove the behavior; the spec states the intent.\n\n## ADR\n\nWrite one when a decision is hard to reverse, has real alternatives, or\nsomeone will later ask \"why is it like this?\" (a dependency, a data format,\nan architecture boundary, a security trade-off). Number them in order. Never\nedit an accepted ADR's decision: write a new one that supersedes it, and mark\nthe old one \"Superseded by NNNN\".\n\n## CHANGELOG\n\nFollows Keep a Changelog. Add entries under `Unreleased` as changes land, in\nwords a user understands; build them from the `feat:` and `fix:` commits\n(see the `git-workflow` skill), and skip `refactor:`, `test:` and `chore:`\nunless users notice them. Mark breaking changes clearly.\n\n## Code comments\n\n- Public items: a doc comment saying what it does, not how.\n- Other comments explain **why**: a constraint, a workaround, a non-obvious\n  choice. Never restate what the code says.\n- Delete comments that are no longer true. No commented-out code.\n\n## Before finishing\n\n1. Check every command, path and example you wrote against the code.\n2. Reread what you wrote against `references\u002Fstyle.md` and cut what the\n   reader does not need.\n3. Search the docs for statements your change made false, and fix them.\n4. Reply in a few lines: files changed and anything left undocumented.\n","# Docs\n\nGoal: a reader (person or agent) understands the project from the docs alone,\nand every line is still true. Wrong docs are worse than none: agents trust them.\n\n## Rules for every document\n\n- Write for the reader: what they need to use or change the project, in that\n  order.\n- One source of truth: each fact lives in one place; elsewhere, link to it.\n- Examples must run: copy them from a real run or a test, never from memory.\n- Docs change with the code, in the same pull request.\n- Describe **what** and **why**. The **how** lives in the code.\n\nBefore writing, read `references\u002Fstyle.md` (how to write: words, sentences,\nstructure).\n\n## Where each thing lives\n\n| Document | Says | Template |\n|---|---|---|\n| `README.md` | What it is (short), install, quick start, links | `assets\u002Freadme.md` |\n| `docs\u002Fspec.md` | The whole project: purpose, concepts, behavior, constraints | `assets\u002Fspec.md` |\n| `docs\u002Fadr\u002FNNNN-\u003Ctitle>.md` | Why one decision was made | `assets\u002Fadr.md` |\n| `CHANGELOG.md` | What changed for users, per release | `assets\u002Fchangelog.md` |\n| Code comments | Why the code is the way it is | (below) |\n\nPer-feature documents come from other skills: `docs\u002Frequirements\u002F` from the\n`requirements` skill, `docs\u002Fplans\u002F` from the `implementation-plan` skill.\nFollow the project's own layout if it already has one.\n\n## README\n\nStart with **What it is**: 2 to 4 sentences on what, for whom and which\nproblem, then **Non-goals**. Then install, a quick start that works when\ncopied, and links to the spec and other docs. Keep details out; link instead.\n\n## Spec\n\nThe full description of the project, precise enough that someone could\nrebuild a project that behaves the same without seeing the code.\n- Describe behavior from the outside: commands or endpoints, inputs, outputs,\n  errors. No function or file names: they go stale at every refactor.\n- Name the constraints that must never break (security, trust, platforms).\n- Link ADRs for the reasons; do not repeat them.\n- When a change alters behavior, update the spec in the same pull request.\n  The tests prove the behavior; the spec states the intent.\n\n## ADR\n\nWrite one when a decision is hard to reverse, has real alternatives, or\nsomeone will later ask \"why is it like this?\" (a dependency, a data format,\nan architecture boundary, a security trade-off). Number them in order. Never\nedit an accepted ADR's decision: write a new one that supersedes it, and mark\nthe old one \"Superseded by NNNN\".\n\n## CHANGELOG\n\nFollows Keep a Changelog. Add entries under `Unreleased` as changes land, in\nwords a user understands; build them from the `feat:` and `fix:` commits\n(see the `git-workflow` skill), and skip `refactor:`, `test:` and `chore:`\nunless users notice them. Mark breaking changes clearly.\n\n## Code comments\n\n- Public items: a doc comment saying what it does, not how.\n- Other comments explain **why**: a constraint, a workaround, a non-obvious\n  choice. Never restate what the code says.\n- Delete comments that are no longer true. No commented-out code.\n\n## Before finishing\n\n1. Check every command, path and example you wrote against the code.\n2. Reread what you wrote against `references\u002Fstyle.md` and cut what the\n   reader does not need.\n3. Search the docs for statements your change made false, and fix them.\n4. Reply in a few lines: files changed and anything left undocumented.\n",{"name":5,"description":7},"main","b3235ac1d89c9647507e5697eedf0ca4efb18e47","examples\u002Fskills\u002Fdocs","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97","2026-11-12 03:39:53",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add gustavoSaboia97\u002Fcasulo --skill docs",{"tool":36,"command":37},"bunx","bunx skills add gustavoSaboia97\u002Fcasulo --skill docs",{"tool":39,"command":40},"pnpm","pnpm dlx skills add gustavoSaboia97\u002Fcasulo --skill docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fdocs\u002FSKILL.md",true,[44,50,54,58,62],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"assets\u002Fadr.md","ASSET","资产文件",471,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fdocs\u002Fassets\u002Fadr.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"assets\u002Fchangelog.md",539,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fdocs\u002Fassets\u002Fchangelog.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Freadme.md",521,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fdocs\u002Fassets\u002Freadme.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"assets\u002Fspec.md",981,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fdocs\u002Fassets\u002Fspec.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fstyle.md","REFERENCE","参考文档",3467,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fdocs\u002Freferences\u002Fstyle.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FC535ZW2293Q4925SDA5C4","{name=null}","Describe what {name} does and when the agent should use it","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Ftemplates\u002Fskill.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FC50ATDXWWH6C86220G7R9","tdd","Develops with TDD driven by BDD scenarios (Given\u002FWhen\u002FThen), writing only the functional, regression and unit tests that protect real behavior. Use when implementing a feature, fixing a bug, or when asked for tests, TDD, BDD, regression tests or coverage.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FC4WJJ6KJM6DEJQWBG16HC","security-audit","Audits code for exploitable security problems (injection, broken access control, leaked secrets, unsafe input handling, vulnerable dependencies) and reports only verified findings with severity and fix. Use when asked for a security review or audit, before a release, or when a change touches authentication, permissions, secrets, user input, file paths, commands or network calls.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7FC4RZ6Q313R8W3J4F58KFZ","requirements","Turns a request or idea into clear, testable requirements, with scope, user stories and Given\u002FWhen\u002FThen acceptance criteria. Use when starting a new feature or project, when a request is vague, or when asked for requirements, user stories, acceptance criteria or a feature spec.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Frequirements\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7FC4PBM8TXFZGBA9RN3967W","refactoring","Restructures existing code without changing its behavior, in small steps with the tests green after each one. Use when asked to refactor, clean up, simplify, rename, extract, move or reorganize code, or to work on items recorded as \"Refactor later\".","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Frefactoring\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7FC4KEBD4F92H6RMPPZJRZH","implementation-plan","Turns requirements into a short implementation plan of small, verifiable steps, each with the files it touches and the test scenarios it covers. Use after requirements are clear and before coding, or when asked to plan, break down or estimate a change.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fimplementation-plan\u002FSKILL.md",[],[]]