- always use conventional commit format, with prefix feat/fix/refactor/chore
- specify the crate if relevant, e.g.
fix(mcp-hello) ...
- specify the crate if relevant, e.g.
- prefer to use
cargoto modify Cargo.toml files over editing them directly- this helps ensure we install the latest version of components etc
- always run
cargo fmtbefore committing
The project is divided into crates:
MCP: Model Context Protocol
Each crate/component has its own AGENTS.md file that summarizes the component and the features and constraints that have been established so far.
At the end of each task, for the corresponding AGENTS.md files:
- check that no listed features or constraints have been accidentally removed or violated.
- update the list to add, remove, or modify any features or constraints involved in this specific task.
The list should always be formatted as brief bullet points with hierarchical structure. Sub-lists may be nested as deeply as necessary. Minor/unimportant details should be omitted. e.g:
- The textbox allows both prompts and commands
- Commands start with a /
- Example:
/helplists commands
- Example:
- Ctrl-D will exit
- Commands start with a /
A template for component-specific AGENTS.md files follows:
Brief description of the component.
A bullet-point list of key dependencies and the reason they are needed. Minor dependencies are omitted.
A bullet-point list of the component's features.
A bullet-point list of the component's constraints.