Project Rules

Project rules let you define custom instructions that are automatically injected into every prompt when Codeep is run inside a specific project. This lets you enforce coding standards, style preferences, and project-specific context without repeating yourself.

Creating rules

Create one of these files in your project root. Codeep detects them automatically on startup, in this priority order:

.codeep/rules.md — Codeep-native, committed with the repo
CODEEP.md — Codeep-native, root-level convenience
AGENTS.md — cross-tool standard (Claude Code, Cursor, Kilo Code)

The first non-empty file wins. So if you already have an AGENTS.md from another tool, Codeep will read it as-is — no duplication needed. (The CODEEP.md and AGENTS.md fallbacks are CLI features; the Mac app currently reads .codeep/rules.md only.)

$ mkdir -p .codeep
$ touch .codeep/rules.md

Example rules file

# .codeep/rules.md
 
## Code Style
- Use TypeScript strict mode, no `any` types
- Prefer `const` over `let`, never use `var`
- Use Tailwind CSS for all styling
 
## Architecture
- Components go in src/components/
- API routes go in src/app/api/
- Use Prisma for all database access
 
## Testing
- Write tests for all utility functions
- Use Vitest, not Jest

★

Rules are plain markdown. Use headings to organize them into sections. Keep rules concise — the shorter and clearer, the better the AI follows them.

Priority

Only the first non-empty file is loaded — they are not concatenated. This lets you keep a trimmed AGENTS.md for other tools and a richer Codeep-specific rules file side by side; the Codeep-native one takes precedence.

★

Coming from Claude Code or Cursor? Your existing AGENTS.md works as-is. No changes needed.

Providers Zed Editor (ACP)