Loading...
Loading...
Found 28 Skills
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.
TDD applied to documentation - create production-ready skills. Use when authoring new skills. Includes writing style guidelines for clear prose.
How to create and structure skills for this repository. Covers the type system (guideline vs pattern), frontmatter conventions, and behavioral instructions. Follow when creating or updating any skill.
Documentation guidelines for Mastra. This skill should be used when writing or editing documentation for Mastra. Triggers on tasks involving documentation creation or updates.
Write BDD test scenarios in Gherkin for a feature
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.
Guidelines for creating and modifying markdown files. Use when writing documentation, README files, or any markdown content.
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.
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.
Add an implementation requirement to the ***implementation reqs*** section of a ***plain spec file. Use when the user wants to add non-functional requirements like technology choices, architectural constraints, coding standards, data formats, error handling strategies, or any HOW-to-build guidance to a .plain file.
Use when you have specs or requirements for a multi-step task to break it down into detailed tasks, before executing it
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.