Loading
Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project.
Recommended by author
This prompt takes no variables — just pick a model and run.
--- name: 'Tui: tui-init-command' category: tui codex_version: rust-v0.128.0-alpha.1 codex_commit: 8148b7b1f8660e464661743587f754471ae60868 source: path: codex-rs/tui/prompt_for_init_command.md kind: include_str reached_from: - slash_dispatch.rs:159 extraction: pass: 1 method: file variables: [] tokens: o200k_base: 322 description: '`codex-rs/tui/prompt_for_init_command.md`' --- Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project. Document Requirements - Title the document "Repository Guidelines". - Use Markdown headings (#, ##, etc.) for structure. - Keep the document concise. 200-400 words is optimal. - Keep explanations short, direct, and specific to this repository. - Provide examples where helpful (commands, directory paths, naming patterns). - Maintain a professional, instructional tone. Recommended Sections Project Structure & Module Organization - Outline the project structure, including where the source code, tests, and assets are located. Build, Test, and Development Commands - List key commands for building, testing, and running locally (e.g., npm test, make build). - Briefly explain what each command does. Coding Style & Naming Conventions - Specify indentation rules, language-specific style preferences, and naming patterns. - Include any formatting or linting tools used. Testing Guidelines - Identify testing frameworks and coverage requirements. - State test naming conventions and how to run tests. Commit & Pull Request Guidelines - Summarize commit message conventions found in the project’s Git history. - Outline pull request requirements (descriptions, linked issues, screenshots, etc.). (Optional) Add other sections if relevant, such as Security & Configuration Tips, Architecture Overview, or Agent-Specific Instructions.
Running prompts needs a free account.
Sign in and we'll stream the response from Claude Sonnet 4.6 right here — no config needed for the platform models.
Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project.
--- name: 'Tui: tui-init-command' category: tui codex_version: rust-v0.128.0-alpha.1 codex_commit: 8148b7b1f8660e464661743587f754471ae60868 source: path: codex-rs/tui/prompt_for_init_command.md kind: include_str reached_from: - slash_dispatch.rs:159 extraction: pass: 1 method: file variables: [] tokens: o200k_base: 322 description: '`codex-rs/tui/prompt_for_init_command.md`' --- Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project. Document Requirements - Title the document "Repository Guidelines". - Use Markdown headings (#, ##, etc.) for structure. - Keep the document concise. 200-400 words is optimal. - Keep explanations short, direct, and specific to this repository. - Provide examples where helpful (commands, directory paths, naming patterns). - Maintain a professional, instructional tone. Recommended Sections Project Structure & Module Organization - Outline the project structure, including where the source code, tests, and assets are located. Build, Test, and Development Commands - List key commands for building, testing, and running locally (e.g., npm test, make build). - Briefly explain what each command does. Coding Style & Naming Conventions - Specify indentation rules, language-specific style preferences, and naming patterns. - Include any formatting or linting tools used. Testing Guidelines - Identify testing frameworks and coverage requirements. - State test naming conventions and how to run tests. Commit & Pull Request Guidelines - Summarize commit message conventions found in the project’s Git history. - Outline pull request requirements (descriptions, linked issues, screenshots, etc.). (Optional) Add other sections if relevant, such as Security & Configuration Tips, Architecture Overview, or Agent-Specific Instructions.