Loading...
Loading...
Found 750 Skills
Takes a campaign brief and submitted creator content description and produces a structured pass/fail checklist against every brief requirement. This skill should be used when checking if creator content matches the brief, reviewing influencer deliverables against requirements, auditing submitted content for brief compliance, verifying a creator hit all the brief requirements, running a content QA check before approval, comparing a draft to the original brief, grading content against campaign specifications, or reviewing creator submissions before giving approval. For converting raw feedback into a polished revision request to send to a creator, see content-approval-feedback-formatter. For FTC disclosure compliance specifically, see ftc-disclosure-spot-checker.
Core iOS/Swift development skills. Used when writing or modifying Swift/SwiftUI/UIKit code, designing UI architecture, optimizing performance, creating components, and handling navigation. Covers Swift coding specifications, SwiftUI best practices, UIKit development, navigation architecture (Coordinator/NavigationStack), animations, component design, and performance optimization.
Generates a 6-step frontend planning document pipeline (requirements → user flows → page spec → use cases → component tree → state/API integration) into docs/en/specifications/<domain>/, with domain analysis, tech stack detection, and user review gates at each step.
Manages persistent Knowledge Graph for specifications. Caches agent discoveries and codebase analysis to remember findings across sessions. Validates task dependencies, stores patterns, components, and APIs to avoid redundant exploration. Use when: you need to cache analysis results, remember findings, reuse previous discoveries, look up what we found, spec-to-tasks needs to persist codebase analysis, task-implementation needs to validate contracts, or any command needs to query existing patterns/components/APIs.
Specifications and Methods for Character and Scene Extraction
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.
Vue2 Frontend Code Review Assistant. Reviews code changes in the src directory of Vue2 projects. Covers 9 major dimensions: component specifications, code style, naming, logic, network requests, computed, security, best practices, and absolute prohibitions. Trigger scenarios: pre-merge review, pre-commit quality check, Code Review for Vue2 code.
Used for drafting or revising official documents of the administrative agencies of the Republic of China (letters, official letters, announcements, memoranda, etc.), correctly applying paragraph structures, terminology, and format rules in accordance with the Document Processing Manual and Reference Specifications for Government Document Formats. This skill is used when users need to write letters to government agencies, internal memoranda, announcements, meeting notices, or inquire about official document terminology, address terms, and expressions of expectations and purposes.
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
Technical specification and design document expert. Use when writing design docs, RFCs, ADRs, or evaluating technology choices. Covers C4 model, system design, and architecture documentation.
Reference guide for OpenAPI specification best practices, naming conventions, and expressing complex REST API patterns like polymorphism, enums, file uploads, and server-sent events. Use when writing or improving OpenAPI specs to ensure they follow established conventions and generate quality SDKs.
Use when a Spec Kit feature needs `spec.md` authored or rewritten from natural-language requirements, especially when the feature has no usable specification or requirements are too vague for planning.