Loading...
Loading...
Found 26 Skills
Read this skill before updating changelogs
Write, review, or improve Swift APIs using Swift API Design Guidelines for naming, argument labels, documentation comments, terminology, and general conventions. Use when designing new APIs, refactoring existing interfaces, or reviewing API clarity and fluency.
Create, update, or supersede architecture decision records under `architecture-decisions/`. Use when the user asks for ADR work or `spec-loop-plan-task` routes ADR writing.
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.
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
Write elegant, narrative-driven documentation that treats codebases and systems as exhibits worth exploring. Use when creating documentation for Wanderers and visitors who want to understand how Grove works. This is the "fancy" documentation style—warm, inviting, meant to be read and enjoyed.
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.
Documentation standards, API docs, and technical writing guidelines
Doctrine Extensions (Gedmo). Use when working with doctrine extensions.
Manage project rules and standards in docs/rules/. Use when creating coding standards, git conventions, style guides, or any enforceable project rules. Routes to specialized sub-skills for code, git, and infrastructure rules.
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.