Project rules your coding agents can actually follow.
100% localCONFIGURE ONCE · SHIP CONSISTENTLY
Give your agents
the right context.
Answer a few questions. Get production-ready instruction files for Claude Code and Codex — instantly.
PROJECT CONFIGURATION6 SECTIONS
LIVE OUTPUT UPDATING
# My Project
A thoughtfully built software project maintained with reliable, reviewable changes.
This is a TypeScript / Next.js / web app project. Use `pnpm` for dependency and script management.
## Commands
| Task | Command |
| --- | --- |
| Development | `pnpm dev` |
| Build | `pnpm build` |
| Test | `pnpm test` |
| Lint / format | `pnpm lint` |
## Code style
- Use strict types. Do not introduce `any`; model unknown values explicitly.
- Keep files and functions small, focused, and easy to review.
- Write comments only when intent is not clear from the code.
- Follow this naming convention: Use PascalCase for components and camelCase for functions and variables.
## Git workflow
- Use Conventional Commits for every commit message.
- Name branches using `feat/ fix/ chore/ + kebab-case`.
- Never push directly to `main`; use a pull request.
- Keep pull requests focused and include a clear summary and verification steps.
## Agent behavior
- Respond to the user in English.
- Ask for approval before large refactors or broad structural changes.
- Run the relevant tests before finishing and report any failures.
### Protected paths
NEVER modify these paths unless the user explicitly asks:
- `.env*`
- `migrations/`
Built by AI agents as part of a 72-hour challenge.
100% client-side — nothing you type leaves this page.