Agent Rules
An agent with no instructions makes its own calls, and it makes them differently every session. So before we start building QR Studio, we hand it a set of project rules it reads on every run: how to plan, when to test, and which design to follow. It's a small amount of work up front that pays off across the entire build.
What you'll walk away with:
- Writing project-level rules that your coding agent picks up automatically, without you pasting them into every chat
- CLAUDE.md and AGENTS.md, what each one is for, and how they relate to each other
- Setting expectations for planning and testing once, so you're not repeating yourself for the rest of the project
- Pointing the agent at a design system so new screens match the ones that already exist
- Sharing one set of rules across different coding agents instead of maintaining a separate copy for each
- Importing extra instruction files into agent memory as the project grows past a single file