vrr/OmniRoute
2
0
Fork 0
mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-04-28 06:19:46 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
OmniRoute/GEMINI.md
diegosouzapw adf59ddce7 chore(scripts): add scratch maintenance utilities and ai workspace rules 
Add one-off database inspection and cleanup scripts under
`scripts/scratch/` for local debugging and maintenance work.

Document root cleanliness and file placement expectations for AI
assistants in `GEMINI.md` to keep temporary scripts and tests out of
the project root.
2026-04-16 16:07:44 -03:00

1.1 KiB
Raw Blame History

Security and Cleanliness Rules for AI Assistants

1. File Placement & Organization

  • Test Files: ALL unit tests, integration tests, ecosystem tests, or Vitest files MUST strictly be placed within the tests/ directory (e.g., tests/unit/, tests/integration/). NEVER create test files in the project root (/).
  • Scripts and Utilities: ALL maintenance, debugging, generation, or experimental scripts (.cjs, .mjs, .js, .ts) MUST be placed strictly inside the scripts/ directory or scripts/scratch/ for temporary one-offs. NEVER dump loose scripts in the project root (/).

The Project Root MUST ONLY CONTAIN:

  • Configuration files (vitest.config.ts, next.config.mjs, eslint.config.mjs, etc.)
  • Dependency files (package.json, package-lock.json)
  • Documentation files (README.md, CHANGELOG.md, AGENTS.md)
  • CI/CD files and ignore definitions (.gitignore, .dockerignore)

When creating any validation tests or one-off logic scripts, default to using scripts/scratch/ or the tests/unit/ directories according to your goals. Do not pollute the / root context.