generic-agent-creator-structure

The standard agent file structure enforces a flat directory layout within the `agents/` folder. It mandates specific naming conventions and requires mandatory content sections like Identity, Knowledge, and Instructions for each agent definition file.

Agent files must follow a strict naming pattern based on domain, platform, and concern. For example, a generic API specification reviewer agent should be named `generic-api-spec-reviewer.md` to maintain project consistency.

To create a project-agnostic generic agent, place a flat markdown file in the `agents/` directory. Ensure the file includes mandatory frontmatter and content sections such as Identity, Knowledge, and Instructions as defined by the structure standard.

No, the agent structure standard specifies a flat file structure. All agent files must reside directly in the `agents/` directory without nested subfolders to simplify creation, review, and maintenance.

Required content sections for an agent definition file include Identity, Knowledge, and Instructions. These mandatory sections ensure the agent has a clear template and adheres to project standards for generic agents.

Standardizing agent file naming and folder placement ensures consistency and adherence to project standards. This practice simplifies agent creation, code review, and long-term maintenance across different generic agents.