Loading...
Loading...
Found 376 Skills
OpenAPI Specification 3.2 — write and interpret OpenAPI descriptions (OAD), paths, operations, parameters, request/response, schema (JSON Schema 2020-12), security, and extensions. Use when authoring or validating OpenAPI 3.2 documents.
This skill should be used when the user wants to visualize data. It intelligently selects the most suitable chart type from 26 available options, extracts parameters based on detailed specifications, and generates a chart image using a JavaScript script.
This skill should be used when the user asks to "create a PRD for Replit", "write product requirements", "document app specifications", "prepare a product spec", or needs a comprehensive specification document that Replit Agent can use for complex, multi-feature applications. Creates structured PRDs optimized for AI-powered development.
Visual design guidance for bold, minimal presentations. Provides layout patterns, typography hierarchy, color specifications, and slide composition rules. Use when asking "how should this slide look?", "design guidance for...", "what layout for this slide?", or when translating content into visual structure for a presentation.
Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.
To be used when users mention mystery, detective, crime or suspense narratives - Provides genre specifications, clue placement, and fair play principles for mystery novels
OAuth 2.0/2.1 specification expert with deep RFC knowledge and Fastify integration patterns
Professional 12306 train ticket schedule inquiry skill, supporting accurate station selection, date specification and train information retrieval. Using verified browser operation SOP processes and direct URL parameter query strategy to ensure the accuracy of query results. Suitable for scenarios where users need to query train schedules, ticket availability, train times and other 12306-related inquiries.
Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization. Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL. Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.
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.
Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs.
Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations. Invoke for legacy analysis, code archaeology, undocumented features.