[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CQQJXB75XEC7D42SWBESZ":3,"skill-same:01M71CQQJXB75XEC7D42SWBESZ":65},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M71CQQJXB75XEC7D42SWBESZ","urban-planning-troubleshooting-guide",null,"Diagnose and resolve common problems a town planner meets in planning departments and consultancy offices.\nTRIGGERS - Use when a town planner needs a troubleshooting & problem solving for developers, councils and communities in planning departments and consultancy offices.","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\u002Furban-planning-troubleshooting-guide\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"planning","urban planning troubleshooting guide","troubleshooting","troubleshooting guide","guide","communities","problem","diagnose","for","triggers","use","when","common","planner","problem solving","2026-11-10 10:12:30",false,"---\nname: urban-planning-troubleshooting-guide\ndescription: |\n  Diagnose and resolve common problems a town planner meets in planning departments and consultancy offices.\n  TRIGGERS - Use when a town planner needs a troubleshooting & problem solving for developers, councils and communities in planning departments and consultancy offices.\ncategory: Urban Planning\nlicense: MIT\nversion: 1.0\n---\n# Troubleshooting & Problem Solving — Urban Planning\n\nDiagnose and resolve common problems a town planner meets in planning departments and consultancy offices. The deliverable is a troubleshooting guide: symptoms, likely causes, checks and fixes.\nThis skill is written for a town planner working with developers, councils and communities in planning departments and consultancy offices.\n\n## When to use\n- You are a town planner preparing, delivering or reviewing this part of your work in planning departments and consultancy offices.\n- You need a defensible, repeatable approach that produces a troubleshooting guide: symptoms, likely causes, checks and fixes.\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| Local plan | the statutory document guiding development in an area |\n| Determination | the formal decision on a planning application |\n| Material consideration | a planning factor legally relevant to a decision |\n\n## Workflow\n1. **Step 1** - Describe the problem precisely from the record in planning applications — when it started, what changed, who it affects\n2. **Step 2** - Work from most likely and most dangerous causes first; rule out anything connected to missed consultation deadlines early\n3. **Step 3** - Run checks in a logical order using GIS mapping, changing one variable at a time so the cause can be isolated\n4. **Step 4** - Apply the fix, then verify against application determination times that the problem is actually resolved, not just quieter\n5. **Step 5** - Document the diagnosis and fix so the next occurrence is faster, and flag recurring problems for root-cause work\n\n## Profession-Specific Components\n| Component | Details for Urban Planning |\n|-----------|-------------------------------|\n| Core documentation | planning applications; policy documents; site appraisals; consultation reports |\n| Core tools & equipment | GIS mapping; planning portals; modelling software; consultation platforms |\n| People involved | developers, councils and communities; the town planner; colleagues and other services in planning departments and consultancy offices |\n| Primary record | planning applications — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in planning departments and consultancy offices] | **Objective:** [What this must achieve] | **Audience:** [developers, councils and communities and other stakeholders]\n\nThe finished output is a troubleshooting guide: symptoms, likely causes, checks and fixes, 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 planning applications.\n2. **Short-term:** Complete the workflow steps and record outcomes against application determination times.\n3. **Medium-term:** Review results, close actions, and update local procedures in planning departments and consultancy offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| application determination times | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n| appeal outcomes | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n| consultation engagement | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n| policy adoption | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: missed consultation deadlines.\n- Never let this happen: policy conflicts.\n- Never let this happen: appeals lost on process.\n- Work only within the competence and authority of a town planner; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to planning departments and consultancy offices'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 town planner in planning departments and consultancy offices applies this workflow for developers, councils and communities: they open\nplanning applications, work through the five steps using GIS mapping, and close by recording\nthe outcome against application determination times and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Troubleshooting & Problem Solving — Urban Planning\n\nDiagnose and resolve common problems a town planner meets in planning departments and consultancy offices. The deliverable is a troubleshooting guide: symptoms, likely causes, checks and fixes.\nThis skill is written for a town planner working with developers, councils and communities in planning departments and consultancy offices.\n\n## When to use\n- You are a town planner preparing, delivering or reviewing this part of your work in planning departments and consultancy offices.\n- You need a defensible, repeatable approach that produces a troubleshooting guide: symptoms, likely causes, checks and fixes.\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| Local plan | the statutory document guiding development in an area |\n| Determination | the formal decision on a planning application |\n| Material consideration | a planning factor legally relevant to a decision |\n\n## Workflow\n1. **Step 1** - Describe the problem precisely from the record in planning applications — when it started, what changed, who it affects\n2. **Step 2** - Work from most likely and most dangerous causes first; rule out anything connected to missed consultation deadlines early\n3. **Step 3** - Run checks in a logical order using GIS mapping, changing one variable at a time so the cause can be isolated\n4. **Step 4** - Apply the fix, then verify against application determination times that the problem is actually resolved, not just quieter\n5. **Step 5** - Document the diagnosis and fix so the next occurrence is faster, and flag recurring problems for root-cause work\n\n## Profession-Specific Components\n| Component | Details for Urban Planning |\n|-----------|-------------------------------|\n| Core documentation | planning applications; policy documents; site appraisals; consultation reports |\n| Core tools & equipment | GIS mapping; planning portals; modelling software; consultation platforms |\n| People involved | developers, councils and communities; the town planner; colleagues and other services in planning departments and consultancy offices |\n| Primary record | planning applications — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in planning departments and consultancy offices] | **Objective:** [What this must achieve] | **Audience:** [developers, councils and communities and other stakeholders]\n\nThe finished output is a troubleshooting guide: symptoms, likely causes, checks and fixes, 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 planning applications.\n2. **Short-term:** Complete the workflow steps and record outcomes against application determination times.\n3. **Medium-term:** Review results, close actions, and update local procedures in planning departments and consultancy offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| application determination times | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n| appeal outcomes | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n| consultation engagement | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n| policy adoption | Agree a local target and track the trend | Measured from planning applications and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: missed consultation deadlines.\n- Never let this happen: policy conflicts.\n- Never let this happen: appeals lost on process.\n- Work only within the competence and authority of a town planner; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to planning departments and consultancy offices'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 town planner in planning departments and consultancy offices applies this workflow for developers, councils and communities: they open\nplanning applications, work through the five steps using GIS mapping, and close by recording\nthe outcome against application determination times 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":39,"category":40,"description":41},1,"Urban Planning","Diagnose and resolve common problems a town planner meets in planning departments and consultancy offices.\nTRIGGERS - Use when a town planner needs a troubleshooting & problem solving for developers, councils and communities in planning departments and consultancy offices.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Furban-planning-troubleshooting-guide",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill urban-planning-troubleshooting-guide",{"tool":57,"command":58},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill urban-planning-troubleshooting-guide",{"tool":60,"command":61},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill urban-planning-troubleshooting-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Furban-planning-troubleshooting-guide\u002FSKILL.md",true,[],[66,79,92,105,122,136],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":34},"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",[],[73,74,21,22,23,33,27,75,76,31,30,77,29,78,28,26,25,24],"youth work troubleshooting guide","work","outreach","settings","people","worker",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":34},"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",[],[86,74,87,88,30,77,29,89,78,28,90,27,24,91,75,76],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":34},"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",[],[99,100,74,101,102,75,76,77,29,78,28,103,104,27,24,30],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":116,"publishedAt":34},"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",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[117,74,118,119,27,120,24,28,121,75,76,30,77,29,78],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":34},"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",[],[129,130,131,74,132,76,23,133,75,30,77,29,78,28,27,134,135,24],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":145,"publishedAt":34},"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",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000015","视觉设计",[74,146,147,148,27,28,78,149,150,24,76,75,77,29,30],"service","plan","youth work service plan","design","as"]