generic-skill-creator-structure

The standard skill unit folder structure requires a defined folder placement and a SKILL.md file that adheres to canonical naming conventions and formatting rules. This structure ensures operational consistency and discoverability across the project.

You validate a markdown skill file by checking its YAML frontmatter and content sections against project-specific constraints for generic, mobile, and backend skill types. This ensures the skill adheres to required naming and structural conventions.

A SKILL.md file requires specific content sections including Context, Instructions, Steps, and Constraints. These sections guide the necessary documentation to maintain best practices and standardize skill creation.

Yes, this skill structure template validates against project-specific constraints for generic, mobile, and backend skill types. It enforces adherence to defined YAML frontmatter and markdown content formats for each platform.

You need YAML frontmatter in skill markdown files to enforce discoverability and operational consistency. It establishes a canonical structure that standardizes skill creation and validation across the project.

No, you must use the specified naming conventions based on domain and platform. Enforcing naming conventions standardizes skill creation and ensures all skill units maintain operational consistency before submission.