技能 Context-Driven Development
📦

Context-Driven Development

安全

Mettre en œuvre des flux de travail de développement axés sur le contexte

Les équipes struggle with inconsistent AI outputs and scattered project knowledge. This skill establishes structured context artifacts that ensure aligned AI behavior and preserve institutional memory across development sessions.

支持: Claude Codex Code(CC)
🥉 72 青铜
1

下载技能 ZIP

2

在 Claude 中上传

前往 设置 → 功能 → 技能 → 上传技能

3

开启并开始使用

测试它

正在使用“Context-Driven Development”。 Set up context for a new SaaS project with TypeScript backend and React frontend

预期结果:

  • Created conductor/product.md with product vision, target users, and core features
  • Created conductor/tech-stack.md documenting TypeScript, Node.js, React, and PostgreSQL
  • Created conductor/workflow.md with TDD practices, git conventions, and code review requirements
  • Created conductor/tracks.md as empty registry ready for work items
  • Generated code_styleguides/typescript.md with project-specific conventions

正在使用“Context-Driven Development”。 Validate context before starting implementation on authentication feature

预期结果:

  • Product context: product.md accurately describes authentication requirements
  • Technical context: tech-stack.md includes JWT library dependency needed for implementation
  • Workflow context: workflow.md specifies testing requirements that apply to this feature
  • Recommendation: Context is current and ready for implementation

安全审计

安全
v1 • 2/24/2026

This skill contains only documentation and instructional content with no executable code, scripts, or network operations. Static analysis scanned 0 files and found no security patterns. The skill provides guidance on managing project context artifacts (product.md, tech-stack.md, workflow.md) for AI-assisted development workflows. No security risks identified.

0
已扫描文件
0
分析行数
0
发现项
1
审计总数
未发现安全问题
审计者: claude

质量评分

38
架构
100
可维护性
87
内容
50
社区
100
安全
74
规范符合性

你能构建什么

Onboard new team members to established projects

Use context artifacts to rapidly bring new developers up to speed on product vision, tech stack decisions, and team workflows without requiring extensive pair programming or documentation hunting.

Establish consistent AI interaction patterns

Create a persistent context foundation that ensures AI assistants produce aligned outputs across different sessions and team members, reducing the need to re-explain project context repeatedly.

Transition from ad-hoc to structured development

Migrate existing projects from scattered documentation and implicit knowledge to a formalized context structure that survives team changes and informs future decisions.

试试这些提示

Beginner: Set up context for a new project 
I am starting a new project and want to implement context-driven development. Help me create the initial product.md, tech-stack.md, and workflow.md files. Ask me questions about my product vision, technology preferences, and desired workflows to generate appropriate context artifacts.
Intermediate: Validate existing context accuracy 
Review my current context artifacts in the conductor/ directory. Check if product.md reflects implemented features, if tech-stack.md matches actual dependencies, and if workflow.md describes current practices. List any discrepancies and propose specific updates.
Advanced: Migrate brownfield project to context-driven approach 
Analyze my existing codebase and extract implicit context to populate product.md, tech-stack.md, and workflow.md. Identify current patterns, dependencies, and workflows. Then recommend any gaps between current practices and desired standards that should be documented.
Expert: Synchronize context after major feature completion 
A major feature has just been completed and merged. Guide me through updating all affected context artifacts: move features from planned to implemented in product.md, document any new dependencies in tech-stack.md, update tracks.md status, and ensure all cross-references remain accurate.

最佳实践

  • Read all context artifacts before starting work to ensure you have current information about product goals, technology constraints, and workflow requirements.
  • Update context artifacts as part of completing each track, not as a separate task. Make small incremental changes alongside code commits.
  • Include context artifact changes in code reviews to ensure the team validates documentation accuracy and maintains shared understanding.

避免

  • Stale context: Allowing documentation to become outdated leads to misaligned AI outputs and team confusion. Update context as part of every track completion.
  • Context sprawl: Creating new document types outside the defined artifact structure scatters information. Use the established structure and resist proliferation.
  • Over-specification: Documenting every detail makes context impossible to maintain. Focus only on decisions that affect AI behavior and team alignment.

常见问题

How often should I update context artifacts?
Update context artifacts whenever the information they contain changes. This typically happens when completing a feature track, adding dependencies, or modifying workflows. Treat context updates as part of the definition of done for each work item.
What if my team already has documentation in a different format?
You can migrate existing documentation into the context artifact structure. Extract relevant information from existing docs and populate the appropriate artifacts. The key is having a single source of truth for each type of information, regardless of where it started.
Is context-driven development suitable for solo developers?
Yes. While the methodology emphasizes team alignment, it also provides significant benefits for individual developers by preserving your own decisions and rationale over time, ensuring consistent AI interactions across sessions, and making it easier to resume work after interruptions.
How do I handle context for multiple projects?
Each project should have its own independent context structure in a conductor/ directory at the project root. Context is project-specific because product vision, tech stack, and workflows differ between projects. Do not share context artifacts across projects.
What happens if context artifacts conflict with each other?
Conflicts indicate outdated or inconsistent documentation. Resolve by determining which artifact has the correct current information, then update the conflicting artifacts to match. Use the product.md as the primary source for what you are building, and ensure tech-stack.md and workflow.md support those goals.
Can I use this methodology without the Conductor tool?
Yes. The context-driven development methodology is tool-agnostic. While Conductor provides automation for setup and maintenance, you can manually create and maintain the context artifacts following the same structure and principles described in this skill.

开发者详情

作者

sickn33

许可证

MIT

仓库

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/context-driven-development

引用

main

文件结构

📄 SKILL.md