[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XRK8HTZF9MYHHX1F41CS5":3,"skill-same:01M77XRK8HTZF9MYHHX1F41CS5":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M77XRK8HTZF9MYHHX1F41CS5","inherit-legacy-style",null,"Legacy-project style inheritance skill. Use when the user types \u002Finherit-legacy-style, or when onboarding an AI coding agent onto a hand-written legacy project and you need to prevent \"style drift\" (the model imposing its pretrained mainstream idioms onto the project). Language- and framework-agnostic — it aligns meta-architecture only, not syntax. Once run, it becomes a behavioral constraint on all subsequent coding tasks. Do NOT use for pure research or one-off questions unrelated to code-style alignment.","503496348-ops\u002Fmischief-production","503496348-ops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266905914?v=4","01M77X5J7XQWWZGT8998HDGXQM","AtomCollide","01M77X5J8V78Y3NXMY6BBC75X9",2,"MIT","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-inherit-legacy-style\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: inherit-legacy-style\ndescription: Legacy-project style inheritance skill. Use when the user types \u002Finherit-legacy-style, or when onboarding an AI coding agent onto a hand-written legacy project and you need to prevent \"style drift\" (the model imposing its pretrained mainstream idioms onto the project). Language- and framework-agnostic — it aligns meta-architecture only, not syntax. Once run, it becomes a behavioral constraint on all subsequent coding tasks. Do NOT use for pure research or one-off questions unrelated to code-style alignment.\nmetadata:\n  origin: community\nallowed-tools: Read, Glob, Grep, Bash, Edit, Write, AskUserQuestion\n---\n\n# Inherit Legacy Style\n\nPrevents AI code style drift in legacy projects by scanning the codebase for implicit conventions across 4 meta-architecture dimensions, resolving conflicts with the user one at a time, and crystallizing the consensus into an enforceable `.ai-style-rules.md`. Fully language- and framework-agnostic.\n\n## When to Activate\n\n- User types `\u002Finherit-legacy-style`\n- User mentions onboarding AI onto a hand-written legacy project\n- User is worried about AI-generated code \"drifting\" from existing project conventions\n- User wants to extract and codify their project's implicit coding rules\n\n## When to Use\n\nUse this skill when you need to preserve legacy project style and prevent AI-generated style drift. See **When to Activate** above for trigger conditions.\n\n## Prerequisites\n\n- Git (recommended; non-Git projects fall back to file timestamps for incremental mode)\n- Read\u002FWrite access to the project root (generates `.ai-style-rules.md` and optionally `CLAUDE.md`)\n\n## Workflow\n\n### Step 0 — Auto-Detect Mode\n\nSilently check for `.ai-style-rules.md` at the project root:\n\n| File exists? | Mode |\n|---|---|\n| No | **Branch A — First-time Full-Scan** |\n| Yes | **Branch B — Incremental Sniff** |\n\nAnnounce the mode in one line and proceed — never ask the user to pick.\n\n### Branch A — First-time Full-Scan\n\n**1. Measure scale, pick a scanning tier**\n\n```bash\ngit ls-files | grep -cE '\\.(js|ts|jsx|tsx|vue|py|go|rs|java|kt|rb|php|cs|swift|c|cpp|h)$'\n```\n\n| Tier | Source files | Strategy |\n|---|---|---|\n| Small | ≲ 50 | Full close-read every source |\n| Medium | 50–500 | Infra layer = full read; business layer = sample 2–3 per dimension |\n| Large | ≳ 500 | Strict sampling + budget cap; `--stat` summary first, then targeted reads |\n\n**2. Scan along 4 dimensions**\n\n1. **File Anatomy** — in-file declaration order (imports → types → main logic → helpers → export)\n2. **State & Control Flow** — naming conventions for async state, pagination, flags\n3. **Infrastructure** — where cross-cutting utils live (interceptors, formatters, middleware)\n4. **Error Handling** — try\u002Fcatch vs global interceptor vs Result return; null-check habits\n\n**3. Apply signal-threshold noise reduction**\n\nBefore interrupting the user, evaluate signal strength:\n\n- **Weak signal** → auto-suppress: minority \u003C5% AND count \u003C10 → majority wins, minority goes to DONTs\n- **Strong signal** → grill: near-even split, or semantic fork on a core dimension\n- **Small-project exception**: sources ≲50, \"3 vs 2\" is NOT a majority → grill it\n\n**4. Resolve conflicts one at a time (Grilling Protocol)**\n\nFor each strong-signal conflict, present exactly ONE question with 4 options:\n\n> Evidence: `pathA` uses style X, `pathB` uses style Y\n> WARNING: Risk: mixing both fractures the project style\n> Choose: `1` follow X  `2` follow Y  `3` this is evolution, update rules  `4` I have a new rule\n\nSuspend until the user answers, then proceed to the next conflict. Never stack questions.\n\n**5. Generate `.ai-style-rules.md`** with three mandatory sections:\n- **[Golden Files]** — real exemplar paths annotated with what they demonstrate\n- **[Naming & State-Control Rules]** — concrete, checkable conventions\n- **[DONTs]** — anti-patterns that must not propagate\n\n**6. Install the persistent hook**\n\nAsk the user for enforcement strength (use `AskUserQuestion`):\n\n| Option | Mechanism |\n|---|---|\n| **1** Soft hook (recommended) | Write `@.ai-style-rules.md` reference into project `CLAUDE.md` |\n| **2** Hard hook | Soft hook + `PreToolUse[Write\\|Edit\\|MultiEdit]` Hook in `settings.json` |\n| **3** No hook | Keep the rules file; user references manually |\n\n### Branch B — Incremental Sniff\n\n1. Read existing `.ai-style-rules.md`; if it has a commit fingerprint, `git diff \u003Clast_hash> HEAD --stat` to pinpoint delta\n2. Read recent Git changes (`git log -3 --stat` → inspect suspect files on demand)\n3. For oversized diffs (>hundreds of files): `--stat` summary only + sample the largest changes\n4. Compare new code against recorded rules → conflicts go through Grilling Protocol\n5. Append evolution log at the end of `.ai-style-rules.md` (never overwrite old rules)\n\n### Per-Turn Enforcement\n\nWhen `.ai-style-rules.md` is in context (loaded via CLAUDE.md), every code-writing task must open with a **compliance declaration** in the reasoning chain, naming the exemplar being followed and the DONTs being avoided.\n\n## How It Works\n\nThis skill auto-detects whether it's a first-time or incremental run via `.ai-style-rules.md` presence:\n\n- **First-time (Branch A)** — Measures project scale, scans codebase across 4 meta-architecture dimensions (File Anatomy, State & Control Flow, Infrastructure, Error Handling), applies signal-threshold noise reduction to suppress weak conflicts, resolves strong-signal conflicts one-at-a-time with the user, generates `.ai-style-rules.md` with Golden Files \u002F Naming Rules \u002F DONTs, and offers optional enforcement hooks.\n- **Incremental (Branch B)** — Reads existing rules, checks recent Git diffs for new or conflicting patterns, runs the same one-at-a-time grilling protocol for any conflicts found, and appends evolution logs without overwriting existing rules.\n- **Per-Turn Enforcement** — When hooked via `CLAUDE.md`, every code-writing task opens with a compliance declaration naming the exemplar followed and the DONTs avoided.\n\n## Output Specification\n\n- `.ai-style-rules.md` at project root (with commit fingerprint + scale tier in header)\n- Optionally `CLAUDE.md` with `@.ai-style-rules.md` reference\n- Evolution logs appended as `### [YYYY-MM-DD] Style Evolution Log` entries\n\n## Anti-Patterns\n\n- FAIL: Do NOT skip the scale measurement step — sampling a 30-file project \"starves\" it; full-scanning a 5,000-file repo blows up\n- FAIL: Do NOT stack multiple conflict questions at once — grilling is strictly one-at-a-time\n- FAIL: Do NOT overwrite old rules in incremental mode — always append evolution logs\n- FAIL: Do NOT default to \"hard hook\" without asking — enforcement strength is the user's call\n- FAIL: Do NOT judge syntax or tech-stack quality — this skill aligns meta-architecture only\n- FAIL: Do NOT copy bugs from exemplar files — reuse structure, flag defects\n\n## Best Practices\n\n- Announce the detected mode (first-time vs incremental) and scale tier in one line before scanning\n- For large projects, read `--stat` summaries first, then targeted `Read` on suspect files\n- Let the signal threshold handle noise — a 843-vs-8 naming split should auto-resolve without user interruption\n- When in doubt about signal strength, lean toward asking\n- The CLAUDE.md soft hook (`@.ai-style-rules.md`) is usually sufficient; hard hook only if the user wants mechanical enforcement\n\n## Related Skills\n\n- `init` — initialize a new CLAUDE.md with codebase documentation\n- `code-review` — review diffs for correctness and style issues\n- `simplify` — review code for reuse and simplification opportunities\n\n## Examples\n\n1. **First-time onboarding**\n   - User: \"Help me onboard AI to this older codebase without changing its style.\"\n   - Action: Run Branch A full-scan → measure scale → scan 4 dimensions → grill conflicts → generate `.ai-style-rules.md` → offer hook strength (soft\u002Fhard\u002Fnone).\n\n2. **Incremental update after team changes**\n   - User: \"We added a new module; keep existing style rules intact.\"\n   - Action: Run Branch B incremental sniff → compare Git deltas to recorded rules → grill any new conflicts → append evolution log without overwriting.\n\n3. **Enforcing DONTs via CLAUDE.md**\n   - User: \"Make sure all new code stays consistent with the project's rules.\"\n   - Action: Soft hook installed → `.ai-style-rules.md` auto-loaded every session → every code-writing task opens with compliance declaration, reusing exemplar patterns and avoiding DONTs.\n","# Inherit Legacy Style\n\nPrevents AI code style drift in legacy projects by scanning the codebase for implicit conventions across 4 meta-architecture dimensions, resolving conflicts with the user one at a time, and crystallizing the consensus into an enforceable `.ai-style-rules.md`. Fully language- and framework-agnostic.\n\n## When to Activate\n\n- User types `\u002Finherit-legacy-style`\n- User mentions onboarding AI onto a hand-written legacy project\n- User is worried about AI-generated code \"drifting\" from existing project conventions\n- User wants to extract and codify their project's implicit coding rules\n\n## When to Use\n\nUse this skill when you need to preserve legacy project style and prevent AI-generated style drift. See **When to Activate** above for trigger conditions.\n\n## Prerequisites\n\n- Git (recommended; non-Git projects fall back to file timestamps for incremental mode)\n- Read\u002FWrite access to the project root (generates `.ai-style-rules.md` and optionally `CLAUDE.md`)\n\n## Workflow\n\n### Step 0 — Auto-Detect Mode\n\nSilently check for `.ai-style-rules.md` at the project root:\n\n| File exists? | Mode |\n|---|---|\n| No | **Branch A — First-time Full-Scan** |\n| Yes | **Branch B — Incremental Sniff** |\n\nAnnounce the mode in one line and proceed — never ask the user to pick.\n\n### Branch A — First-time Full-Scan\n\n**1. Measure scale, pick a scanning tier**\n\n```bash\ngit ls-files | grep -cE '\\.(js|ts|jsx|tsx|vue|py|go|rs|java|kt|rb|php|cs|swift|c|cpp|h)$'\n```\n\n| Tier | Source files | Strategy |\n|---|---|---|\n| Small | ≲ 50 | Full close-read every source |\n| Medium | 50–500 | Infra layer = full read; business layer = sample 2–3 per dimension |\n| Large | ≳ 500 | Strict sampling + budget cap; `--stat` summary first, then targeted reads |\n\n**2. Scan along 4 dimensions**\n\n1. **File Anatomy** — in-file declaration order (imports → types → main logic → helpers → export)\n2. **State & Control Flow** — naming conventions for async state, pagination, flags\n3. **Infrastructure** — where cross-cutting utils live (interceptors, formatters, middleware)\n4. **Error Handling** — try\u002Fcatch vs global interceptor vs Result return; null-check habits\n\n**3. Apply signal-threshold noise reduction**\n\nBefore interrupting the user, evaluate signal strength:\n\n- **Weak signal** → auto-suppress: minority \u003C5% AND count \u003C10 → majority wins, minority goes to DONTs\n- **Strong signal** → grill: near-even split, or semantic fork on a core dimension\n- **Small-project exception**: sources ≲50, \"3 vs 2\" is NOT a majority → grill it\n\n**4. Resolve conflicts one at a time (Grilling Protocol)**\n\nFor each strong-signal conflict, present exactly ONE question with 4 options:\n\n> Evidence: `pathA` uses style X, `pathB` uses style Y\n> WARNING: Risk: mixing both fractures the project style\n> Choose: `1` follow X  `2` follow Y  `3` this is evolution, update rules  `4` I have a new rule\n\nSuspend until the user answers, then proceed to the next conflict. Never stack questions.\n\n**5. Generate `.ai-style-rules.md`** with three mandatory sections:\n- **[Golden Files]** — real exemplar paths annotated with what they demonstrate\n- **[Naming & State-Control Rules]** — concrete, checkable conventions\n- **[DONTs]** — anti-patterns that must not propagate\n\n**6. Install the persistent hook**\n\nAsk the user for enforcement strength (use `AskUserQuestion`):\n\n| Option | Mechanism |\n|---|---|\n| **1** Soft hook (recommended) | Write `@.ai-style-rules.md` reference into project `CLAUDE.md` |\n| **2** Hard hook | Soft hook + `PreToolUse[Write\\|Edit\\|MultiEdit]` Hook in `settings.json` |\n| **3** No hook | Keep the rules file; user references manually |\n\n### Branch B — Incremental Sniff\n\n1. Read existing `.ai-style-rules.md`; if it has a commit fingerprint, `git diff \u003Clast_hash> HEAD --stat` to pinpoint delta\n2. Read recent Git changes (`git log -3 --stat` → inspect suspect files on demand)\n3. For oversized diffs (>hundreds of files): `--stat` summary only + sample the largest changes\n4. Compare new code against recorded rules → conflicts go through Grilling Protocol\n5. Append evolution log at the end of `.ai-style-rules.md` (never overwrite old rules)\n\n### Per-Turn Enforcement\n\nWhen `.ai-style-rules.md` is in context (loaded via CLAUDE.md), every code-writing task must open with a **compliance declaration** in the reasoning chain, naming the exemplar being followed and the DONTs being avoided.\n\n## How It Works\n\nThis skill auto-detects whether it's a first-time or incremental run via `.ai-style-rules.md` presence:\n\n- **First-time (Branch A)** — Measures project scale, scans codebase across 4 meta-architecture dimensions (File Anatomy, State & Control Flow, Infrastructure, Error Handling), applies signal-threshold noise reduction to suppress weak conflicts, resolves strong-signal conflicts one-at-a-time with the user, generates `.ai-style-rules.md` with Golden Files \u002F Naming Rules \u002F DONTs, and offers optional enforcement hooks.\n- **Incremental (Branch B)** — Reads existing rules, checks recent Git diffs for new or conflicting patterns, runs the same one-at-a-time grilling protocol for any conflicts found, and appends evolution logs without overwriting existing rules.\n- **Per-Turn Enforcement** — When hooked via `CLAUDE.md`, every code-writing task opens with a compliance declaration naming the exemplar followed and the DONTs avoided.\n\n## Output Specification\n\n- `.ai-style-rules.md` at project root (with commit fingerprint + scale tier in header)\n- Optionally `CLAUDE.md` with `@.ai-style-rules.md` reference\n- Evolution logs appended as `### [YYYY-MM-DD] Style Evolution Log` entries\n\n## Anti-Patterns\n\n- FAIL: Do NOT skip the scale measurement step — sampling a 30-file project \"starves\" it; full-scanning a 5,000-file repo blows up\n- FAIL: Do NOT stack multiple conflict questions at once — grilling is strictly one-at-a-time\n- FAIL: Do NOT overwrite old rules in incremental mode — always append evolution logs\n- FAIL: Do NOT default to \"hard hook\" without asking — enforcement strength is the user's call\n- FAIL: Do NOT judge syntax or tech-stack quality — this skill aligns meta-architecture only\n- FAIL: Do NOT copy bugs from exemplar files — reuse structure, flag defects\n\n## Best Practices\n\n- Announce the detected mode (first-time vs incremental) and scale tier in one line before scanning\n- For large projects, read `--stat` summaries first, then targeted `Read` on suspect files\n- Let the signal threshold handle noise — a 843-vs-8 naming split should auto-resolve without user interruption\n- When in doubt about signal strength, lean toward asking\n- The CLAUDE.md soft hook (`@.ai-style-rules.md`) is usually sufficient; hard hook only if the user wants mechanical enforcement\n\n## Related Skills\n\n- `init` — initialize a new CLAUDE.md with codebase documentation\n- `code-review` — review diffs for correctness and style issues\n- `simplify` — review code for reuse and simplification opportunities\n\n## Examples\n\n1. **First-time onboarding**\n   - User: \"Help me onboard AI to this older codebase without changing its style.\"\n   - Action: Run Branch A full-scan → measure scale → scan 4 dimensions → grill conflicts → generate `.ai-style-rules.md` → offer hook strength (soft\u002Fhard\u002Fnone).\n\n2. **Incremental update after team changes**\n   - User: \"We added a new module; keep existing style rules intact.\"\n   - Action: Run Branch B incremental sniff → compare Git deltas to recorded rules → grill any new conflicts → append evolution log without overwriting.\n\n3. **Enforcing DONTs via CLAUDE.md**\n   - User: \"Make sure all new code stays consistent with the project's rules.\"\n   - Action: Soft hook installed → `.ai-style-rules.md` auto-loaded every session → every code-writing task opens with compliance declaration, reusing exemplar patterns and avoiding DONTs.\n",{"name":5,"metadata":24,"description":7,"allowed-tools":26},{"origin":25},"community","Read, Glob, Grep, Bash, Edit, Write, AskUserQuestion","main","c9103dbad48ef3005f163584d0f2abd4591217f6","skills\u002Fecc-inherit-legacy-style",1,"https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production","https:\u002F\u002Fgithub.com\u002F503496348-ops","https:\u002F\u002F503496348-ops.github.io\u002Fatomcollide-product-matrix\u002F#tree","元素碰撞-AtomCollide-AI 智能体实验室 测试人专属成长社群 正式招募\r\n我们的目标很纯粹：连接每一位测试工程师\u002FAI使用探索与爱好者，让你在这里既能扎实打磨技术硬实力，也能打通职业晋升的新通路，这是一个专注于AI领域的开源组","2026-07-30 00:35:42",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add 503496348-ops\u002Fmischief-production --skill inherit-legacy-style",{"tool":42,"command":43},"bunx","bunx skills add 503496348-ops\u002Fmischief-production --skill inherit-legacy-style",{"tool":45,"command":46},"pnpm","pnpm dlx skills add 503496348-ops\u002Fmischief-production --skill inherit-legacy-style","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-inherit-legacy-style\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M77YG7NPZHE751W9QGK3H9ED","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-skills\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M77YG4HPYH0GJP974DZ6KCPQ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-plans\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M77YFZW1FZ1GVC5C89NPE5M8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M77YFVPWANT5VE5GWBTKHPA2","using-智械工程","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-superpowers\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77YFQJAW5PX3QYSBCD3B24S","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77YFMSTB70VX8W2QHNJWYB0","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-test-driven-development\u002FSKILL.md",[],[]]