Loading...
Loading...
Found 30 Skills
Documentation standards, API docs, and technical writing guidelines
Doctrine Extensions (Gedmo). Use when working with doctrine extensions.
Non-negotiable code quality standards for testing, structure, naming, error handling, and documentation
Use this skill whenever creating, updating, or reviewing a skill file. Do not wait for an explicit request — if a skill is being created or edited, this skill applies.
Create new skills, modify and improve existing skills. Use when users want to create a skill from scratch, edit or optimize an existing skill, turn a workflow into a reusable skill, or improve a skill's description for better triggering.
Create user-focused, SEO-optimized changelog entries for software releases. Use when writing release notes, version updates, product changelogs, or "what's new" documentation for developer tools.
This is a skill to check whether the content of CHANGELOG.md in a framework intended for external release is appropriate. It is used when updating or reviewing CHANGELOG.md.
Documentation guidelines for Mastra. This skill should be used when writing or editing documentation for Mastra. Triggers on tasks involving documentation creation or updates.
Use this skill whenever creating or editing any markdown file. Do not wait for an explicit request — if a markdown file is being created or edited, this skill applies.
Draft or update requirement documents under `easysdd/requirements/` for the project — describe a capability's "reason for existence, solution approach, and boundaries" using **user stories + plain language**, so non-technical readers can quickly grasp the key highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: when the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or when it is found during the feature-design phase that there is no corresponding requirement for the capability to be implemented this time.
Provides spec writing guidelines with 6 core areas and boundary system. Use when writing SPEC.md, defining requirements, creating project specifications, 요구사항 정의, or 스펙 작성.
TDD applied to documentation - create production-ready skills. Use when authoring new skills. Includes writing style guidelines for clear prose.