[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EEMCEXSW312W2JB4NK1X0M":3,"skill-same:01M7EEMCEXSW312W2JB4NK1X0M":61},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EEMCEXSW312W2JB4NK1X0M","tdd",null,"Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","luestr\u002Fskills","luestr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152216177?v=4","01M7EEH85TQXC26ZZTNFPWV5E9","可莉","01M7EEH86EYXTVTCERP22VMFXX",94,"MIT","https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fmattpocock\u002Fen-US\u002Fengineering\u002Ftdd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tdd\ndescription: Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.\nmetadata:\n  language: en-US\n---\n\n# Test-Driven Development\n\nTDD is the red → green loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, the anti-patterns, and the rules of the loop. Every section applies on every cycle: consult them before and during the loop, not after.\n\nWhen exploring the codebase, read `GLOSSARY.md` (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.\n\n## What a good test is\n\nTests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. A good test reads like a specification: \"user can checkout with valid cart\" tells you exactly what capability exists, and it survives refactors because it doesn't care about internal structure.\n\nSee [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines.\n\n## Seams: where tests go\n\nA **seam** is the public boundary you test at: the interface where you observe behavior without reaching inside. Tests live at seams, never against internals.\n\n**Test only at pre-agreed seams.** Before writing any test, write down the seams under test and confirm them with the user. No test is written at an unconfirmed seam. You can't test everything, so agreeing the seams up front is how testing effort lands on the critical paths and complex logic instead of every edge case.\n\nAsk: \"What's the public interface, and which seams should we test?\" Give each proposed seam a one-line note on what it catches and what it misses.\n\nWhen the shape of that interface is itself in question (how deep the module is, where the seam belongs, what the interface should expose), call the Skill tool with \"codebase-design\" for the vocabulary. It is the shared source of the module, interface, depth, seam, adapter, leverage and locality terms, and it is a reference to consult, not a session to run.\n\n## Anti-patterns\n\n- **Implementation-coupled**: mocks internal collaborators, tests private methods, or verifies through a side channel (querying the database instead of using the interface). The tell: the test breaks when you refactor but behavior hasn't changed.\n- **Tautological**: the assertion recomputes the expected value the way the code does (`expect(add(a, b)).toBe(a + b)`, a snapshot derived by hand the same way, a constant asserted equal to itself), so it passes by construction and can never disagree with the code. Expected values must come from an independent source of truth: a known-good literal, a worked example, the spec.\n- **Horizontal slicing**: writing all tests first, then all implementation. Bulk tests verify _imagined_ behavior: you test the _shape_ of things rather than user-facing behavior, the tests go insensitive to real changes, and you commit to test structure before understanding the implementation. Work in **vertical slices** instead: one test → one implementation → repeat, each test a **tracer bullet** that responds to what the last cycle taught you.\n\n## Rules of the loop\n\n- **Red before green.** Write the failing test first, then only enough code to pass it. Don't anticipate future tests or add speculative features.\n- **One slice at a time.** One seam, one test, one minimal implementation per cycle.\n- **Refactoring is not part of the loop.** It belongs to the review stage (see the `code-review` skill), not the red → green implementation cycle.\n","# Test-Driven Development\n\nTDD is the red → green loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, the anti-patterns, and the rules of the loop. Every section applies on every cycle: consult them before and during the loop, not after.\n\nWhen exploring the codebase, read `GLOSSARY.md` (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.\n\n## What a good test is\n\nTests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. A good test reads like a specification: \"user can checkout with valid cart\" tells you exactly what capability exists, and it survives refactors because it doesn't care about internal structure.\n\nSee [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines.\n\n## Seams: where tests go\n\nA **seam** is the public boundary you test at: the interface where you observe behavior without reaching inside. Tests live at seams, never against internals.\n\n**Test only at pre-agreed seams.** Before writing any test, write down the seams under test and confirm them with the user. No test is written at an unconfirmed seam. You can't test everything, so agreeing the seams up front is how testing effort lands on the critical paths and complex logic instead of every edge case.\n\nAsk: \"What's the public interface, and which seams should we test?\" Give each proposed seam a one-line note on what it catches and what it misses.\n\nWhen the shape of that interface is itself in question (how deep the module is, where the seam belongs, what the interface should expose), call the Skill tool with \"codebase-design\" for the vocabulary. It is the shared source of the module, interface, depth, seam, adapter, leverage and locality terms, and it is a reference to consult, not a session to run.\n\n## Anti-patterns\n\n- **Implementation-coupled**: mocks internal collaborators, tests private methods, or verifies through a side channel (querying the database instead of using the interface). The tell: the test breaks when you refactor but behavior hasn't changed.\n- **Tautological**: the assertion recomputes the expected value the way the code does (`expect(add(a, b)).toBe(a + b)`, a snapshot derived by hand the same way, a constant asserted equal to itself), so it passes by construction and can never disagree with the code. Expected values must come from an independent source of truth: a known-good literal, a worked example, the spec.\n- **Horizontal slicing**: writing all tests first, then all implementation. Bulk tests verify _imagined_ behavior: you test the _shape_ of things rather than user-facing behavior, the tests go insensitive to real changes, and you commit to test structure before understanding the implementation. Work in **vertical slices** instead: one test → one implementation → repeat, each test a **tracer bullet** that responds to what the last cycle taught you.\n\n## Rules of the loop\n\n- **Red before green.** Write the failing test first, then only enough code to pass it. Don't anticipate future tests or add speculative features.\n- **One slice at a time.** One seam, one test, one minimal implementation per cycle.\n- **Refactoring is not part of the loop.** It belongs to the review stage (see the `code-review` skill), not the red → green implementation cycle.\n",{"name":5,"metadata":24,"description":7},{"language":25},"en-US","main","e755255990a0250bbae1a416cea9388f10b6bf6a","mattpocock\u002Fen-US\u002Fengineering\u002Ftdd",1,"https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fluestr","2026-11-14 01:15:26",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add luestr\u002Fskills --skill tdd",{"tool":39,"command":40},"bunx","bunx skills add luestr\u002Fskills --skill tdd",{"tool":42,"command":43},"pnpm","pnpm dlx skills add luestr\u002Fskills --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fmattpocock\u002Fen-US\u002Fengineering\u002Ftdd\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",87,"https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fmattpocock\u002Fen-US\u002Fengineering\u002Ftdd\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"mocking.md",1481,"https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fmattpocock\u002Fen-US\u002Fengineering\u002Ftdd\u002Fmocking.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"tests.md",2214,"https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fmattpocock\u002Fen-US\u002Fengineering\u002Ftdd\u002Ftests.md",[62,69,75,82,88,95],{"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},"01M7EESZM2QJKA5M0QS4M0WNGA","write-ublock-origin-filters","完整的 uBlock Origin (uBO) 静态过滤语法参考。编写 uBlock Origin 自定义过滤规则时使用此技能，涵盖广告拦截、隐私保护或内容过滤。包含基础网络过滤模式（||、*、^、|）、所有网络过滤选项（$domain、$third-party、$important、$redirect、$removeparam、$csp、$replace、$header、$method、$denyallow、$badfilter、$all 等）、内容类型选项（$script、$image、$stylesheet、$font、$media、$xhr、$popup、$document、$frame 等）、元素隐藏规则（## 选择器、实体匹配、主机名正则）、过程式元素隐藏过滤器（:has、:has-text、:matches-css、:upward、:xpath、:matches-path、:watch-attr 等）、动作操作符（:remove、:style、:remove-attr、:remove-class）、HTML 过滤器（##^）、响应头过滤（##^responseheader）、脚本注入（##+js()）以及预处理指令（!#include、!#if）。当用户提到 uBlock Origin 过滤规则、uBO 语法、广告拦截规则、元素隐藏规则、过程式选择器、脚本注入或希望编写\u002F调试任何 uBO 兼容过滤列表时触发。即使用户只是在编写或调试 uBlock Origin 过滤规则、创建自定义过滤列表或从 AdBlock Plus\u002FAdGuard 迁移过滤规则到 uBO，也应使用此技能。","https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fwrite-ublock-origin-filters\u002Fzh-CN\u002Fwrite-ublock-origin-filters\u002FSKILL.md",[],[],{"skillNo":70,"name":64,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EESN8NBTRJE793B87NBGA5","Complete uBlock Origin (uBO) static filter reference. Use this skill when writing or debugging uBO custom filters or filter lists for ad blocking, privacy or content filtering, or when migrating filters from AdBlock Plus\u002FAdGuard. Covers network patterns (||, *, ^, |) and options ($domain, $third-party, $important, $redirect, $removeparam, $csp, $replace, $header, $method, $badfilter, $all), content-type options ($script, $image, $stylesheet, $font, $media, $xhr, $popup, $document, $frame), cosmetic filters (##, CSS selectors, entity matching), procedural filters (:has, :has-text, :matches-css, :upward, :xpath, :matches-path, :watch-attr), action operators (:remove, :style, :remove-attr), HTML filters (##^), response-header filtering (##^responseheader), scriptlet injection (##+js()), and pre-parsing directives (!#include, !#if). Trigger whenever the user mentions uBO syntax, ad blocking rules, element hiding, procedural selectors, scriptlet injection, or a uBO-compatible filter list.","https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fwrite-ublock-origin-filters\u002Fen-US\u002Fwrite-ublock-origin-filters\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EESH94GM6NWB3JAFRH7D8S","write-tampermonkey-scripts","引导 AI 代理规划、编写、调试、测试和维护 Tampermonkey 用户脚本。当用户请求用户脚本、浏览器页面自动化、DOM 增强、Tampermonkey 元数据、GM_* API、@match、@grant、@run-at、@connect、跨源请求、SPA 页面集成或脚本注入任务时使用此技能，即使用户没有明确提及 Tampermonkey。","https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fwrite-tampermonkey-scripts\u002Fzh-CN\u002Fwrite-tampermonkey-scripts\u002FSKILL.md",[],[],{"skillNo":83,"name":77,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7EESCKXFQ793C4TCKSV0GZ1","Guide an AI agent through planning, writing, debugging, testing, and maintaining Tampermonkey userscripts. Use this skill whenever a user asks for a userscript, browser-page automation, DOM enhancement, Tampermonkey metadata, GM_* API, @match, @grant, @run-at, @connect, cross-origin request, SPA page integration, or script injection task, even when Tampermonkey is not named explicitly.","https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fwrite-tampermonkey-scripts\u002Fen-US\u002Fwrite-tampermonkey-scripts\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7EES6SHP4F6DTQYRJ944KMR","write-adguard-filters","编写 AdGuard 自定义过滤规则时使用此技能。涵盖基本规则语法、所有修饰符（$domain\u002F$third-party\u002F$important\u002F$redirect\u002F$replace\u002F$removeparam\u002F$cookie\u002F$csp 等）、外观规则（元素隐藏\u002FCSS\u002FExtended CSS 选择器）、HTML 过滤、JavaScript\u002F脚本片段规则、非基本规则修饰符、预处理器指令和调试技巧。当用户提及 AdGuard 过滤规则、广告拦截规则语法、过滤器列表编写、ABP 语法兼容、元素隐藏规则、Extended CSS 选择器（:has\u002F:contains\u002F:matches-css 等）时触发。即使用户只是在编写或调试任何类型的广告过滤规则，也应使用此技能。","https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fwrite-adguard-filters\u002Fzh-CN\u002Fwrite-adguard-filters\u002FSKILL.md",[],[],{"skillNo":96,"name":90,"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},"01M7EERZ661557QAD511EBSCCK","Complete AdGuard filtering rules syntax reference. Use this skill when writing AdGuard custom filters. Covers basic rule syntax, all modifiers ($domain\u002F$third-party\u002F$important\u002F$redirect\u002F$replace\u002F$removeparam\u002F$cookie\u002F$csp etc.), cosmetic rules (element hiding\u002FCSS\u002FExtended CSS selectors), HTML filtering, JavaScript\u002Fscriptlet rules, non-basic rule modifiers, preprocessor directives, and debugging. Trigger when user mentions AdGuard filtering rules, ad blocking rule syntax, filter list authoring, ABP syntax compatibility, element hiding rules, Extended CSS selectors (:has\u002F:contains\u002F:matches-css etc.). Use this skill even when the user is just writing or debugging any type of ad filtering rules.","https:\u002F\u002Fgithub.com\u002Fluestr\u002Fskills\u002Fblob\u002Fmain\u002Fwrite-adguard-filters\u002Fen-US\u002Fwrite-adguard-filters\u002FSKILL.md",[],[]]