Codex & Coding Advanced Codex

Codex AGENTS.md Project Instructions Generator

Create a clear AGENTS.md instruction file for Codex that defines project context, coding rules, safety requirements, verification commands, file boundaries, and development workflows.

Browse more prompts
Best forCoding
ToolCodex
DifficultyAdvanced
Copied10 times
Full Prompt
You are an expert software engineering lead and Codex workflow designer.

Your task is to create a practical AGENTS.md file that helps Codex or an AI coding assistant work safely and effectively inside a software project.

The AGENTS.md file should give the AI assistant clear project instructions, coding standards, file boundaries, verification commands, safety rules, and workflow expectations.

Context:
Project name: [Project name]
Project purpose: [Project purpose]
Tech stack: [Tech stack]
Frameworks and libraries: [Frameworks and libraries]
Repository structure: [Repository structure]
Important directories: [Important directories]
Files or folders Codex may edit: [Files or folders Codex may edit]
Files or folders Codex must not edit: [Files or folders Codex must not edit]
Coding standards: [Coding standards]
Testing commands: [Testing commands]
Build commands: [Build commands]
Lint commands: [Lint commands]
Deployment or cache commands: [Deployment or cache commands]
Environment details without secrets: [Environment details without secrets]
Security rules: [Security rules]
Known risks or fragile areas: [Known risks or fragile areas]
Preferred workflow: [Preferred workflow]
Definition of done: [Definition of done]

Important constraints:
- Do not include secrets, tokens, credentials, private keys, or sensitive environment values.
- Do not invent commands if they are not provided.
- If a command is unknown, write a placeholder and explain that the project owner should fill it in.
- Keep instructions practical and specific to the project.
- Avoid generic AI instructions that do not help with actual coding work.
- Make the AGENTS.md file useful for future Codex sessions.

Task:
1. Analyze the project context.
2. Create a complete AGENTS.md draft.
3. Add task workflow instructions.
4. Add safety boundaries.
5. Add verification section.
6. Add final reporting format.

Output format:
## AGENTS.md Draft
Provide the full copy-ready AGENTS.md content.

## Missing Information
List anything the project owner should still provide.

## Suggested Improvements
Suggest optional improvements to make future Codex work safer and more reliable.

Verification:
Before finalizing, check that no secrets are included, instructions are project-specific, editing boundaries are clear, verification commands are present or marked as placeholders, and the AGENTS.md file can be copied directly into the repository root.

Begin by generating the AGENTS.md draft.

Variables to Replace

  • Project name
  • Project purpose
  • Tech stack
  • Frameworks and libraries
  • Repository structure
  • Important directories
  • Files or folders Codex may edit
  • Files or folders Codex must not edit
  • Coding standards
  • Testing commands
  • Build commands
  • Lint commands
  • Deployment or cache commands
  • Environment details without secrets
  • Security rules
  • Known risks or fragile areas
  • Preferred workflow
  • Definition of done

How to Use This Prompt

Replace the placeholders with your project details, then run the prompt in Codex or ChatGPT. Copy the generated AGENTS.md file into your repository root and adjust any missing commands or project-specific rules.

Example Use Case

A Laravel founder wants Codex to work more safely inside a production web app. They provide the tech stack, important folders, cache commands, files that must not be touched, and verification commands. The prompt produces a reusable AGENTS.md file that guides future Codex sessions.

Build stronger AI systems

Use Amo.ng prompts as reusable building blocks, then go deeper with RichlyAI training and tools.

RichlyAI Learn RichlyAI Hub

Related Prompts

Browse all