Project rules

Put standing instructions for the assistant in a file at the root of your project. They're included with every request, so you don't have to repeat how to build, test or style the code.

Where to put them

Lamied reads these files from the workspace root, in this order, and uses every one that exists:

1. LAMIED.md
2. .lamied/rules.md
3. AGENTS.md, the convention other AI coding tools share, so one file can serve them all

Rules for one folder

A folder can have rules of its own, in the same files: a LAMIED.md, .lamied/rules.md or AGENTS.md inside it. In a monorepo, each package can say how it is built and tested.

• The assistant gets a folder's rules the first time it reads or changes a file there, or lists, searches or runs a command in that folder. It gets them once in a conversation.
• They apply to the files under that folder. There, they take precedence over the project-wide rules, and a deeper folder's rules over a shallower one's.
• Dependency, build and hidden folders, such as node_modules, dist, vendor and .github, are never read for rules. Code you didn't write can't instruct the assistant.

Coming from Claude Code

When a folder has none of the files above, Lamied reads CLAUDE.md or .claude/CLAUDE.md instead. A project set up for Claude Code works as it is. Its hooks carry over too; see Hooks.

What to write

Short, specific instructions work best:

• how to install, build, run and test the project;
• code conventions and patterns to follow;
• architecture notes: where things live and why;
• things to avoid.

# Conventions
- TypeScript strict mode; no default exports.
- Run `pnpm test --filter api` after changing services/api.
- Money is stored as integer cents, never floats.
- Never edit files under generated/.

How they're used

• They're read again at the start of every step, so an edit takes effect even in the middle of a task.
• Helper agents (research and worktree agents) follow the same rules.
• Up to 32,000 characters of the project-wide rules are used, and up to 16,000 of a folder's. The assistant is told if the text was cut short.
• Empty or binary files, files over 256 KB, and links pointing outside the workspace are skipped.

Rules can guide, not grant

A repository you open may not be yours, so its rules are treated as guidance only. They can't grant permissions, turn off approvals or override Lamied's own safety rules. Approvals are enforced by the app itself. See Plan Mode and approvals.