project-context
Skill2 starsChanged 8 months agoMITView on GitHub
Project context management skill for managing user profiles and project context. This skill is invoked by brainstorming and executing-plans skills, not triggered independently. Invoked to get user profile when brainstorming is activated, automatically updates project context when executing-plans completes.
33 other projects use a version of this.
Adopted by
Most recently taken up by
- shinpr/ai-coding-project-boilerplatetheir own version, first seen Nov 13, 2026
- advait/effect-durable-agenttheir own version, first seen Nov 8, 2026
- upex-galaxy/agentic-qa-boilerplatetheir own version, first seen Nov 7, 2026
- egorfedorov/claude-context-optimizertheir own version, first seen Nov 1, 2026
- ritamgh/claude-skillstheir own version, first seen Nov 1, 2026
- OpenxIntelligence/Coding-Agent-Skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- shinpr/ai-coding-project-boilerplate★ 239same name
- egorfedorov/claude-context-optimizer★ 130same name
- TenureAI/PhD-Zero★ 52same name
- upex-galaxy/agentic-qa-boilerplate★ 26same name
- sergeeey/Claude-cod-top-2026★ 9same name
- perhapsspy/project-context★ 7same name
- advait/effect-durable-agent★ 4same name
- aida-core/aida-marketplace★ 4same name
- I-Onlabs/claude-code-skills★ 4same name
- IgorBabikov/Flowcairn★ 4same name
23 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- brainstormingSkill
- code-commentatorSkill
- executing-plansSkill
- writing-planSkill
The file
Files
Project Context Skill
This skill manages user profiles and project context, providing context information to other skills.
Core Responsibilities
| Responsibility | Description | Maintenance Method |
| User Profile Reading | Load user profile, provide user information for brainstorming | Agent automatic |
| User Profile Updating | Identify user preferences during dialogue, automatically update profile | Agent automatic + proactive trigger |
| Project Context Management | Record current project state, provide background for future planning | Agent automatic (when executing-plans completes) |
Proactive Update Mechanism
User Profile Proactive Update Triggers
⚠️ Must proactively update user profile in the following situations:
Technical Preference Identification:
- User explicitly expresses preference for a certain framework/library
- User shows tendencies in technical selection
- User demonstrates new tech stack usage experience
Decision Tendency Identification:
- User shows consistent tendencies across multiple decisions (quality first/efficiency first)
- User's attitude toward risk (conservative/aggressive)
- User's attitude toward refactoring (small frequent changes/big refactoring)
Interaction Style Identification:
- User preference for detailed explanations or concise descriptions
- User preference for multiple choice questions or open-ended questions
- User wants confirmation at each step or at key milestones
Capability Assessment Updates:
- User demonstrates capabilities beyond expectations in certain areas
- User needs more guidance in certain areas
Project Context Proactive Update Triggers
⚠️ Must proactively update project context in the following situations:
On Feature Completion:
- Each feature implementation must be recorded to project context upon completion
- Record technical decisions and reasoning
- Record encountered problems and solutions
On Architecture Changes:
- Major changes in project structure
- Introduction of new dependencies or tech stacks
- Modifications to core design patterns
On Test Status Updates:
- Test coverage changes
- Test strategy adjustments
- Test framework changes
File Locations
| File | Path | Purpose |
| User Profile | design/context/user-profile.md | Cross-session user preferences |
| Project Context | design/context/project-context.md | Project persistent state record |
User Profile
Basic Information
| Field | Content | Update Date |
| User Positioning | [Senior Developer/Mid-level Developer/Product Manager/Other] | - |
| Technical Background | [Main languages, frameworks, tech stacks used] | - |
| First Recorded | YYYY-MM-DD | - |
| Last Updated | YYYY-MM-DD | - |
Technical Preferences
| Type | Preference | Notes |
| Frontend Framework | [React/Vue/Angular/Other] | - |
| Backend Language | [Node.js/Python/Go/Rust/Other] | - |
| Code Style | [Specific standards or style description] | - |
Decision Tendencies
| Scenario | Tendency | Manifestation |
| Regular Development | [Quality First/Efficiency First/Balance] | [Specific manifestation] |
| Emergency Situations | [Quality First/Efficiency First/Balance] | [Specific manifestation] |
| Refactoring Scenarios | [Quality First/Efficiency First/Balance] | [Specific manifestation] |
Risk Appetite
- Technical Selection: [Conservative/Moderate/Aggressive]
- Refactoring Decisions: [Small frequent changes/Medium iterations/Big refactoring]
- Dependency Introduction: [Minimal dependencies/Moderate dependencies/Willing to try new things]
Interaction Style
| Aspect | Preference | Description |
| Detail Level | [Detailed/Concise/Moderate] | - |
| Feedback Frequency | [Each step/Key milestones/After completion] | - |
| Explanation Depth | [In-depth explanation/Summary/No explanation needed] | - |
| Question Format | [Multiple choice/Open-ended/Both acceptable] | - |
Capability Assessment
| Capability Area | Self-assessed Level | Notes |
| Frontend Development | [Junior/Mid-level/Senior] | - |
| Backend Development | [Junior/Mid-level/Senior] | - |
| Architecture Design | [Junior/Mid-level/Senior] | - |
| Performance Optimization | [Junior/Mid-level/Senior] | - |
Update History
| Date | Update Content | Trigger Scenario |
| YYYY-MM-DD | [Initial creation] | First dialogue |
| YYYY-MM-DD | [Update content] | [Trigger scenario] |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.