Purpose: This file contains STRICT, ENFORCEABLE rules for AI agents working on Dissect project.
AI agents MUST read this file at the START of every session, BEFORE any other action.
Project CANNOT exceed 10% progress until Mom Test is COMPLETE.
Every project MUST track progress in SESSION_SUMMARY.md with PESSIMISTIC estimates.
Every session MUST update SESSION_SUMMARY.md with BOTH English and French versions.
All code MUST have minimum 60% test coverage. No exceptions.
All code MUST pass security scans before commit.
If any step fails, the agent MUST report it and retry.
AI agents are CO-ENGINEERS, not typists. Push back on bad ideas.
Emojis are FORBIDDEN in ALL project files, code, comments, documentation. No exceptions.
Certain files MUST be in .gitignore and NEVER committed publicly.
When rules are updated in ANY project, SYNC to ~/Documents/kuro-rules (master copy).
Every project MUST have a roadmap file (PLAN.md or ROADMAP.md) and all development MUST follow it.
Every roadmap MUST have a minimum duration of one month with clearly defined phases.
At progress milestones (25%, 50%, 75%, 90%, 95%), the product MUST be validated through Mom Test and Marketing Test before continuing.
When ANY rule file is updated, ALL rule files MUST be updated to include the same rule.
AI agents MUST proactively identify and remove unused, outdated, or obsolete files, folders, and residues from the repository before and during any coding session.
| Category | Examples |
|---|---|
| Dated Files | Old log files, timestamped backups, deprecated feature files |
| Unused Files | Dead code, unused modules, orphaned test files |
| Old Residues | Temporary files, cache folders, build artifacts (.pyc, pycache) |
| Unnecessary Folders | Empty directories, duplicate folders, obsolete feature folders |
BEFORE starting any coding session:
1. SCAN: List all files in the repository
2. IDENTIFY: Look for files with dates in names, old versions, deprecated features
3. VERIFY: Check each file is still used/necessary
4. REPORT: List any unused/outdated items to user
5. DELETE: Remove only after user confirmation
All session summaries from ALL projects MUST be consolidated in a central location for easy reference and cross-project intelligence.
~/Documents/docs/
~/Documents/docs/
├── session_summaries/
│ ├── project-name-1/
│ │ ├── 2025-01-15.md
│ │ └── ...
│ └── README.md
└── SYNC_LOG.md
- Every session from every project MUST create a summary in this central folder
- Naming convention:
YYYY-MM-DD-project-name.md - Bilingual: Each summary must include both English and French sections
- Central Sync: Copy session summaries here after each session ends
| Rule | Consequence of Violation |
|---|---|
| Rule 1 (Read First) | STOP and read rules |
| Rule 2 (Mom Test) | STOP implementation, complete deliverables |
| Rule 3 (Progress) | Recalculate with pessimistic estimate |
| Rule 4 (Session Summary) | Create summary immediately |
| Rule 5 (Testing) | STOP features, write tests |
| Rule 6 (Security) | STOP commit, fix vulnerabilities |
| Rule 7 (No Silent Failures) | Report and retry |
| Rule 8 (Critical Thinking) | Apply questions retroactively |
| Rule 9 (No Emojis) | REMOVE emojis immediately |
| Rule 10 (File Protection) | Remove from git, add to .gitignore |
| Rule 11 (Sync) | Sync to kuro-rules immediately |
| Rule 12 (Roadmap) | STOP and create PLAN.md |
| Rule 13 (Roadmap Duration) | STOP and expand plan if < 1 month |
| Rule 14 (Periodic Validation) | STOP and conduct validation |
| Rule 15 (Rule Sync) | SYNC immediately |
| Rule 34 (Repo Hygiene) | LIST and DELETE unused files |
| Rule 35 (Central Summaries) | COPY to ~/Documents/docs/ |
These rules are NON-NEGOTIABLE. They exist to ensure:
- User problems are validated before building solutions
- Code quality meets professional standards
- Security is never compromised
- Progress is accurately tracked
- Knowledge persists across sessions