I have two files and a directory.
1: AGENTS.md
This is widely support, except by Claude. I’l come back to Claude, but for the AGENTS.md, it has about 200 lines of direct instructions, and then a section that points to other documentation.
I’ve included a snippet from that section below.
## Related Documentation
This document provides an overview of the project structure and development guidelines. For detailed guides on specific topics, refer to the following documentation files in the `devprompts/` directory:
* **`devprompts/react-component-architecture.md`** - Detailed guidelines for React component architecture, file organization, hooks, utilities, and refactoring patterns for the `src/front/react-maintainlibraries` application.
* **`devprompts/react-maintain-libraries-styling.md`** - Comprehensive styling guidelines for the React maintain libraries app, including tab navigation structure, color coding, badge states, implementation examples, and visual hierarchy.
* **`devprompts/api-creation-guide.md`** - Complete guide for creating REST API endpoints, including authentication classes, step-by-step creation instructions, parameter validation, error handling, response formats, server-side processing preference, and testing examples.
2: The devprompts directory.
This contains about 20 files, typically 4-500 lines long, that go into a lot more detail about that particular task.
They reference each other where needed.
Below is a snippet of the first few lines of the react-component-architecture one:
# React Component Architecture Guidelines
**When to use:** Creating or modifying React components in `src/front/react-maintainlibraries` (structure, hooks, columns, refactors).
**Summary (read first):**
- Component files (`.jsx`) should primarily contain JSX and composition; no API or complex logic in `.jsx`.
- Logic, state, and API calls go in `hooks/`; column definitions in `columns/`; shared UI in `components/`; constants in `utils/`.
- Components over 500 lines should be refactored; extract repeated patterns into hooks or utilities.
- Custom hooks must start with `use`; use the directory structure and patterns described below.
This document provides **code organization and architecture guidelines** for React components in the `src/front/react-maintainlibraries` application. These guidelines enforce separation of concerns, maintainability, and code reusability.
**Note:** This document focuses on code structure, file organization, hooks, and refactoring patterns. For visual design, styling, colors, and UI patterns specific to the maintain libraries app, see `devprompts/react-maintain-libraries-styling.md`.
[… etc …]
3: CLAUDE.md
The CLAUDE.md specification allows an “import” feature using @, so most of this is just importing the AGENTS.md
However, there are a few Claude-specifics in there, mainly around doing the git branch stuff / CI inspection stuff automatically, and updating our Trello.
As “things other than Claude” have got more agentic, I’ll probably move some of this to AGENTS.md
@AGENTS.md
## Workflow Instructions
When working on any task in this repository, you **must** follow the steps in:
- [devprompts/all-tasks.md](devprompts/all-tasks.md) — standard git workflow for every task (branching, committing, CI, PR)
- [devprompts/tasks-from-trello.md](devprompts/tasks-from-trello.md) — additional steps when the task originates from Trello (assigning, moving card, attaching PR, moving to Review)