Cleanup safety model: risk classes, plan and confirmation
Risk classification, review and confirmation before cleanup.
Development manual
An agent-first application, developed with ProjectStore.
This project is both a Mac utility and a worked example of development with humans and agents. Contributions made with your own agent are welcome.
People set goals and approve decisions. Agents help plan, implement, challenge proposals and review changes. The shared vault keeps the context available across contributors and sessions.
- Project memory
- DeepDriveCleaner-projectstore
- Interface designs
- Claude Artifact
- Agent reference
- Agent notes (plain text)
How a change is developed
Code and project memory are separate repositories. Start with the vault, check for overlapping work and follow the project's gates.
- ArtifactWrite a story with acceptance criteria. Record significant decisions in an ADR; add a spec when needed.
- CriticA fresh-context critic checks the proposal before implementation. A human approves the artifact.
- PlannerRead the code map and existing implementation to decide where the change belongs.
- ImplementationBuild the agreed behavior and run checks relevant to the change.
- ReviewerAn independent reviewer compares the diff with the acceptance criteria. Record evidence before closing the story.
Contributor setup
Full contributing guide ↗Requirements: Node.js 20 or later. Run setup in a regular terminal, outside an agent session. Clone the two repositories side by side.
1.Clone and bind the project
git clone https://github.com/SmartAndPoint/DeepDriveCleaner.git git clone https://github.com/SmartAndPoint/DeepDriveCleaner-projectstore.git cd DeepDriveCleaner npx projectstore setup --vault ../DeepDriveCleaner-projectstore
2.Start Claude Code or Codex
Start your agent inside the DeepDriveCleaner code directory. Give it this orientation prompt before asking it to change code:
Where are we? Read AGENTS.md and the bound ProjectStore vault. Summarize active epics, open stories and relevant decisions. Help me choose a small contribution and check for overlapping work. Follow the project's artifact, critic, planner and reviewer gates. Propose the next step before changing code.
Review the interface designs in Claude Artifact before proposing UI changes. ↗
3.Keep the change reviewable
Agree on a story, keep the diff focused and attach relevant validation. Coordinate code and vault pull requests so the reviewer can follow the intent and implementation.
make check- Rust changes: formatting, clippy and tests.
make app-test- App logic changes: DDCKit tests.
Project records
Browse the vault ↗Status snapshot: 28 October 2026. The vault is the source of truth. Titles below retain their original English.
Rust core: library + CLI with JSON output
The shared engine and its command-line boundary.
Faster clean: re-check only what the selection needs
Parent epic: Menu bar app. A performance change with explicit cleanup-check constraints.
License and contribution terms
The code is source-available under PolyForm Noncommercial 1.0.0. Contributions also grant SmartAndPoint the right to use, modify and relicense them, including commercially. Read the original terms before contributing.
