[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C46G00XGM34RZAS02DE5BF":3,"skill-same:01M6C46G00XGM34RZAS02DE5BF":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6C46G00XGM34RZAS02DE5BF","property-based-testing",null,"Incremental rollout policy for property-based testing that preserves readable example-based tests while adding invariant-focused randomized verification. Use when adding randomized testing, validating input ranges, or verifying mathematical properties. DO NOT USE FOR: example-based unit\u002Fintegration tests or TDD workflow (use test-driven-development), React component tests (use ui-testing), or E2E browser tests (use webapp-testing).","Grimblaz\u002Fagent-orchestra","Grimblaz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F74755849?v=4","01M6C430M9XZDHGHPWQVTQ3KMA","01M6C430RJY3MMX0QAZ3X8DR3Y",3,"MIT","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fproperty-based-testing\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"property based testing","testing","verification","webapp","example","rollout","use","e2e","tdd workflow","integration","ui","browser","development","integration tests","component","react","test","workflow","tdd","policy","2026-11-10 10:12:30",false,"---\nname: property-based-testing\ndescription: \"Incremental rollout policy for property-based testing that preserves readable example-based tests while adding invariant-focused randomized verification. Use when adding randomized testing, validating input ranges, or verifying mathematical properties. DO NOT USE FOR: example-based unit\u002Fintegration tests or TDD workflow (use test-driven-development), React component tests (use ui-testing), or E2E browser tests (use webapp-testing).\"\n---\n\n# Property-Based Testing Skill\n\nUse PBT as a complement to example-based tests.\n\n## Rollout Policy\n\n1. Start in domain logic with pure invariants first.\n2. Keep existing unit\u002Fintegration tests as readability and regression anchors.\n3. Begin with small run counts in PR CI, then increase in scheduled or nightly runs.\n4. Require reproducible seeds in all failure reports.\n5. Avoid initial rollout in UI\u002Fadapters until core invariants are stable.\n\n## Guardrails\n\n- Do not replace readable example-based tests with PBT.\n- Keep properties behavior-focused, not implementation-coupled.\n- Treat flaky generators\u002Fshrinking issues as `test defect` and route for test refinement.\n- If infrastructure instability dominates, classify as `harness\u002Fenv defect` and fix the harness before expanding PBT scope.\n\n## Adoption Guidance\n\n- Start with a small invariant set and expand gradually.\n- Add PBT where domain rules are stable and deterministic.\n- Scale run volume only after repeated stable results.\n\n## Gotchas\n\n| Trigger                                                                     | Gotcha                                                                                                  | Fix                                                                                              |\n| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |\n| Replacing readable example-based tests with PBT to be \"more thorough\"       | Example-based tests serve as readable documentation and regression anchors; removing them loses context | PBT complements, never replaces, example-based tests                                             |\n| Writing a property that asserts internal computation steps                  | Property breaks on any internal refactor, same flaw as testing implementation details                   | Keep properties behavior-focused; test invariants (observable outcomes), not mechanisms          |\n| Adding PBT to UI or adapter layers before core domain invariants are stable | Unstable core means properties change constantly; high churn                                            | Start in domain logic with pure invariants; expand outward after stability                       |\n| Setting `runs: 1000` in CI from the start                                   | Slow CI blocks the team immediately on PBT adoption                                                     | Start small in CI (50–100 runs); increase in scheduled or nightly runs after stability confirmed |\n| Not requiring reproducible seeds in failure reports                         | Intermittent PBT failure looks flaky but is reproducible with the right seed                            | Require seed capture in all failure reports from day one                                         |\n| Treating intermittent PBT failures as domain bugs without triage            | Root cause may be the generator or shrinking logic, not domain code                                     | Classify as `test defect`, route to test refinement before investigating domain code             |\n","# Property-Based Testing Skill\n\nUse PBT as a complement to example-based tests.\n\n## Rollout Policy\n\n1. Start in domain logic with pure invariants first.\n2. Keep existing unit\u002Fintegration tests as readability and regression anchors.\n3. Begin with small run counts in PR CI, then increase in scheduled or nightly runs.\n4. Require reproducible seeds in all failure reports.\n5. Avoid initial rollout in UI\u002Fadapters until core invariants are stable.\n\n## Guardrails\n\n- Do not replace readable example-based tests with PBT.\n- Keep properties behavior-focused, not implementation-coupled.\n- Treat flaky generators\u002Fshrinking issues as `test defect` and route for test refinement.\n- If infrastructure instability dominates, classify as `harness\u002Fenv defect` and fix the harness before expanding PBT scope.\n\n## Adoption Guidance\n\n- Start with a small invariant set and expand gradually.\n- Add PBT where domain rules are stable and deterministic.\n- Scale run volume only after repeated stable results.\n\n## Gotchas\n\n| Trigger                                                                     | Gotcha                                                                                                  | Fix                                                                                              |\n| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |\n| Replacing readable example-based tests with PBT to be \"more thorough\"       | Example-based tests serve as readable documentation and regression anchors; removing them loses context | PBT complements, never replaces, example-based tests                                             |\n| Writing a property that asserts internal computation steps                  | Property breaks on any internal refactor, same flaw as testing implementation details                   | Keep properties behavior-focused; test invariants (observable outcomes), not mechanisms          |\n| Adding PBT to UI or adapter layers before core domain invariants are stable | Unstable core means properties change constantly; high churn                                            | Start in domain logic with pure invariants; expand outward after stability                       |\n| Setting `runs: 1000` in CI from the start                                   | Slow CI blocks the team immediately on PBT adoption                                                     | Start small in CI (50–100 runs); increase in scheduled or nightly runs after stability confirmed |\n| Not requiring reproducible seeds in failure reports                         | Intermittent PBT failure looks flaky but is reproducible with the right seed                            | Require seed capture in all failure reports from day one                                         |\n| Treating intermittent PBT failures as domain bugs without triage            | Root cause may be the generator or shrinking logic, not domain code                                     | Classify as `test defect`, route to test refinement before investigating domain code             |\n",{"name":5,"description":7},"main","d5486aacc32c9ca1b07173cfd530f8fe75c29e58","skills\u002Fproperty-based-testing",0,"https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra","https:\u002F\u002Fgithub.com\u002FGrimblaz","2026-08-16 01:12:46",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Grimblaz\u002Fagent-orchestra --skill property-based-testing",{"tool":61,"command":62},"bunx","bunx skills add Grimblaz\u002Fagent-orchestra --skill property-based-testing",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Grimblaz\u002Fagent-orchestra --skill property-based-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fproperty-based-testing\u002FSKILL.md",true,[],[70,90,114,130,158,178],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":80,"publishedAt":43},"01M6C48YMJVFHM7DVGG1WWW5RJ","webapp-testing","Playwright end-to-end testing guidance for web apps, with practical patterns and setup steps. Use when creating or improving browser-based E2E coverage, test stability, and CI execution. DO NOT USE FOR: React component tests (use ui-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), or randomized property tests (use property-based-testing).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[76,77],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[24,81,26,82,41,40,83,39,84,38,37,85,35,34,86,87,30,88,89,29],"webapp testing","canvas","playwright","web","debugging","ci","execution","game","coverage",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":43},"01M6C48TNNP2KCSQXV8YK7SK49","verification-before-completion","Evidence-based verification checklist before marking work complete. Use before PRs, releases, marking tickets done, or any \"I'm finished\" declaration; also when naming a baseline commit for a differential suite claim, when designing a mutation campaign or red-run evidence, when making an absence claim, a universal claim, or a one-time demonstration offered as a standing guarantee, when attributing a measurement or claiming a sweep or verification loop is complete, and when stating what a check or a CI suite will do about a change. DO NOT USE FOR: post-merge cleanup or archival (use post-pr-review) or processing GitHub review comments (use code-review-intake).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[25,97,98,99,100,101,102,103,104,105,106,107,86,108,109,110,111,29,112,113],"verification before completion","review","change","commit","merge","pr","cleanup","run","code","code-review","intake","loop","verification loop","work","check","evidence","campaign",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":43},"01M6C48QZWNTP7JGKD32QZAKKX","validation-methodology","Reusable validation and review methodology for staged validation, failure triage, and prosecution-depth setup. Use when running validation ladders, triaging failures, or executing adversarial review passes. DO NOT USE FOR: CE Gate orchestration, specialist dispatch ownership, or step execution flow (keep those in Code-Conductor).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fvalidation-methodology\u002FSKILL.md",[],[121,122,123,98,124,125,126,127,105,128,87,29,129],"validation","methodology","validation methodology","triage","orchestration","setup","adversarial review","flow","dispatch",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":144,"publishedAt":43},"01M6C48MCAHG5Z79BJ369CRYRZ","upstream-onboarding","Shared opening-phase protocol for upstream agents (Experience-Owner, Solution-Designer, Issue-Planner) and Code-Conductor when invoked on an existing GitHub issue. Renders a scaled context brief and runs a standards check on inherited work at each phase boundary. Use when a user-invocable agent receives a request referencing an existing GitHub issue and must load solution-authoring and upstream-onboarding at the opening phase. DO NOT USE FOR: subagent dispatches (which already operate within an assessed session context); post-merge review (use post-pr-review); research or non-tree subagents.","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fupstream-onboarding\u002FSKILL.md",[136,139],{"categoryNo":137,"categoryName":138,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[145,146,98,147,148,101,149,102,105,150,151,152,153,154,155,110,111,156,157,29],"onboarding","upstream onboarding","github","research","standards check","protocol","brief","boundary","designer","subagent","planner","user","session",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":172,"publishedAt":43},"01M6C48GPVE120TGPMD1CS365H","ui-testing","Resilient React component testing strategies focusing on user behavior. Use when writing or reviewing component-level React tests, fixing flaky component tests, or establishing React testing patterns. DO NOT USE FOR: Playwright E2E tests (use webapp-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), UI component design (use frontend-design), or randomized property tests (use property-based-testing).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fui-testing\u002FSKILL.md",[164,165,166,169],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":170,"categoryName":171,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000032","设计师",[24,33,173,174,175,176,82,40,83,39,38,37,85,35,34,177,30,88,29,26],"ui testing","frontend","design","writing","testing patterns",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":186,"publishedAt":43},"01M6C48DRJ9XBDR2FW0W37DY53","ui-iteration","Reusable screenshot-driven UI polish workflow for iterative visual refinement. Use when improving layout, hierarchy, spacing, feedback, or Tailwind-based presentation through repeated review-and-adjust passes. DO NOT USE FOR: functional bug fixing, accessibility-only audits, or major redesign strategy work (use Code-Smith or frontend-design).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fui-iteration\u002FSKILL.md",[184,185],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":170,"categoryName":171,"taxonomyType":142,"taxonomyTypeDesc":143},[33,187,174,175,98,40,188,105,189,190,191,192,193,110,194,195,29,196],"ui iteration","accessibility","screenshot","Tailwind","polish","ui polish","feedback","redesign","strategy","only"]