[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ES0QM0CXESP7FB0X1EZTZP":3,"skill-same:01M7ES0QM0CXESP7FB0X1EZTZP":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ES0QM0CXESP7FB0X1EZTZP","test-behavior",null,"Apply when writing, changing, reviewing or keeping a test. Call the code the way its users do and assert the exact result they see; rewrite or delete any test that would pass if the code under test returned nothing.","Ventorius\u002Fven-stack","Ventorius","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5689509?v=4","01M7ERRDPQ5YXCNXJZWEKQNP50","Sebastian Basznianin","01M7ERRDQ9S0ZD9YMH1RN1WVP7",0,"MIT","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Ftest-behavior\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-behavior\ndescription: \"Apply when writing, changing, reviewing or keeping a test. Call the code the way its users do and assert the exact result they see; rewrite or delete any test that would pass if the code under test returned nothing.\"\nmetadata:\n  layer: L2\n  source: cursor\u002Fplugins@1e5c90a:pstack\u002Fskills\u002Fprinciple-test-behavior-not-implementation\u002FSKILL.md + mattpocock\u002Fskills@49dd158:skills\u002Fengineering\u002Ftdd\u002Ftests.md\n  license: MIT\n---\n\n# Test Behavior\n\nA test calls the code the way its users do and asserts the exact result they see. Rewrite or delete any test that would still pass if every function it imports returned nothing or a wrong value.\n\n**Why:** A good test fails when behavior breaks and keeps passing through a refactor that leaves behavior alone. A test tied to internals does the opposite: it breaks on harmless changes and stays green on real ones, so people learn to ignore it.\n\n**These shapes fail the check:**\n- A loose assertion or none: \"is defined\", \"is truthy\", \"does not throw\", \"greater than zero\".\n- Only that something was called, or not called, or that a result is empty.\n- An expected value computed the way the code computes it, or by calling the code itself.\n- A restated constant, config default, table row or prompt string.\n- Assertions on data the test built, with no call to the subject.\n- Mocks of the module's own collaborators, tests of private functions, assertions on call counts or order.\n- Checking through a side door, such as reading storage directly, instead of through the interface.\n\n**Fix:**\n- Call the subject in the test body with one concrete input and assert the literal output or effect.\n- For a stand-in at a real seam, assert the payload it received, not only that it was called.\n- For an absence, also assert the presence on another input.\n- For a constant, test the mechanism that reads it with one input instead of restating the value.\n- Verify through the interface: create something, then read it back the way a caller would.\n- Name the test after the behavior (\"a widget over its limit is rejected\"), not the mechanism.\n\n**Keep:** checks that relate rows across tables (a key present in both, a parent that exists) and compile-time type tests.\n\n**The test:** Change the implementation without changing behavior: the test should pass. Break the behavior: it should fail. If either doesn't happen, the test is wrong.\n","# Test Behavior\n\nA test calls the code the way its users do and asserts the exact result they see. Rewrite or delete any test that would still pass if every function it imports returned nothing or a wrong value.\n\n**Why:** A good test fails when behavior breaks and keeps passing through a refactor that leaves behavior alone. A test tied to internals does the opposite: it breaks on harmless changes and stays green on real ones, so people learn to ignore it.\n\n**These shapes fail the check:**\n- A loose assertion or none: \"is defined\", \"is truthy\", \"does not throw\", \"greater than zero\".\n- Only that something was called, or not called, or that a result is empty.\n- An expected value computed the way the code computes it, or by calling the code itself.\n- A restated constant, config default, table row or prompt string.\n- Assertions on data the test built, with no call to the subject.\n- Mocks of the module's own collaborators, tests of private functions, assertions on call counts or order.\n- Checking through a side door, such as reading storage directly, instead of through the interface.\n\n**Fix:**\n- Call the subject in the test body with one concrete input and assert the literal output or effect.\n- For a stand-in at a real seam, assert the payload it received, not only that it was called.\n- For an absence, also assert the presence on another input.\n- For a constant, test the mechanism that reads it with one input instead of restating the value.\n- Verify through the interface: create something, then read it back the way a caller would.\n- Name the test after the behavior (\"a widget over its limit is rejected\"), not the mechanism.\n\n**Keep:** checks that relate rows across tables (a key present in both, a parent that exists) and compile-time type tests.\n\n**The test:** Change the implementation without changing behavior: the test should pass. Break the behavior: it should fail. If either doesn't happen, the test is wrong.\n",{"name":5,"metadata":24,"description":7},{"layer":25,"source":26,"license":15},"L2","cursor\u002Fplugins@1e5c90a:pstack\u002Fskills\u002Fprinciple-test-behavior-not-implementation\u002FSKILL.md + mattpocock\u002Fskills@49dd158:skills\u002Fengineering\u002Ftdd\u002Ftests.md","main","e57e3dd5c8aec0fe40658397aee9fd9b1d77bb60","plugins\u002Fven\u002Fskills\u002Ftest-behavior","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack","https:\u002F\u002Fgithub.com\u002FVentorius","Heavy testing believer. Workflow automation fan. Fullstack JS developer.","2026-11-04 04:05:46",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Ventorius\u002Fven-stack --skill test-behavior",{"tool":40,"command":41},"bunx","bunx skills add Ventorius\u002Fven-stack --skill test-behavior",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Ventorius\u002Fven-stack --skill test-behavior","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Ftest-behavior\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7ES1P06ZPAGTT7YS4V6MS32","yeet","Take every local change green through the repo's own checks, slice it into conventional commits, push, and with --pr open a pull request on the code host. Use only when the user explicitly asks to yeet, or to commit and push everything; never on your own initiative.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7ES1JHVQEN3YYMRZEBM2E79","write-docs","Write or update documentation from the code: gather facts, pick the shape for the reader, write it plain, and prove every command and path in it. Use when asked to document a repo, module or feature, or to bring stale docs up to date.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fwrite-docs\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7ES1DD3YVMF1MY7D51R6516","why","Find why code is shaped the way it is (design rationale, trade-offs, regressions, odd thresholds) from history, tickets, docs and chat, citing every claim and stating its confidence. Use for 'why does X work this way', 'why did we pick Y', or before changing code whose purpose is unclear.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7ES18XVRZGQ0V1BBZH63Q8W","verify","Prove a change works with the check that matches its type, do the read-back, and log the pass against the exact tree. Use when a change is ready to call done, before review, commit or stopping, and whenever ven-decisions end refuses an unverified tree.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7ES15Z3W8QTJH4CRAJ53D2G","unslop","Cut AI writing tells (filler, model vocabulary, metaphor nouns, hedging, formatting tics) from text while keeping every fact. Use when editing or checking any prose before it ships: docs, PR bodies, reports, skill text.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7ES12GT9WD9NE2X3M1B29ZZ","type-discipline","Apply when designing types or data shapes, reviewing a signature, or handling outside data, in any language. Make wrong states fail early: in the compiler for typed languages, in validated runtime contracts for untyped ones.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Ftype-discipline\u002FSKILL.md",[],[]]