Claude Code Project Context

This skill loads project-specific development instructions from `CLAUDE.md` and applies multi-file rule context from `./cursor/rules/**/*` (adapted from Cursor IDE).

What This Skill Does

Instructions

When the user invokes this skill:

1. **Read the CLAUDE.md file** at the project root (or `./CLAUDE.md` if in subdirectory)

- Extract all sections: Commands, Known Issues, Recent Changes, Testing Protocol

- Store these as active context for the session

2. **Load all rule files from `./cursor/rules/**/*`**

- Use Glob to find all files matching pattern `cursor/rules/**/*`

- Read each file and parse headers for `ruletype` metadata

- Treat rule files with equal importance to CLAUDE.md

- Replace "Cursor" with "Claude" in rule content where it refers to the IDE/agent

3. **Apply context based on rule types**

- If `ruletype: priority` → always apply before other rules

- If `ruletype: constraint` → enforce as hard requirement

- If `ruletype: reference` → load as background context

- If `ruletype: workflow` → follow as process guideline

4. **Enforce testing protocol before any commit operations**

- Run `npm run type-check` first

- Run `npm run build` second

- Run `npm test` third

- If any command fails, halt commit and report errors

- Only proceed with commit if all three pass

5. **Provide context-aware assistance**

- Reference Known Issues when debugging related problems

- Suggest relevant commands from the Commands section

- Follow Recent Changes for code style consistency

- Apply rule-based constraints from `./cursor/rules/`

Examples

**Example 1: User asks to make changes and commit**

**Example 2: User reports test failures**

**Example 3: User asks about build commands**

Constraints

Notes

This skill is designed for projects that use cross-IDE development contexts. It ensures consistency when migrating from Cursor IDE to Claude Code by preserving rule-based workflows and project-specific conventions.