PUBLIC · DOCUMENTATION

Draft project instructions an agent can follow

Capture conventions, boundaries, and verification in a concise Markdown file.

When to use it

When an assistant will work in a repository more than once and keeps relearning the same conventions.

What to expect

A concise instruction file grounded in the repository's own commands and conventions, with rules separated from suggestions and boundaries stated.

Example

A monorepo with one package manager, a test command per package, and a folder that must never be edited by hand.

Add your context

Optional. Leave fields blank to copy a reusable template. What you type stays in this tab.

repositorytool and supported filenamecommandsconventionsboundaries

PROMPT TEMPLATE

Draft a project instruction Markdown file for {{REPOSITORY}}.

Intended tool and filename: {{TOOL_AND_FILENAME}}
Verified project commands: {{VERIFIED_COMMANDS}}
Repository conventions: {{CONVENTIONS}}
Sensitive or restricted areas: {{BOUNDARIES}}

Use repository evidence to describe structure, setup, coding conventions, validation, and change boundaries. Distinguish rules from suggestions. Include guidance to preserve unrelated changes and report unverified outcomes.

Keep instructions concise and specific. Do not invent commands, override higher-priority instructions, embed secrets, or assume one tool reads another tool’s filename. Return the Markdown and any assumptions needing confirmation.

5 of 5 context fields remaining.

Free to copy. Use it in the tools you already have.

← Back to the library