[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HQ0GV05ZN11QEZQ2SZP9TR":3,"skill-same:01M6HQ0GV05ZN11QEZQ2SZP9TR":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":75},"01M6HQ0GV05ZN11QEZQ2SZP9TR","team-level",null,"Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area\u002Flevel creation.","welflau\u002Fai-dev-system","welflau","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7010385?v=4","01M6HPTDGF18RFY07M229P8CTM","01M6HPTDMRMZCJPYBFEA9XVVYT",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fteam-level\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"team level","team","world","for","true","narrative","complete","name","systems","creation","director","design","task","Art","builder","write","read","Bash","orchestrate","qa","2026-11-10 10:12:30",false,"---\nname: team-level\ndescription: \"Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area\u002Flevel creation.\"\nargument-hint: \"[level name or area to design]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite\n---\n\nWhen this skill is invoked:\n\n**Decision Points:** At each step transition, use `AskUserQuestion` to present\nthe user with the subagent's proposals as selectable options. Write the agent's\nfull analysis in conversation, then capture the decision with concise labels.\nThe user must approve before moving to the next step.\n\n1. **Read the argument** for the target level or area (e.g., `tutorial`,\n   `forest dungeon`, `hub town`, `final boss arena`).\n\n2. **Gather context**:\n   - Read the game concept at `design\u002Fgdd\u002Fgame-concept.md`\n   - Read game pillars at `design\u002Fgdd\u002Fgame-pillars.md`\n   - Read existing level docs in `design\u002Flevels\u002F`\n   - Read relevant narrative docs in `design\u002Fnarrative\u002F`\n   - Read world-building docs for the area's region\u002Ffaction\n\n## How to Delegate\n\nUse the Task tool to spawn each team member as a subagent:\n- `subagent_type: narrative-director` — Narrative purpose, characters, emotional arc\n- `subagent_type: world-builder` — Lore context, environmental storytelling, world rules\n- `subagent_type: level-designer` — Spatial layout, pacing, encounters, navigation\n- `subagent_type: systems-designer` — Enemy compositions, loot tables, difficulty balance\n- `subagent_type: art-director` — Visual theme, color palette, lighting, asset requirements\n- `subagent_type: qa-tester` — Test cases, boundary testing, playtest checklist\n\nAlways provide full context in each agent's prompt (game concept, pillars, existing level docs, narrative docs).\n\n3. **Orchestrate the level design team** in sequence:\n\n### Step 1: Narrative Context (narrative-director + world-builder)\nSpawn the `narrative-director` agent to:\n- Define the narrative purpose of this area (what story beats happen here?)\n- Identify key characters, dialogue triggers, and lore elements\n- Specify emotional arc (how should the player feel entering, during, leaving?)\n\nSpawn the `world-builder` agent to:\n- Provide lore context for the area (history, faction presence, ecology)\n- Define environmental storytelling opportunities\n- Specify any world rules that affect gameplay in this area\n\n### Step 2: Layout and Encounter Design (level-designer)\nSpawn the `level-designer` agent to:\n- Design the spatial layout (critical path, optional paths, secrets)\n- Define pacing curve (tension peaks, rest areas, exploration zones)\n- Place encounters with difficulty progression\n- Design environmental puzzles or navigation challenges\n- Define points of interest and landmarks for wayfinding\n- Specify entry\u002Fexit points and connections to adjacent areas\n\n### Step 3: Systems Integration (systems-designer)\nSpawn the `systems-designer` agent to:\n- Specify enemy compositions and encounter formulas\n- Define loot tables and reward placement\n- Balance difficulty relative to expected player level\u002Fgear\n- Design any area-specific mechanics or environmental hazards\n- Specify resource distribution (health pickups, save points, shops)\n\n### Step 4: Visual Direction (art-director)\nSpawn the `art-director` agent to:\n- Define the visual theme and color palette for the area\n- Specify lighting mood and time-of-day settings\n- List required art assets (environment props, unique assets)\n- Define visual landmarks and sight lines\n- Specify any special VFX needs (weather, particles, fog)\n\n### Step 5: QA Planning (qa-tester)\nSpawn the `qa-tester` agent to:\n- Write test cases for the critical path\n- Identify boundary and edge cases (sequence breaks, softlocks)\n- Create a playtest checklist for the area\n- Define acceptance criteria for level completion\n\n4. **Compile the level design document** combining all team outputs into the\n   level design template format.\n\n5. **Save to** `design\u002Flevels\u002F[level-name].md`.\n\n6. **Output a summary** with: area overview, encounter count, estimated asset\n   list, narrative beats, and any cross-team dependencies or open questions.\n","When this skill is invoked:\n\n**Decision Points:** At each step transition, use `AskUserQuestion` to present\nthe user with the subagent's proposals as selectable options. Write the agent's\nfull analysis in conversation, then capture the decision with concise labels.\nThe user must approve before moving to the next step.\n\n1. **Read the argument** for the target level or area (e.g., `tutorial`,\n   `forest dungeon`, `hub town`, `final boss arena`).\n\n2. **Gather context**:\n   - Read the game concept at `design\u002Fgdd\u002Fgame-concept.md`\n   - Read game pillars at `design\u002Fgdd\u002Fgame-pillars.md`\n   - Read existing level docs in `design\u002Flevels\u002F`\n   - Read relevant narrative docs in `design\u002Fnarrative\u002F`\n   - Read world-building docs for the area's region\u002Ffaction\n\n## How to Delegate\n\nUse the Task tool to spawn each team member as a subagent:\n- `subagent_type: narrative-director` — Narrative purpose, characters, emotional arc\n- `subagent_type: world-builder` — Lore context, environmental storytelling, world rules\n- `subagent_type: level-designer` — Spatial layout, pacing, encounters, navigation\n- `subagent_type: systems-designer` — Enemy compositions, loot tables, difficulty balance\n- `subagent_type: art-director` — Visual theme, color palette, lighting, asset requirements\n- `subagent_type: qa-tester` — Test cases, boundary testing, playtest checklist\n\nAlways provide full context in each agent's prompt (game concept, pillars, existing level docs, narrative docs).\n\n3. **Orchestrate the level design team** in sequence:\n\n### Step 1: Narrative Context (narrative-director + world-builder)\nSpawn the `narrative-director` agent to:\n- Define the narrative purpose of this area (what story beats happen here?)\n- Identify key characters, dialogue triggers, and lore elements\n- Specify emotional arc (how should the player feel entering, during, leaving?)\n\nSpawn the `world-builder` agent to:\n- Provide lore context for the area (history, faction presence, ecology)\n- Define environmental storytelling opportunities\n- Specify any world rules that affect gameplay in this area\n\n### Step 2: Layout and Encounter Design (level-designer)\nSpawn the `level-designer` agent to:\n- Design the spatial layout (critical path, optional paths, secrets)\n- Define pacing curve (tension peaks, rest areas, exploration zones)\n- Place encounters with difficulty progression\n- Design environmental puzzles or navigation challenges\n- Define points of interest and landmarks for wayfinding\n- Specify entry\u002Fexit points and connections to adjacent areas\n\n### Step 3: Systems Integration (systems-designer)\nSpawn the `systems-designer` agent to:\n- Specify enemy compositions and encounter formulas\n- Define loot tables and reward placement\n- Balance difficulty relative to expected player level\u002Fgear\n- Design any area-specific mechanics or environmental hazards\n- Specify resource distribution (health pickups, save points, shops)\n\n### Step 4: Visual Direction (art-director)\nSpawn the `art-director` agent to:\n- Define the visual theme and color palette for the area\n- Specify lighting mood and time-of-day settings\n- List required art assets (environment props, unique assets)\n- Define visual landmarks and sight lines\n- Specify any special VFX needs (weather, particles, fog)\n\n### Step 5: QA Planning (qa-tester)\nSpawn the `qa-tester` agent to:\n- Write test cases for the critical path\n- Identify boundary and edge cases (sequence breaks, softlocks)\n- Create a playtest checklist for the area\n- Define acceptance criteria for level completion\n\n4. **Compile the level design document** combining all team outputs into the\n   level design template format.\n\n5. **Save to** `design\u002Flevels\u002F[level-name].md`.\n\n6. **Output a summary** with: area overview, encounter count, estimated asset\n   list, narrative beats, and any cross-team dependencies or open questions.\n",{"name":5,"description":7,"allowed-tools":53,"argument-hint":54,"user-invocable":55},"Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite","[level name or area to design]",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fteam-level",1,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system","https:\u002F\u002Fgithub.com\u002Fwelflau","2026-11-12 14:55:20",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":55},[65,68,71],{"tool":66,"command":67},"npx","npx skills add welflau\u002Fai-dev-system --skill team-level",{"tool":69,"command":70},"bunx","bunx skills add welflau\u002Fai-dev-system --skill team-level",{"tool":72,"command":73},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill team-level","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fteam-level\u002FSKILL.md",[],[77,109,138,163,186,209],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":91,"publishedAt":108},"01M6HS9Z4B0YA8CJCS2Y2F04Y3","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FSKILL.md",[85,88],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":89,"categoryName":90,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,31],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","with","2026-11-11 15:11:14",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":108},"01M6HRAGMG7JF0HXYHMA5QHS8A","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",[120,121,122,123,124,43,125,126,127,128,129,130,131,132,133,134,135,136,137],"internal comms","comms","status","help","SET","use","reports","me","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":48},"01M6HSTDP4M3JFXEBK91VFB4PA","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FSKILL.md",[145],{"categoryNo":89,"categoryName":90,"taxonomyType":20,"taxonomyTypeDesc":21},[147,98,148,149,42,95,150,151,152,153,154,155,156,157,125,158,159,160,161,31,162],"web artifacts builder","artifacts","artifacts builder","css","components","react","routing","state management","state","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":48},"01M6HSDXH0JSP8R3QTNY9XZ8HN","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FSKILL.md",[170,171,172],{"categoryNo":89,"categoryName":90,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[95,39,174,150,98,151,152,175,176,177,148,178,104,179,125,180,181,182,183,107,184,185],"frontend design","react components","create","code","examples","landing","ui design","pages","aesthetics","web ui","generic","when",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":190,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":48},"01M6HSA77QYVP7A72HREGTDN2C","algorithmic-art","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FSKILL.md",[193],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[195,41,196,176,177,197,198,199,200,125,201,202,36,203,107,204,205,206,207,208,185],"algorithmic art","algorithmic","flow","js","work","interactive","generative art","exploration","users","Existing","request","generative","copyright","fields",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":48},"01M6HS9HE0X390Y6RQKTY1YNGJ","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FSKILL.md",[216],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[218,219,220,221,100,222,148,124,223,224,179,225,226,181,227,107,228,229,230,31,231,232],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]