[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AJWBWMGR2FMW0B048NPF6J":3,"skill-same:01M7AJWBWMGR2FMW0B048NPF6J":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AJWBWMGR2FMW0B048NPF6J","claudeloop-testing",null,"Explains claudeloop's testing philosophy and pytest layout — fakes over mocks for every port, FakeClock\u002FFakeSleeper for simulating multi-day waits without real sleeping, mandatory Hypothesis property tests for numeric\u002Ftime-based invariants, per-layer coverage gates (100% for domain and application), and the documented","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_runners\u002Fclaude\u002F.agents\u002Fskills\u002Fclaudeloop-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: claudeloop-testing\ndescription: Explains claudeloop's testing philosophy and pytest layout — fakes over mocks for every port, FakeClock\u002FFakeSleeper for simulating multi-day waits without real sleeping, mandatory Hypothesis property tests for numeric\u002Ftime-based invariants, per-layer coverage gates (100% for domain and application), and the documented # pragma no cover policy. Use this whenever writing or modifying any test under tests\u002F, whenever the user asks how to test something in this codebase, mentions coverage, Hypothesis, property-based testing, or asks why a coverage gate failed. Make sure to consult this before adding a mock (this codebase uses fakes implementing real Protocols instead), before adding a numeric or time-based config field without a property test, and before adding a # pragma no cover without a stated reason — all three are enforced review expectations here, not suggestions.\n---\n\n# claudeloop testing philosophy\n\n\n> **Codex skill mirror** of `.claude\u002Fskills\u002Fclaudeloop-testing\u002FSKILL.md`. When this guidance changes, update Claude skill, Cursor rule, and `.agents\u002Fskills\u002F` in the same PR.\n\n## Layout\n\n```\ntests\u002Fdomain\u002F           # pure unit + Hypothesis property tests\ntests\u002Fapplication\u002F      # fakes for every port (fakes.py), zero real I\u002FO\ntests\u002Finfrastructure\u002F   # adapters (incl. scripted test-agent unit tests)\ntests\u002Fcli\u002F\ntests\u002Flive\u002F             # opt-in free + paid live tiers\ntests\u002Flive\u002Fsystem\u002F      # marker: system — real FS\u002Fgit\u002FCLI + scripted agent\n```\n\nRun: `pytest` (skips `live` and `system` via addopts).\nSystem harness: `pytest -m system`.\nLive free: `pytest -m live`. Paid: `pytest -m \"live and paid\" --run-paid-live`.\nSee `docs\u002Fguides\u002Flive-testing.md`.\n\nCoverage: `pytest --cov-report=term-missing` (already the default via\n`addopts` in `pyproject.toml`).\n\nTest-only agent gate (composition root only; not a user feature):\n`CLAUDELOOP_ALLOW_TEST_AGENT=1` + `CLAUDELOOP_TEST_AGENT_SCRIPT=\u003Cjson>`.\n\n## Coverage is per-layer, not global — and why\n\nThere is deliberately **no** blanket `--cov-fail-under` in `pyproject.toml`.\nCI enforces coverage separately per layer: **100%** on `domain\u002F` and\n`application\u002F` (zero I\u002FO, zero third-party deps — no excuse for an untested\nbranch, and this is the code deciding whether an unattended multi-day run\nkeeps going, waits, or gives up), a lower floor on `infrastructure\u002F`\u002F`cli\u002F`.\nWhen adding domain code, run coverage scoped to it and treat anything less\nthan 100% as a defect, not a number to negotiate down.\n\n## Fakes, never `unittest.mock.Mock`, for ports\n\nEvery port in `application\u002Fports.py` gets a real class\nimplementing the same `Protocol` — checked by `mypy --strict` against the\nport shape. A `Mock` has no such check; a port method rename silently\nbreaks nothing in test code, possibly not even at runtime. If you're\ntempted to `from unittest.mock import Mock` for a port, write a small\n`FakeXxx` class instead.\n\n## `FakeClock` \u002F `FakeSleeper` — never sleep for real in a test\n\n`domain\u002Fwaiting.py` is designed entirely around instants\n(`next_probe_instant() -> datetime`), never durations, specifically so\ntests never call real `time.sleep()`. Pattern (tests\u002Fapplication\u002Ffakes.py):\n\n```python\nclock = FakeClock(start=NOW)\nsleeper = FakeSleeper(clock)  # sleep_until(instant) jumps clock straight there, no real delay\n```\n\nThis is what lets a test simulate a **seven-day rate-limit wait** or the\n**credit-top-up scenario** (already covered at the domain layer —\n`test_credit_topup_sequence_resumes_after_several_failed_probes` in\n`tests\u002Fdomain\u002Ftest_loop.py`) in milliseconds. Do not use\n`unittest.mock.patch(\"time.sleep\")` — a real fake port is one thing to\nreason about; a patched stdlib call is something every test touching timing\nhas to remember to apply consistently.\n\n## Hypothesis property tests are mandatory for numeric\u002Ftime-based logic\n\nNot a nice-to-have. `test_property_credits_probe_never_in_the_past_and_never_exceeds_ceiling`\nin `tests\u002Fdomain\u002Ftest_waiting.py` caught a real production-shaped bug during\ndevelopment: `probe_count=29, factor=3.0` overflowed `timedelta`'s max\nmagnitude via unclamped exponential backoff — an example-based test at any\nhand-picked `probe_count` would never have found this. When you add a\nnumeric config field (an interval, ceiling, factor, budget cap), write a\n`@given(...)` test asserting the invariant holds across the *entire* valid\ninput space, not a handful of examples. Two existing property tests to use\nas templates: the one above, and\n`test_property_never_proposes_instant_beyond_max_wait`.\n\n## Golden fixtures from real transcripts\n\nPrefer capturing real observed SDK\u002FAPI payloads as test fixtures over\ninventing synthetic ones — a real `credits_required` 429 rejection from a\ndevelopment transcript is already used this way; the shape of a real error\npayload is rarely exactly what you'd guess.\n\n## `# pragma: no cover` — reserved, and always justified inline\n\nEvery use must carry a comment explaining *why* the branch is unreachable,\nnot just that it is. Two real examples already in the codebase:\n\n```python\nif candidate \u003C now:  # pragma: no cover — unreachable: all config intervals are\n    candidate = now  # validated positive in __post_init__, so every branch above\n    # already yields candidate >= now. Kept as a defensive invariant guard.\n```\n\nA bare `# pragma: no cover` with no reasoning will be rejected in review —\ngrep the codebase for the pattern above before adding a new one, and match\nthat level of specificity.\n\n## Full reference\n\n`docs\u002Fcontributing\u002Ftesting.md`.\n","# claudeloop testing philosophy\n\n\n> **Codex skill mirror** of `.claude\u002Fskills\u002Fclaudeloop-testing\u002FSKILL.md`. When this guidance changes, update Claude skill, Cursor rule, and `.agents\u002Fskills\u002F` in the same PR.\n\n## Layout\n\n```\ntests\u002Fdomain\u002F           # pure unit + Hypothesis property tests\ntests\u002Fapplication\u002F      # fakes for every port (fakes.py), zero real I\u002FO\ntests\u002Finfrastructure\u002F   # adapters (incl. scripted test-agent unit tests)\ntests\u002Fcli\u002F\ntests\u002Flive\u002F             # opt-in free + paid live tiers\ntests\u002Flive\u002Fsystem\u002F      # marker: system — real FS\u002Fgit\u002FCLI + scripted agent\n```\n\nRun: `pytest` (skips `live` and `system` via addopts).\nSystem harness: `pytest -m system`.\nLive free: `pytest -m live`. Paid: `pytest -m \"live and paid\" --run-paid-live`.\nSee `docs\u002Fguides\u002Flive-testing.md`.\n\nCoverage: `pytest --cov-report=term-missing` (already the default via\n`addopts` in `pyproject.toml`).\n\nTest-only agent gate (composition root only; not a user feature):\n`CLAUDELOOP_ALLOW_TEST_AGENT=1` + `CLAUDELOOP_TEST_AGENT_SCRIPT=\u003Cjson>`.\n\n## Coverage is per-layer, not global — and why\n\nThere is deliberately **no** blanket `--cov-fail-under` in `pyproject.toml`.\nCI enforces coverage separately per layer: **100%** on `domain\u002F` and\n`application\u002F` (zero I\u002FO, zero third-party deps — no excuse for an untested\nbranch, and this is the code deciding whether an unattended multi-day run\nkeeps going, waits, or gives up), a lower floor on `infrastructure\u002F`\u002F`cli\u002F`.\nWhen adding domain code, run coverage scoped to it and treat anything less\nthan 100% as a defect, not a number to negotiate down.\n\n## Fakes, never `unittest.mock.Mock`, for ports\n\nEvery port in `application\u002Fports.py` gets a real class\nimplementing the same `Protocol` — checked by `mypy --strict` against the\nport shape. A `Mock` has no such check; a port method rename silently\nbreaks nothing in test code, possibly not even at runtime. If you're\ntempted to `from unittest.mock import Mock` for a port, write a small\n`FakeXxx` class instead.\n\n## `FakeClock` \u002F `FakeSleeper` — never sleep for real in a test\n\n`domain\u002Fwaiting.py` is designed entirely around instants\n(`next_probe_instant() -> datetime`), never durations, specifically so\ntests never call real `time.sleep()`. Pattern (tests\u002Fapplication\u002Ffakes.py):\n\n```python\nclock = FakeClock(start=NOW)\nsleeper = FakeSleeper(clock)  # sleep_until(instant) jumps clock straight there, no real delay\n```\n\nThis is what lets a test simulate a **seven-day rate-limit wait** or the\n**credit-top-up scenario** (already covered at the domain layer —\n`test_credit_topup_sequence_resumes_after_several_failed_probes` in\n`tests\u002Fdomain\u002Ftest_loop.py`) in milliseconds. Do not use\n`unittest.mock.patch(\"time.sleep\")` — a real fake port is one thing to\nreason about; a patched stdlib call is something every test touching timing\nhas to remember to apply consistently.\n\n## Hypothesis property tests are mandatory for numeric\u002Ftime-based logic\n\nNot a nice-to-have. `test_property_credits_probe_never_in_the_past_and_never_exceeds_ceiling`\nin `tests\u002Fdomain\u002Ftest_waiting.py` caught a real production-shaped bug during\ndevelopment: `probe_count=29, factor=3.0` overflowed `timedelta`'s max\nmagnitude via unclamped exponential backoff — an example-based test at any\nhand-picked `probe_count` would never have found this. When you add a\nnumeric config field (an interval, ceiling, factor, budget cap), write a\n`@given(...)` test asserting the invariant holds across the *entire* valid\ninput space, not a handful of examples. Two existing property tests to use\nas templates: the one above, and\n`test_property_never_proposes_instant_beyond_max_wait`.\n\n## Golden fixtures from real transcripts\n\nPrefer capturing real observed SDK\u002FAPI payloads as test fixtures over\ninventing synthetic ones — a real `credits_required` 429 rejection from a\ndevelopment transcript is already used this way; the shape of a real error\npayload is rarely exactly what you'd guess.\n\n## `# pragma: no cover` — reserved, and always justified inline\n\nEvery use must carry a comment explaining *why* the branch is unreachable,\nnot just that it is. Two real examples already in the codebase:\n\n```python\nif candidate \u003C now:  # pragma: no cover — unreachable: all config intervals are\n    candidate = now  # validated positive in __post_init__, so every branch above\n    # already yields candidate >= now. Kept as a defensive invariant guard.\n```\n\nA bare `# pragma: no cover` with no reasoning will be rejected in review —\ngrep the codebase for the pattern above before adding a new one, and match\nthat level of specificity.\n\n## Full reference\n\n`docs\u002Fcontributing\u002Ftesting.md`.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_runners\u002Fclaude\u002F.agents\u002Fskills\u002Fclaudeloop-testing",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill claudeloop-testing",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill claudeloop-testing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill claudeloop-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_runners\u002Fclaude\u002F.agents\u002Fskills\u002Fclaudeloop-testing\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},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\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},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\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},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\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},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\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},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\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},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]