[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERSYB85D8G2CDQ2QMW0366":3,"skill-same:01M7ERSYB85D8G2CDQ2QMW0366":58},{"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},"01M7ERSYB85D8G2CDQ2QMW0366","deep-modules",null,"Apply when designing or reshaping a module's interface, deciding where a seam goes, or making code easier to test. Put a lot of behavior behind a small interface, at a seam where something really varies, and test through it.","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\u002Fdeep-modules\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deep-modules\ndescription: \"Apply when designing or reshaping a module's interface, deciding where a seam goes, or making code easier to test. Put a lot of behavior behind a small interface, at a seam where something really varies, and test through it.\"\nmetadata:\n  layer: L2\n  source: mattpocock\u002Fskills@49dd158:skills\u002Fengineering\u002Fcodebase-design\u002FSKILL.md + DEEPENING.md + DESIGN-IT-TWICE.md\n  license: MIT\n---\n\n# Deep Modules\n\nPut a lot of behavior behind a small interface, at a seam where something actually varies, and test it through that interface.\n\n**Why:** A deep module gives callers leverage (more capability per thing they must learn) and maintainers locality (change, bugs and verification gather in one place). A shallow module makes every caller learn nearly as much as the implementation knows, so complexity spreads instead of shrinking.\n\nThe interface is everything a caller must know: the signature, plus invariants, ordering, error modes, required configuration and performance. Use the exact terms in [references\u002Fvocabulary.md](references\u002Fvocabulary.md).\n\n**Pattern:**\n- **Shrink the interface.** Fewer entry points, simpler parameters, more hidden inside. A good default makes the common call trivial.\n- **Depth belongs to the interface.** The inside may be small swappable parts with their own internal seams; they just aren't exposed.\n- **One adapter is a guess; two make a seam.** Add a seam only where something varies, usually production and test.\n- **Take dependencies, don't create them.** Pass collaborators in, so a test can hand over a stand-in.\n- **Return results instead of mutating.** A function that returns a value is easier to test than one that edits its argument in place.\n- **Test where callers call.** Tests cross the same seam callers do. After deepening, replace the old tests on the shallow parts with tests at the new interface.\n- **Design it twice** when the interface is a real decision. Dependency kinds, seam rules and how to compare alternatives are in [references\u002Fdeepening.md](references\u002Fdeepening.md).\n\n**The test:**\n- **Deletion:** imagine deleting the module. If complexity vanishes, it was a pass-through. If it reappears in every caller, it was earning its keep.\n- **Surface:** is the interface nearly as large as the implementation? Then it is shallow.\n- **Reach:** does a test have to get past the interface to check something? Then the module is the wrong shape.\n\n**Stop:** Don't measure depth as implementation lines over interface lines; that rewards padding. Don't split a module into a chain of tiny pass-throughs so each piece looks simple.\n","# Deep Modules\n\nPut a lot of behavior behind a small interface, at a seam where something actually varies, and test it through that interface.\n\n**Why:** A deep module gives callers leverage (more capability per thing they must learn) and maintainers locality (change, bugs and verification gather in one place). A shallow module makes every caller learn nearly as much as the implementation knows, so complexity spreads instead of shrinking.\n\nThe interface is everything a caller must know: the signature, plus invariants, ordering, error modes, required configuration and performance. Use the exact terms in [references\u002Fvocabulary.md](references\u002Fvocabulary.md).\n\n**Pattern:**\n- **Shrink the interface.** Fewer entry points, simpler parameters, more hidden inside. A good default makes the common call trivial.\n- **Depth belongs to the interface.** The inside may be small swappable parts with their own internal seams; they just aren't exposed.\n- **One adapter is a guess; two make a seam.** Add a seam only where something varies, usually production and test.\n- **Take dependencies, don't create them.** Pass collaborators in, so a test can hand over a stand-in.\n- **Return results instead of mutating.** A function that returns a value is easier to test than one that edits its argument in place.\n- **Test where callers call.** Tests cross the same seam callers do. After deepening, replace the old tests on the shallow parts with tests at the new interface.\n- **Design it twice** when the interface is a real decision. Dependency kinds, seam rules and how to compare alternatives are in [references\u002Fdeepening.md](references\u002Fdeepening.md).\n\n**The test:**\n- **Deletion:** imagine deleting the module. If complexity vanishes, it was a pass-through. If it reappears in every caller, it was earning its keep.\n- **Surface:** is the interface nearly as large as the implementation? Then it is shallow.\n- **Reach:** does a test have to get past the interface to check something? Then the module is the wrong shape.\n\n**Stop:** Don't measure depth as implementation lines over interface lines; that rewards padding. Don't split a module into a chain of tiny pass-throughs so each piece looks simple.\n",{"name":5,"metadata":24,"description":7},{"layer":25,"source":26,"license":15},"L2","mattpocock\u002Fskills@49dd158:skills\u002Fengineering\u002Fcodebase-design\u002FSKILL.md + DEEPENING.md + DESIGN-IT-TWICE.md","main","e57e3dd5c8aec0fe40658397aee9fd9b1d77bb60","plugins\u002Fven\u002Fskills\u002Fdeep-modules","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 deep-modules",{"tool":40,"command":41},"bunx","bunx skills add Ventorius\u002Fven-stack --skill deep-modules",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Ventorius\u002Fven-stack --skill deep-modules","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdeep-modules\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdeepening.md","REFERENCE","参考文档",2512,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdeep-modules\u002Freferences\u002Fdeepening.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fvocabulary.md",2183,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdeep-modules\u002Freferences\u002Fvocabulary.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[]]