Cursor rule

1---
2description: When completing tasks autonomously without human supervision
3alwaysApply: false
4version: 2.0.0
5---
6 
7# Autonomous Development Workflow
8 
9For AI agents completing tasks without human supervision. The goal: deliver a clean pull
10request that passes all checks and gets merged without back-and-forth.
11 
12## Before Implementation
13 
14Read all cursor rules in `rules/`. These define the project's standards. Every
15applicable rule must be followed.
16 
17If `CLAUDE.md` or `AGENTS.md` exist in the project root, read those for additional
18context.
19 
20## Implementation
21 
22Write code following all cursor rules. Reference specific rules by reading the files
23directly.
24 
25## Validation - Use the Tooling
26 
27The project has tooling configured. We use it instead of manually trying to comply.
28 
29Check for pre-commit and run if exists:
30 
31```bash
32[ -f .pre-commit-config.yaml ] && pre-commit run --all-files
33```
34 
35Read `.github/workflows/build.yml` (or ci.yml, test.yml) and replicate those validation
36steps locally, for example:
37 
38```bash
39ruff check --fix .    # Auto-fix linting
40ruff format .         # Auto-format code
41pytest                # Run tests
42```
43 
44If we added functionality, we add tests following project patterns. Aim for 95%
45coverage - solid testing without obsessing over every edge case.
46 
47Only commit and push when all validation passes. Green checks make for happy merges! ✅
48 
49## Self-Review
50 
51Run `git diff` and review every change, as a senior developer would.
52 
53Read through ALL cursor rules again and verify our code follows each applicable
54guideline.
55 
56Would we approve this in code review? If not, keep iterating until it's something we're
57pleased with.
58 
59## Submission
60 
61Generate commit message following git-commit-message.mdc (if present).
62 
63Use `gh pr create` to submit a high-quality pull request with clear description of what
64changed and why.
65 
66## Boundaries
67 
68Proceed autonomously: using existing tooling, following established patterns, changes
69within task scope.
70 
71Ask first: major architectural changes, changes that would result in data loss, etc.
72 
73## Success
74 
75A successful autonomous PR means: all automated checks pass, code follows all cursor
76rules, tests are green, and the developer merges it without requesting changes. Use the
77tooling to get there - it's our friend! 🎉
78