[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB35DB02GEZR4EM3DFWDSK":3,"skill-same:01M6KB35DB02GEZR4EM3DFWDSK":57},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6KB35DB02GEZR4EM3DFWDSK","remember",null,"Explicitly save important knowledge to auto-memory with timestamp and context. Use when a discovery is too important to rely on auto-capture.","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\u002Fremember\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28],"memory","discovery","save","knowledge","capture","timestamp","context","use","auto","with","2026-11-10 10:12:30",false,"---\nname: \"remember\"\ndescription: \"Explicitly save important knowledge to auto-memory with timestamp and context. Use when a discovery is too important to rely on auto-capture.\"\ncommand: \u002Fsi:remember\n---\n\n# \u002Fsi:remember — Save Knowledge Explicitly\n\nWrites an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.\n\n## Usage\n\n```\n\u002Fsi:remember \u003Cwhat to remember>\n\u002Fsi:remember \"This project's CI requires Node 20 LTS — v22 breaks the build\"\n\u002Fsi:remember \"The \u002Fapi\u002Fauth endpoint uses a custom JWT library, not passport\"\n\u002Fsi:remember \"Reza prefers explicit error handling over try-catch-all patterns\"\n```\n\n## When to Use\n\n| Situation | Example |\n|-----------|---------|\n| Hard-won debugging insight | \"CORS errors on \u002Fapi\u002Fupload are caused by the CDN, not the backend\" |\n| Project convention not in CLAUDE.md | \"We use barrel exports in src\u002Fcomponents\u002F\" |\n| Tool-specific gotcha | \"Jest needs `--forceExit` flag or it hangs on DB tests\" |\n| Architecture decision | \"We chose Drizzle over Prisma for type-safe SQL\" |\n| Preference you want Claude to learn | \"Don't add comments explaining obvious code\" |\n\n## Workflow\n\n### Step 1: Parse the knowledge\n\nExtract from the user's input:\n- **What**: The concrete fact or pattern\n- **Why it matters**: Context (if provided)\n- **Scope**: Project-specific or global?\n\n### Step 2: Check for duplicates\n\n```bash\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\" 2>\u002Fdev\u002Fnull\n```\n\nIf a similar entry exists:\n- Show it to the user\n- Ask: \"Update the existing entry or add a new one?\"\n\n### Step 3: Write to MEMORY.md\n\nAppend to the end of `MEMORY.md`:\n\n```markdown\n- {{concise fact or pattern}}\n```\n\nKeep entries concise — one line when possible. Auto-memory entries don't need timestamps, IDs, or metadata. They're notes, not database records.\n\nIf MEMORY.md is over 180 lines, warn the user:\n\n```\n⚠️ MEMORY.md is at {{n}}\u002F200 lines. Consider running \u002Fsi:review to free space.\n```\n\n### Step 4: Suggest promotion\n\nIf the knowledge sounds like a rule (imperative, always\u002Fnever, convention):\n\n```\n? This sounds like it could be a CLAUDE.md rule rather than a memory entry.\n   Rules are enforced with higher priority. Want to \u002Fsi:promote it instead?\n```\n\n### Step 5: Confirm\n\n```\n✅ Saved to auto-memory\n\n  \"{{entry}}\"\n\n  MEMORY.md: {{n}}\u002F200 lines\n  Claude will see this at the start of every session in this project.\n```\n\n## What NOT to use \u002Fsi:remember for\n\n- **Temporary context**: Use session memory or just tell Claude in conversation\n- **Enforced rules**: Use `\u002Fsi:promote` to write directly to CLAUDE.md\n- **Cross-project knowledge**: Use `~\u002F.claude\u002FCLAUDE.md` for global rules\n- **Sensitive data**: Never store credentials, tokens, or secrets in memory files\n\n## Tips\n\n- Be concise — one line beats a paragraph\n- Include the concrete command or value, not just the concept\n  - ✅ \"Build with `pnpm build`, tests with `pnpm test:e2e`\"\n  - ❌ \"The project uses pnpm for building and testing\"\n- If you're remembering the same thing twice, promote it to CLAUDE.md\n","# \u002Fsi:remember — Save Knowledge Explicitly\n\nWrites an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.\n\n## Usage\n\n```\n\u002Fsi:remember \u003Cwhat to remember>\n\u002Fsi:remember \"This project's CI requires Node 20 LTS — v22 breaks the build\"\n\u002Fsi:remember \"The \u002Fapi\u002Fauth endpoint uses a custom JWT library, not passport\"\n\u002Fsi:remember \"Reza prefers explicit error handling over try-catch-all patterns\"\n```\n\n## When to Use\n\n| Situation | Example |\n|-----------|---------|\n| Hard-won debugging insight | \"CORS errors on \u002Fapi\u002Fupload are caused by the CDN, not the backend\" |\n| Project convention not in CLAUDE.md | \"We use barrel exports in src\u002Fcomponents\u002F\" |\n| Tool-specific gotcha | \"Jest needs `--forceExit` flag or it hangs on DB tests\" |\n| Architecture decision | \"We chose Drizzle over Prisma for type-safe SQL\" |\n| Preference you want Claude to learn | \"Don't add comments explaining obvious code\" |\n\n## Workflow\n\n### Step 1: Parse the knowledge\n\nExtract from the user's input:\n- **What**: The concrete fact or pattern\n- **Why it matters**: Context (if provided)\n- **Scope**: Project-specific or global?\n\n### Step 2: Check for duplicates\n\n```bash\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\" 2>\u002Fdev\u002Fnull\n```\n\nIf a similar entry exists:\n- Show it to the user\n- Ask: \"Update the existing entry or add a new one?\"\n\n### Step 3: Write to MEMORY.md\n\nAppend to the end of `MEMORY.md`:\n\n```markdown\n- {{concise fact or pattern}}\n```\n\nKeep entries concise — one line when possible. Auto-memory entries don't need timestamps, IDs, or metadata. They're notes, not database records.\n\nIf MEMORY.md is over 180 lines, warn the user:\n\n```\n⚠️ MEMORY.md is at {{n}}\u002F200 lines. Consider running \u002Fsi:review to free space.\n```\n\n### Step 4: Suggest promotion\n\nIf the knowledge sounds like a rule (imperative, always\u002Fnever, convention):\n\n```\n? This sounds like it could be a CLAUDE.md rule rather than a memory entry.\n   Rules are enforced with higher priority. Want to \u002Fsi:promote it instead?\n```\n\n### Step 5: Confirm\n\n```\n✅ Saved to auto-memory\n\n  \"{{entry}}\"\n\n  MEMORY.md: {{n}}\u002F200 lines\n  Claude will see this at the start of every session in this project.\n```\n\n## What NOT to use \u002Fsi:remember for\n\n- **Temporary context**: Use session memory or just tell Claude in conversation\n- **Enforced rules**: Use `\u002Fsi:promote` to write directly to CLAUDE.md\n- **Cross-project knowledge**: Use `~\u002F.claude\u002FCLAUDE.md` for global rules\n- **Sensitive data**: Never store credentials, tokens, or secrets in memory files\n\n## Tips\n\n- Be concise — one line beats a paragraph\n- Include the concrete command or value, not just the concept\n  - ✅ \"Build with `pnpm build`, tests with `pnpm test:e2e`\"\n  - ❌ \"The project uses pnpm for building and testing\"\n- If you're remembering the same thing twice, promote it to CLAUDE.md\n",{"name":5,"command":34,"description":7},"\u002Fsi:remember","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering-team\u002Fself-improving-agent\u002Fskills\u002Fremember",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill remember",{"tool":49,"command":50},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill remember",{"tool":52,"command":53},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill remember","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fremember\u002FSKILL.md",true,[],[58,89,114,139,171,191],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":69,"publishedAt":29},"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",[64],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[70,71,72,73,74,75,76,77,26,78,79,80,81,82,83,84,85,86,87,88],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":29},"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",[],[96,97,98,99,100,101,102,103,77,26,104,105,106,107,108,109,110,111,112,113],"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":29},"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",[],[121,122,123,124,125,126,127,128,129,26,130,131,132,133,134,135,136,137,138,88],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":153,"publishedAt":29},"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",[145,150],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":151,"categoryName":152,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000032","设计师",[154,155,138,156,157,158,159,160,161,26,162,163,164,165,166,167,168,169,88,170],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":29},"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",[177],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[179,155,138,180,181,182,183,184,70,185,161,186,122,187,188,189,105,166,88,190],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":204,"publishedAt":29},"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",[197,200,203],{"categoryNo":198,"categoryName":199,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":201,"categoryName":202,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[205,206,155,138,180,207,208,74,161,209,210,211,212,213,106,214,215,216,217,88],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]