AGENTS.md Contributor Guide
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
Build, Test, and Development Commands
- 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.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: agents-writer3description: Use when creating or updating AGENTS.md contributor guidelines for this repository.4---56# AGENTS.md Contributor Guide78Generate a file named AGENTS.md that serves as a contributor guide for this repository.910Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section.1112Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project.1314# Document Requirements1516- Title the document "Repository Guidelines".17- Use Markdown headings (#, ##, etc.) for structure.18- Keep the document concise. 200-400 words is optimal.19- Keep explanations short, direct, and specific to this repository.20- Provide examples where helpful (commands, directory paths, naming patterns).21- Maintain a professional, instructional tone.2223# Recommended Sections2425## Build, Test, and Development Commands2627- Specify indentation rules, language-specific style preferences, and naming patterns.28- Include any formatting or linting tools used.2930## Testing Guidelines3132- Identify testing frameworks and coverage requirements.33- State test naming conventions and how to run tests.3435## Commit & Pull Request Guidelines3637- Summarize commit message conventions found in the project’s Git history.38- Outline pull request requirements (descriptions, linked issues, screenshots, etc.).3940(Optional) Add other sections if relevant, such as Security & Configuration Tips, Architecture Overview, or Agent-Specific Instructions.4142---43> Converted and distributed by [TomeVault](https://tomevault.io/claim/narumiruna) — claim your Tome and manage your conversions.44<!-- tomevault:4.0:skill_md:2026-04-11 -->