element-definition-convention

Naming conventions standardize plugin elements by enforcing kebab-case format for agents, skills, and commands. This Skill validates that your component names follow the team standard, making them predictable and reducing future refactoring when new developers onboard or components scale.

Plugin elements require mandatory frontmatter fields: name and description. This Skill ensures all agents, skills, and commands include these fields, improving discoverability and providing context for AI systems and human reviewers to understand component purpose immediately.

Documentation structure requires specific sections—Overview, Responsibilities, Basic Policy—written in plain Japanese style with bullet points. This Skill enforces these sections across all plugin elements, ensuring uniform clarity and making onboarding predictable for new contributors.

Yes. This Skill automatically validates agent, skill, and command definitions against standardized naming, frontmatter, and documentation format rules. It generates checklists and templates for authoring, catching inconsistencies before publication and preventing downstream refactoring.

Validation fails and the Skill generates a checklist of missing or incorrect elements—naming violations, absent frontmatter fields, or incomplete required sections. You then correct these issues using the provided templates before your definitions can be published.