[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70G7MDHCT0V9Y80MQBTM6T7":3,"skill-same:01M70G7MDHCT0V9Y80MQBTM6T7":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70G7MDHCT0V9Y80MQBTM6T7","inherit-legacy-style",null,"Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook. Use when onboarding an AI agent onto a hand-written legacy codebase or extracting a project's unwritten coding rules.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Finherit-legacy-style\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"inherit legacy style","Legacy","style","drift","when","at","hand","extracting","coding rules","project","time","writing","community","conflicts","files","scanning","one at a time","projects","Bash","ai agent","2026-11-10 10:12:30",false,"---\nname: inherit-legacy-style\ndescription: Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook. Use when onboarding an AI agent onto a hand-written legacy codebase or extracting a project's unwritten coding rules.\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":49,"description":7,"allowed-tools":50},{"origin":36},"Read, Glob, Grep, Bash, Edit, Write, AskUserQuestion","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Finherit-legacy-style",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill inherit-legacy-style",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill inherit-legacy-style",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill inherit-legacy-style","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Finherit-legacy-style\u002FSKILL.md",true,[],[74,82,90,97,104,111],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":89},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":89},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":89},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":89},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]