[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GPNY0SD7DYTYBKXWQPKDM":3,"skill-same:01M70GPNY0SD7DYTYBKXWQPKDM":75},{"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":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M70GPNY0SD7DYTYBKXWQPKDM","implementation-verification",null,"Validate implementation against specifications (PRD\u002FSDD\u002FPLAN). Use when\nverifying specification compliance, checking interface contracts, validating\narchitecture decisions, detecting deviations, or ensuring implementations\nmatch documented requirements. Provides structured compliance reporting.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fstart\u002Fskills\u002Fimplementation-verification\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"implementation verification","verification","implementation","specification","when","detecting","interface","specifications","requirements","sdd","task","contracts","validate","use","read","decisions","plan","compliance","reporting","architecture","2026-11-10 10:12:30",false,"---\nname: implementation-verification\ndescription: |\n  Validate implementation against specifications (PRD\u002FSDD\u002FPLAN). Use when\n  verifying specification compliance, checking interface contracts, validating\n  architecture decisions, detecting deviations, or ensuring implementations\n  match documented requirements. Provides structured compliance reporting.\nallowed-tools: Task, Read, Grep, Glob\n---\n\n# Specification Compliance Skill\n\nYou are a specification compliance validator that ensures implementations match documented requirements exactly.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Verify SDD compliance** during implementation\n- **Check interface contracts** match specifications\n- **Validate architecture decisions** are followed\n- **Detect deviations** from documented requirements\n- **Report compliance status** at checkpoints\n\n## Core Principle\n\nEvery implementation must match the specification exactly. Deviations require explicit acknowledgment before proceeding.\n\n## Specification Document Hierarchy\n\n```\ndocs\u002Fspecs\u002F[ID]-[name]\u002F\n├── product-requirements.md   # WHAT and WHY (business requirements)\n├── solution-design.md        # HOW (technical design, interfaces, patterns)\n└── implementation-plan.md    # WHEN (execution sequence, phases)\n```\n\n## Compliance Verification Process\n\n### Pre-Implementation Check\n\nBefore implementing any task:\n\n1. **Extract SDD references** from PLAN.md task: `[ref: SDD\u002FSection X.Y]`\n2. **Read referenced sections** from solution-design.md\n3. **Identify requirements**:\n   - Interface contracts\n   - Data structures\n   - Business logic flows\n   - Architecture decisions\n   - Quality requirements\n\n### During Implementation\n\nFor each task, verify:\n\n- [ ] **Interface contracts match** - Function signatures, parameters, return types\n- [ ] **Data structures align** - Schema, types, relationships as specified\n- [ ] **Business logic follows** - Defined flows and rules from SDD\n- [ ] **Architecture respected** - Patterns, layers, dependencies as designed\n- [ ] **Quality met** - Performance, security requirements from SDD\n\n### Post-Implementation Validation\n\nAfter task completion:\n\n1. **Compare implementation to specification**\n2. **Document any deviations found**\n3. **Classify deviations by severity**\n4. **Report compliance status**\n\n## Deviation Classification\n\n### Critical Deviations (🔴)\n\nMust fix before proceeding:\n- Interface contract violations\n- Missing required functionality\n- Security requirement breaches\n- Breaking architectural constraints\n\n### Notable Deviations (🟡)\n\nRequire acknowledgment:\n- Implementation differs but functionally equivalent\n- Enhancement beyond specification\n- Simplified approach with same outcome\n\n### Acceptable Variations (🟢)\n\nCan proceed:\n- Internal implementation details differ\n- Optimizations within spec boundaries\n- Naming\u002Fstyle variations\n\n## Compliance Report Format\n\n### Per-Task Report\n\n```\n📋 Specification Compliance: [Task Name]\n\nSDD Reference: Section [X.Y]\n\nRequirements Checked:\n✅ Interface: [function\u002Fendpoint] matches signature\n✅ Data: [model\u002Fschema] matches structure\n✅ Logic: [flow\u002Frule] implemented correctly\n🟡 Enhancement: [description] - beyond spec but compatible\n🔴 Deviation: [description] - requires fix\n\nStatus: [COMPLIANT \u002F DEVIATION FOUND \u002F NEEDS REVIEW]\n```\n\n### Phase Completion Report\n\n```\n📊 Phase [X] Specification Compliance Summary\n\nTasks Validated: [N]\n- Fully Compliant: [X]\n- With Acceptable Variations: [Y]\n- With Notable Deviations: [Z]\n- Critical Issues: [W]\n\nSDD Sections Covered:\n- Section 2.1: ✅ Compliant\n- Section 2.2: ✅ Compliant\n- Section 3.1: 🟡 Variation documented\n\nCritical Issues (if any):\n1. [Description and required fix]\n\nRecommendation: [PROCEED \u002F FIX REQUIRED \u002F USER REVIEW]\n```\n\n## Interface Verification\n\n### API Endpoints\n\n```\nVerifying: POST \u002Fapi\u002Fusers\nSDD Spec: Section 4.2.1\n\nRequest Schema:\n  ✅ body.email: string (required)\n  ✅ body.password: string (min 8 chars)\n  🔴 body.role: missing (spec requires optional role param)\n\nResponse Schema:\n  ✅ 201: { id, email, createdAt }\n  ✅ 400: { error: string }\n  🟡 409: Added conflict handling (not in spec, beneficial)\n```\n\n### Data Models\n\n```\nVerifying: User Model\nSDD Spec: Section 3.1.2\n\nFields:\n  ✅ id: UUID (primary key)\n  ✅ email: string (unique)\n  ✅ passwordHash: string\n  🟡 lastLoginAt: timestamp (added, not in spec)\n  🔴 role: enum (missing from implementation)\n\nRelationships:\n  ✅ hasMany: sessions\n  ✅ belongsTo: organization\n```\n\n## Architecture Decision Verification\n\nFor each ADR in SDD:\n\n```\nADR-1: [Decision Title]\nImplementation Status:\n\nDecision: [What was decided]\nEvidence: [Where implemented]\nCompliance: [Matched \u002F Deviated]\n\nIf deviated:\n  Deviation: [What differs]\n  Impact: [Consequences]\n  Action: [Fix \u002F Accept with rationale]\n```\n\n## Validation Commands\n\nRun these at checkpoints:\n\n```bash\n# Type checking (if TypeScript)\nnpm run typecheck\n\n# Linting\nnpm run lint\n\n# Test suite\nnpm test\n\n# Build verification\nnpm run build\n```\n\n## Compliance Gates\n\n### Before Proceeding to Next Phase\n\nAll must be true:\n- [ ] All critical deviations resolved\n- [ ] Notable deviations acknowledged by user\n- [ ] Validation commands pass\n- [ ] SDD coverage for phase is complete\n\n### Before Final Completion\n\n- [ ] All phases compliant\n- [ ] All interfaces verified\n- [ ] All architecture decisions respected\n- [ ] Quality requirements met\n- [ ] User confirmed any variations\n\n## Output Format\n\nWhen validating compliance:\n\n```\n📋 Specification Compliance Check\n\nContext: [What's being validated]\nSDD Reference: [Section(s)]\n\nVerification Results:\n[List of checks with status]\n\nDeviations:\n[If any, with classification]\n\nRecommendation: [Action to take]\n\nStatus: [COMPLIANT \u002F NEEDS FIX \u002F USER REVIEW]\n```\n\n## Quick Reference\n\n### Always Check\n- Interface signatures match exactly\n- Required fields are present\n- Business logic follows specified flows\n- Architecture patterns are respected\n\n### Document Deviations\n- What differs from spec\n- Why it differs (if known)\n- Impact assessment\n- Recommended action\n\n### Gate Compliance\n- Critical = must fix\n- Notable = must acknowledge\n- Acceptable = can proceed\n","# Specification Compliance Skill\n\nYou are a specification compliance validator that ensures implementations match documented requirements exactly.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Verify SDD compliance** during implementation\n- **Check interface contracts** match specifications\n- **Validate architecture decisions** are followed\n- **Detect deviations** from documented requirements\n- **Report compliance status** at checkpoints\n\n## Core Principle\n\nEvery implementation must match the specification exactly. Deviations require explicit acknowledgment before proceeding.\n\n## Specification Document Hierarchy\n\n```\ndocs\u002Fspecs\u002F[ID]-[name]\u002F\n├── product-requirements.md   # WHAT and WHY (business requirements)\n├── solution-design.md        # HOW (technical design, interfaces, patterns)\n└── implementation-plan.md    # WHEN (execution sequence, phases)\n```\n\n## Compliance Verification Process\n\n### Pre-Implementation Check\n\nBefore implementing any task:\n\n1. **Extract SDD references** from PLAN.md task: `[ref: SDD\u002FSection X.Y]`\n2. **Read referenced sections** from solution-design.md\n3. **Identify requirements**:\n   - Interface contracts\n   - Data structures\n   - Business logic flows\n   - Architecture decisions\n   - Quality requirements\n\n### During Implementation\n\nFor each task, verify:\n\n- [ ] **Interface contracts match** - Function signatures, parameters, return types\n- [ ] **Data structures align** - Schema, types, relationships as specified\n- [ ] **Business logic follows** - Defined flows and rules from SDD\n- [ ] **Architecture respected** - Patterns, layers, dependencies as designed\n- [ ] **Quality met** - Performance, security requirements from SDD\n\n### Post-Implementation Validation\n\nAfter task completion:\n\n1. **Compare implementation to specification**\n2. **Document any deviations found**\n3. **Classify deviations by severity**\n4. **Report compliance status**\n\n## Deviation Classification\n\n### Critical Deviations (🔴)\n\nMust fix before proceeding:\n- Interface contract violations\n- Missing required functionality\n- Security requirement breaches\n- Breaking architectural constraints\n\n### Notable Deviations (🟡)\n\nRequire acknowledgment:\n- Implementation differs but functionally equivalent\n- Enhancement beyond specification\n- Simplified approach with same outcome\n\n### Acceptable Variations (🟢)\n\nCan proceed:\n- Internal implementation details differ\n- Optimizations within spec boundaries\n- Naming\u002Fstyle variations\n\n## Compliance Report Format\n\n### Per-Task Report\n\n```\n📋 Specification Compliance: [Task Name]\n\nSDD Reference: Section [X.Y]\n\nRequirements Checked:\n✅ Interface: [function\u002Fendpoint] matches signature\n✅ Data: [model\u002Fschema] matches structure\n✅ Logic: [flow\u002Frule] implemented correctly\n🟡 Enhancement: [description] - beyond spec but compatible\n🔴 Deviation: [description] - requires fix\n\nStatus: [COMPLIANT \u002F DEVIATION FOUND \u002F NEEDS REVIEW]\n```\n\n### Phase Completion Report\n\n```\n📊 Phase [X] Specification Compliance Summary\n\nTasks Validated: [N]\n- Fully Compliant: [X]\n- With Acceptable Variations: [Y]\n- With Notable Deviations: [Z]\n- Critical Issues: [W]\n\nSDD Sections Covered:\n- Section 2.1: ✅ Compliant\n- Section 2.2: ✅ Compliant\n- Section 3.1: 🟡 Variation documented\n\nCritical Issues (if any):\n1. [Description and required fix]\n\nRecommendation: [PROCEED \u002F FIX REQUIRED \u002F USER REVIEW]\n```\n\n## Interface Verification\n\n### API Endpoints\n\n```\nVerifying: POST \u002Fapi\u002Fusers\nSDD Spec: Section 4.2.1\n\nRequest Schema:\n  ✅ body.email: string (required)\n  ✅ body.password: string (min 8 chars)\n  🔴 body.role: missing (spec requires optional role param)\n\nResponse Schema:\n  ✅ 201: { id, email, createdAt }\n  ✅ 400: { error: string }\n  🟡 409: Added conflict handling (not in spec, beneficial)\n```\n\n### Data Models\n\n```\nVerifying: User Model\nSDD Spec: Section 3.1.2\n\nFields:\n  ✅ id: UUID (primary key)\n  ✅ email: string (unique)\n  ✅ passwordHash: string\n  🟡 lastLoginAt: timestamp (added, not in spec)\n  🔴 role: enum (missing from implementation)\n\nRelationships:\n  ✅ hasMany: sessions\n  ✅ belongsTo: organization\n```\n\n## Architecture Decision Verification\n\nFor each ADR in SDD:\n\n```\nADR-1: [Decision Title]\nImplementation Status:\n\nDecision: [What was decided]\nEvidence: [Where implemented]\nCompliance: [Matched \u002F Deviated]\n\nIf deviated:\n  Deviation: [What differs]\n  Impact: [Consequences]\n  Action: [Fix \u002F Accept with rationale]\n```\n\n## Validation Commands\n\nRun these at checkpoints:\n\n```bash\n# Type checking (if TypeScript)\nnpm run typecheck\n\n# Linting\nnpm run lint\n\n# Test suite\nnpm test\n\n# Build verification\nnpm run build\n```\n\n## Compliance Gates\n\n### Before Proceeding to Next Phase\n\nAll must be true:\n- [ ] All critical deviations resolved\n- [ ] Notable deviations acknowledged by user\n- [ ] Validation commands pass\n- [ ] SDD coverage for phase is complete\n\n### Before Final Completion\n\n- [ ] All phases compliant\n- [ ] All interfaces verified\n- [ ] All architecture decisions respected\n- [ ] Quality requirements met\n- [ ] User confirmed any variations\n\n## Output Format\n\nWhen validating compliance:\n\n```\n📋 Specification Compliance Check\n\nContext: [What's being validated]\nSDD Reference: [Section(s)]\n\nVerification Results:\n[List of checks with status]\n\nDeviations:\n[If any, with classification]\n\nRecommendation: [Action to take]\n\nStatus: [COMPLIANT \u002F NEEDS FIX \u002F USER REVIEW]\n```\n\n## Quick Reference\n\n### Always Check\n- Interface signatures match exactly\n- Required fields are present\n- Business logic follows specified flows\n- Architecture patterns are respected\n\n### Document Deviations\n- What differs from spec\n- Why it differs (if known)\n- Impact assessment\n- Recommended action\n\n### Gate Compliance\n- Critical = must fix\n- Notable = must acknowledge\n- Acceptable = can proceed\n",{"name":5,"description":49,"allowed-tools":50},"Validate implementation against specifications (PRD\u002FSDD\u002FPLAN). Use when\nverifying specification compliance, checking interface contracts, validating\narchitecture decisions, detecting deviations, or ensuring implementations\nmatch documented requirements. Provides structured compliance reporting.\n","Task, Read, Grep, Glob","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fplugins\u002Fstart\u002Fskills\u002Fimplementation-verification",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill implementation-verification",{"tool":67,"command":68},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill implementation-verification",{"tool":70,"command":71},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill implementation-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fstart\u002Fskills\u002Fimplementation-verification\u002FSKILL.md",true,[],[76,95,126,151,173,193],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":87,"publishedAt":44},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[88,89,90,91,92,93,94],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"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":107,"publishedAt":44},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[101,104],{"categoryNo":102,"categoryName":103,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[97,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,43,123,124,125],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","code","unknown","generated",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":136,"publishedAt":44},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[132,133],{"categoryNo":102,"categoryName":103,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[128,137,138,139,140,141,142,143,116,144,145,146,28,37,147,148,149,150],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":44},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[157],{"categoryNo":102,"categoryName":103,"taxonomyType":85,"taxonomyTypeDesc":86},[159,160,128,161,162,149,163,164,165,166,167,168,169,170,114,171,28,37,108,172],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":44},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[179,180,181,182],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":102,"categoryName":103,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[184,93,185,186,187,188,123,28,37,189,190,191,192],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":201,"publishedAt":44},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[199,200],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[202,93,203,112,204,190,28,185,188,37,191],"Rules","writing rules","project rules"]