[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70Q616CAPTTVPTCK2CPDYRF":3,"skill-same:01M70Q616CAPTTVPTCK2CPDYRF":69},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M70Q616CAPTTVPTCK2CPDYRF","aerospace-engineering-records-documentation",null,"Create and maintain accurate, auditable records for work with aircraft manufacturers, airlines and space agencies.\nTRIGGERS - Use when a aerospace engineer needs a records & documentation for aircraft manufacturers, airlines and space agencies in design offices, test facilities and hangars.","lionelsimai\u002Fclaude-skills-collection","lionelsimai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260158848?v=4","01M6CHZPS8G9TSB113TT0BBM6E","Lionel ","01M6CHZPXGW2SPE3BHQTGJ0S8J",38,"MIT","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Faerospace-engineering-records-documentation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"documentation","aerospace engineering records documentation","aerospace engineering","engineering","aerospace","records","space","aerospace engineer","work","test","create","with","when","use","maintain","design","triggers","engineer","for","2026-11-10 10:12:30",false,"---\nname: aerospace-engineering-records-documentation\ndescription: |\n  Create and maintain accurate, auditable records for work with aircraft manufacturers, airlines and space agencies.\n  TRIGGERS - Use when a aerospace engineer needs a records & documentation for aircraft manufacturers, airlines and space agencies in design offices, test facilities and hangars.\ncategory: Aerospace Engineering\nlicense: MIT\nversion: 1.0\n---\n# Records & Documentation — Aerospace Engineering\n\nCreate and maintain accurate, auditable records for work with aircraft manufacturers, airlines and space agencies. The deliverable is a documentation standard, templates and a completed record set.\nThis skill is written for a aerospace engineer working with aircraft manufacturers, airlines and space agencies in design offices, test facilities and hangars.\n\n## When to use\n- You are a aerospace engineer preparing, delivering or reviewing this part of your work in design offices, test facilities and hangars.\n- You need a defensible, repeatable approach that produces a documentation standard, templates and a completed record set.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Certification | official approval that a design meets safety standards |\n| Fatigue life | how long a component withstands repeated loading |\n| Thrust | the force produced by an engine |\n\n## Workflow\n1. **Step 1** - Use design analyses as the single source of truth; record facts, observations and decisions — not speculation\n2. **Step 2** - Write entries contemporaneously where possible, dated and attributable, in the format design offices, test facilities and hangars requires\n3. **Step 3** - Record measurements and outcomes that feed test programme milestones exactly as observed, with units and method noted\n4. **Step 4** - Store and share records under the confidentiality and retention rules that apply in design offices, test facilities and hangars, guarding against test incidents\n5. **Step 5** - Audit a sample of records monthly for completeness and correct anything missing while the work is still current\n\n## Profession-Specific Components\n| Component | Details for Aerospace Engineering |\n|-----------|-------------------------------|\n| Core documentation | design analyses; test reports; certification documents; maintenance data |\n| Core tools & equipment | simulation software; wind tunnels; test instrumentation; CAD systems |\n| People involved | aircraft manufacturers, airlines and space agencies; the aerospace engineer; colleagues and other services in design offices, test facilities and hangars |\n| Primary record | design analyses — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design offices, test facilities and hangars] | **Objective:** [What this must achieve] | **Audience:** [aircraft manufacturers, airlines and space agencies and other stakeholders]\n\nThe finished output is a documentation standard, templates and a completed record set, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in design analyses.\n2. **Short-term:** Complete the workflow steps and record outcomes against test programme milestones.\n3. **Medium-term:** Review results, close actions, and update local procedures in design offices, test facilities and hangars.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| test programme milestones | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n| certification findings | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n| weight targets met | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n| reliability data | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: test incidents.\n- Never let this happen: certification delays.\n- Never let this happen: fatigue failures.\n- Work only within the competence and authority of a aerospace engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design offices, test facilities and hangars's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA aerospace engineer in design offices, test facilities and hangars applies this workflow for aircraft manufacturers, airlines and space agencies: they open\ndesign analyses, work through the five steps using simulation software, and close by recording\nthe outcome against test programme milestones and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Records & Documentation — Aerospace Engineering\n\nCreate and maintain accurate, auditable records for work with aircraft manufacturers, airlines and space agencies. The deliverable is a documentation standard, templates and a completed record set.\nThis skill is written for a aerospace engineer working with aircraft manufacturers, airlines and space agencies in design offices, test facilities and hangars.\n\n## When to use\n- You are a aerospace engineer preparing, delivering or reviewing this part of your work in design offices, test facilities and hangars.\n- You need a defensible, repeatable approach that produces a documentation standard, templates and a completed record set.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Certification | official approval that a design meets safety standards |\n| Fatigue life | how long a component withstands repeated loading |\n| Thrust | the force produced by an engine |\n\n## Workflow\n1. **Step 1** - Use design analyses as the single source of truth; record facts, observations and decisions — not speculation\n2. **Step 2** - Write entries contemporaneously where possible, dated and attributable, in the format design offices, test facilities and hangars requires\n3. **Step 3** - Record measurements and outcomes that feed test programme milestones exactly as observed, with units and method noted\n4. **Step 4** - Store and share records under the confidentiality and retention rules that apply in design offices, test facilities and hangars, guarding against test incidents\n5. **Step 5** - Audit a sample of records monthly for completeness and correct anything missing while the work is still current\n\n## Profession-Specific Components\n| Component | Details for Aerospace Engineering |\n|-----------|-------------------------------|\n| Core documentation | design analyses; test reports; certification documents; maintenance data |\n| Core tools & equipment | simulation software; wind tunnels; test instrumentation; CAD systems |\n| People involved | aircraft manufacturers, airlines and space agencies; the aerospace engineer; colleagues and other services in design offices, test facilities and hangars |\n| Primary record | design analyses — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design offices, test facilities and hangars] | **Objective:** [What this must achieve] | **Audience:** [aircraft manufacturers, airlines and space agencies and other stakeholders]\n\nThe finished output is a documentation standard, templates and a completed record set, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in design analyses.\n2. **Short-term:** Complete the workflow steps and record outcomes against test programme milestones.\n3. **Medium-term:** Review results, close actions, and update local procedures in design offices, test facilities and hangars.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| test programme milestones | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n| certification findings | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n| weight targets met | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n| reliability data | Agree a local target and track the trend | Measured from design analyses and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: test incidents.\n- Never let this happen: certification delays.\n- Never let this happen: fatigue failures.\n- Work only within the competence and authority of a aerospace engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design offices, test facilities and hangars's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA aerospace engineer in design offices, test facilities and hangars applies this workflow for aircraft manufacturers, airlines and space agencies: they open\ndesign analyses, work through the five steps using simulation software, and close by recording\nthe outcome against test programme milestones and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n",{"name":5,"license":15,"version":43,"category":44,"description":45},1,"Aerospace Engineering","Create and maintain accurate, auditable records for work with aircraft manufacturers, airlines and space agencies.\nTRIGGERS - Use when a aerospace engineer needs a records & documentation for aircraft manufacturers, airlines and space agencies in design offices, test facilities and hangars.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Faerospace-engineering-records-documentation",5,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection","https:\u002F\u002Fgithub.com\u002Flionelsimai","www.theaicapitol.com","Founder at The AI Capitol | I help founders turn AI into 10X revenue through systems, not tools. Ex-Apple • Ex-TikTok 👉 http:\u002F\u002Flionelsim.substack.com","2026-11-09 07:48:48",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill aerospace-engineering-records-documentation",{"tool":61,"command":62},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill aerospace-engineering-records-documentation",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill aerospace-engineering-records-documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Faerospace-engineering-records-documentation\u002FSKILL.md",true,[],[70,90,102,115,132,146],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"01M71E7TB5HAR0K6EXB80YXBT7","youth-work-troubleshooting-guide","Diagnose and resolve common problems a youth worker meets in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a troubleshooting & problem solving for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-troubleshooting-guide\u002FSKILL.md",[],[77,27,78,79,80,81,37,82,83,84,31,85,32,86,35,87,88,89],"youth work troubleshooting guide","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"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":38},"01M71E7R3YHK4RAQVCRPB4CTXN","youth-work-tools-equipment-checklist","Select, check and maintain the tools and equipment a youth worker relies on.\nTRIGGERS - Use when a youth worker needs a tools & equipment checklist for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-tools-equipment-checklist\u002FSKILL.md",[],[97,27,98,99,31,85,32,33,86,35,100,37,89,101,82,83],"youth work tools equipment checklist","checklist","Tools","select","check",{"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":38},"01M71E7NX1BMFEFBH01KCRJDEP","youth-work-supplies-procurement","Specify, source and manage the supplies and materials used in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a supplies & procurement for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-supplies-procurement\u002FSKILL.md",[],[109,110,27,111,112,82,83,85,32,86,35,113,114,37,89,31],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":126,"publishedAt":38},"01M71E7JVFP6P96GAT2VT9JY0D","youth-work-stakeholder-presentation","Present youth worker findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a youth worker needs a stakeholder presentation for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-stakeholder-presentation\u002FSKILL.md",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[127,27,128,129,37,130,89,35,131,82,83,31,85,32,86],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":38},"01M71E7GE5VA1RG4XEM2GAZRFY","youth-work-session-delivery","Prepare for and deliver a professional session or appointment for young people and their communities in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a session delivery guide for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-session-delivery\u002FSKILL.md",[],[139,140,141,27,142,83,80,143,82,31,85,32,86,35,37,144,145,89],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":38},"01M71E7DQSMY2ZW1BF3A1Z0VJM","youth-work-service-plan","Design a realistic, measurable service plan for young people and their communities as a youth worker.\nTRIGGERS - Use when a youth worker needs a service plan design for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-service-plan\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000015","视觉设计",[27,156,157,158,37,35,86,34,159,89,83,82,85,32,31],"service","plan","youth work service plan","as"]