[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPX1SGC6JCG59RC6KSD5HD":3,"skill-same:01M6HPX1SGC6JCG59RC6KSD5HD":66},{"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":17,"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":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":65},"01M6HPX1SGC6JCG59RC6KSD5HD","brainstorm",null,"Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.","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\u002Fbrainstorm\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"psychology","hint","for","concept","techniques","websearch","true","player","studio","theme","professional","ZeRO","frameworks","exploration","document","ideation","write","read","game","open","2026-11-10 10:12:30",false,"---\nname: brainstorm\ndescription: \"Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.\"\nargument-hint: \"[genre or theme hint, or 'open' for fully open brainstorm]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Write, WebSearch, AskUserQuestion\n---\n\nWhen this skill is invoked:\n\n1. **Parse the argument** for an optional genre\u002Ftheme hint (e.g., `roguelike`,\n   `space survival`, `cozy farming`). If `open` or no argument, start from\n   scratch.\n\n2. **Check for existing concept work**:\n   - Read `design\u002Fgdd\u002Fgame-concept.md` if it exists (resume, don't restart)\n   - Read `design\u002Fgdd\u002Fgame-pillars.md` if it exists (build on established pillars)\n\n3. **Run through ideation phases** interactively, asking the user questions at\n   each phase. Do NOT generate everything silently — the goal is **collaborative\n   exploration** where the AI acts as a creative facilitator, not a replacement\n   for the human's vision.\n\n   **Use `AskUserQuestion`** at key decision points throughout brainstorming:\n   - Constrained taste questions (genre preferences, scope, team size)\n   - Concept selection (\"Which 2-3 concepts resonate?\") after presenting options\n   - Direction choices (\"Develop further, explore more, or prototype?\")\n   - Pillar ranking after concepts are refined\n   Write full creative analysis in conversation text first, then use\n   `AskUserQuestion` to capture the decision with concise labels.\n\n   Professional studio brainstorming principles to follow:\n   - Withhold judgment — no idea is bad during exploration\n   - Encourage unusual ideas — outside-the-box thinking sparks better concepts\n   - Build on each other — \"yes, and...\" responses, not \"but...\"\n   - Use constraints as creative fuel — limitations often produce the best ideas\n   - Time-box each phase — keep momentum, don't over-deliberate early\n\n---\n\n### Phase 1: Creative Discovery\n\nStart by understanding the person, not the game. Ask these questions\nconversationally (not as a checklist):\n\n**Emotional anchors**:\n- What's a moment in a game that genuinely moved you, thrilled you, or made\n  you lose track of time? What specifically created that feeling?\n- Is there a fantasy or power trip you've always wanted in a game but never\n  quite found?\n\n**Taste profile**:\n- What 3 games have you spent the most time with? What kept you coming back?\n- Are there genres you love? Genres you avoid? Why?\n- Do you prefer games that challenge you, relax you, tell you stories,\n  or let you express yourself?\n\n**Practical constraints** (shape the sandbox before brainstorming):\n- Solo developer or team? What skills are available?\n- Timeline: weeks, months, or years?\n- Any platform constraints? (PC only? Mobile? Console?)\n- First game or experienced developer?\n\n**Synthesize** the answers into a **Creative Brief** — a 3-5 sentence\nsummary of the person's emotional goals, taste profile, and constraints.\nRead the brief back and confirm it captures their intent.\n\n---\n\n### Phase 2: Concept Generation\n\nUsing the creative brief as a foundation, generate **3 distinct concepts**\nthat each take a different creative direction. Use these ideation techniques:\n\n**Technique 1: Verb-First Design**\nStart with the core player verb (build, fight, explore, solve, survive,\ncreate, manage, discover) and build outward from there. The verb IS the game.\n\n**Technique 2: Mashup Method**\nCombine two unexpected elements: [Genre A] + [Theme B]. The tension between\nthe two creates the unique hook. (e.g., \"farming sim + cosmic horror\",\n\"roguelike + dating sim\", \"city builder + real-time combat\")\n\n**Technique 3: Experience-First Design (MDA Backward)**\nStart from the desired player emotion (aesthetic goal from MDA framework:\nsensation, fantasy, narrative, challenge, fellowship, discovery, expression,\nsubmission) and work backward to the dynamics and mechanics that produce it.\n\nFor each concept, present:\n- **Working Title**\n- **Elevator Pitch** (1-2 sentences — must pass the \"10-second test\")\n- **Core Verb** (the single most common player action)\n- **Core Fantasy** (the emotional promise)\n- **Unique Hook** (passes the \"and also\" test: \"Like X, AND ALSO Y\")\n- **Primary MDA Aesthetic** (which emotion dominates?)\n- **Estimated Scope** (small \u002F medium \u002F large)\n- **Why It Could Work** (1 sentence on market\u002Faudience fit)\n- **Biggest Risk** (1 sentence on the hardest unanswered question)\n\nPresent all three. Ask the user to pick one, combine elements, or request\nnew concepts. Never pressure toward a choice — let them sit with it.\n\n---\n\n### Phase 3: Core Loop Design\n\nFor the chosen concept, use structured questioning to build the core loop.\nThe core loop is the beating heart of the game — if it isn't fun in\nisolation, no amount of content or polish will save the game.\n\n**30-Second Loop** (moment-to-moment):\n- What is the player physically doing most often?\n- Is this action intrinsically satisfying? (Would they do it with no\n  rewards, no progression, no story — just for the feel of it?)\n- What makes this action feel good? (Audio feedback, visual juice,\n  timing satisfaction, tactical depth?)\n\n**5-Minute Loop** (short-term goals):\n- What structures the moment-to-moment play into cycles?\n- Where does \"one more turn\" \u002F \"one more run\" psychology kick in?\n- What choices does the player make at this level?\n\n**Session Loop** (30-120 minutes):\n- What does a complete session look like?\n- Where are the natural stopping points?\n- What's the \"hook\" that makes them think about the game when not playing?\n\n**Progression Loop** (days\u002Fweeks):\n- How does the player grow? (Power? Knowledge? Options? Story?)\n- What's the long-term goal? When is the game \"done\"?\n\n**Player Motivation Analysis** (based on Self-Determination Theory):\n- **Autonomy**: How much meaningful choice does the player have?\n- **Competence**: How does the player feel their skill growing?\n- **Relatedness**: How does the player feel connected (to characters,\n  other players, or the world)?\n\n---\n\n### Phase 4: Pillars and Boundaries\n\nGame pillars are used by real AAA studios (God of War, Hades, The Last of\nUs) to keep hundreds of team members making decisions that all point the\nsame direction. Even for solo developers, pillars prevent scope creep and\nkeep the vision sharp.\n\nCollaboratively define **3-5 pillars**:\n- Each pillar has a **name** and **one-sentence definition**\n- Each pillar has a **design test**: \"If we're debating between X and Y,\n  this pillar says we choose __\"\n- Pillars should feel like they create tension with each other — if all\n  pillars point the same way, they're not doing enough work\n\nThen define **3+ anti-pillars** (what this game is NOT):\n- Anti-pillars prevent the most common form of scope creep: \"wouldn't it\n  be cool if...\" features that don't serve the core vision\n- Frame as: \"We will NOT do [thing] because it would compromise [pillar]\"\n\n---\n\n### Phase 5: Player Type Validation\n\nUsing the Bartle taxonomy and Quantic Foundry motivation model, validate\nwho this game is actually for:\n\n- **Primary player type**: Who will LOVE this game? (Achievers, Explorers,\n  Socializers, Competitors, Creators, Storytellers)\n- **Secondary appeal**: Who else might enjoy it?\n- **Who is this NOT for**: Being clear about who won't like this game is as\n  important as knowing who will\n- **Market validation**: Are there successful games that serve a similar\n  player type? What can we learn from their audience size?\n\n---\n\n### Phase 6: Scope and Feasibility\n\nGround the concept in reality:\n\n- **Engine recommendation** (Godot \u002F Unity \u002F Unreal) with reasoning based\n  on concept needs, team expertise, and platform targets\n- **Art pipeline**: What's the art style and how labor-intensive is it?\n- **Content scope**: Estimate level\u002Farea count, item count, gameplay hours\n- **MVP definition**: What's the absolute minimum build that tests \"is the\n  core loop fun?\"\n- **Biggest risks**: Technical risks, design risks, market risks\n- **Scope tiers**: What's the full vision vs. what ships if time runs out?\n\n---\n\n4. **Generate the game concept document** using the template at\n   `.claude\u002Fdocs\u002Ftemplates\u002Fgame-concept.md`. Fill in ALL sections from the\n   brainstorm conversation, including the MDA analysis, player motivation\n   profile, and flow state design sections.\n\n5. **Save to** `design\u002Fgdd\u002Fgame-concept.md`, creating directories as needed.\n\n6. **Suggest next steps** (in this order — this is the professional studio\n   pre-production pipeline):\n   - \"Run `\u002Fsetup-engine [engine] [version]` to configure the engine and populate version-aware reference docs\"\n   - \"Use `\u002Fdesign-review design\u002Fgdd\u002Fgame-concept.md` to validate completeness\"\n   - \"Discuss vision with the `creative-director` agent for pillar refinement\"\n   - \"Decompose the concept into individual systems with `\u002Fmap-systems` — maps dependencies, assigns priorities, and creates the systems index\"\n   - \"Author per-system GDDs with `\u002Fdesign-system` — guided, section-by-section GDD writing\"\n   - \"Prototype the core loop with `\u002Fprototype [core-mechanic]`\"\n   - \"Playtest the prototype with `\u002Fplaytest-report` to validate the hypothesis\"\n   - \"If validated, plan the first sprint with `\u002Fsprint-plan new`\"\n\n7. **Output a summary** with the chosen concept's elevator pitch, pillars,\n   primary player type, engine recommendation, biggest risk, and file path.\n","When this skill is invoked:\n\n1. **Parse the argument** for an optional genre\u002Ftheme hint (e.g., `roguelike`,\n   `space survival`, `cozy farming`). If `open` or no argument, start from\n   scratch.\n\n2. **Check for existing concept work**:\n   - Read `design\u002Fgdd\u002Fgame-concept.md` if it exists (resume, don't restart)\n   - Read `design\u002Fgdd\u002Fgame-pillars.md` if it exists (build on established pillars)\n\n3. **Run through ideation phases** interactively, asking the user questions at\n   each phase. Do NOT generate everything silently — the goal is **collaborative\n   exploration** where the AI acts as a creative facilitator, not a replacement\n   for the human's vision.\n\n   **Use `AskUserQuestion`** at key decision points throughout brainstorming:\n   - Constrained taste questions (genre preferences, scope, team size)\n   - Concept selection (\"Which 2-3 concepts resonate?\") after presenting options\n   - Direction choices (\"Develop further, explore more, or prototype?\")\n   - Pillar ranking after concepts are refined\n   Write full creative analysis in conversation text first, then use\n   `AskUserQuestion` to capture the decision with concise labels.\n\n   Professional studio brainstorming principles to follow:\n   - Withhold judgment — no idea is bad during exploration\n   - Encourage unusual ideas — outside-the-box thinking sparks better concepts\n   - Build on each other — \"yes, and...\" responses, not \"but...\"\n   - Use constraints as creative fuel — limitations often produce the best ideas\n   - Time-box each phase — keep momentum, don't over-deliberate early\n\n---\n\n### Phase 1: Creative Discovery\n\nStart by understanding the person, not the game. Ask these questions\nconversationally (not as a checklist):\n\n**Emotional anchors**:\n- What's a moment in a game that genuinely moved you, thrilled you, or made\n  you lose track of time? What specifically created that feeling?\n- Is there a fantasy or power trip you've always wanted in a game but never\n  quite found?\n\n**Taste profile**:\n- What 3 games have you spent the most time with? What kept you coming back?\n- Are there genres you love? Genres you avoid? Why?\n- Do you prefer games that challenge you, relax you, tell you stories,\n  or let you express yourself?\n\n**Practical constraints** (shape the sandbox before brainstorming):\n- Solo developer or team? What skills are available?\n- Timeline: weeks, months, or years?\n- Any platform constraints? (PC only? Mobile? Console?)\n- First game or experienced developer?\n\n**Synthesize** the answers into a **Creative Brief** — a 3-5 sentence\nsummary of the person's emotional goals, taste profile, and constraints.\nRead the brief back and confirm it captures their intent.\n\n---\n\n### Phase 2: Concept Generation\n\nUsing the creative brief as a foundation, generate **3 distinct concepts**\nthat each take a different creative direction. Use these ideation techniques:\n\n**Technique 1: Verb-First Design**\nStart with the core player verb (build, fight, explore, solve, survive,\ncreate, manage, discover) and build outward from there. The verb IS the game.\n\n**Technique 2: Mashup Method**\nCombine two unexpected elements: [Genre A] + [Theme B]. The tension between\nthe two creates the unique hook. (e.g., \"farming sim + cosmic horror\",\n\"roguelike + dating sim\", \"city builder + real-time combat\")\n\n**Technique 3: Experience-First Design (MDA Backward)**\nStart from the desired player emotion (aesthetic goal from MDA framework:\nsensation, fantasy, narrative, challenge, fellowship, discovery, expression,\nsubmission) and work backward to the dynamics and mechanics that produce it.\n\nFor each concept, present:\n- **Working Title**\n- **Elevator Pitch** (1-2 sentences — must pass the \"10-second test\")\n- **Core Verb** (the single most common player action)\n- **Core Fantasy** (the emotional promise)\n- **Unique Hook** (passes the \"and also\" test: \"Like X, AND ALSO Y\")\n- **Primary MDA Aesthetic** (which emotion dominates?)\n- **Estimated Scope** (small \u002F medium \u002F large)\n- **Why It Could Work** (1 sentence on market\u002Faudience fit)\n- **Biggest Risk** (1 sentence on the hardest unanswered question)\n\nPresent all three. Ask the user to pick one, combine elements, or request\nnew concepts. Never pressure toward a choice — let them sit with it.\n\n---\n\n### Phase 3: Core Loop Design\n\nFor the chosen concept, use structured questioning to build the core loop.\nThe core loop is the beating heart of the game — if it isn't fun in\nisolation, no amount of content or polish will save the game.\n\n**30-Second Loop** (moment-to-moment):\n- What is the player physically doing most often?\n- Is this action intrinsically satisfying? (Would they do it with no\n  rewards, no progression, no story — just for the feel of it?)\n- What makes this action feel good? (Audio feedback, visual juice,\n  timing satisfaction, tactical depth?)\n\n**5-Minute Loop** (short-term goals):\n- What structures the moment-to-moment play into cycles?\n- Where does \"one more turn\" \u002F \"one more run\" psychology kick in?\n- What choices does the player make at this level?\n\n**Session Loop** (30-120 minutes):\n- What does a complete session look like?\n- Where are the natural stopping points?\n- What's the \"hook\" that makes them think about the game when not playing?\n\n**Progression Loop** (days\u002Fweeks):\n- How does the player grow? (Power? Knowledge? Options? Story?)\n- What's the long-term goal? When is the game \"done\"?\n\n**Player Motivation Analysis** (based on Self-Determination Theory):\n- **Autonomy**: How much meaningful choice does the player have?\n- **Competence**: How does the player feel their skill growing?\n- **Relatedness**: How does the player feel connected (to characters,\n  other players, or the world)?\n\n---\n\n### Phase 4: Pillars and Boundaries\n\nGame pillars are used by real AAA studios (God of War, Hades, The Last of\nUs) to keep hundreds of team members making decisions that all point the\nsame direction. Even for solo developers, pillars prevent scope creep and\nkeep the vision sharp.\n\nCollaboratively define **3-5 pillars**:\n- Each pillar has a **name** and **one-sentence definition**\n- Each pillar has a **design test**: \"If we're debating between X and Y,\n  this pillar says we choose __\"\n- Pillars should feel like they create tension with each other — if all\n  pillars point the same way, they're not doing enough work\n\nThen define **3+ anti-pillars** (what this game is NOT):\n- Anti-pillars prevent the most common form of scope creep: \"wouldn't it\n  be cool if...\" features that don't serve the core vision\n- Frame as: \"We will NOT do [thing] because it would compromise [pillar]\"\n\n---\n\n### Phase 5: Player Type Validation\n\nUsing the Bartle taxonomy and Quantic Foundry motivation model, validate\nwho this game is actually for:\n\n- **Primary player type**: Who will LOVE this game? (Achievers, Explorers,\n  Socializers, Competitors, Creators, Storytellers)\n- **Secondary appeal**: Who else might enjoy it?\n- **Who is this NOT for**: Being clear about who won't like this game is as\n  important as knowing who will\n- **Market validation**: Are there successful games that serve a similar\n  player type? What can we learn from their audience size?\n\n---\n\n### Phase 6: Scope and Feasibility\n\nGround the concept in reality:\n\n- **Engine recommendation** (Godot \u002F Unity \u002F Unreal) with reasoning based\n  on concept needs, team expertise, and platform targets\n- **Art pipeline**: What's the art style and how labor-intensive is it?\n- **Content scope**: Estimate level\u002Farea count, item count, gameplay hours\n- **MVP definition**: What's the absolute minimum build that tests \"is the\n  core loop fun?\"\n- **Biggest risks**: Technical risks, design risks, market risks\n- **Scope tiers**: What's the full vision vs. what ships if time runs out?\n\n---\n\n4. **Generate the game concept document** using the template at\n   `.claude\u002Fdocs\u002Ftemplates\u002Fgame-concept.md`. Fill in ALL sections from the\n   brainstorm conversation, including the MDA analysis, player motivation\n   profile, and flow state design sections.\n\n5. **Save to** `design\u002Fgdd\u002Fgame-concept.md`, creating directories as needed.\n\n6. **Suggest next steps** (in this order — this is the professional studio\n   pre-production pipeline):\n   - \"Run `\u002Fsetup-engine [engine] [version]` to configure the engine and populate version-aware reference docs\"\n   - \"Use `\u002Fdesign-review design\u002Fgdd\u002Fgame-concept.md` to validate completeness\"\n   - \"Discuss vision with the `creative-director` agent for pillar refinement\"\n   - \"Decompose the concept into individual systems with `\u002Fmap-systems` — maps dependencies, assigns priorities, and creates the systems index\"\n   - \"Author per-system GDDs with `\u002Fdesign-system` — guided, section-by-section GDD writing\"\n   - \"Prototype the core loop with `\u002Fprototype [core-mechanic]`\"\n   - \"Playtest the prototype with `\u002Fplaytest-report` to validate the hypothesis\"\n   - \"If validated, plan the first sprint with `\u002Fsprint-plan new`\"\n\n7. **Output a summary** with the chosen concept's elevator pitch, pillars,\n   primary player type, engine recommendation, biggest risk, and file path.\n",{"name":5,"description":7,"allowed-tools":43,"argument-hint":44,"user-invocable":45},"Read, Glob, Grep, Write, WebSearch, AskUserQuestion","[genre or theme hint, or 'open' for fully open brainstorm]",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fbrainstorm",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":54,"prompt":64,"zipAvailable":45},[55,58,61],{"tool":56,"command":57},"npx","npx skills add welflau\u002Fai-dev-system --skill brainstorm",{"tool":59,"command":60},"bunx","bunx skills add welflau\u002Fai-dev-system --skill brainstorm",{"tool":62,"command":63},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill brainstorm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fbrainstorm\u002FSKILL.md",[],[67,101,130,156,186,210],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":83,"publishedAt":100},"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",[75,80],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000009","前端开发",[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,20],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","with","2026-11-11 15:11:14",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":111,"publishedAt":100},"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",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000005","邮件与沟通",[112,113,114,115,116,34,117,118,119,120,121,122,123,124,125,126,127,128,129],"internal comms","comms","status","help","SET","use","reports","me","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":38},"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",[137],{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},[139,90,140,141,142,87,143,144,145,146,147,148,149,150,117,151,152,153,154,20,155],"web artifacts builder","artifacts","artifacts builder","builder","css","components","react","routing","state management","state","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":172,"publishedAt":38},"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",[163,164,167],{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":165,"categoryName":166,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":168,"categoryName":169,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[87,173,174,143,90,144,145,175,176,177,140,178,96,179,117,180,181,182,183,99,184,185],"design","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":71,"licenseFileUrl":190,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":38},"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":165,"categoryName":166,"taxonomyType":78,"taxonomyTypeDesc":79},[195,196,197,176,177,198,199,200,201,117,202,31,203,204,99,205,206,207,208,209,185],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","systems","users","Existing","request","generative","copyright","fields",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":214,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":38},"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",[217],{"categoryNo":165,"categoryName":166,"taxonomyType":78,"taxonomyTypeDesc":79},[219,220,27,221,92,222,140,116,223,224,179,225,226,181,227,99,228,229,230,20,231,232],"theme factory","factory","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]