[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPZ6SYJ543CJ9SRMXK2AS9":3,"skill-same:01M6HPZ6SYJ543CJ9SRMXK2AS9":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},"01M6HPZ6SYJ543CJ9SRMXK2AS9","project-stage-detect",null,"Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.","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\u002Fproject-stage-detect\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"project stage detect","detect","project","stage","gaps","artifacts","Existing","recommend","role","true","next steps","filter","next","analyze project","read","grep","analyze","designer","Bash","state","2026-11-10 10:12:30",false,"---\nname: project-stage-detect\ndescription: \"Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.\"\nargument-hint: \"[optional: role filter like 'programmer' or 'designer']\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Bash\n---\n\n# Project Stage Detection\n\nThis skill scans your project to determine its current development stage, completeness\nof artifacts, and gaps that need attention. It's especially useful when:\n- Starting with an existing project\n- Onboarding to a codebase\n- Checking what's missing before a milestone\n- Understanding \"where are we?\"\n\n---\n\n## Workflow\n\n### 1. Scan Key Directories\n\nAnalyze project structure and content:\n\n**Design Documentation** (`design\u002F`):\n- Count GDD files in `design\u002Fgdd\u002F*.md`\n- Check for game-concept.md, game-pillars.md, systems-index.md\n- If systems-index.md exists, count total systems vs. designed systems\n- Analyze completeness (Overview, Detailed Design, Edge Cases, etc.)\n- Count narrative docs in `design\u002Fnarrative\u002F`\n- Count level designs in `design\u002Flevels\u002F`\n\n**Source Code** (`src\u002F`):\n- Count source files (language-agnostic)\n- Identify major systems (directories with 5+ files)\n- Check for core\u002F, gameplay\u002F, ai\u002F, networking\u002F, ui\u002F directories\n- Estimate lines of code (rough scale)\n\n**Production Artifacts** (`production\u002F`):\n- Check for active sprint plans\n- Look for milestone definitions\n- Find roadmap documents\n\n**Prototypes** (`prototypes\u002F`):\n- Count prototype directories\n- Check for READMEs (documented vs undocumented)\n- Assess if prototypes are archived or active\n\n**Architecture Docs** (`docs\u002Farchitecture\u002F`):\n- Count ADRs (Architecture Decision Records)\n- Check for overview\u002Findex documents\n\n**Tests** (`tests\u002F`):\n- Count test files\n- Estimate test coverage (rough heuristic)\n\n### 2. Classify Project Stage\n\nBased on scanned artifacts, determine stage. Check `production\u002Fstage.txt` first —\nif it exists, use its value (explicit override from `\u002Fgate-check`). Otherwise,\nauto-detect using these heuristics (check from most-advanced backward):\n\n| Stage | Indicators |\n|-------|-----------|\n| **Concept** | No game concept doc, brainstorming phase |\n| **Systems Design** | Game concept exists, systems index missing or incomplete |\n| **Technical Setup** | Systems index exists, engine not configured |\n| **Pre-Production** | Engine configured, `src\u002F` has \u003C10 source files |\n| **Production** | `src\u002F` has 10+ source files, active development |\n| **Polish** | Explicit only (set by `\u002Fgate-check` Production → Polish gate) |\n| **Release** | Explicit only (set by `\u002Fgate-check` Polish → Release gate) |\n\n### 3. Collaborative Gap Identification\n\n**DO NOT** just list missing files. Instead, **ask clarifying questions**:\n\n- \"I see combat code (`src\u002Fgameplay\u002Fcombat\u002F`) but no `design\u002Fgdd\u002Fcombat-system.md`. Was this prototyped first, or should we reverse-document?\"\n- \"You have 15 ADRs but no architecture overview. Should I create one to help new contributors?\"\n- \"No sprint plans in `production\u002F`. Are you tracking work elsewhere (Jira, Trello, etc.)?\"\n- \"I found a game concept but no systems index. Have you decomposed the concept into individual systems yet, or should we run `\u002Fmap-systems`?\"\n- \"Prototypes directory has 3 projects with no READMEs. Were these experiments, or do they need documentation?\"\n\n### 4. Generate Stage Report\n\nUse template: `.claude\u002Fdocs\u002Ftemplates\u002Fproject-stage-report.md`\n\n**Report structure**:\n```markdown\n# Project Stage Analysis\n\n**Date**: [date]\n**Stage**: [Concept\u002FSystems Design\u002FTechnical Setup\u002FPre-Production\u002FProduction\u002FPolish\u002FRelease]\n\n## Completeness Overview\n- Design: [X%] ([N] docs, [gaps])\n- Code: [X%] ([N] files, [systems])\n- Architecture: [X%] ([N] ADRs, [gaps])\n- Production: [X%] ([status])\n- Tests: [X%] ([coverage estimate])\n\n## Gaps Identified\n1. [Gap description + clarifying question]\n2. [Gap description + clarifying question]\n\n## Recommended Next Steps\n[Priority-ordered list based on stage and role]\n```\n\n### 5. Role-Filtered Recommendations (Optional)\n\nIf user provided a role argument (e.g., `\u002Fproject-stage-detect programmer`):\n\n**Programmer**:\n- Focus on architecture docs, test coverage, missing ADRs\n- Code-to-docs gaps\n\n**Designer**:\n- Focus on GDD completeness, missing design sections\n- Prototype documentation\n\n**Producer**:\n- Focus on sprint plans, milestone tracking, roadmap\n- Cross-team coordination docs\n\n**General** (no role):\n- Holistic view of all gaps\n- Highest-priority items across domains\n\n### 6. Request Approval Before Writing\n\n**Collaborative protocol**:\n```\nI've analyzed your project. Here's what I found:\n\n[Show summary]\n\nGaps identified:\n1. [Gap 1 + question]\n2. [Gap 2 + question]\n\nRecommended next steps:\n- [Priority 1]\n- [Priority 2]\n- [Priority 3]\n\nMay I write the full stage analysis to production\u002Fproject-stage-report.md?\n```\n\nWait for user approval before creating the file.\n\n---\n\n## Example Usage\n\n```bash\n# General project analysis\n\u002Fproject-stage-detect\n\n# Programmer-focused analysis\n\u002Fproject-stage-detect programmer\n\n# Designer-focused analysis\n\u002Fproject-stage-detect designer\n```\n\n---\n\n## Follow-Up Actions\n\nAfter generating the report, suggest relevant next steps:\n\n- **Concept exists but no systems index?** → `\u002Fmap-systems` to decompose into systems\n- **Missing design docs?** → `\u002Freverse-document design src\u002F[system]`\n- **Missing architecture docs?** → `\u002Farchitecture-decision` or `\u002Freverse-document architecture`\n- **Prototypes need documentation?** → `\u002Freverse-document concept prototypes\u002F[name]`\n- **No sprint plan?** → `\u002Fsprint-plan`\n- **Approaching milestone?** → `\u002Fmilestone-review`\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Question First**: Ask about gaps, don't assume\n2. **Present Options**: \"Should I create X, or is it tracked elsewhere?\"\n3. **User Decides**: Wait for direction\n4. **Show Draft**: Display report summary\n5. **Get Approval**: \"May I write to production\u002Fproject-stage-report.md?\"\n\n**Never** silently write files. **Always** show findings and ask before creating artifacts.\n","# Project Stage Detection\n\nThis skill scans your project to determine its current development stage, completeness\nof artifacts, and gaps that need attention. It's especially useful when:\n- Starting with an existing project\n- Onboarding to a codebase\n- Checking what's missing before a milestone\n- Understanding \"where are we?\"\n\n---\n\n## Workflow\n\n### 1. Scan Key Directories\n\nAnalyze project structure and content:\n\n**Design Documentation** (`design\u002F`):\n- Count GDD files in `design\u002Fgdd\u002F*.md`\n- Check for game-concept.md, game-pillars.md, systems-index.md\n- If systems-index.md exists, count total systems vs. designed systems\n- Analyze completeness (Overview, Detailed Design, Edge Cases, etc.)\n- Count narrative docs in `design\u002Fnarrative\u002F`\n- Count level designs in `design\u002Flevels\u002F`\n\n**Source Code** (`src\u002F`):\n- Count source files (language-agnostic)\n- Identify major systems (directories with 5+ files)\n- Check for core\u002F, gameplay\u002F, ai\u002F, networking\u002F, ui\u002F directories\n- Estimate lines of code (rough scale)\n\n**Production Artifacts** (`production\u002F`):\n- Check for active sprint plans\n- Look for milestone definitions\n- Find roadmap documents\n\n**Prototypes** (`prototypes\u002F`):\n- Count prototype directories\n- Check for READMEs (documented vs undocumented)\n- Assess if prototypes are archived or active\n\n**Architecture Docs** (`docs\u002Farchitecture\u002F`):\n- Count ADRs (Architecture Decision Records)\n- Check for overview\u002Findex documents\n\n**Tests** (`tests\u002F`):\n- Count test files\n- Estimate test coverage (rough heuristic)\n\n### 2. Classify Project Stage\n\nBased on scanned artifacts, determine stage. Check `production\u002Fstage.txt` first —\nif it exists, use its value (explicit override from `\u002Fgate-check`). Otherwise,\nauto-detect using these heuristics (check from most-advanced backward):\n\n| Stage | Indicators |\n|-------|-----------|\n| **Concept** | No game concept doc, brainstorming phase |\n| **Systems Design** | Game concept exists, systems index missing or incomplete |\n| **Technical Setup** | Systems index exists, engine not configured |\n| **Pre-Production** | Engine configured, `src\u002F` has \u003C10 source files |\n| **Production** | `src\u002F` has 10+ source files, active development |\n| **Polish** | Explicit only (set by `\u002Fgate-check` Production → Polish gate) |\n| **Release** | Explicit only (set by `\u002Fgate-check` Polish → Release gate) |\n\n### 3. Collaborative Gap Identification\n\n**DO NOT** just list missing files. Instead, **ask clarifying questions**:\n\n- \"I see combat code (`src\u002Fgameplay\u002Fcombat\u002F`) but no `design\u002Fgdd\u002Fcombat-system.md`. Was this prototyped first, or should we reverse-document?\"\n- \"You have 15 ADRs but no architecture overview. Should I create one to help new contributors?\"\n- \"No sprint plans in `production\u002F`. Are you tracking work elsewhere (Jira, Trello, etc.)?\"\n- \"I found a game concept but no systems index. Have you decomposed the concept into individual systems yet, or should we run `\u002Fmap-systems`?\"\n- \"Prototypes directory has 3 projects with no READMEs. Were these experiments, or do they need documentation?\"\n\n### 4. Generate Stage Report\n\nUse template: `.claude\u002Fdocs\u002Ftemplates\u002Fproject-stage-report.md`\n\n**Report structure**:\n```markdown\n# Project Stage Analysis\n\n**Date**: [date]\n**Stage**: [Concept\u002FSystems Design\u002FTechnical Setup\u002FPre-Production\u002FProduction\u002FPolish\u002FRelease]\n\n## Completeness Overview\n- Design: [X%] ([N] docs, [gaps])\n- Code: [X%] ([N] files, [systems])\n- Architecture: [X%] ([N] ADRs, [gaps])\n- Production: [X%] ([status])\n- Tests: [X%] ([coverage estimate])\n\n## Gaps Identified\n1. [Gap description + clarifying question]\n2. [Gap description + clarifying question]\n\n## Recommended Next Steps\n[Priority-ordered list based on stage and role]\n```\n\n### 5. Role-Filtered Recommendations (Optional)\n\nIf user provided a role argument (e.g., `\u002Fproject-stage-detect programmer`):\n\n**Programmer**:\n- Focus on architecture docs, test coverage, missing ADRs\n- Code-to-docs gaps\n\n**Designer**:\n- Focus on GDD completeness, missing design sections\n- Prototype documentation\n\n**Producer**:\n- Focus on sprint plans, milestone tracking, roadmap\n- Cross-team coordination docs\n\n**General** (no role):\n- Holistic view of all gaps\n- Highest-priority items across domains\n\n### 6. Request Approval Before Writing\n\n**Collaborative protocol**:\n```\nI've analyzed your project. Here's what I found:\n\n[Show summary]\n\nGaps identified:\n1. [Gap 1 + question]\n2. [Gap 2 + question]\n\nRecommended next steps:\n- [Priority 1]\n- [Priority 2]\n- [Priority 3]\n\nMay I write the full stage analysis to production\u002Fproject-stage-report.md?\n```\n\nWait for user approval before creating the file.\n\n---\n\n## Example Usage\n\n```bash\n# General project analysis\n\u002Fproject-stage-detect\n\n# Programmer-focused analysis\n\u002Fproject-stage-detect programmer\n\n# Designer-focused analysis\n\u002Fproject-stage-detect designer\n```\n\n---\n\n## Follow-Up Actions\n\nAfter generating the report, suggest relevant next steps:\n\n- **Concept exists but no systems index?** → `\u002Fmap-systems` to decompose into systems\n- **Missing design docs?** → `\u002Freverse-document design src\u002F[system]`\n- **Missing architecture docs?** → `\u002Farchitecture-decision` or `\u002Freverse-document architecture`\n- **Prototypes need documentation?** → `\u002Freverse-document concept prototypes\u002F[name]`\n- **No sprint plan?** → `\u002Fsprint-plan`\n- **Approaching milestone?** → `\u002Fmilestone-review`\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Question First**: Ask about gaps, don't assume\n2. **Present Options**: \"Should I create X, or is it tracked elsewhere?\"\n3. **User Decides**: Wait for direction\n4. **Show Draft**: Display report summary\n5. **Get Approval**: \"May I write to production\u002Fproject-stage-report.md?\"\n\n**Never** silently write files. **Always** show findings and ask before creating artifacts.\n",{"name":5,"description":7,"allowed-tools":43,"argument-hint":44,"user-invocable":45},"Read, Glob, Grep, Bash","[optional: role filter like 'programmer' or 'designer']",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fproject-stage-detect",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 project-stage-detect",{"tool":59,"command":60},"bunx","bunx skills add welflau\u002Fai-dev-system --skill project-stage-detect",{"tool":62,"command":63},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill project-stage-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fproject-stage-detect\u002FSKILL.md",[],[67,102,131,155,185,209],{"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":101},"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,100],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","with","for","2026-11-11 15:11:14",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":112,"publishedAt":101},"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",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000005","邮件与沟通",[113,114,115,116,117,118,119,120,121,122,123,20,124,125,126,127,128,129,130],"internal comms","comms","status","help","SET","write","use","reports","me","incident","leadership","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":139,"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",[138],{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},[140,90,23,141,142,87,143,144,145,146,147,37,148,149,119,150,151,152,153,100,154],"web artifacts builder","artifacts builder","builder","css","components","react","routing","state management","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":171,"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",[162,163,166],{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":164,"categoryName":165,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[87,172,173,143,90,144,145,174,175,176,23,177,96,178,119,179,180,181,182,99,183,184],"design","frontend design","react components","create","code","examples","landing","ui design","pages","aesthetics","web ui","generic","when",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":193,"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",[192],{"categoryNo":164,"categoryName":165,"taxonomyType":78,"taxonomyTypeDesc":79},[194,195,196,175,176,197,198,199,200,119,201,202,203,204,99,24,205,206,207,208,184],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","systems","users","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":71,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":217,"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",[216],{"categoryNo":164,"categoryName":165,"taxonomyType":78,"taxonomyTypeDesc":79},[218,219,220,221,92,222,23,117,223,224,178,225,226,180,227,99,228,229,230,100,231,232],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]