[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FQCPYFDY2TYBPFSTWVNV7":3,"skill-same:01M70FQCPYFDY2TYBPFSTWVNV7":78},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70FQCPYFDY2TYBPFSTWVNV7","config-gc",null,"Garbage collection for your Claude Code configuration. Periodically scans ~\u002F.claude (skills, memory, hooks, permissions, MCP servers, caches) for redundant, stale, orphaned, or low-value items, then walks the user through a confirm-each-deletion cleanup. Use when the user says \"clean up my config\", \"config GC\", \"too many skills\", \"audit my setup\", \"my .claude is bloated\", or asks for a periodic config review.","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\u002Fconfig-gc\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"config gc","config","gc","hooks","when","value","for","deletion","my","clean","periodic","MCP","up","collection","audit","permissions","code","cleanup","memory","review","2026-11-10 10:12:30",false,"---\nname: config-gc\ndescription: Garbage collection for your Claude Code configuration. Periodically scans ~\u002F.claude (skills, memory, hooks, permissions, MCP servers, caches) for redundant, stale, orphaned, or low-value items, then walks the user through a confirm-each-deletion cleanup. Use when the user says \"clean up my config\", \"config GC\", \"too many skills\", \"audit my setup\", \"my .claude is bloated\", or asks for a periodic config review.\nmetadata:\n  origin: ECC\n---\n\n# Config GC — Garbage Collection for Claude Code Setups\n\nBorrowed from runtime garbage collection: periodically scan for objects that are no longer referenced, redundant, expired, or low-value, and reclaim the space. The critical difference: **here, collection requires a human in the loop. Never delete autonomously.**\n\n## When to Activate\n\n- The user asks to clean up, audit, or slim down their Claude Code configuration\n- The user complains about too many skills, noisy hooks, or slow session startup\n- A monthly\u002Fperiodic config review is due\n- After installing a large skill pack (e.g. this repo), to reconcile overlaps with existing setup\n\nDo NOT activate for: cleaning project source code (that's refactoring), clearing chat history, or uninstalling Claude Code itself.\n\n## Design Philosophy\n\n1. **Append-only configs leak.** Skills, memory files, hooks, and permission entries only ever get added. Without periodic review they rot silently.\n2. **Regular audits beat one-time purges.** Scan every ~30 days, propose a small batch of candidates each time.\n3. **Per-channel strategies.** Each accumulation type (skills, hooks, permissions, ...) has its own staleness signals — don't apply one rule everywhere.\n4. **Soft-delete first.** Rename to `.disabled` > move to `~\u002F.claude\u002F_gc_trash\u002F` > real deletion. Always keep an undo path.\n5. **Forced human-in-the-loop.** Every candidate gets its own `[y\u002Fn\u002Fskip]` confirmation. No \"yes to all\" shortcut.\n6. **Keep a log.** Every GC run appends to `~\u002F.claude\u002Fgc_log.md`: what was touched, why, and how to undo it.\n\n## Scan Channels\n\n| # | Channel | Path | Staleness \u002F redundancy signals |\n|---|---------|------|--------------------------------|\n| 1 | Skills | `~\u002F.claude\u002Fskills\u002F*\u002F` | Heavily overlapping names; never triggered in recent transcripts; domain mismatch with the user's actual work; broken or empty SKILL.md |\n| 2 | Memory | `~\u002F.claude\u002F**\u002Fmemory\u002F*.md` + its index | Multiple index entries for one topic; contents contradicting newer entries; dates that have passed; orphan files missing from the index; sub-100-word fragments that should merge |\n| 3 | Hooks | `~\u002F.claude\u002Fhooks\u002F` + settings | Scripts present on disk but referenced by no hook config; old versions superseded by rewrites |\n| 4 | Permissions | `permissions.allow` in `settings.json` \u002F `settings.local.json` | Duplicate entries; specific entries already covered by a wildcard (e.g. `Bash(git push)` when `Bash(*)` is allowed); one-off grants from past experiments |\n| 5 | MCP servers | `~\u002F.claude.json` or project `.mcp.json` | Servers that fail to connect; functional duplicates; long-unused |\n| 6 | Scheduled reminders \u002F jobs | wherever the user keeps them | Fired one-shots older than 30 days; jobs whose target scripts no longer exist |\n| 7 | Project history | `~\u002F.claude\u002Fprojects\u002F*\u002F` | Stale handoff snapshots; session records superseded by newer state |\n| 8 | Runtime caches | `cache\u002F`, `file-history\u002F`, `logs\u002F`, `shell-snapshots\u002F` | Sort by size and mtime; propose items >30 days old and large |\n\n## Workflow\n\n1. **Scan** all channels (or the subset the user names). Collect candidates with: path, channel, signal that flagged it, size, last-modified.\n2. **Rank** by confidence (broken\u002Forphaned = high; merely old = low) and present as a numbered table. Cap each run at ~20 candidates — GC is periodic, not exhaustive.\n3. **Confirm one by one.** For each candidate show the evidence, then ask `[y\u002Fn\u002Fskip]`. The user can stop at any point.\n4. **Soft-delete confirmed items**: prefer `.disabled` rename for skills\u002Fhooks and `_gc_trash\u002F\u003Cdate>\u002F` move for files. Permission entries live in JSON (no comments possible): back up the settings file, record each removed entry verbatim in `gc_log.md`, then remove it from the `allow` array with `jq`. Only hard-delete when the user explicitly asks.\n5. **Log** the run to `~\u002F.claude\u002Fgc_log.md`: timestamp, items actioned, undo instructions.\n6. **Report**: reclaimed size, channels still healthy, suggested next review date.\n\n## Example Scan Commands\n\nOrphaned hook scripts (channel 3) — scripts on disk that no hook config references:\n\n```bash\nfor f in ~\u002F.claude\u002Fhooks\u002F*; do\n  name=$(basename \"$f\")\n  grep -rq \"$name\" ~\u002F.claude\u002Fsettings.json ~\u002F.claude\u002Fsettings.local.json 2>\u002Fdev\u002Fnull \\\n    || echo \"ORPHAN: $f\"\ndone\n```\n\nRedundant permission entries (channel 4) — duplicates, and specific grants shadowed by a wildcard:\n\n```bash\njq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json | sort | uniq -d\nif jq -e '.permissions.allow | index(\"Bash(*)\")' ~\u002F.claude\u002Fsettings.local.json >\u002Fdev\u002Fnull; then\n  jq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json \\\n    | grep '^Bash(' | grep -vF 'Bash(*)'\nfi\n```\n\nLargest stale caches (channel 8) — `du -k` instead of GNU-only `find -printf`, so it works on macOS\u002FBSD too:\n\n```bash\nfind ~\u002F.claude\u002Ffile-history ~\u002F.claude\u002Fshell-snapshots -type f -mtime +30 \\\n  -exec du -k {} + 2>\u002Fdev\u002Fnull | sort -rn | head -20\n```\n\nSoft-delete with undo path (capture the date once so the log can't disagree with the directory):\n\n```bash\ngc_date=$(date +%Y-%m-%d)\nmkdir -p ~\u002F.claude\u002F_gc_trash\u002F$gc_date\nmv ~\u002F.claude\u002Fskills\u002Fdead-skill ~\u002F.claude\u002F_gc_trash\u002F$gc_date\u002F\necho \"$(date -Iseconds) moved skills\u002Fdead-skill -> _gc_trash\u002F$gc_date\u002F (undo: mv back)\" >> ~\u002F.claude\u002Fgc_log.md\n```\n\nRemoving a confirmed-redundant permission entry (JSON has no comments — back up, log, then edit):\n\n```bash\ncp ~\u002F.claude\u002Fsettings.local.json ~\u002F.claude\u002Fsettings.local.json.bak\necho \"$(date -Iseconds) removed permission entry: Bash(git push) (undo: restore from .bak or re-add)\" >> ~\u002F.claude\u002Fgc_log.md\njq '.permissions.allow -= [\"Bash(git push)\"]' ~\u002F.claude\u002Fsettings.local.json.bak \\\n  > ~\u002F.claude\u002Fsettings.local.json\n```\n\n## Anti-Patterns\n\n- **Bulk approval.** Asking \"delete all 15? [y\u002Fn]\" defeats the design. One item, one decision.\n- **Hard-deleting on first pass.** If there's no `_gc_trash\u002F` copy or `.disabled` rename, you did it wrong.\n- **Treating \"old\" as \"dead\".** A skill untouched for 60 days may be seasonal (tax season, quarterly reviews). Age is a signal, not a verdict — that's why a human confirms.\n- **Cleaning memory by truncation.** Merging two contradicting memory files requires reading both and keeping the newer truth, not deleting the longer one.\n- **Touching anything outside `~\u002F.claude`** (or the project's `.claude\u002F`). Config GC never wanders into source trees.\n\n## Best Practices\n\n- Run after big additions, not just on a calendar: installing a 50-skill pack is exactly when overlap with existing skills appears.\n- When two skills overlap, prefer disabling the one with the weaker trigger description — it's the one that was probably never firing anyway.\n- Permission cleanup is the highest-value channel per minute spent: redundant allow-entries make security review harder.\n- Keep `gc_log.md` forever. It's tiny, and \"when did I disable that hook and why\" comes up more often than you'd think.\n\n## Related Skills\n\n- `skill-stocktake` — audits skill *quality*; config-gc audits skill *existence*. Run stocktake on what survives GC.\n- `workspace-surface-audit` — the additive counterpart: recommends what to install. config-gc is the subtractive half of the same lifecycle.\n- `configure-ecc` — after installing skills with it, run config-gc to reconcile overlaps with your pre-existing setup.\n- `continuous-learning` — produces the memory files this skill later audits.\n- `security-review` — pairs well with the permissions channel.\n","# Config GC — Garbage Collection for Claude Code Setups\n\nBorrowed from runtime garbage collection: periodically scan for objects that are no longer referenced, redundant, expired, or low-value, and reclaim the space. The critical difference: **here, collection requires a human in the loop. Never delete autonomously.**\n\n## When to Activate\n\n- The user asks to clean up, audit, or slim down their Claude Code configuration\n- The user complains about too many skills, noisy hooks, or slow session startup\n- A monthly\u002Fperiodic config review is due\n- After installing a large skill pack (e.g. this repo), to reconcile overlaps with existing setup\n\nDo NOT activate for: cleaning project source code (that's refactoring), clearing chat history, or uninstalling Claude Code itself.\n\n## Design Philosophy\n\n1. **Append-only configs leak.** Skills, memory files, hooks, and permission entries only ever get added. Without periodic review they rot silently.\n2. **Regular audits beat one-time purges.** Scan every ~30 days, propose a small batch of candidates each time.\n3. **Per-channel strategies.** Each accumulation type (skills, hooks, permissions, ...) has its own staleness signals — don't apply one rule everywhere.\n4. **Soft-delete first.** Rename to `.disabled` > move to `~\u002F.claude\u002F_gc_trash\u002F` > real deletion. Always keep an undo path.\n5. **Forced human-in-the-loop.** Every candidate gets its own `[y\u002Fn\u002Fskip]` confirmation. No \"yes to all\" shortcut.\n6. **Keep a log.** Every GC run appends to `~\u002F.claude\u002Fgc_log.md`: what was touched, why, and how to undo it.\n\n## Scan Channels\n\n| # | Channel | Path | Staleness \u002F redundancy signals |\n|---|---------|------|--------------------------------|\n| 1 | Skills | `~\u002F.claude\u002Fskills\u002F*\u002F` | Heavily overlapping names; never triggered in recent transcripts; domain mismatch with the user's actual work; broken or empty SKILL.md |\n| 2 | Memory | `~\u002F.claude\u002F**\u002Fmemory\u002F*.md` + its index | Multiple index entries for one topic; contents contradicting newer entries; dates that have passed; orphan files missing from the index; sub-100-word fragments that should merge |\n| 3 | Hooks | `~\u002F.claude\u002Fhooks\u002F` + settings | Scripts present on disk but referenced by no hook config; old versions superseded by rewrites |\n| 4 | Permissions | `permissions.allow` in `settings.json` \u002F `settings.local.json` | Duplicate entries; specific entries already covered by a wildcard (e.g. `Bash(git push)` when `Bash(*)` is allowed); one-off grants from past experiments |\n| 5 | MCP servers | `~\u002F.claude.json` or project `.mcp.json` | Servers that fail to connect; functional duplicates; long-unused |\n| 6 | Scheduled reminders \u002F jobs | wherever the user keeps them | Fired one-shots older than 30 days; jobs whose target scripts no longer exist |\n| 7 | Project history | `~\u002F.claude\u002Fprojects\u002F*\u002F` | Stale handoff snapshots; session records superseded by newer state |\n| 8 | Runtime caches | `cache\u002F`, `file-history\u002F`, `logs\u002F`, `shell-snapshots\u002F` | Sort by size and mtime; propose items >30 days old and large |\n\n## Workflow\n\n1. **Scan** all channels (or the subset the user names). Collect candidates with: path, channel, signal that flagged it, size, last-modified.\n2. **Rank** by confidence (broken\u002Forphaned = high; merely old = low) and present as a numbered table. Cap each run at ~20 candidates — GC is periodic, not exhaustive.\n3. **Confirm one by one.** For each candidate show the evidence, then ask `[y\u002Fn\u002Fskip]`. The user can stop at any point.\n4. **Soft-delete confirmed items**: prefer `.disabled` rename for skills\u002Fhooks and `_gc_trash\u002F\u003Cdate>\u002F` move for files. Permission entries live in JSON (no comments possible): back up the settings file, record each removed entry verbatim in `gc_log.md`, then remove it from the `allow` array with `jq`. Only hard-delete when the user explicitly asks.\n5. **Log** the run to `~\u002F.claude\u002Fgc_log.md`: timestamp, items actioned, undo instructions.\n6. **Report**: reclaimed size, channels still healthy, suggested next review date.\n\n## Example Scan Commands\n\nOrphaned hook scripts (channel 3) — scripts on disk that no hook config references:\n\n```bash\nfor f in ~\u002F.claude\u002Fhooks\u002F*; do\n  name=$(basename \"$f\")\n  grep -rq \"$name\" ~\u002F.claude\u002Fsettings.json ~\u002F.claude\u002Fsettings.local.json 2>\u002Fdev\u002Fnull \\\n    || echo \"ORPHAN: $f\"\ndone\n```\n\nRedundant permission entries (channel 4) — duplicates, and specific grants shadowed by a wildcard:\n\n```bash\njq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json | sort | uniq -d\nif jq -e '.permissions.allow | index(\"Bash(*)\")' ~\u002F.claude\u002Fsettings.local.json >\u002Fdev\u002Fnull; then\n  jq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json \\\n    | grep '^Bash(' | grep -vF 'Bash(*)'\nfi\n```\n\nLargest stale caches (channel 8) — `du -k` instead of GNU-only `find -printf`, so it works on macOS\u002FBSD too:\n\n```bash\nfind ~\u002F.claude\u002Ffile-history ~\u002F.claude\u002Fshell-snapshots -type f -mtime +30 \\\n  -exec du -k {} + 2>\u002Fdev\u002Fnull | sort -rn | head -20\n```\n\nSoft-delete with undo path (capture the date once so the log can't disagree with the directory):\n\n```bash\ngc_date=$(date +%Y-%m-%d)\nmkdir -p ~\u002F.claude\u002F_gc_trash\u002F$gc_date\nmv ~\u002F.claude\u002Fskills\u002Fdead-skill ~\u002F.claude\u002F_gc_trash\u002F$gc_date\u002F\necho \"$(date -Iseconds) moved skills\u002Fdead-skill -> _gc_trash\u002F$gc_date\u002F (undo: mv back)\" >> ~\u002F.claude\u002Fgc_log.md\n```\n\nRemoving a confirmed-redundant permission entry (JSON has no comments — back up, log, then edit):\n\n```bash\ncp ~\u002F.claude\u002Fsettings.local.json ~\u002F.claude\u002Fsettings.local.json.bak\necho \"$(date -Iseconds) removed permission entry: Bash(git push) (undo: restore from .bak or re-add)\" >> ~\u002F.claude\u002Fgc_log.md\njq '.permissions.allow -= [\"Bash(git push)\"]' ~\u002F.claude\u002Fsettings.local.json.bak \\\n  > ~\u002F.claude\u002Fsettings.local.json\n```\n\n## Anti-Patterns\n\n- **Bulk approval.** Asking \"delete all 15? [y\u002Fn]\" defeats the design. One item, one decision.\n- **Hard-deleting on first pass.** If there's no `_gc_trash\u002F` copy or `.disabled` rename, you did it wrong.\n- **Treating \"old\" as \"dead\".** A skill untouched for 60 days may be seasonal (tax season, quarterly reviews). Age is a signal, not a verdict — that's why a human confirms.\n- **Cleaning memory by truncation.** Merging two contradicting memory files requires reading both and keeping the newer truth, not deleting the longer one.\n- **Touching anything outside `~\u002F.claude`** (or the project's `.claude\u002F`). Config GC never wanders into source trees.\n\n## Best Practices\n\n- Run after big additions, not just on a calendar: installing a 50-skill pack is exactly when overlap with existing skills appears.\n- When two skills overlap, prefer disabling the one with the weaker trigger description — it's the one that was probably never firing anyway.\n- Permission cleanup is the highest-value channel per minute spent: redundant allow-entries make security review harder.\n- Keep `gc_log.md` forever. It's tiny, and \"when did I disable that hook and why\" comes up more often than you'd think.\n\n## Related Skills\n\n- `skill-stocktake` — audits skill *quality*; config-gc audits skill *existence*. Run stocktake on what survives GC.\n- `workspace-surface-audit` — the additive counterpart: recommends what to install. config-gc is the subtractive half of the same lifecycle.\n- `configure-ecc` — after installing skills with it, run config-gc to reconcile overlaps with your pre-existing setup.\n- `continuous-learning` — produces the memory files this skill later audits.\n- `security-review` — pairs well with the permissions channel.\n",{"name":5,"metadata":54,"description":7},{"origin":55},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fconfig-gc",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill config-gc",{"tool":70,"command":71},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill config-gc",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill config-gc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fconfig-gc\u002FSKILL.md",true,[],[79,87,95,102,109,116],{"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":86},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":94},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":94},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":94},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":94},"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",[],[]]