[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FC50ATDXWWH6C86220G7R9":3,"skill-same:01M7FC50ATDXWWH6C86220G7R9":54},{"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},"01M7FC50ATDXWWH6C86220G7R9","tdd",null,"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.","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\u002Ftdd\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: tdd\ndescription: 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.\n---\n\n# Scenario-driven TDD\n\nEvery test protects a behavior someone would notice if it broke.\nA few right tests are worth more than many obvious ones.\n\n## 1. List the scenarios before the code\n\n```\nScenario: \u003Cbehavior, in the words of whoever uses it>\n  Given \u003Cinitial state>\n  When \u003Caction>\n  Then \u003Cobservable result>\n```\n\nIf the requirements or the plan already list the scenarios, use those.\nOtherwise cover only the main path, the boundary of each rule (the value that\npasses and the one that fails) and each error the user sees, and for a new or\nambiguous task show the list to the user before going on. For a bug, the\nscenario is the bug.\n\n## 2. Pick one level per scenario\n\n- **Functional** (default): through the public entry point (CLI, API, exported function).\n- **Unit**: pure logic with many branches, where a functional test cannot reach.\n- **Regression**: every fixed bug gets a test that failed before the fix.\n\n## 3. Red, green, refactor\n\nOne scenario at a time:\n\n1. Write the test and run it. It must fail **for the expected reason** (an\n   assertion, not a compile error). If it passes on the first run, review it.\n2. Write the least code that makes it pass.\n3. Refactor with the suite green and run it again.\n\nNever change an existing test just to make it pass. If the expected behavior\nchanged, say so.\n\n## 4. Write the test\n\nEvery test must have three blocks, in this order and once each:\n\n```\n\u002F\u002F Given  (setup)  prepare the state\n\u002F\u002F When   (run)    one single action\n\u002F\u002F Then   (assert) check the observable result\n```\n\nTests must be simple: no `if`, loops or logic of their own, little setup and a\nsingle action. If a test does not fit that (huge setup, many mocks, several\nactions), the problem is usually the code: propose simplifying the design\n(see the `design-principles` skill) instead of complicating the test.\n\nBefore writing, read `references\u002Fwriting.md` (rules and what **not** to test)\nand `references\u002Fexamples.md` (examples per language).\n\nFollow the project's test conventions (`AGENTS.md`, `CLAUDE.md`, existing\ntests). Do not add a BDD framework if the project does not use one.\n\n## When done\n\nRun the whole suite and answer in a few lines: scenarios covered and at which\nlevel, what you chose **not** to test and why, and the suite result.\n","# Scenario-driven TDD\n\nEvery test protects a behavior someone would notice if it broke.\nA few right tests are worth more than many obvious ones.\n\n## 1. List the scenarios before the code\n\n```\nScenario: \u003Cbehavior, in the words of whoever uses it>\n  Given \u003Cinitial state>\n  When \u003Caction>\n  Then \u003Cobservable result>\n```\n\nIf the requirements or the plan already list the scenarios, use those.\nOtherwise cover only the main path, the boundary of each rule (the value that\npasses and the one that fails) and each error the user sees, and for a new or\nambiguous task show the list to the user before going on. For a bug, the\nscenario is the bug.\n\n## 2. Pick one level per scenario\n\n- **Functional** (default): through the public entry point (CLI, API, exported function).\n- **Unit**: pure logic with many branches, where a functional test cannot reach.\n- **Regression**: every fixed bug gets a test that failed before the fix.\n\n## 3. Red, green, refactor\n\nOne scenario at a time:\n\n1. Write the test and run it. It must fail **for the expected reason** (an\n   assertion, not a compile error). If it passes on the first run, review it.\n2. Write the least code that makes it pass.\n3. Refactor with the suite green and run it again.\n\nNever change an existing test just to make it pass. If the expected behavior\nchanged, say so.\n\n## 4. Write the test\n\nEvery test must have three blocks, in this order and once each:\n\n```\n\u002F\u002F Given  (setup)  prepare the state\n\u002F\u002F When   (run)    one single action\n\u002F\u002F Then   (assert) check the observable result\n```\n\nTests must be simple: no `if`, loops or logic of their own, little setup and a\nsingle action. If a test does not fit that (huge setup, many mocks, several\nactions), the problem is usually the code: propose simplifying the design\n(see the `design-principles` skill) instead of complicating the test.\n\nBefore writing, read `references\u002Fwriting.md` (rules and what **not** to test)\nand `references\u002Fexamples.md` (examples per language).\n\nFollow the project's test conventions (`AGENTS.md`, `CLAUDE.md`, existing\ntests). Do not add a BDD framework if the project does not use one.\n\n## When done\n\nRun the whole suite and answer in a few lines: scenarios covered and at which\nlevel, what you chose **not** to test and why, and the suite result.\n",{"name":5,"description":7},"main","b3235ac1d89c9647507e5697eedf0ca4efb18e47","examples\u002Fskills\u002Ftdd","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 tdd",{"tool":36,"command":37},"bunx","bunx skills add gustavoSaboia97\u002Fcasulo --skill tdd",{"tool":39,"command":40},"pnpm","pnpm dlx skills add gustavoSaboia97\u002Fcasulo --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftdd\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fexamples.md","REFERENCE","参考文档",1801,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftdd\u002Freferences\u002Fexamples.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fwriting.md",1131,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftdd\u002Freferences\u002Fwriting.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":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},"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":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},"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":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},"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",[],[],{"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},"01M7FC4GKWFFCJNJTYT7BGR0C3","git-workflow","Creates branches, small Conventional Commits and pull request descriptions, safely. Use when committing, writing a commit message, creating a branch, pushing, opening or describing a pull request, or resolving a merge conflict.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fgit-workflow\u002FSKILL.md",[],[]]