[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70R90K559X2P7WZ7TYBV42H":3,"skill-same:01M70R90K559X2P7WZ7TYBV42H":64},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M70R90K559X2P7WZ7TYBV42H","architectural-technology-session-delivery",null,"Prepare for and deliver a professional session or appointment for architects, developers and homeowners in design studios and construction sites.\nTRIGGERS - Use when a architectural technologist needs a session delivery guide for architects, developers and homeowners in design studios and construction sites.","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\u002Farchitectural-technology-session-delivery\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"architectural technology session delivery","session","technology","delivery","deliver","professional","for","triggers","sites","design","use","when","prepare","guide","2026-11-10 10:12:30",false,"---\nname: architectural-technology-session-delivery\ndescription: |\n  Prepare for and deliver a professional session or appointment for architects, developers and homeowners in design studios and construction sites.\n  TRIGGERS - Use when a architectural technologist needs a session delivery guide for architects, developers and homeowners in design studios and construction sites.\ncategory: Architectural Technology\nlicense: MIT\nversion: 1.0\n---\n# Session Delivery Guide — Architectural Technology\n\nPrepare for and deliver a professional session or appointment for architects, developers and homeowners in design studios and construction sites. The deliverable is a session plan, delivery checklist and post-session record.\nThis skill is written for a architectural technologist working with architects, developers and homeowners in design studios and construction sites.\n\n## When to use\n- You are a architectural technologist preparing, delivering or reviewing this part of your work in design studios and construction sites.\n- You need a defensible, repeatable approach that produces a session plan, delivery checklist and post-session record.\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| Building regulations | legal standards for design and construction work |\n| Detailing | the precise drawings of how building elements join |\n| Clash detection | finding conflicts between building systems in a model |\n\n## Workflow\n1. **Step 1** - Review technical drawings before the session so you know the history, goals and any cautions such as regulation non-compliance\n2. **Step 2** - Prepare the space and CAD and BIM software; check everything works and is safe before architects, developers and homeowners arrive\n3. **Step 3** - Open the session by agreeing the focus and what a good outcome looks like, linked to drawing issue timeliness\n4. **Step 4** - Deliver the session, adapting in the moment while staying inside the agreed plan and professional scope\n5. **Step 5** - Close by summarising what was covered, confirming follow-ups, and completing the session record the same day\n\n## Profession-Specific Components\n| Component | Details for Architectural Technology |\n|-----------|-------------------------------|\n| Core documentation | technical drawings; detail specifications; building regulation submissions; site reports |\n| Core tools & equipment | CAD and BIM software; specification tools; survey equipment; printing and plotting |\n| People involved | architects, developers and homeowners; the architectural technologist; colleagues and other services in design studios and construction sites |\n| Primary record | technical drawings — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design studios and construction sites] | **Objective:** [What this must achieve] | **Audience:** [architects, developers and homeowners and other stakeholders]\n\nThe finished output is a session plan, delivery checklist and post-session record, 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 technical drawings.\n2. **Short-term:** Complete the workflow steps and record outcomes against drawing issue timeliness.\n3. **Medium-term:** Review results, close actions, and update local procedures in design studios and construction sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| drawing issue timeliness | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n| regulation approval rates | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n| site query counts | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n| client satisfaction | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: regulation non-compliance.\n- Never let this happen: detailing errors causing site problems.\n- Never let this happen: clash detection missed.\n- Work only within the competence and authority of a architectural technologist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design studios and construction sites'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 architectural technologist in design studios and construction sites applies this workflow for architects, developers and homeowners: they open\ntechnical drawings, work through the five steps using CAD and BIM software, and close by recording\nthe outcome against drawing issue timeliness and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Session Delivery Guide — Architectural Technology\n\nPrepare for and deliver a professional session or appointment for architects, developers and homeowners in design studios and construction sites. The deliverable is a session plan, delivery checklist and post-session record.\nThis skill is written for a architectural technologist working with architects, developers and homeowners in design studios and construction sites.\n\n## When to use\n- You are a architectural technologist preparing, delivering or reviewing this part of your work in design studios and construction sites.\n- You need a defensible, repeatable approach that produces a session plan, delivery checklist and post-session record.\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| Building regulations | legal standards for design and construction work |\n| Detailing | the precise drawings of how building elements join |\n| Clash detection | finding conflicts between building systems in a model |\n\n## Workflow\n1. **Step 1** - Review technical drawings before the session so you know the history, goals and any cautions such as regulation non-compliance\n2. **Step 2** - Prepare the space and CAD and BIM software; check everything works and is safe before architects, developers and homeowners arrive\n3. **Step 3** - Open the session by agreeing the focus and what a good outcome looks like, linked to drawing issue timeliness\n4. **Step 4** - Deliver the session, adapting in the moment while staying inside the agreed plan and professional scope\n5. **Step 5** - Close by summarising what was covered, confirming follow-ups, and completing the session record the same day\n\n## Profession-Specific Components\n| Component | Details for Architectural Technology |\n|-----------|-------------------------------|\n| Core documentation | technical drawings; detail specifications; building regulation submissions; site reports |\n| Core tools & equipment | CAD and BIM software; specification tools; survey equipment; printing and plotting |\n| People involved | architects, developers and homeowners; the architectural technologist; colleagues and other services in design studios and construction sites |\n| Primary record | technical drawings — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design studios and construction sites] | **Objective:** [What this must achieve] | **Audience:** [architects, developers and homeowners and other stakeholders]\n\nThe finished output is a session plan, delivery checklist and post-session record, 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 technical drawings.\n2. **Short-term:** Complete the workflow steps and record outcomes against drawing issue timeliness.\n3. **Medium-term:** Review results, close actions, and update local procedures in design studios and construction sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| drawing issue timeliness | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n| regulation approval rates | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n| site query counts | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n| client satisfaction | Agree a local target and track the trend | Measured from technical drawings and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: regulation non-compliance.\n- Never let this happen: detailing errors causing site problems.\n- Never let this happen: clash detection missed.\n- Work only within the competence and authority of a architectural technologist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design studios and construction sites'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 architectural technologist in design studios and construction sites applies this workflow for architects, developers and homeowners: they open\ntechnical drawings, work through the five steps using CAD and BIM software, and close by recording\nthe outcome against drawing issue timeliness 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":38,"category":39,"description":40},1,"Architectural Technology","Prepare for and deliver a professional session or appointment for architects, developers and homeowners in design studios and construction sites.\nTRIGGERS - Use when a architectural technologist needs a session delivery guide for architects, developers and homeowners in design studios and construction sites.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Farchitectural-technology-session-delivery",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill architectural-technology-session-delivery",{"tool":56,"command":57},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill architectural-technology-session-delivery",{"tool":59,"command":60},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill architectural-technology-session-delivery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Farchitectural-technology-session-delivery\u002FSKILL.md",true,[],[65,85,98,111,128,137],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":33},"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",[],[72,73,74,75,32,76,25,77,78,79,30,80,29,81,26,82,83,84],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"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":33},"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",[],[92,73,93,94,30,80,29,95,81,26,96,25,84,97,77,78],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":33},"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",[],[105,106,73,107,108,77,78,80,29,81,26,109,110,25,84,30],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":122,"publishedAt":33},"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",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[123,73,124,125,25,126,84,26,127,77,78,30,80,29,81],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":33},"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",[],[22,135,20,73,136,78,32,31,77,30,80,29,81,26,25,24,23,84],"work session","youth work session delivery",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":146,"publishedAt":33},"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",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000015","视觉设计",[73,147,148,149,25,26,81,28,150,84,78,77,80,29,30],"service","plan","youth work service plan","as"]