mtkell
/
chronogrid
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

cleaned up automated coding rule sets

This commit is contained in:
Mike Kell 2026-08-09 23:36:34 -04:00
parent 2ea039de7e
commit 5277879dc0
2 changed files with 72 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
.clinerules
View File

@ -12,3 +12,39 @@
3. SINGLE SOURCE OF TRUTH: 3. SINGLE SOURCE OF TRUTH:
- Prior to modifying data structures, consult `docs/API_CONTRACTS/schema.sql` and `docs/ARCHITECTURE/01-OSAD-system-architecture.md`. - Prior to modifying data structures, consult `docs/API_CONTRACTS/schema.sql` and `docs/ARCHITECTURE/01-OSAD-system-architecture.md`.
- Update documentation in `/docs` concurrently with code changes. - Update documentation in `/docs` concurrently with code changes.
4. AUTONOMOUS TASK EXECUTION PROTOCOL:
When instructed to "Execute next task" or run an autonomous cycle, perform the following 7 steps in sequence:
Step 1: STATE DISCOVERY
- Read `.clinerules` and `docs/ARCHITECTURE/01-OSAD-system-architecture.md`.
- Inspect files in `docs/TASKS/` to locate the FIRST incomplete task (`[ ]`) in chronological order.
- Read `DECISION_LOG.md` to review the latest architectural context.
- Explicitly state the Task ID and title being tackled.
Step 2: FEATURE BRANCH CREATION
- Ensure working on `main` and updated: `git checkout main && git pull origin main`
- Create a dedicated feature branch: `git checkout -b feature/<task-id>-<short-description>`
Step 3: IMPLEMENTATION
- Read relevant specs in `/docs` (`schema.sql`, `security-and-crypto.md`, etc.).
- Write code required ONLY for the target task while respecting all local-first mandates.
Step 4: TESTING & VERIFICATION
- Run the local verification suite: `powershell -File scripts/verify_agent_work.ps1`
- Run crate unit tests: `cargo test --package <crate_name>`
- Iteratively fix any compiler or test errors until all checks pass cleanly.
Step 5: DOCUMENTATION & ADL UPDATE
- Update the task status to `[x]` in `docs/TASKS/`.
- If architectural decisions or schema adjustments were made, log them in `DECISION_LOG.md` and create a record in `docs/ARCHITECTURE/ADR/`.
Step 6: COMMIT & MERGE
- Stage changes: `git add .`
- Commit: `git commit -m "feat(<scope>): complete <Task ID> - <Task Title>"`
- Merge into main: `git checkout main && git merge feature/<task-id>-<short-description> --no-ff -m "chore: merge feature/<task-id> into main"`
Step 7: REMOTE PUSH & CLEANUP
- Push main: `git push origin main`
- Remove feature branch: `git branch -d feature/<task-id>-<short-description>`
- Provide a concise summary of completed work, test status, and the upcoming task for the next cycle.

36
.cursor/rules/00-system-mandates.md
View File

@ -12,3 +12,39 @@
3. SINGLE SOURCE OF TRUTH: 3. SINGLE SOURCE OF TRUTH:
- Prior to modifying data structures, consult `docs/API_CONTRACTS/schema.sql` and `docs/ARCHITECTURE/01-OSAD-system-architecture.md`. - Prior to modifying data structures, consult `docs/API_CONTRACTS/schema.sql` and `docs/ARCHITECTURE/01-OSAD-system-architecture.md`.
- Update documentation in `/docs` concurrently with code changes. - Update documentation in `/docs` concurrently with code changes.
4. AUTONOMOUS TASK EXECUTION PROTOCOL:
When instructed to "Execute next task" or run an autonomous cycle, perform the following 7 steps in sequence:
Step 1: STATE DISCOVERY
- Read `.clinerules` and `docs/ARCHITECTURE/01-OSAD-system-architecture.md`.
- Inspect files in `docs/TASKS/` to locate the FIRST incomplete task (`[ ]`) in chronological order.
- Read `DECISION_LOG.md` to review the latest architectural context.
- Explicitly state the Task ID and title being tackled.
Step 2: FEATURE BRANCH CREATION
- Ensure working on `main` and updated: `git checkout main && git pull origin main`
- Create a dedicated feature branch: `git checkout -b feature/<task-id>-<short-description>`
Step 3: IMPLEMENTATION
- Read relevant specs in `/docs` (`schema.sql`, `security-and-crypto.md`, etc.).
- Write code required ONLY for the target task while respecting all local-first mandates.
Step 4: TESTING & VERIFICATION
- Run the local verification suite: `powershell -File scripts/verify_agent_work.ps1`
- Run crate unit tests: `cargo test --package <crate_name>`
- Iteratively fix any compiler or test errors until all checks pass cleanly.
Step 5: DOCUMENTATION & ADL UPDATE
- Update the task status to `[x]` in `docs/TASKS/`.
- If architectural decisions or schema adjustments were made, log them in `DECISION_LOG.md` and create a record in `docs/ARCHITECTURE/ADR/`.
Step 6: COMMIT & MERGE
- Stage changes: `git add .`
- Commit: `git commit -m "feat(<scope>): complete <Task ID> - <Task Title>"`
- Merge into main: `git checkout main && git merge feature/<task-id>-<short-description> --no-ff -m "chore: merge feature/<task-id> into main"`
Step 7: REMOTE PUSH & CLEANUP
- Push main: `git push origin main`
- Remove feature branch: `git branch -d feature/<task-id>-<short-description>`
- Provide a concise summary of completed work, test status, and the upcoming task for the next cycle.