Project facts
Stack, package manager, deployment choice, build commands, and non-negotiable working rules.
LOCAL DEVELOPER TOOL · NO API REQUIRED
Turn the rules in your head into a project file your coding agent can follow. Enter your stack and boundaries; download a clear, reusable instruction file.
Developers need a repeatable way to state commands, code conventions, and hard boundaries—without writing the same setup document from scratch.
Stack, package manager, deployment choice, build commands, and non-negotiable working rules.
The browser inserts those choices into a concise Markdown structure. No project files are uploaded.
A ready-to-copy CLAUDE.md, AGENTS.md, or GEMINI.md file for the project root.
The first version solves the structured part reliably. A future “improve my existing file” feature can use an AI API only when users ask for it.
browser form → validated selections → Markdown template → copy / .md downloadThere is no user account, server database, secret key, or third-party API in this version. That keeps the privacy claim true, the response instant, and operating cost at zero.
The purpose, inputs, outputs, and limitations are stated in visible text. WebApplication and FAQ structured data express the same facts without fake claims or keyword padding.
It creates a starting Markdown file containing a project’s commands, architecture notes, and working rules. Review it before committing: a generator cannot know hidden project details.
Enter stable project facts: the stack, package manager, deployment target, and boundaries such as whether an agent may add dependencies or rewrite Git history.
Different coding assistants use different project-instruction conventions. This tool provides equivalent starting files so teams can maintain consistent rules.
No. This version creates Markdown from local form choices. It does not upload your project description or invoke an AI API.