To maintain the high quality and uniformity of this skills library, all contributions must adhere to the following strict rules:
- One Skill = One Folder: Every skill must live in its own directory under the appropriate category inside
skills/. - Must Include
SKILL.md: The core file must be namedSKILL.mdand placed at the root of the skill folder. Optional files likeexamples.mdorreferences.mdare permitted. - Must Follow the Schema: The
SKILL.mdfile must strictly adhere toschema/SKILL_SCHEMA.md, including frontmatter and exact header names. - Define Usage Conditions: You must clearly state the exact conditions for activation in the "When to use" section.
- No Overlap: Your skill must cover a unique pattern. It must not overlap with existing skills in the repository.
- Manually Testable: Every skill's workflow must act as a mental checklist that a human developer can manually test and execute.
- No Vague Advice: "Write clean code" is not a skill. Provide concrete, actionable rules and hard constraints.