agents.md

alwaysApply
true

Definition

• This project is called AIPM - short for AI project manager. It is a TUI application that helps users intelligently manage their tasks.
• When the user says "AI", "agent", or "AIPM AI agent", he is referring to the AI agent being used within AIPM.

Commit Discipline

• Commit after every discrete action. Each meaningful change (e.g. adding a feature, fixing a bug, refactoring, updating docs, adding a test) must be committed individually before moving on.
• Use concise, imperative commit messages (e.g. add bucket column reordering, fix off-by-one in timeline view).
• Do not batch unrelated changes into a single commit.
• If a task involves multiple steps, commit after each step — not all at the end.

Releases

• When asked to create a release: bump the version in apps/tui/Cargo.toml, commit, push, then create the release with gh release create.
• Releases must be published immediately — do not use --draft.
• Include release notes with concise, descriptive bullet points explaining what changed (e.g. - Add @ autocomplete dropdown for selecting tasks by ID or title). Do not just list version numbers or raw commit messages.
• Each bullet should describe the user-facing change, not implementation details.

Comments

• By default, avoid writing comments at all.
• If you write one, it should be about "Why", not "What".

General

• Avoid creating unnecessary structs, enums, or traits if they are not shared. Prefer inlining types when they're only used in one place.
• Run cargo fmt --manifest-path apps/tui/Cargo.toml before committing to ensure consistent formatting.
• Run cargo clippy --manifest-path apps/tui/Cargo.toml --all-targets -- -D warnings and fix any warnings before committing.
• Run cargo check --manifest-path apps/tui/Cargo.toml periodically while making Rust changes to catch errors early — don't wait until the end.
• Run cargo build --manifest-path apps/tui/Cargo.toml after code changes to verify compilation before committing.
• Keep commits small and reviewable.