[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBHW1SS8N385RCY4KJ2KX4":3,"skill-same:01M7FBHW1SS8N385RCY4KJ2KX4":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FBHW1SS8N385RCY4KJ2KX4","test-driven-development",null,"Headcount engineering policy for test-driven development adoption, unit testing expectations, and testing governance.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: test-driven-development\ndescription: \"Headcount engineering policy for test-driven development adoption, unit testing expectations, and testing governance.\"\n---\n\n# Test-driven development\n\n## The loop\n\n1. **Red** — write one test that fails for the right reason. Run it. A test that passes immediately\n   is testing nothing; a test that errors instead of failing is testing the wrong thing.\n2. **Green** — the smallest change that makes it pass. Ugly is fine here.\n3. **Refactor** — clean up with the test green. If it goes red, you changed behavior, not structure.\n\nNever skip step 1. Writing the test after the code produces a test shaped to the implementation,\nwhich is the one shape that cannot catch the implementation being wrong.\n\n## What to test\n\nTest behavior at the boundary a caller actually depends on. For each unit ask: if this broke\nsilently, who notices and how? If the answer is nobody, delete the code rather than test it.\n\n- **Test**: branching logic, boundary conditions, error paths, anything with a past bug, contracts\n  between modules.\n- **Do not test**: getters, framework behavior, private helpers reachable only through a public path\n  already covered, exact wording of log lines.\n\n## Bugs\n\nEvery bug gets a failing test *before* the fix, reproducing it at the smallest scope that shows it.\nThat test is the proof the bug existed and the guard that it stays fixed. A fix without one is a\nclaim.\n\n## Rules\n\n- One behavior per test. A test asserting five things tells you almost nothing when it fails.\n- The test name states the behavior, not the method: `rejects_expired_token`, not `test_auth`.\n- Never weaken an assertion to get green. If a test is inconvenient, the design is telling you\n  something.\n- Never mock what you own — mock the network and the clock, not your own modules. Mocking your own\n  code tests the mock.\n\n## Never\n\n- Write the test after the code and call it test-driven. You will test what you built rather than what was required.\n- Skip watching the test fail. A test that has never failed proves nothing.\n- Delete or skip a failing test to unblock a release. Fix it, or revert what broke it.\n- Treat a coverage number as the goal. It counts lines executed, not behavior pinned down.\n\n## Return contract\n\nReport the tests added, what each pins down, what is deliberately untested and why, and the actual\ncommand you ran with its output. \"Tests pass\" without the command output is not a result.\n","# Test-driven development\n\n## The loop\n\n1. **Red** — write one test that fails for the right reason. Run it. A test that passes immediately\n   is testing nothing; a test that errors instead of failing is testing the wrong thing.\n2. **Green** — the smallest change that makes it pass. Ugly is fine here.\n3. **Refactor** — clean up with the test green. If it goes red, you changed behavior, not structure.\n\nNever skip step 1. Writing the test after the code produces a test shaped to the implementation,\nwhich is the one shape that cannot catch the implementation being wrong.\n\n## What to test\n\nTest behavior at the boundary a caller actually depends on. For each unit ask: if this broke\nsilently, who notices and how? If the answer is nobody, delete the code rather than test it.\n\n- **Test**: branching logic, boundary conditions, error paths, anything with a past bug, contracts\n  between modules.\n- **Do not test**: getters, framework behavior, private helpers reachable only through a public path\n  already covered, exact wording of log lines.\n\n## Bugs\n\nEvery bug gets a failing test *before* the fix, reproducing it at the smallest scope that shows it.\nThat test is the proof the bug existed and the guard that it stays fixed. A fix without one is a\nclaim.\n\n## Rules\n\n- One behavior per test. A test asserting five things tells you almost nothing when it fails.\n- The test name states the behavior, not the method: `rejects_expired_token`, not `test_auth`.\n- Never weaken an assertion to get green. If a test is inconvenient, the design is telling you\n  something.\n- Never mock what you own — mock the network and the clock, not your own modules. Mocking your own\n  code tests the mock.\n\n## Never\n\n- Write the test after the code and call it test-driven. You will test what you built rather than what was required.\n- Skip watching the test fail. A test that has never failed proves nothing.\n- Delete or skip a failing test to unblock a release. Fix it, or revert what broke it.\n- Treat a coverage number as the goal. It counts lines executed, not behavior pinned down.\n\n## Return contract\n\nReport the tests added, what each pins down, what is deliberately untested and why, and the actual\ncommand you ran with its output. \"Tests pass\" without the command output is not a result.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Ftest-driven-development",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill test-driven-development",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill test-driven-development",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill test-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"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},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\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},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\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},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\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},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\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},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]