[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB321YP0VZ8MJ82QGEXTP6":3,"skill-same:01M6KB321YP0VZ8MJ82QGEXTP6":53},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6KB321YP0VZ8MJ82QGEXTP6","promote",null,"Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude\u002Frules\u002F for permanent enforcement.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fpromote\u002FSKILL.md",[],[5,19,20,21,22,23,24],"memory","Rules","auto","enforcement","pattern","for","2026-11-10 10:12:30",false,"---\nname: \"promote\"\ndescription: \"Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude\u002Frules\u002F for permanent enforcement.\"\ncommand: \u002Fsi:promote\n---\n\n# \u002Fsi:promote — Graduate Learnings to Rules\n\nMoves a proven pattern from Claude's auto-memory into the project's rule system, where it becomes an enforced instruction rather than a background note.\n\n## Usage\n\n```\n\u002Fsi:promote \u003Cpattern description>                    # Auto-detect best target\n\u002Fsi:promote \u003Cpattern> --target claude.md             # Promote to CLAUDE.md\n\u002Fsi:promote \u003Cpattern> --target rules\u002Ftesting.md      # Promote to scoped rule\n\u002Fsi:promote \u003Cpattern> --target rules\u002Fapi.md --paths \"src\u002Fapi\u002F**\u002F*.ts\"  # Scoped with paths\n```\n\n## Workflow\n\n### Step 1: Understand the pattern\n\nParse the user's description. If vague, ask one clarifying question:\n- \"What specific behavior should Claude follow?\"\n- \"Does this apply to all files or specific paths?\"\n\n### Step 2: Find the pattern in auto-memory\n\n```bash\n# Search MEMORY.md for related entries\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -ni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002FMEMORY.md\"\n```\n\nShow the matching entries and confirm they're what the user means.\n\n### Step 3: Determine the right target\n\n| Pattern scope | Target | Example |\n|---|---|---|\n| Applies to entire project | `.\u002FCLAUDE.md` | \"Use pnpm, not npm\" |\n| Applies to specific file types | `.claude\u002Frules\u002F\u003Ctopic>.md` | \"API handlers need validation\" |\n| Applies to all your projects | `~\u002F.claude\u002FCLAUDE.md` | \"Prefer explicit error handling\" |\n\nIf the user didn't specify a target, recommend one based on scope.\n\n### Step 4: Distill into a concise rule\n\nTransform the learning from auto-memory's note format into CLAUDE.md's instruction format:\n\n**Before** (MEMORY.md — descriptive):\n> The project uses pnpm workspaces. When I tried npm install it failed. The lock file is pnpm-lock.yaml. Must use pnpm install for dependencies.\n\n**After** (CLAUDE.md — prescriptive):\n```markdown\n## Build & Dependencies\n- Package manager: pnpm (not npm). Use `pnpm install`.\n```\n\n**Rules for distillation:**\n- One line per rule when possible\n- Imperative voice (\"Use X\", \"Always Y\", \"Never Z\")\n- Include the command or example, not just the concept\n- No backstory — just the instruction\n\n### Step 5: Write to target\n\n**For CLAUDE.md:**\n1. Read existing CLAUDE.md\n2. Find the appropriate section (or create one)\n3. Append the new rule under the right heading\n4. If file would exceed 200 lines, suggest using `.claude\u002Frules\u002F` instead\n\n**For `.claude\u002Frules\u002F`:**\n1. Create the file if it doesn't exist\n2. Add YAML frontmatter with `paths` if scoped\n3. Write the rule content\n\n```markdown\n---\npaths:\n  - \"src\u002Fapi\u002F**\u002F*.ts\"\n  - \"tests\u002Fapi\u002F**\u002F*\"\n---\n\n# API Development Rules\n\n- All endpoints must validate input with Zod schemas\n- Use `ApiError` class for error responses (not raw Error)\n- Include OpenAPI JSDoc comments on handler functions\n```\n\n### Step 6: Clean up auto-memory\n\nAfter promoting, remove or mark the original entry in MEMORY.md:\n\n```bash\n# Show what will be removed\ngrep -n \"\u003Cpattern>\" \"$MEMORY_DIR\u002FMEMORY.md\"\n```\n\nAsk the user to confirm removal. Then edit MEMORY.md to remove the promoted entry. This frees space for new learnings.\n\n### Step 7: Confirm\n\n```\n✅ Promoted to {{target}}\n\nRule: \"{{distilled rule}}\"\nSource: MEMORY.md line {{n}} (removed)\nMEMORY.md: {{lines}}\u002F200 lines remaining\n\nThe pattern is now an enforced instruction. Claude will follow it in all future sessions.\n```\n\n## Promotion Decision Guide\n\n### Promote when:\n- Pattern appeared 3+ times in auto-memory\n- You corrected Claude about it more than once\n- It's a project convention that any contributor should know\n- It prevents a recurring mistake\n\n### Don't promote when:\n- It's a one-time debugging note (leave in auto-memory)\n- It's session-specific context (session memory handles this)\n- It might change soon (e.g., during a migration)\n- It's already covered by existing rules\n\n### CLAUDE.md vs .claude\u002Frules\u002F\n\n| Use CLAUDE.md for | Use .claude\u002Frules\u002F for |\n|---|---|\n| Global project rules | File-type-specific patterns |\n| Build commands | Testing conventions |\n| Architecture decisions | API design rules |\n| Team conventions | Framework-specific gotchas |\n\n## Tips\n\n- Keep CLAUDE.md under 200 lines — use rules\u002F for overflow\n- One rule per line is easier to maintain than paragraphs\n- Include the concrete command, not just the concept\n- Review promoted rules quarterly — remove what's no longer relevant\n","# \u002Fsi:promote — Graduate Learnings to Rules\n\nMoves a proven pattern from Claude's auto-memory into the project's rule system, where it becomes an enforced instruction rather than a background note.\n\n## Usage\n\n```\n\u002Fsi:promote \u003Cpattern description>                    # Auto-detect best target\n\u002Fsi:promote \u003Cpattern> --target claude.md             # Promote to CLAUDE.md\n\u002Fsi:promote \u003Cpattern> --target rules\u002Ftesting.md      # Promote to scoped rule\n\u002Fsi:promote \u003Cpattern> --target rules\u002Fapi.md --paths \"src\u002Fapi\u002F**\u002F*.ts\"  # Scoped with paths\n```\n\n## Workflow\n\n### Step 1: Understand the pattern\n\nParse the user's description. If vague, ask one clarifying question:\n- \"What specific behavior should Claude follow?\"\n- \"Does this apply to all files or specific paths?\"\n\n### Step 2: Find the pattern in auto-memory\n\n```bash\n# Search MEMORY.md for related entries\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -ni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002FMEMORY.md\"\n```\n\nShow the matching entries and confirm they're what the user means.\n\n### Step 3: Determine the right target\n\n| Pattern scope | Target | Example |\n|---|---|---|\n| Applies to entire project | `.\u002FCLAUDE.md` | \"Use pnpm, not npm\" |\n| Applies to specific file types | `.claude\u002Frules\u002F\u003Ctopic>.md` | \"API handlers need validation\" |\n| Applies to all your projects | `~\u002F.claude\u002FCLAUDE.md` | \"Prefer explicit error handling\" |\n\nIf the user didn't specify a target, recommend one based on scope.\n\n### Step 4: Distill into a concise rule\n\nTransform the learning from auto-memory's note format into CLAUDE.md's instruction format:\n\n**Before** (MEMORY.md — descriptive):\n> The project uses pnpm workspaces. When I tried npm install it failed. The lock file is pnpm-lock.yaml. Must use pnpm install for dependencies.\n\n**After** (CLAUDE.md — prescriptive):\n```markdown\n## Build & Dependencies\n- Package manager: pnpm (not npm). Use `pnpm install`.\n```\n\n**Rules for distillation:**\n- One line per rule when possible\n- Imperative voice (\"Use X\", \"Always Y\", \"Never Z\")\n- Include the command or example, not just the concept\n- No backstory — just the instruction\n\n### Step 5: Write to target\n\n**For CLAUDE.md:**\n1. Read existing CLAUDE.md\n2. Find the appropriate section (or create one)\n3. Append the new rule under the right heading\n4. If file would exceed 200 lines, suggest using `.claude\u002Frules\u002F` instead\n\n**For `.claude\u002Frules\u002F`:**\n1. Create the file if it doesn't exist\n2. Add YAML frontmatter with `paths` if scoped\n3. Write the rule content\n\n```markdown\n---\npaths:\n  - \"src\u002Fapi\u002F**\u002F*.ts\"\n  - \"tests\u002Fapi\u002F**\u002F*\"\n---\n\n# API Development Rules\n\n- All endpoints must validate input with Zod schemas\n- Use `ApiError` class for error responses (not raw Error)\n- Include OpenAPI JSDoc comments on handler functions\n```\n\n### Step 6: Clean up auto-memory\n\nAfter promoting, remove or mark the original entry in MEMORY.md:\n\n```bash\n# Show what will be removed\ngrep -n \"\u003Cpattern>\" \"$MEMORY_DIR\u002FMEMORY.md\"\n```\n\nAsk the user to confirm removal. Then edit MEMORY.md to remove the promoted entry. This frees space for new learnings.\n\n### Step 7: Confirm\n\n```\n✅ Promoted to {{target}}\n\nRule: \"{{distilled rule}}\"\nSource: MEMORY.md line {{n}} (removed)\nMEMORY.md: {{lines}}\u002F200 lines remaining\n\nThe pattern is now an enforced instruction. Claude will follow it in all future sessions.\n```\n\n## Promotion Decision Guide\n\n### Promote when:\n- Pattern appeared 3+ times in auto-memory\n- You corrected Claude about it more than once\n- It's a project convention that any contributor should know\n- It prevents a recurring mistake\n\n### Don't promote when:\n- It's a one-time debugging note (leave in auto-memory)\n- It's session-specific context (session memory handles this)\n- It might change soon (e.g., during a migration)\n- It's already covered by existing rules\n\n### CLAUDE.md vs .claude\u002Frules\u002F\n\n| Use CLAUDE.md for | Use .claude\u002Frules\u002F for |\n|---|---|\n| Global project rules | File-type-specific patterns |\n| Build commands | Testing conventions |\n| Architecture decisions | API design rules |\n| Team conventions | Framework-specific gotchas |\n\n## Tips\n\n- Keep CLAUDE.md under 200 lines — use rules\u002F for overflow\n- One rule per line is easier to maintain than paragraphs\n- Include the concrete command, not just the concept\n- Review promoted rules quarterly — remove what's no longer relevant\n",{"name":5,"command":30,"description":7},"\u002Fsi:promote","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering-team\u002Fself-improving-agent\u002Fskills\u002Fpromote",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill promote",{"tool":45,"command":46},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill promote",{"tool":48,"command":49},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill promote","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fpromote\u002FSKILL.md",true,[],[54,85,110,135,167,187],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":65,"publishedAt":25},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[60],{"categoryNo":61,"categoryName":62,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,24],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":25},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[92,93,94,95,96,97,98,99,73,74,100,101,102,103,104,105,106,107,108,109],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":25},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,125,74,126,127,128,129,130,131,132,133,134,24],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":149,"publishedAt":25},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[141,146],{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":147,"categoryName":148,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000032","设计师",[150,151,134,152,153,154,155,156,157,74,158,159,160,161,162,163,164,165,24,166],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":25},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[173],{"categoryNo":61,"categoryName":62,"taxonomyType":63,"taxonomyTypeDesc":64},[175,151,134,176,177,178,179,180,66,181,157,182,118,183,184,185,101,162,24,186],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":200,"publishedAt":25},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[193,196,199],{"categoryNo":194,"categoryName":195,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":197,"categoryName":198,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":61,"categoryName":62,"taxonomyType":63,"taxonomyTypeDesc":64},[201,202,151,134,176,203,204,70,157,205,206,207,208,209,102,210,211,212,213,24],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]