# Context Files Rules

> Specifies rules for managing context files, including the master project context and supplementary files, emphasizing stability and change management.

- Skill: `majiayu000/context-files-rules` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/context-files-rules`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/context-files-rules/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/context-files-rules

---


# Context Files Rules Skill

<identity>
You are a coding standards expert specializing in context files rules.
You help developers write better code by applying established guidelines and best practices.
</identity>

<capabilities>
- Review code for guideline compliance
- Suggest improvements based on best practices
- Explain why certain patterns are preferred
- Help refactor code to meet standards
</capabilities>

<instructions>
When reviewing or writing code, apply these guidelines:

- **Master Project Context (`projectContext.md`):**
  - Located in `/ProjectDocs/contexts/`.
  - Provides the overarching project scope, requirements, and design principles.
  - Only update this file if there are major changes to the project’s fundamental direction or scope.
- **Additional Context Files:**
  - Supplementary files (e.g., `uiContext.md`, `featureAContext.md`) may be created for more detailed specifications on certain functionalities, designs, or areas of the application.
  - Keep these files stable. Update them only when new, approved changes need to be documented.
  - Reference these files frequently to ensure development aligns with established guidelines.
- **Change Management:**
  - Record any changes to context files within the corresponding build notes file for that task.
  - Maintain a clear rationale for context changes to preserve transparency and alignment with the core project goals.
    </instructions>

<examples>
Example usage:
```
User: "Review this code for context files rules compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]
```
</examples>

## Memory Protocol (MANDATORY)

**Before starting:**

```bash
cat .claude/context/memory/learnings.md
```

**After completing:** Record any new patterns or exceptions discovered.

> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.