Loading...
Loading...
Found 195 Skills
Write and research technical documentation. Cover information architecture, style guides, API documentation, user research, content strategy, and documentation operations. Triggers on "write technical documentation", "create API docs", "developer tutorial", "information architecture", "style guide", "content strategy", "documentation audit", "user research", or "technical writing". Developer learning programs and curriculum: developer-education-lead.
Guides creation and modification of ASP.NET Core Web API endpoints with correct HTTP semantics, OpenAPI metadata, and error handling. USE FOR: adding new API endpoints (controllers or minimal APIs), wiring up OpenAPI/Swagger, creating .http test files, setting up global error handling middleware. DO NOT USE FOR: general C# coding style, EF Core data access or query optimization (use optimizing-ef-core-queries), frontend/Blazor work, gRPC services, or SignalR hubs.
Use when the task involves an external library or package and current API docs are needed before writing code.
Automatically generate comprehensive backend API documentation in AGENTS.md format. Use when the user requests to: (1) Document backend API endpoints, (2) Update backend API specifications after code changes, (3) Create or refresh backend/AGENTS.md with complete API documentation including request/response schemas, business rules, and authentication details, (4) Generate API documentation from FastAPI route files
Generate comprehensive AGENTS.md documentation for backend projects with complete API specifications, business rules, data models, and data flows. Use when (1) Creating AGENTS.md from existing CLAUDE.md, (2) Documenting backend API modules with FastAPI routes, (3) Migrating documentation to AGENTS.md/CLAUDE.md symlink structure, (4) Adding complete API interface documentation to existing specs, (5) Creating module-level AGENTS.md for specific features (mcp, teamo_code, file_system, etc.)
Implement API versioning with backward compatibility, deprecation notices, and migration paths. Use when managing API versions and backward compatibility. Trigger with phrases like "version the API", "manage API versions", or "handle API versioning".
USE FOR web search. Returns ranked results with snippets, URLs, thumbnails. Supports freshness filters, SafeSearch, Goggles for custom ranking, pagination. Primary search endpoint.
Generate videos from text and image prompts via Together AI. 15+ models including Veo 2/3, Sora 2, Kling 2.1, Hailuo 02, Seedance, PixVerse, Vidu. Supports text-to-video, image-to-video, keyframe control, and reference images. Use when users want to generate videos, create video content, animate images, or work with any video generation task.
Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the boundary, idempotency, ETag concurrency, HTTP caching, error handling, security, API documentation, controller advice, and problem details for errors. Part of the skills-for-java project
Generate reference documentation entry by entry for the public surface of a library (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental difference from guidedoc: guidedoc teaches you how to use something, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When the user says "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are discovered after feature-acceptance.
Use when the user wants to extract, generate, refine, or harden an OpenAPI or Swagger specification from an existing API application, service, project, repo, routes, controllers, handlers, or codebase. Select this skill for any request whose intent is to derive, extract, generate, reverse-engineer, infer, document, or harden an OpenAPI or Swagger contract from an existing application or source code. This includes generic prompts about producing an API spec/docs/schema/contract for an existing app, project, service, repo, endpoints, routes, or controllers. Prefer this skill over extraction-only skills when the prompt is about an existing application or codebase and the expected outcome is an accurate extracted contract plus post-extraction refinement.
Generate API documentation from source code with JSDoc and OpenAPI support