Create Instructions md
# Create Instructions.md
## Purpose
Create a reusable instructions file for AI-assisted development sessions.
## When to Use
Use when a team wants consistent assistant behavior across tools and projects.
## Inputs Needed
- `<PROJECT_NAME>`
- `<TECH_STACK>`
- `<TASK>`
- `<CONSTRAINTS>`
- `<OUTPUT_FORMAT>`
## Prompt
Create an `instructions.md` file for AI-assisted work on `<PROJECT_NAME>`.
Tech stack: `<TECH_STACK>`
Primary task types: `<TASK>`
Constraints: `<CONSTRAINTS>`
The instructions should cover:
- How the assistant should inspect the repo.
- How it should propose and execute changes.
- How it should handle tests and validation.
- How it should summarize work.
- Security and privacy requirements.
- Rules for avoiding broad refactors unless requested.
Keep the file platform-agnostic so it works with GitHub Copilot Chat, Codex, Claude Code, Cursor, and similar tools.
Output format: `<OUTPUT_FORMAT>`
## Expected Output
A clean `instructions.md` draft with practical, reusable assistant guidance.
## Quality Rules
- Keep instructions generic and publishable.
- Include no credentials, private URLs, or internal names.
- Prefer specific verification behavior.
- Emphasize small focused sessions.when to use it
Community prompt sourced from the open-source GitHub repo nprasann/ai-engineering-prompt-templates (MIT). A "Create Instructions md" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
nprasann/ai-engineering-prompt-templates · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar