[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSN39FP07BCTDXTV9ED4FW":3,"skill-same:01M6CSN39FP07BCTDXTV9ED4FW":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6CSN39FP07BCTDXTV9ED4FW","context-driven-development",null,"Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcontext-driven-development\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"development","context","context driven development","documentation","code","team","guide","alignment","community","artifact","2026-11-10 10:12:30",false,"---\nname: context-driven-development\ndescription: \"Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.\"\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\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## Do not use this skill when\n\n- The task is unrelated to context-driven development\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Use this skill when\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## Do not use this skill when\n\n- The task is unrelated to context-driven development\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Use this skill when\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,"risk":34,"source":27,"date_added":35,"description":7},"unknown","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcontext-driven-development",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill context-driven-development",{"tool":50,"command":51},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill context-driven-development",{"tool":53,"command":54},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill context-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcontext-driven-development\u002FSKILL.md",true,[58,64,68,72,76,80,84,88],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"Archetypes.md","REFERENCE","参考文档",15634,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FArchetypes.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"Foundation.md",12791,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FFoundation.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"LeveragePoints.md",11965,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FLeveragePoints.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"Workflows\u002FCausalLoop.md",9763,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FWorkflows\u002FCausalLoop.md",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":78,"sourceHtmlUrl":79},"Workflows\u002FConceptMap.md",9101,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FWorkflows\u002FConceptMap.md",{"path":81,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":82,"sourceHtmlUrl":83},"Workflows\u002FFindArchetype.md",13168,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FWorkflows\u002FFindArchetype.md",{"path":85,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":86,"sourceHtmlUrl":87},"Workflows\u002FFindLeverage.md",14585,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FWorkflows\u002FFindLeverage.md",{"path":89,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":90,"sourceHtmlUrl":91},"Workflows\u002FIceberg.md",10637,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FSystemsThinking\u002FWorkflows\u002FIceberg.md",[93,106,122,149,168,195],{"skillNo":94,"name":95,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":103,"publishedAt":29},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[98],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[104,105],"Test Skill","test",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":29},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[113,114,115,116,117,118,119,27,120,121],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":131,"publishedAt":29},"01M6GDRKEA0WE670SPFWX5GKCN","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000023","Skill与智能体开发",[132,133,134,135,136,137,138,139,140,141,142,143,144,145,27,146,147,148],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":29},"01M6GDRFS1452PC71JQ38S24HR","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[155],{"categoryNo":129,"categoryName":130,"taxonomyType":101,"taxonomyTypeDesc":102},[157,132,158,159,160,161,162,27,137,163,145,164,142,141,136,165,120,166,138,167],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":29},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000009","前端开发",[178,179,180,181,182,121,183,184,185,186,187,188,116,189,190,191,192,27,193,194],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":29},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[201],{"categoryNo":129,"categoryName":130,"taxonomyType":101,"taxonomyTypeDesc":102},[203,204,205,206,207,208,209,210,27,211,212,213,214,215,216,217,218,23,219,138],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","rust"]