Loading...
Loading...
Found 24 Skills
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
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.
Apply Swift API Design Guidelines to name, label, and document Swift APIs. Covers argument label rules (prepositional phrase rule, grammatical phrase rule, first-label omission), mutating/nonmutating pair naming (-ed/-ing participle pattern, form- prefix, sort/sorted, formUnion/union), side-effect naming (noun for pure, verb for mutating), documentation comment structure (summary by declaration kind, O(1) complexity rule), clarity at call site, role-based naming, protocol naming (-able/-ible/-ing), default arguments over method families, casing conventions, and terminology. Use when designing new Swift APIs, reviewing naming and argument labels, writing documentation comments, or refactoring for call site clarity.
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.
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.
TDD applied to documentation - create production-ready skills. Use when authoring new skills. Includes writing style guidelines for clear prose.
Write or update backend feature documentation that follows a repo's DOCUMENTATION_GUIDELINES.md (or equivalent) across any project. Use when asked to create/update module docs, API contracts, or backend documentation that must include architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.
Rewrite Rust documentation comments to ensure all documentation and comments are in English, following rustdoc guidelines. Use when the user wants to clean up Rust documentation, translate Chinese comments to English, fix missing documentation, or ensure rustdoc compliance in a Rust codebase.
Write a bounded fresh-context prompt or file for continuation, implementation, research, refactor, bugfix, review, or review-fix work.
Write or rewrite the repo-root README.md.