24 lines
1003 B
Markdown
24 lines
1003 B
Markdown
# agent rules
|
|
|
|
## priorities
|
|
- optimize for simplicity, boringness, and long-term maintainability
|
|
- prefer minimal diffs; avoid refactors unless required for the active task
|
|
|
|
## tech stack
|
|
- python; pandas or polars
|
|
- file storage: json and csv, no sqlite or databases
|
|
- do not add new dependencies unless explicitly approved; if unavoidable, document justification in the active task notes
|
|
|
|
## workflow
|
|
- prefer direct argv commands (no bash -lc / compound shell chains) unless necessary
|
|
- work on ONE task at a time unless explicitly instructed otherwise
|
|
- at the start of work, state the task id you are executing
|
|
- do not start work unless a task id is specified; if missing, choose the earliest unchecked task and say so
|
|
- propose incremental steps
|
|
- always include basic tests for core logic
|
|
- when you complete a task:
|
|
- mark it [x] in pm/tasks.md
|
|
- fill in evidence with commit hash + commands run
|
|
- never mark complete unless acceptance criteria are met
|
|
- include date and time (HH:MM)
|