Loading...
Loading...
Found 34 Skills
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.
Enforcement skill for consistent documentation standards
Read this skill before updating changelogs
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
A clear, concise description of what this skill does (1-2 sentences). Focus on the VALUE it provides to the user.
Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.
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.
Writing technical blog posts about tldraw features and implementation details. Use when creating blog content about how tldraw solves interesting problems.
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.
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.
A collection of technical writing rules to significantly improve the quality of your writing. Achieve professional writing quality by eliminating redundant expressions, avoiding repeated sentence endings, correctly distinguishing between kanji and hiragana, using active voice, and placing subjects and predicates close together, among other practices. This must be referenced for all tasks involving text output or generation. Applicable tasks include creating PR descriptions, writing technical documents, design documents, specifications, and procedure manuals, updating README/CLAUDE.md/Confluence pages, generating commit messages, summarizing survey results and specifications, outputting in Markdown, improving and reviewing existing text, etc. This skill is triggered by all requests involving text output, such as "write", "create", "compose", "summarize", "add to", "output", "improve", "review", "document", "create a PR", "output in Markdown", etc. Refer to this skill even for short instructions or implicit text generation tasks. Explicit mention of the skill name is not required.
Curated documentation reference for developers building with Pinecone. Contains links to official docs organized by topic and data format references. Use when writing Pinecone code, looking up API parameters, or needing the correct format for vectors or records.