[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPZJ6B5WCPP496A82KYYCC":3,"skill-same:01M6HPZJ6B5WCPP496A82KYYCC":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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":65},"01M6HPZJ6B5WCPP496A82KYYCC","retrospective",null,"Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.","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\u002Fretrospective\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"git log","for","true","insights","actionable","sprint","name","iteration","velocity","next","patterns","log","write","read","work","grep","analyzing","dev","git","2026-11-10 10:12:30",false,"---\nname: retrospective\ndescription: \"Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.\"\nargument-hint: \"[sprint-N|milestone-name]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Write\ncontext: |\n  !git log --oneline --since=\"2 weeks ago\" 2>\u002Fdev\u002Fnull\n---\n\nWhen this skill is invoked:\n\n1. **Read the argument** to determine whether this is a sprint retrospective\n   (`sprint-N`) or a milestone retrospective (`milestone-name`).\n\n2. **Read the sprint or milestone plan** from the appropriate location:\n   - Sprint plans: `production\u002Fsprints\u002F`\n   - Milestone definitions: `production\u002Fmilestones\u002F`\n\n   Extract: planned tasks, estimated effort, owners, and goals.\n\n3. **Read the git log** for the period covered by the sprint or milestone to\n   understand what was actually committed and when.\n\n4. **Scan for completed and incomplete tasks** by comparing the plan against\n   actual deliverables. Check for:\n   - Tasks completed as planned\n   - Tasks completed but modified from the plan\n   - Tasks carried over (not completed)\n   - Tasks added mid-sprint (unplanned work)\n   - Tasks removed or descoped\n\n5. **Scan the codebase for TODO\u002FFIXME trends**:\n   - Count current TODO\u002FFIXME\u002FHACK comments\n   - Compare to previous sprint counts if available (check previous\n     retrospectives)\n   - Note whether technical debt is growing or shrinking\n\n6. **Read previous retrospectives** (if any) from `production\u002Fsprints\u002F` or\n   `production\u002Fmilestones\u002F` to check:\n   - Were previous action items addressed?\n   - Are the same problems recurring?\n   - How has velocity trended?\n\n7. **Generate the retrospective**:\n\n```markdown\n## Retrospective: [Sprint N \u002F Milestone Name]\nPeriod: [Start Date] -- [End Date]\nGenerated: [Date]\n\n### Metrics\n\n| Metric | Planned | Actual | Delta |\n|--------|---------|--------|-------|\n| Tasks | [X] | [Y] | [+\u002F- Z] |\n| Completion Rate | -- | [Z%] | -- |\n| Story Points \u002F Effort Days | [X] | [Y] | [+\u002F- Z] |\n| Bugs Found | -- | [N] | -- |\n| Bugs Fixed | -- | [N] | -- |\n| Unplanned Tasks Added | -- | [N] | -- |\n| Commits | -- | [N] | -- |\n\n### Velocity Trend\n\n| Sprint | Planned | Completed | Rate |\n|--------|---------|-----------|------|\n| [N-2] | [X] | [Y] | [Z%] |\n| [N-1] | [X] | [Y] | [Z%] |\n| [N] (current) | [X] | [Y] | [Z%] |\n\n**Trend**: [Increasing \u002F Stable \u002F Decreasing]\n[One sentence explaining the trend]\n\n### What Went Well\n- [Observation backed by specific data or examples]\n- [Another positive observation]\n- [Recognize specific contributions or decisions that paid off]\n\n### What Went Poorly\n- [Specific issue with measurable impact -- e.g., \"Feature X took 5 days\n  instead of estimated 2, blocking tasks Y and Z\"]\n- [Another issue with impact]\n- [Do not assign blame -- focus on systemic causes]\n\n### Blockers Encountered\n\n| Blocker | Duration | Resolution | Prevention |\n|---------|----------|------------|------------|\n| [What blocked progress] | [How long] | [How it was resolved] | [How to prevent recurrence] |\n\n### Estimation Accuracy\n\n| Task | Estimated | Actual | Variance | Likely Cause |\n|------|-----------|--------|----------|--------------|\n| [Most overestimated task] | [X] | [Y] | [+Z] | [Why] |\n| [Most underestimated task] | [X] | [Y] | [-Z] | [Why] |\n\n**Overall estimation accuracy**: [X%] of tasks within +\u002F- 20% of estimate\n\n[Analysis: Are we consistently over- or under-estimating? For which types of\ntasks? What adjustment should we apply?]\n\n### Carryover Analysis\n\n| Task | Original Sprint | Times Carried | Reason | Action |\n|------|----------------|---------------|--------|--------|\n| [Task that was not completed] | [Sprint N-X] | [N] | [Why] | [Complete \u002F Descope \u002F Redesign] |\n\n### Technical Debt Status\n- Current TODO count: [N] (previous: [N])\n- Current FIXME count: [N] (previous: [N])\n- Current HACK count: [N] (previous: [N])\n- Trend: [Growing \u002F Stable \u002F Shrinking]\n- [Note any areas of concern]\n\n### Previous Action Items Follow-Up\n\n| Action Item (from Sprint N-1) | Status | Notes |\n|-------------------------------|--------|-------|\n| [Previous action] | [Done \u002F In Progress \u002F Not Started] | [Context] |\n\n### Action Items for Next Iteration\n\n| # | Action | Owner | Priority | Deadline |\n|---|--------|-------|----------|----------|\n| 1 | [Specific, measurable action] | [Who] | [High\u002FMed\u002FLow] | [When] |\n| 2 | [Another action] | [Who] | [Priority] | [When] |\n\n### Process Improvements\n- [Specific change to how we work, with expected benefit]\n- [Another improvement -- keep it to 2-3 actionable items, not a wish list]\n\n### Summary\n[2-3 sentence overall assessment: Was this a good sprint\u002Fmilestone? What is\nthe single most important thing to change going forward?]\n```\n\n8. **Save the retrospective** to the appropriate location:\n   - Sprint: `production\u002Fsprints\u002Fsprint-[N]-retrospective.md`\n   - Milestone: `production\u002Fmilestones\u002F[milestone-name]-retrospective.md`\n\n   Create the directory if it does not exist.\n\n9. **Output a summary** to the user with: completion rate, velocity trend\n   direction, top blocker, and the most important action item.\n\n### Guidelines\n\n- Be honest and specific. Vague retrospectives (\"communication could be\n  better\") produce vague improvements. Use data and examples.\n- Focus on systemic issues, not individual blame.\n- Limit action items to 3-5. More than that dilutes focus.\n- Every action item must have an owner and a deadline.\n- Check whether previous action items were completed. Recurring unaddressed\n  items are a process smell.\n- If this is a milestone retrospective, also evaluate whether the milestone\n  goals were achieved and what that means for the overall project timeline.\n","When this skill is invoked:\n\n1. **Read the argument** to determine whether this is a sprint retrospective\n   (`sprint-N`) or a milestone retrospective (`milestone-name`).\n\n2. **Read the sprint or milestone plan** from the appropriate location:\n   - Sprint plans: `production\u002Fsprints\u002F`\n   - Milestone definitions: `production\u002Fmilestones\u002F`\n\n   Extract: planned tasks, estimated effort, owners, and goals.\n\n3. **Read the git log** for the period covered by the sprint or milestone to\n   understand what was actually committed and when.\n\n4. **Scan for completed and incomplete tasks** by comparing the plan against\n   actual deliverables. Check for:\n   - Tasks completed as planned\n   - Tasks completed but modified from the plan\n   - Tasks carried over (not completed)\n   - Tasks added mid-sprint (unplanned work)\n   - Tasks removed or descoped\n\n5. **Scan the codebase for TODO\u002FFIXME trends**:\n   - Count current TODO\u002FFIXME\u002FHACK comments\n   - Compare to previous sprint counts if available (check previous\n     retrospectives)\n   - Note whether technical debt is growing or shrinking\n\n6. **Read previous retrospectives** (if any) from `production\u002Fsprints\u002F` or\n   `production\u002Fmilestones\u002F` to check:\n   - Were previous action items addressed?\n   - Are the same problems recurring?\n   - How has velocity trended?\n\n7. **Generate the retrospective**:\n\n```markdown\n## Retrospective: [Sprint N \u002F Milestone Name]\nPeriod: [Start Date] -- [End Date]\nGenerated: [Date]\n\n### Metrics\n\n| Metric | Planned | Actual | Delta |\n|--------|---------|--------|-------|\n| Tasks | [X] | [Y] | [+\u002F- Z] |\n| Completion Rate | -- | [Z%] | -- |\n| Story Points \u002F Effort Days | [X] | [Y] | [+\u002F- Z] |\n| Bugs Found | -- | [N] | -- |\n| Bugs Fixed | -- | [N] | -- |\n| Unplanned Tasks Added | -- | [N] | -- |\n| Commits | -- | [N] | -- |\n\n### Velocity Trend\n\n| Sprint | Planned | Completed | Rate |\n|--------|---------|-----------|------|\n| [N-2] | [X] | [Y] | [Z%] |\n| [N-1] | [X] | [Y] | [Z%] |\n| [N] (current) | [X] | [Y] | [Z%] |\n\n**Trend**: [Increasing \u002F Stable \u002F Decreasing]\n[One sentence explaining the trend]\n\n### What Went Well\n- [Observation backed by specific data or examples]\n- [Another positive observation]\n- [Recognize specific contributions or decisions that paid off]\n\n### What Went Poorly\n- [Specific issue with measurable impact -- e.g., \"Feature X took 5 days\n  instead of estimated 2, blocking tasks Y and Z\"]\n- [Another issue with impact]\n- [Do not assign blame -- focus on systemic causes]\n\n### Blockers Encountered\n\n| Blocker | Duration | Resolution | Prevention |\n|---------|----------|------------|------------|\n| [What blocked progress] | [How long] | [How it was resolved] | [How to prevent recurrence] |\n\n### Estimation Accuracy\n\n| Task | Estimated | Actual | Variance | Likely Cause |\n|------|-----------|--------|----------|--------------|\n| [Most overestimated task] | [X] | [Y] | [+Z] | [Why] |\n| [Most underestimated task] | [X] | [Y] | [-Z] | [Why] |\n\n**Overall estimation accuracy**: [X%] of tasks within +\u002F- 20% of estimate\n\n[Analysis: Are we consistently over- or under-estimating? For which types of\ntasks? What adjustment should we apply?]\n\n### Carryover Analysis\n\n| Task | Original Sprint | Times Carried | Reason | Action |\n|------|----------------|---------------|--------|--------|\n| [Task that was not completed] | [Sprint N-X] | [N] | [Why] | [Complete \u002F Descope \u002F Redesign] |\n\n### Technical Debt Status\n- Current TODO count: [N] (previous: [N])\n- Current FIXME count: [N] (previous: [N])\n- Current HACK count: [N] (previous: [N])\n- Trend: [Growing \u002F Stable \u002F Shrinking]\n- [Note any areas of concern]\n\n### Previous Action Items Follow-Up\n\n| Action Item (from Sprint N-1) | Status | Notes |\n|-------------------------------|--------|-------|\n| [Previous action] | [Done \u002F In Progress \u002F Not Started] | [Context] |\n\n### Action Items for Next Iteration\n\n| # | Action | Owner | Priority | Deadline |\n|---|--------|-------|----------|----------|\n| 1 | [Specific, measurable action] | [Who] | [High\u002FMed\u002FLow] | [When] |\n| 2 | [Another action] | [Who] | [Priority] | [When] |\n\n### Process Improvements\n- [Specific change to how we work, with expected benefit]\n- [Another improvement -- keep it to 2-3 actionable items, not a wish list]\n\n### Summary\n[2-3 sentence overall assessment: Was this a good sprint\u002Fmilestone? What is\nthe single most important thing to change going forward?]\n```\n\n8. **Save the retrospective** to the appropriate location:\n   - Sprint: `production\u002Fsprints\u002Fsprint-[N]-retrospective.md`\n   - Milestone: `production\u002Fmilestones\u002F[milestone-name]-retrospective.md`\n\n   Create the directory if it does not exist.\n\n9. **Output a summary** to the user with: completion rate, velocity trend\n   direction, top blocker, and the most important action item.\n\n### Guidelines\n\n- Be honest and specific. Vague retrospectives (\"communication could be\n  better\") produce vague improvements. Use data and examples.\n- Focus on systemic issues, not individual blame.\n- Limit action items to 3-5. More than that dilutes focus.\n- Every action item must have an owner and a deadline.\n- Check whether previous action items were completed. Recurring unaddressed\n  items are a process smell.\n- If this is a milestone retrospective, also evaluate whether the milestone\n  goals were achieved and what that means for the overall project timeline.\n",{"name":5,"context":42,"description":7,"allowed-tools":43,"argument-hint":44,"user-invocable":45},"!git log --oneline --since=\"2 weeks ago\" 2>\u002Fdev\u002Fnull","Read, Glob, Grep, Write","[sprint-N|milestone-name]",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fretrospective",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 retrospective",{"tool":59,"command":60},"bunx","bunx skills add welflau\u002Fai-dev-system --skill retrospective",{"tool":62,"command":63},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill retrospective","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fretrospective\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,19],"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,30,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":37},"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,19,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":37},"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":37},"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,32,200,117,201,202,203,204,99,205,206,207,208,209,185],"algorithmic art","Art","algorithmic","flow","js","interactive","generative art","exploration","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":37},"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,221,222,92,223,140,116,224,225,179,226,227,181,228,99,229,230,231,19,232,233],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]