michele/periscope
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add Periscope Cursor engineering constitution and always-on rules.

Browse Source 
Docs-only: master CODING_CONSTITUTION plus seven .mdc splits. Git policy is
phase = test then commit+push; deploy only after a macro-phase.
This commit is contained in:
michele
2026-09-20 18:06:00 +02:00
parent 6d6e70cec0
commit 0533d4ebd2
8 changed files with 226 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.cursor/rules/40-testing.mdc
+16
View File
@@ -0,0 +1,16 @@
---
alwaysApply: true
---
# Periscope Cursor Engineering Rules
Mandatory for every Cursor agent working on Periscope. This section is copied from `docs/development/CODING_CONSTITUTION.md` and must not contradict that master.
## 4. Testing
- Write tests before considering a slice done. Prefer tests that lock behavior (graph topology, finding codes, via≠pad, review isolation) over tests that assert overlay stamps or file provenance comments.
- `pytest` from the worktree with the project venv. Do not claim green from a system Python missing deps.
- One malformed IC must not kill the whole review; keep per-IC isolation tests.
- Do not add tests whose only job is to require `Native Periscope overlay` in a copied file.
- UI changes: exercise the flow (not a single screenshot). If no browser tools, say what was not verified.
- Installing docs/rules is a docs phase: existence and internal consistency of the seven `.mdc` files plus this master is the check. There is no product pytest gate for markdown-only.