[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AJXAFBTKM0ACPHWTYQ4X5E":3,"skill-same:01M7AJXAFBTKM0ACPHWTYQ4X5E":49},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AJXAFBTKM0ACPHWTYQ4X5E","claudeloop-architecture",null,"Explains claudeloop's onion architecture — the four layers (domain, application, infrastructure, cli), the import-linter contract enforcing them, and exactly where new code belongs. Use this whenever adding a new file, class, or function to src\u002Fclaudeloop\u002F, whenever unsure which layer something belongs in, whenever import-linter or lint-imports fails, or when the user mentions \"onion architecture\", \"layers\", \"ports and adapters\", \"bootstrap.py\", \"composition root\", or asks \"where should this go\". Make sure to consult this before writing any new module under src\u002Fclaudeloop\u002F — placing code in the wrong layer is the most common mistake in this codebase and import-linter will reject it in CI regardless.","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.claude\u002Fskills\u002Fclaudeloop-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: claudeloop-architecture\ndescription: Explains claudeloop's onion architecture — the four layers (domain, application, infrastructure, cli), the import-linter contract enforcing them, and exactly where new code belongs. Use this whenever adding a new file, class, or function to src\u002Fclaudeloop\u002F, whenever unsure which layer something belongs in, whenever import-linter or lint-imports fails, or when the user mentions \"onion architecture\", \"layers\", \"ports and adapters\", \"bootstrap.py\", \"composition root\", or asks \"where should this go\". Make sure to consult this before writing any new module under src\u002Fclaudeloop\u002F — placing code in the wrong layer is the most common mistake in this codebase and import-linter will reject it in CI regardless.\nallowed-tools: Read Grep Glob Bash(lint-imports)\n---\n\n# claudeloop architecture\n\n`claudeloop` is a strict onion \u002F ports-and-adapters design. Dependencies\npoint inward only. This is enforced in CI and pre-commit by `import-linter`,\nnot by convention — a violation fails with a named contract error, not a\nreview comment.\n\n## The four layers, innermost first\n\n```\nsrc\u002Fclaudeloop\u002F\n├── domain\u002F           # PURE. stdlib only. No I\u002FO, no async, no third-party imports.\n├── application\u002F       # Protocol-based ports + use cases. Imports domain + stdlib only.\n├── infrastructure\u002F    # Adapters. The ONLY layer allowed to import anthropic \u002F\n│                       #   claude_agent_sdk \u002F structlog \u002F httpx \u002F any third-party SDK.\n├── cli\u002F                # Typer commands. Calls application use cases via bootstrap.\n└── bootstrap.py         # Composition root — the ONE module allowed to see every layer.\n```\n\n## The decision test — where does new code go?\n\nAsk in this order:\n\n1. **Does it touch the filesystem, network, clock, or an SDK?**\n   → `infrastructure\u002F`, behind a `Protocol` port defined in\n   `application\u002Fports.py`. Never call `anthropic.*` or `claude_agent_sdk.*`\n   from anywhere else.\n\n2. **Is it a decision — a branch determining what happens next — with zero\n   I\u002FO of its own?**\n   → `domain\u002F`. Test: can you write its test as\n   `assert some_function(SomeDataclass(...)) == ExpectedResult(...)` with no\n   mocking, no fixtures beyond dataclass literals? If yes, it's domain.\n   Existing examples: `domain\u002Fclassify.py` (turn signals → capacity state),\n   `domain\u002Fwaiting.py` (capacity state → next probe instant),\n   `domain\u002Fcompletion.py` (structured output → completion verdict),\n   `domain\u002Floop.py` (the run-loop state machine itself).\n\n3. **Is it orchestration — call a port, feed the result to a domain\n   function, call another port?**\n   → `application\u002F`, as a use case in `application\u002Fusecases\u002F` or inside\n   `application\u002Frunner.py`.\n\n4. **Is it argument parsing or terminal output formatting for a human?**\n   → `cli\u002F`.\n\n**When in doubt, push logic inward.** A `cli\u002F` command containing an\n`if\u002Felif` deciding what a rate-limit response *means* is a bug: that\ndecision belongs in `domain\u002Fclassify.py`, testable with zero CLI process\nspun up.\n\n## The enforced import rules\n\nFrom `pyproject.toml`:\n\n```toml\n[[tool.importlinter.contracts]]\nname = \"Onion layering\"\ntype = \"layers\"\nlayers = [\"claudeloop.cli\", \"claudeloop.bootstrap\", \"claudeloop.application\", \"claudeloop.domain\"]\n\n[[tool.importlinter.contracts]]\nname = \"Infrastructure only reachable from bootstrap\"\ntype = \"forbidden\"\nsource_modules = [\"claudeloop.domain\", \"claudeloop.application\"]\nforbidden_modules = [\"claudeloop.infrastructure\"]\n```\n\nConcretely:\n\n- `domain\u002F*.py` may `import` from stdlib and other `domain\u002F*` modules ONLY.\n  No `typing.Protocol`-based ports either — those live one layer out.\n- `application\u002F*.py` may import `domain` and stdlib. Ports are\n  `typing.Protocol`, never an ABC a concrete adapter must inherit from —\n  this is what keeps `application\u002F` from ever needing to import\n  `infrastructure\u002F` just to name a type.\n- `infrastructure\u002F*.py` may import `domain`, `application`, and any\n  third-party package. This is the ONLY place `anthropic` or\n  `claude_agent_sdk` appears in an `import` statement anywhere in\n  `src\u002Fclaudeloop\u002F`.\n- `cli\u002F*.py` calls into `application\u002F` use cases obtained from\n  `bootstrap.build_runner(...)` (or equivalent) — never constructs an\n  `infrastructure\u002F` adapter directly.\n- `bootstrap.py` is the single seam permitted to import from every layer —\n  it's where a concrete adapter (e.g.\n  `infrastructure.agent.gateway.ClaudeAgentGateway`) gets wired into the\n  `Protocol` port `application\u002Fports.py` declares (e.g. `AgentGateway`).\n\n## Verifying your change respects the contract\n\n```bash\nlint-imports\n```\n\nRun this before committing any new module. It's also a `pre-commit` hook and\nruns in CI (`ci.yml`). A violation names the exact contract broken —\n\"Onion layering\" or \"Infrastructure only reachable from bootstrap\" — and the\noffending import chain.\n\n## Full reference\n\nSee `docs\u002Farchitecture\u002Foverview.md` for the complete layer table and\n`docs\u002Farchitecture\u002Fdecisions\u002F0001-onion-architecture-with-import-linter.md`\nfor why this was chosen over convention-only layering. See\n`docs\u002Farchitecture\u002Fports-and-adapters.md` for the planned port list\n(M2+) and why ports are `Protocol` rather than ABC.\n","# claudeloop architecture\n\n`claudeloop` is a strict onion \u002F ports-and-adapters design. Dependencies\npoint inward only. This is enforced in CI and pre-commit by `import-linter`,\nnot by convention — a violation fails with a named contract error, not a\nreview comment.\n\n## The four layers, innermost first\n\n```\nsrc\u002Fclaudeloop\u002F\n├── domain\u002F           # PURE. stdlib only. No I\u002FO, no async, no third-party imports.\n├── application\u002F       # Protocol-based ports + use cases. Imports domain + stdlib only.\n├── infrastructure\u002F    # Adapters. The ONLY layer allowed to import anthropic \u002F\n│                       #   claude_agent_sdk \u002F structlog \u002F httpx \u002F any third-party SDK.\n├── cli\u002F                # Typer commands. Calls application use cases via bootstrap.\n└── bootstrap.py         # Composition root — the ONE module allowed to see every layer.\n```\n\n## The decision test — where does new code go?\n\nAsk in this order:\n\n1. **Does it touch the filesystem, network, clock, or an SDK?**\n   → `infrastructure\u002F`, behind a `Protocol` port defined in\n   `application\u002Fports.py`. Never call `anthropic.*` or `claude_agent_sdk.*`\n   from anywhere else.\n\n2. **Is it a decision — a branch determining what happens next — with zero\n   I\u002FO of its own?**\n   → `domain\u002F`. Test: can you write its test as\n   `assert some_function(SomeDataclass(...)) == ExpectedResult(...)` with no\n   mocking, no fixtures beyond dataclass literals? If yes, it's domain.\n   Existing examples: `domain\u002Fclassify.py` (turn signals → capacity state),\n   `domain\u002Fwaiting.py` (capacity state → next probe instant),\n   `domain\u002Fcompletion.py` (structured output → completion verdict),\n   `domain\u002Floop.py` (the run-loop state machine itself).\n\n3. **Is it orchestration — call a port, feed the result to a domain\n   function, call another port?**\n   → `application\u002F`, as a use case in `application\u002Fusecases\u002F` or inside\n   `application\u002Frunner.py`.\n\n4. **Is it argument parsing or terminal output formatting for a human?**\n   → `cli\u002F`.\n\n**When in doubt, push logic inward.** A `cli\u002F` command containing an\n`if\u002Felif` deciding what a rate-limit response *means* is a bug: that\ndecision belongs in `domain\u002Fclassify.py`, testable with zero CLI process\nspun up.\n\n## The enforced import rules\n\nFrom `pyproject.toml`:\n\n```toml\n[[tool.importlinter.contracts]]\nname = \"Onion layering\"\ntype = \"layers\"\nlayers = [\"claudeloop.cli\", \"claudeloop.bootstrap\", \"claudeloop.application\", \"claudeloop.domain\"]\n\n[[tool.importlinter.contracts]]\nname = \"Infrastructure only reachable from bootstrap\"\ntype = \"forbidden\"\nsource_modules = [\"claudeloop.domain\", \"claudeloop.application\"]\nforbidden_modules = [\"claudeloop.infrastructure\"]\n```\n\nConcretely:\n\n- `domain\u002F*.py` may `import` from stdlib and other `domain\u002F*` modules ONLY.\n  No `typing.Protocol`-based ports either — those live one layer out.\n- `application\u002F*.py` may import `domain` and stdlib. Ports are\n  `typing.Protocol`, never an ABC a concrete adapter must inherit from —\n  this is what keeps `application\u002F` from ever needing to import\n  `infrastructure\u002F` just to name a type.\n- `infrastructure\u002F*.py` may import `domain`, `application`, and any\n  third-party package. This is the ONLY place `anthropic` or\n  `claude_agent_sdk` appears in an `import` statement anywhere in\n  `src\u002Fclaudeloop\u002F`.\n- `cli\u002F*.py` calls into `application\u002F` use cases obtained from\n  `bootstrap.build_runner(...)` (or equivalent) — never constructs an\n  `infrastructure\u002F` adapter directly.\n- `bootstrap.py` is the single seam permitted to import from every layer —\n  it's where a concrete adapter (e.g.\n  `infrastructure.agent.gateway.ClaudeAgentGateway`) gets wired into the\n  `Protocol` port `application\u002Fports.py` declares (e.g. `AgentGateway`).\n\n## Verifying your change respects the contract\n\n```bash\nlint-imports\n```\n\nRun this before committing any new module. It's also a `pre-commit` hook and\nruns in CI (`ci.yml`). A violation names the exact contract broken —\n\"Onion layering\" or \"Infrastructure only reachable from bootstrap\" — and the\noffending import chain.\n\n## Full reference\n\nSee `docs\u002Farchitecture\u002Foverview.md` for the complete layer table and\n`docs\u002Farchitecture\u002Fdecisions\u002F0001-onion-architecture-with-import-linter.md`\nfor why this was chosen over convention-only layering. See\n`docs\u002Farchitecture\u002Fports-and-adapters.md` for the planned port list\n(M2+) and why ports are `Protocol` rather than ABC.\n",{"name":5,"description":7,"allowed-tools":24},"Read Grep Glob Bash(lint-imports)","develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_runners\u002Fclaude\u002F.claude\u002Fskills\u002Fclaudeloop-architecture",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add the-vibey-project\u002Fvibey --skill claudeloop-architecture",{"tool":41,"command":42},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill claudeloop-architecture",{"tool":44,"command":45},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill claudeloop-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_runners\u002Fclaude\u002F.claude\u002Fskills\u002Fclaudeloop-architecture\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]