Cursor rule

1---
2description: When completing tasks autonomously without human supervision
3alwaysApply: false
4version: 3.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## Spec Quality Is the Bottleneck
13 
14Invest more time understanding the problem than writing the implementation. A precise
15understanding of the problem produces better code than any amount of iteration on an
16ambiguous one. If the task description is ambiguous, clarify before implementing. Quick,
17localized changes with no behavioral impact may proceed directly.
18 
19## Before Implementation
20 
21Assess whether you have enough clarity to implement correctly. Can you articulate the
22problem being solved, what "done" looks like, the edge cases, and the assumptions you're
23making? If not, ask before proceeding.
24 
25Load project standards via `/load-rules`. If that's not available, fall back to reading
26applicable rules directly. Every applicable rule must be followed.
27 
28If `CLAUDE.md` or `AGENTS.md` exist in the project root, read those for additional
29context.
30 
31## Implementation
32 
33Write code following all cursor rules. Reference specific rules by reading the files
34directly.
35 
36## Validation - Use the Tooling
37 
38The project has tooling configured. We use it instead of manually trying to comply.
39 
40Check for pre-commit and run if exists:
41 
42```bash
43[ -f .pre-commit-config.yaml ] && pre-commit run --all-files
44```
45 
46Read `.github/workflows/build.yml` (or ci.yml, test.yml) and replicate those validation
47steps locally, for example:
48 
49```bash
50ruff check --fix .    # Auto-fix linting
51ruff format .         # Auto-format code
52pytest                # Run tests
53```
54 
55If we added functionality, we add tests following project patterns. Aim for 95% coverage
56-- solid testing without obsessing over every edge case.
57 
58Only commit and push when all validation passes.
59 
60## Evaluate Outcomes
61 
62Run `git diff` and review the changes at the feature level. The question isn't "is every
63line correct" -- it's "does this changeset solve the problem cleanly?"
64 
65Verify the implementation delivers what was asked for -- not just technically correct, but
66useful. Check that no unnecessary complexity was introduced.
67 
68Read through applicable rules and verify compliance. Document any assumptions or
69non-obvious choices in the PR description so reviewers understand the decisions made.
70 
71## Submission
72 
73Generate commit message following git-commit-message.mdc (if present).
74 
75Use `gh pr create` to submit a high-quality pull request with clear description of what
76changed and why.
77 
78## Boundaries
79 
80Proceed autonomously: using existing tooling, following established patterns, changes
81within task scope.
82 
83Ask first: major architectural changes, changes that would result in data loss, etc.
84 
85## Success
86 
87A successful autonomous PR means: the implementation solves the stated problem, all
88automated checks pass, code follows project standards, and the developer merges it
89without requesting changes.
90