[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HR4NP760C4V0N2JXHDP1MS":3,"skill-same:01M6HR4NP760C4V0N2JXHDP1MS":69},{"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":22,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6HR4NP760C4V0N2JXHDP1MS","context-driven-development",null,"Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.","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\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fconductor\u002Fskills\u002Fcontext-driven-development\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"development","driven","context driven development","context","methodology","stack","product","use","files","artifacts","project context","relationship","project","workflow","conductor","tech","with","tech-stack","when","2026-11-10 10:12:30",false,"---\nname: context-driven-development\ndescription: Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.\nversion: 1.0.0\n---\n\n# Context-Driven Development\n\nGuide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.\n\n## When to Use This Skill\n\n- Setting up new projects with Conductor\n- Understanding the relationship between context artifacts\n- Maintaining consistency across AI-assisted development sessions\n- Onboarding team members to an existing Conductor project\n- Deciding when to update context documents\n- Managing greenfield vs brownfield project contexts\n\n## Core Philosophy\n\nContext-Driven Development treats project context as a first-class artifact managed alongside code. Instead of relying on ad-hoc prompts or scattered documentation, establish a persistent, structured foundation that informs all AI interactions.\n\nKey principles:\n\n1. **Context precedes code**: Define what you're building and how before implementation\n2. **Living documentation**: Context artifacts evolve with the project\n3. **Single source of truth**: One canonical location for each type of information\n4. **AI alignment**: Consistent context produces consistent AI behavior\n\n## The Workflow\n\nFollow the **Context → Spec & Plan → Implement** workflow:\n\n1. **Context Phase**: Establish or verify project context artifacts exist and are current\n2. **Specification Phase**: Define requirements and acceptance criteria for work units\n3. **Planning Phase**: Break specifications into phased, actionable tasks\n4. **Implementation Phase**: Execute tasks following established workflow patterns\n\n## Artifact Relationships\n\n### product.md - Defines WHAT and WHY\n\nPurpose: Captures product vision, goals, target users, and business context.\n\nContents:\n\n- Product name and one-line description\n- Problem statement and solution approach\n- Target user personas\n- Core features and capabilities\n- Success metrics and KPIs\n- Product roadmap (high-level)\n\nUpdate when:\n\n- Product vision or goals change\n- New major features are planned\n- Target audience shifts\n- Business priorities evolve\n\n### product-guidelines.md - Defines HOW to Communicate\n\nPurpose: Establishes brand voice, messaging standards, and communication patterns.\n\nContents:\n\n- Brand voice and tone guidelines\n- Terminology and glossary\n- Error message conventions\n- User-facing copy standards\n- Documentation style\n\nUpdate when:\n\n- Brand guidelines change\n- New terminology is introduced\n- Communication patterns need refinement\n\n### tech-stack.md - Defines WITH WHAT\n\nPurpose: Documents technology choices, dependencies, and architectural decisions.\n\nContents:\n\n- Primary languages and frameworks\n- Key dependencies with versions\n- Infrastructure and deployment targets\n- Development tools and environment\n- Testing frameworks\n- Code quality tools\n\nUpdate when:\n\n- Adding new dependencies\n- Upgrading major versions\n- Changing infrastructure\n- Adopting new tools or patterns\n\n### workflow.md - Defines HOW to Work\n\nPurpose: Establishes development practices, quality gates, and team workflows.\n\nContents:\n\n- Development methodology (TDD, etc.)\n- Git workflow and commit conventions\n- Code review requirements\n- Testing requirements and coverage targets\n- Quality assurance gates\n- Deployment procedures\n\nUpdate when:\n\n- Team practices evolve\n- Quality standards change\n- New workflow patterns are adopted\n\n### tracks.md - Tracks WHAT'S HAPPENING\n\nPurpose: Registry of all work units with status and metadata.\n\nContents:\n\n- Active tracks with current status\n- Completed tracks with completion dates\n- Track metadata (type, priority, assignee)\n- Links to individual track directories\n\nUpdate when:\n\n- New tracks are created\n- Track status changes\n- Tracks are completed or archived\n\n## Context Maintenance Principles\n\n### Keep Artifacts Synchronized\n\nEnsure changes in one artifact reflect in related documents:\n\n- New feature in product.md → Update tech-stack.md if new dependencies needed\n- Completed track → Update product.md to reflect new capabilities\n- Workflow change → Update all affected track plans\n\n### Update tech-stack.md When Adding Dependencies\n\nBefore adding any new dependency:\n\n1. Check if existing dependencies solve the need\n2. Document the rationale for new dependencies\n3. Add version constraints\n4. Note any configuration requirements\n\n### Update product.md When Features Complete\n\nAfter completing a feature track:\n\n1. Move feature from \"planned\" to \"implemented\" in product.md\n2. Update any affected success metrics\n3. Document any scope changes from original plan\n\n### Verify Context Before Implementation\n\nBefore starting any track:\n\n1. Read all context artifacts\n2. Flag any outdated information\n3. Propose updates before proceeding\n4. Confirm context accuracy with stakeholders\n\n## Greenfield vs Brownfield Handling\n\n### Greenfield Projects (New)\n\nFor new projects:\n\n1. Run `\u002Fconductor:setup` to create all artifacts interactively\n2. Answer questions about product vision, tech preferences, and workflow\n3. Generate initial style guides for chosen languages\n4. Create empty tracks registry\n\nCharacteristics:\n\n- Full control over context structure\n- Define standards before code exists\n- Establish patterns early\n\n### Brownfield Projects (Existing)\n\nFor existing codebases:\n\n1. Run `\u002Fconductor:setup` with existing codebase detection\n2. System analyzes existing code, configs, and documentation\n3. Pre-populate artifacts based on discovered patterns\n4. Review and refine generated context\n\nCharacteristics:\n\n- Extract implicit context from existing code\n- Reconcile existing patterns with desired patterns\n- Document technical debt and modernization plans\n- Preserve working patterns while establishing standards\n\n## Benefits\n\n### Team Alignment\n\n- New team members onboard faster with explicit context\n- Consistent terminology and conventions across the team\n- Shared understanding of product goals and technical decisions\n\n### AI Consistency\n\n- AI assistants produce aligned outputs across sessions\n- Reduced need to re-explain context in each interaction\n- Predictable behavior based on documented standards\n\n### Institutional Memory\n\n- Decisions and rationale are preserved\n- Context survives team changes\n- Historical context informs future decisions\n\n### Quality Assurance\n\n- Standards are explicit and verifiable\n- Deviations from context are detectable\n- Quality gates are documented and enforceable\n\n## Directory Structure\n\n```\nconductor\u002F\n├── index.md              # Navigation hub linking all artifacts\n├── product.md            # Product vision and goals\n├── product-guidelines.md # Communication standards\n├── tech-stack.md         # Technology preferences\n├── workflow.md           # Development practices\n├── tracks.md             # Work unit registry\n├── setup_state.json      # Resumable setup state\n├── code_styleguides\u002F     # Language-specific conventions\n│   ├── python.md\n│   ├── typescript.md\n│   └── ...\n└── tracks\u002F\n    └── \u003Ctrack-id>\u002F\n        ├── spec.md\n        ├── plan.md\n        ├── metadata.json\n        └── index.md\n```\n\n## Context Lifecycle\n\n1. **Creation**: Initial setup via `\u002Fconductor:setup`\n2. **Validation**: Verify before each track\n3. **Evolution**: Update as project grows\n4. **Synchronization**: Keep artifacts aligned\n5. **Archival**: Document historical decisions\n\n## Context Validation Checklist\n\nBefore starting implementation on any track, validate context:\n\n### Product Context\n\n- [ ] product.md reflects current product vision\n- [ ] Target users are accurately described\n- [ ] Feature list is up to date\n- [ ] Success metrics are defined\n\n### Technical Context\n\n- [ ] tech-stack.md lists all current dependencies\n- [ ] Version numbers are accurate\n- [ ] Infrastructure targets are correct\n- [ ] Development tools are documented\n\n### Workflow Context\n\n- [ ] workflow.md describes current practices\n- [ ] Quality gates are defined\n- [ ] Coverage targets are specified\n- [ ] Commit conventions are documented\n\n### Track Context\n\n- [ ] tracks.md shows all active work\n- [ ] No stale or abandoned tracks\n- [ ] Dependencies between tracks are noted\n\n## Common Anti-Patterns\n\nAvoid these context management mistakes:\n\n### Stale Context\n\nProblem: Context documents become outdated and misleading.\nSolution: Update context as part of each track's completion process.\n\n### Context Sprawl\n\nProblem: Information scattered across multiple locations.\nSolution: Use the defined artifact structure; resist creating new document types.\n\n### Implicit Context\n\nProblem: Relying on knowledge not captured in artifacts.\nSolution: If you reference something repeatedly, add it to the appropriate artifact.\n\n### Context Hoarding\n\nProblem: One person maintains context without team input.\nSolution: Review context artifacts in pull requests; make updates collaborative.\n\n### Over-Specification\n\nProblem: Context becomes so detailed it's impossible to maintain.\nSolution: Keep artifacts focused on decisions that affect AI behavior and team alignment.\n\n## Integration with Development Tools\n\n### IDE Integration\n\nConfigure your IDE to display context files prominently:\n\n- Pin conductor\u002Fproduct.md for quick reference\n- Add tech-stack.md to project notes\n- Create snippets for common patterns from style guides\n\n### Git Hooks\n\nConsider pre-commit hooks that:\n\n- Warn when dependencies change without tech-stack.md update\n- Remind to update product.md when feature branches merge\n- Validate context artifact syntax\n\n### CI\u002FCD Integration\n\nInclude context validation in pipelines:\n\n- Check tech-stack.md matches actual dependencies\n- Verify links in context documents resolve\n- Ensure tracks.md status matches git branch state\n\n## Session Continuity\n\nConductor supports multi-session development through context persistence:\n\n### Starting a New Session\n\n1. Read index.md to orient yourself\n2. Check tracks.md for active work\n3. Review relevant track's plan.md for current task\n4. Verify context artifacts are current\n\n### Ending a Session\n\n1. Update plan.md with current progress\n2. Note any blockers or decisions made\n3. Commit in-progress work with clear status\n4. Update tracks.md if status changed\n\n### Handling Interruptions\n\nIf interrupted mid-task:\n\n1. Mark task as `[~]` with note about stopping point\n2. Commit work-in-progress to feature branch\n3. Document any uncommitted decisions in plan.md\n\n## Best Practices\n\n1. **Read context first**: Always read relevant artifacts before starting work\n2. **Small updates**: Make incremental context changes, not massive rewrites\n3. **Link decisions**: Reference context when making implementation choices\n4. **Version context**: Commit context changes alongside code changes\n5. **Review context**: Include context artifact reviews in code reviews\n6. **Validate regularly**: Run context validation checklist before major work\n7. **Communicate changes**: Notify team when context artifacts change significantly\n8. **Preserve history**: Use git to track context evolution over time\n9. **Question staleness**: If context feels wrong, investigate and update\n10. **Keep it actionable**: Every context item should inform a decision or behavior\n","# Context-Driven Development\n\nGuide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.\n\n## When to Use This Skill\n\n- Setting up new projects with Conductor\n- Understanding the relationship between context artifacts\n- Maintaining consistency across AI-assisted development sessions\n- Onboarding team members to an existing Conductor project\n- Deciding when to update context documents\n- Managing greenfield vs brownfield project contexts\n\n## Core Philosophy\n\nContext-Driven Development treats project context as a first-class artifact managed alongside code. Instead of relying on ad-hoc prompts or scattered documentation, establish a persistent, structured foundation that informs all AI interactions.\n\nKey principles:\n\n1. **Context precedes code**: Define what you're building and how before implementation\n2. **Living documentation**: Context artifacts evolve with the project\n3. **Single source of truth**: One canonical location for each type of information\n4. **AI alignment**: Consistent context produces consistent AI behavior\n\n## The Workflow\n\nFollow the **Context → Spec & Plan → Implement** workflow:\n\n1. **Context Phase**: Establish or verify project context artifacts exist and are current\n2. **Specification Phase**: Define requirements and acceptance criteria for work units\n3. **Planning Phase**: Break specifications into phased, actionable tasks\n4. **Implementation Phase**: Execute tasks following established workflow patterns\n\n## Artifact Relationships\n\n### product.md - Defines WHAT and WHY\n\nPurpose: Captures product vision, goals, target users, and business context.\n\nContents:\n\n- Product name and one-line description\n- Problem statement and solution approach\n- Target user personas\n- Core features and capabilities\n- Success metrics and KPIs\n- Product roadmap (high-level)\n\nUpdate when:\n\n- Product vision or goals change\n- New major features are planned\n- Target audience shifts\n- Business priorities evolve\n\n### product-guidelines.md - Defines HOW to Communicate\n\nPurpose: Establishes brand voice, messaging standards, and communication patterns.\n\nContents:\n\n- Brand voice and tone guidelines\n- Terminology and glossary\n- Error message conventions\n- User-facing copy standards\n- Documentation style\n\nUpdate when:\n\n- Brand guidelines change\n- New terminology is introduced\n- Communication patterns need refinement\n\n### tech-stack.md - Defines WITH WHAT\n\nPurpose: Documents technology choices, dependencies, and architectural decisions.\n\nContents:\n\n- Primary languages and frameworks\n- Key dependencies with versions\n- Infrastructure and deployment targets\n- Development tools and environment\n- Testing frameworks\n- Code quality tools\n\nUpdate when:\n\n- Adding new dependencies\n- Upgrading major versions\n- Changing infrastructure\n- Adopting new tools or patterns\n\n### workflow.md - Defines HOW to Work\n\nPurpose: Establishes development practices, quality gates, and team workflows.\n\nContents:\n\n- Development methodology (TDD, etc.)\n- Git workflow and commit conventions\n- Code review requirements\n- Testing requirements and coverage targets\n- Quality assurance gates\n- Deployment procedures\n\nUpdate when:\n\n- Team practices evolve\n- Quality standards change\n- New workflow patterns are adopted\n\n### tracks.md - Tracks WHAT'S HAPPENING\n\nPurpose: Registry of all work units with status and metadata.\n\nContents:\n\n- Active tracks with current status\n- Completed tracks with completion dates\n- Track metadata (type, priority, assignee)\n- Links to individual track directories\n\nUpdate when:\n\n- New tracks are created\n- Track status changes\n- Tracks are completed or archived\n\n## Context Maintenance Principles\n\n### Keep Artifacts Synchronized\n\nEnsure changes in one artifact reflect in related documents:\n\n- New feature in product.md → Update tech-stack.md if new dependencies needed\n- Completed track → Update product.md to reflect new capabilities\n- Workflow change → Update all affected track plans\n\n### Update tech-stack.md When Adding Dependencies\n\nBefore adding any new dependency:\n\n1. Check if existing dependencies solve the need\n2. Document the rationale for new dependencies\n3. Add version constraints\n4. Note any configuration requirements\n\n### Update product.md When Features Complete\n\nAfter completing a feature track:\n\n1. Move feature from \"planned\" to \"implemented\" in product.md\n2. Update any affected success metrics\n3. Document any scope changes from original plan\n\n### Verify Context Before Implementation\n\nBefore starting any track:\n\n1. Read all context artifacts\n2. Flag any outdated information\n3. Propose updates before proceeding\n4. Confirm context accuracy with stakeholders\n\n## Greenfield vs Brownfield Handling\n\n### Greenfield Projects (New)\n\nFor new projects:\n\n1. Run `\u002Fconductor:setup` to create all artifacts interactively\n2. Answer questions about product vision, tech preferences, and workflow\n3. Generate initial style guides for chosen languages\n4. Create empty tracks registry\n\nCharacteristics:\n\n- Full control over context structure\n- Define standards before code exists\n- Establish patterns early\n\n### Brownfield Projects (Existing)\n\nFor existing codebases:\n\n1. Run `\u002Fconductor:setup` with existing codebase detection\n2. System analyzes existing code, configs, and documentation\n3. Pre-populate artifacts based on discovered patterns\n4. Review and refine generated context\n\nCharacteristics:\n\n- Extract implicit context from existing code\n- Reconcile existing patterns with desired patterns\n- Document technical debt and modernization plans\n- Preserve working patterns while establishing standards\n\n## Benefits\n\n### Team Alignment\n\n- New team members onboard faster with explicit context\n- Consistent terminology and conventions across the team\n- Shared understanding of product goals and technical decisions\n\n### AI Consistency\n\n- AI assistants produce aligned outputs across sessions\n- Reduced need to re-explain context in each interaction\n- Predictable behavior based on documented standards\n\n### Institutional Memory\n\n- Decisions and rationale are preserved\n- Context survives team changes\n- Historical context informs future decisions\n\n### Quality Assurance\n\n- Standards are explicit and verifiable\n- Deviations from context are detectable\n- Quality gates are documented and enforceable\n\n## Directory Structure\n\n```\nconductor\u002F\n├── index.md              # Navigation hub linking all artifacts\n├── product.md            # Product vision and goals\n├── product-guidelines.md # Communication standards\n├── tech-stack.md         # Technology preferences\n├── workflow.md           # Development practices\n├── tracks.md             # Work unit registry\n├── setup_state.json      # Resumable setup state\n├── code_styleguides\u002F     # Language-specific conventions\n│   ├── python.md\n│   ├── typescript.md\n│   └── ...\n└── tracks\u002F\n    └── \u003Ctrack-id>\u002F\n        ├── spec.md\n        ├── plan.md\n        ├── metadata.json\n        └── index.md\n```\n\n## Context Lifecycle\n\n1. **Creation**: Initial setup via `\u002Fconductor:setup`\n2. **Validation**: Verify before each track\n3. **Evolution**: Update as project grows\n4. **Synchronization**: Keep artifacts aligned\n5. **Archival**: Document historical decisions\n\n## Context Validation Checklist\n\nBefore starting implementation on any track, validate context:\n\n### Product Context\n\n- [ ] product.md reflects current product vision\n- [ ] Target users are accurately described\n- [ ] Feature list is up to date\n- [ ] Success metrics are defined\n\n### Technical Context\n\n- [ ] tech-stack.md lists all current dependencies\n- [ ] Version numbers are accurate\n- [ ] Infrastructure targets are correct\n- [ ] Development tools are documented\n\n### Workflow Context\n\n- [ ] workflow.md describes current practices\n- [ ] Quality gates are defined\n- [ ] Coverage targets are specified\n- [ ] Commit conventions are documented\n\n### Track Context\n\n- [ ] tracks.md shows all active work\n- [ ] No stale or abandoned tracks\n- [ ] Dependencies between tracks are noted\n\n## Common Anti-Patterns\n\nAvoid these context management mistakes:\n\n### Stale Context\n\nProblem: Context documents become outdated and misleading.\nSolution: Update context as part of each track's completion process.\n\n### Context Sprawl\n\nProblem: Information scattered across multiple locations.\nSolution: Use the defined artifact structure; resist creating new document types.\n\n### Implicit Context\n\nProblem: Relying on knowledge not captured in artifacts.\nSolution: If you reference something repeatedly, add it to the appropriate artifact.\n\n### Context Hoarding\n\nProblem: One person maintains context without team input.\nSolution: Review context artifacts in pull requests; make updates collaborative.\n\n### Over-Specification\n\nProblem: Context becomes so detailed it's impossible to maintain.\nSolution: Keep artifacts focused on decisions that affect AI behavior and team alignment.\n\n## Integration with Development Tools\n\n### IDE Integration\n\nConfigure your IDE to display context files prominently:\n\n- Pin conductor\u002Fproduct.md for quick reference\n- Add tech-stack.md to project notes\n- Create snippets for common patterns from style guides\n\n### Git Hooks\n\nConsider pre-commit hooks that:\n\n- Warn when dependencies change without tech-stack.md update\n- Remind to update product.md when feature branches merge\n- Validate context artifact syntax\n\n### CI\u002FCD Integration\n\nInclude context validation in pipelines:\n\n- Check tech-stack.md matches actual dependencies\n- Verify links in context documents resolve\n- Ensure tracks.md status matches git branch state\n\n## Session Continuity\n\nConductor supports multi-session development through context persistence:\n\n### Starting a New Session\n\n1. Read index.md to orient yourself\n2. Check tracks.md for active work\n3. Review relevant track's plan.md for current task\n4. Verify context artifacts are current\n\n### Ending a Session\n\n1. Update plan.md with current progress\n2. Note any blockers or decisions made\n3. Commit in-progress work with clear status\n4. Update tracks.md if status changed\n\n### Handling Interruptions\n\nIf interrupted mid-task:\n\n1. Mark task as `[~]` with note about stopping point\n2. Commit work-in-progress to feature branch\n3. Document any uncommitted decisions in plan.md\n\n## Best Practices\n\n1. **Read context first**: Always read relevant artifacts before starting work\n2. **Small updates**: Make incremental context changes, not massive rewrites\n3. **Link decisions**: Reference context when making implementation choices\n4. **Version context**: Commit context changes alongside code changes\n5. **Review context**: Include context artifact reviews in code reviews\n6. **Validate regularly**: Run context validation checklist before major work\n7. **Communicate changes**: Notify team when context artifacts change significantly\n8. **Preserve history**: Use git to track context evolution over time\n9. **Question staleness**: If context feels wrong, investigate and update\n10. **Keep it actionable**: Every context item should inform a decision or behavior\n",{"name":5,"version":47,"description":7},"1.0.0","main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fconductor\u002Fskills\u002Fcontext-driven-development",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add welflau\u002Fai-dev-system --skill context-driven-development",{"tool":61,"command":62},"bunx","bunx skills add welflau\u002Fai-dev-system --skill context-driven-development",{"tool":64,"command":65},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill context-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fconductor\u002Fskills\u002Fcontext-driven-development\u002FSKILL.md",true,[],[70,102,130,155,184,209],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":84,"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",[78,81],{"categoryNo":79,"categoryName":80,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,39,100],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","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":74,"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":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",[113,114,115,116,117,118,30,119,120,121,122,35,123,124,125,126,127,128,129],"internal comms","comms","status","help","SET","write","reports","me","incident","leadership","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":74,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":42},"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":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},[139,91,32,140,141,88,142,143,144,145,146,147,148,149,30,150,151,152,153,100,154],"web artifacts builder","artifacts builder","builder","css","components","react","routing","state management","state","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":74,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":171,"publishedAt":42},"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":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":164,"categoryName":165,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[88,172,173,142,91,143,144,174,175,176,32,177,97,178,30,179,180,181,182,39,183,41],"design","frontend design","react components","create","code","examples","landing","ui design","pages","aesthetics","web ui","generic",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":188,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":42},"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",[191],{"categoryNo":164,"categoryName":165,"taxonomyType":20,"taxonomyTypeDesc":21},[193,194,195,175,176,196,197,198,199,30,200,201,202,203,39,204,205,206,207,208,41],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","systems","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":74,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":42},"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":20,"taxonomyTypeDesc":21},[218,219,220,221,93,222,32,117,223,224,178,225,226,180,227,39,228,229,230,100,231,232],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]