[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AJXVPQNAV5N8C2RB6EX4DM":3,"skill-same:01M7AJXVPQNAV5N8C2RB6EX4DM":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},"01M7AJXVPQNAV5N8C2RB6EX4DM","claudeloop-docs",null,"Explains where different kinds of content belong in this repo (CLAUDE.md vs .claude\u002Fskills\u002F vs docs\u002F), how to build and strict-check the MkDocs Material site, and the writing conventions used throughout (Roadmap admonitions, relative links, ADR format). Use this whenever writing or editing any file under docs\u002F, whenever deciding whether new content belongs in CLAUDE.md, a skill, or docs\u002F, whenever the user asks about documentation structure, or before adding a page to mkdocs.yml's nav. Make sure to consult this before adding procedural, multi-step content to CLAUDE.md directly — CLAUDE.md is deliberately kept short and holds only facts; procedures belong in a skill instead, and getting this wrong bloats the context every single session pays for.","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-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: claudeloop-docs\ndescription: Explains where different kinds of content belong in this repo (CLAUDE.md vs .claude\u002Fskills\u002F vs docs\u002F), how to build and strict-check the MkDocs Material site, and the writing conventions used throughout (Roadmap admonitions, relative links, ADR format). Use this whenever writing or editing any file under docs\u002F, whenever deciding whether new content belongs in CLAUDE.md, a skill, or docs\u002F, whenever the user asks about documentation structure, or before adding a page to mkdocs.yml's nav. Make sure to consult this before adding procedural, multi-step content to CLAUDE.md directly — CLAUDE.md is deliberately kept short and holds only facts; procedures belong in a skill instead, and getting this wrong bloats the context every single session pays for.\nallowed-tools: Read Grep Glob Bash(mkdocs *)\n---\n\n# claudeloop documentation\n\n## Where content belongs — the decision table\n\n| Content | Goes in |\n|---|---|\n| An always-true fact, cheap to state, every session needs | `CLAUDE.md` **and** `AGENTS.md` — kept deliberately SHORT, routers not manuals |\n| A procedure for working on a specific part of this codebase | `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` **and** mirrored to `.cursor\u002Frules\u002F\u003Cname>.mdc` **and** `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` |\n| User-facing \"how do I...\" | `docs\u002Fgetting-started\u002F` or `docs\u002Fguides\u002F` |\n| System design — what exists, how pieces fit | `docs\u002Farchitecture\u002F` |\n| The reasoning behind ONE specific hard decision | `docs\u002Farchitecture\u002Fdecisions\u002F` — an ADR |\n| Generated API docs | `docs\u002Freference\u002Fapi.md` via `mkdocstrings` — never hand-write signatures that already exist as docstrings |\n| Contributor process | `docs\u002Fcontributing\u002F` |\n| Historical plans, preserved verbatim once superseded | `docs\u002Fplans\u002F` |\n\n**The CLAUDE.md \u002F AGENTS.md \u002F skill dividing line:** routers hold facts;\nskills\u002Frules hold procedures. If you're about to add a multi-step \"when\ndoing X, do Y then Z\" instruction to `CLAUDE.md` or `AGENTS.md`, it belongs\nin a skill instead — skills load into context only when relevant.\n\n### Three agent surfaces (must stay in sync)\n\n| Surface | Paths |\n|---|---|\n| Claude Code | `CLAUDE.md` + `.claude\u002Fskills\u002F*\u002FSKILL.md` |\n| Cursor | `.cursor\u002Frules\u002Fclaudeloop-router.mdc` (always) + `.cursor\u002Frules\u002Fclaudeloop-*.mdc` |\n| Codex | `AGENTS.md` + `.agents\u002Fskills\u002F*\u002FSKILL.md` |\n\n**PR checklist:** when procedural guidance changes, update all three trees\nin the same PR. No codegen in v1 — manual mirror.\n\n## Building and checking the site\n\n```bash\npip install -e \".[docs]\"\nmkdocs serve      # local preview at http:\u002F\u002F127.0.0.1:8000, live-reloads\nmkdocs build --strict   # what CI runs — fails on ANY warning, most commonly a broken link\n```\n\nRun `mkdocs build --strict` before opening a PR that touches `docs\u002F` — it's\nexactly what `docs.yml` runs in CI.\n\n## Writing conventions\n\n- **Plain markdown only** — the extensions enabled in `mkdocs.yml`\n  (admonitions, code fences, tables) and nothing docs-only-syntax beyond\n  that, because every page must read correctly as plain text on GitHub\n  (`CLAUDE.md` and the skills link straight to file paths, not built-site\n  URLs).\n- **Relative links, not absolute site URLs** — so links work both on GitHub\n  and in the built MkDocs site.\n- **Explain \"why,\" not just \"what.\"** A page restating a function signature\n  the code already shows isn't earning its place — put reasoning a stranger\n  can't get from the code alone into the page. This is exactly the ADRs'\n  purpose.\n- **Mark roadmap content with `!!! note \"Roadmap\"`** at the top of any page\n  describing a not-yet-built milestone, so a reader never mistakes a design\n  intention for current behavior. `grep -rl '!!! note \"Roadmap\"' docs\u002F`\n  finds every page that needs revisiting as a milestone lands.\n- **New page → add it to `mkdocs.yml`'s `nav:`** or `mkdocs build --strict`\n  will not error (an orphaned page is not itself a strict-mode failure) but\n  the page becomes unreachable from the site nav — always add it.\n\n## ADR format\n\nFollow the existing files in `docs\u002Farchitecture\u002Fdecisions\u002F` exactly:\n`NNNN-kebab-case-title.md`, sections `## Status` \u002F `## Context` \u002F `##\nDecision` \u002F `## Consequences`, four-digit zero-padded sequential numbering.\nAdd a new ADR when a PR makes a hard, non-obvious design call worth\npreserving the reasoning for — not for routine changes.\n\n## Full reference\n\n`docs\u002Fcontributing\u002Fdocumentation.md`.\n","# claudeloop documentation\n\n## Where content belongs — the decision table\n\n| Content | Goes in |\n|---|---|\n| An always-true fact, cheap to state, every session needs | `CLAUDE.md` **and** `AGENTS.md` — kept deliberately SHORT, routers not manuals |\n| A procedure for working on a specific part of this codebase | `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` **and** mirrored to `.cursor\u002Frules\u002F\u003Cname>.mdc` **and** `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` |\n| User-facing \"how do I...\" | `docs\u002Fgetting-started\u002F` or `docs\u002Fguides\u002F` |\n| System design — what exists, how pieces fit | `docs\u002Farchitecture\u002F` |\n| The reasoning behind ONE specific hard decision | `docs\u002Farchitecture\u002Fdecisions\u002F` — an ADR |\n| Generated API docs | `docs\u002Freference\u002Fapi.md` via `mkdocstrings` — never hand-write signatures that already exist as docstrings |\n| Contributor process | `docs\u002Fcontributing\u002F` |\n| Historical plans, preserved verbatim once superseded | `docs\u002Fplans\u002F` |\n\n**The CLAUDE.md \u002F AGENTS.md \u002F skill dividing line:** routers hold facts;\nskills\u002Frules hold procedures. If you're about to add a multi-step \"when\ndoing X, do Y then Z\" instruction to `CLAUDE.md` or `AGENTS.md`, it belongs\nin a skill instead — skills load into context only when relevant.\n\n### Three agent surfaces (must stay in sync)\n\n| Surface | Paths |\n|---|---|\n| Claude Code | `CLAUDE.md` + `.claude\u002Fskills\u002F*\u002FSKILL.md` |\n| Cursor | `.cursor\u002Frules\u002Fclaudeloop-router.mdc` (always) + `.cursor\u002Frules\u002Fclaudeloop-*.mdc` |\n| Codex | `AGENTS.md` + `.agents\u002Fskills\u002F*\u002FSKILL.md` |\n\n**PR checklist:** when procedural guidance changes, update all three trees\nin the same PR. No codegen in v1 — manual mirror.\n\n## Building and checking the site\n\n```bash\npip install -e \".[docs]\"\nmkdocs serve      # local preview at http:\u002F\u002F127.0.0.1:8000, live-reloads\nmkdocs build --strict   # what CI runs — fails on ANY warning, most commonly a broken link\n```\n\nRun `mkdocs build --strict` before opening a PR that touches `docs\u002F` — it's\nexactly what `docs.yml` runs in CI.\n\n## Writing conventions\n\n- **Plain markdown only** — the extensions enabled in `mkdocs.yml`\n  (admonitions, code fences, tables) and nothing docs-only-syntax beyond\n  that, because every page must read correctly as plain text on GitHub\n  (`CLAUDE.md` and the skills link straight to file paths, not built-site\n  URLs).\n- **Relative links, not absolute site URLs** — so links work both on GitHub\n  and in the built MkDocs site.\n- **Explain \"why,\" not just \"what.\"** A page restating a function signature\n  the code already shows isn't earning its place — put reasoning a stranger\n  can't get from the code alone into the page. This is exactly the ADRs'\n  purpose.\n- **Mark roadmap content with `!!! note \"Roadmap\"`** at the top of any page\n  describing a not-yet-built milestone, so a reader never mistakes a design\n  intention for current behavior. `grep -rl '!!! note \"Roadmap\"' docs\u002F`\n  finds every page that needs revisiting as a milestone lands.\n- **New page → add it to `mkdocs.yml`'s `nav:`** or `mkdocs build --strict`\n  will not error (an orphaned page is not itself a strict-mode failure) but\n  the page becomes unreachable from the site nav — always add it.\n\n## ADR format\n\nFollow the existing files in `docs\u002Farchitecture\u002Fdecisions\u002F` exactly:\n`NNNN-kebab-case-title.md`, sections `## Status` \u002F `## Context` \u002F `##\nDecision` \u002F `## Consequences`, four-digit zero-padded sequential numbering.\nAdd a new ADR when a PR makes a hard, non-obvious design call worth\npreserving the reasoning for — not for routine changes.\n\n## Full reference\n\n`docs\u002Fcontributing\u002Fdocumentation.md`.\n",{"name":5,"description":7,"allowed-tools":24},"Read Grep Glob Bash(mkdocs *)","develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_runners\u002Fclaude\u002F.claude\u002Fskills\u002Fclaudeloop-docs",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-docs",{"tool":41,"command":42},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill claudeloop-docs",{"tool":44,"command":45},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill claudeloop-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_runners\u002Fclaude\u002F.claude\u002Fskills\u002Fclaudeloop-docs\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",[],[]]