Loading...
Loading...
Found 1,952 Skills
Initialize the design system or create new UI components with accessibility, Tailwind/shadcn integration, and documentation. Use when setting up the initial design system, adding component categories, or creating complex UI components that need design review.
Provides up-to-date documentation and version guidance for external libraries. Use when working with any third-party library (JS, Python, Ruby, Go, .NET, etc.), when the user asks about a library-specific API or best practice, when debugging a dependency issue, or when installing or upgrading a dependency. Prefer this over guessing or relying on stale knowledge.
Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the marketplace, add or update documentation pages, or submit a PR to this project.
Explicit anti-rationalization enforcement for maximum-rigor task execution. Loads all anti-rationalization patterns, gate enforcement, and pressure resistance as a composable modifier on any task. Use when executing critical production changes, security-sensitive code, complex multi-file refactors, or any task where shortcuts could cause harm. Use for "with rigor", "carefully", "maximum verification", or "no shortcuts". Do NOT use for trivial lookups, documentation-only edits, or simple typo fixes where full gate enforcement would be disproportionate overhead.
Unified decision tree for web research and competitive monitoring. Auto-selects WebFetch, Tavily, or agent-browser based on target site characteristics and available API keys. Includes competitor page tracking, snapshot diffing, and change alerting. Use when researching web content, scraping, extracting raw markdown, capturing documentation, or monitoring competitor changes.
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. Part of the skills-for-java project
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
Navigue et interroge la documentation des composants frontend Hexagone (@his/hexa-components). À utiliser quand l'utilisateur pose des questions sur les composants Vue.js Hexagone, les patrons UI, les classes CSS beta-scss, les modules de store Vuex, les directives personnalisées, les règles de validation de formulaires ou le design system frontend Hexagone. Récupère la documentation optimisée LLM depuis le dépôt GitLab.
Firecrawl produces cleaner markdown than WebFetch, handles JavaScript-heavy pages, and avoids content truncation. This skill should be used when fetching URLs, scraping web pages, converting URLs to markdown, extracting web content, searching the web, crawling sites, mapping URLs, LLM-powered extraction, autonomous data gathering with the Agent API, or fetching AI-generated documentation for GitHub repos via DeepWiki. Provides complete coverage of Firecrawl v2.8.0 API endpoints including parallel agents, spark-1-fast model, and sitemap-only crawling.
Answer customer questions about Apollo products (OSS and enterprise) using public documentation and GraphOS MCP Tools. Use this skill when: (1) a customer asks a question about Apollo Router, Server, Client, GraphOS, Federation, Connectors, Rover, or MCP Server, (2) triaging a support question from Slack, Jira, or another channel, (3) researching Apollo product capabilities or configuration, (4) helping a customer troubleshoot an Apollo-related issue.
Query the official CrewAI documentation for answers. Use when the user has a CrewAI question that isn't fully covered by the getting-started, design-agent, design-task skills — e.g., specific API details, configuration options, advanced features, troubleshooting errors, enterprise features, tool references, or anything where the latest docs are the best source of truth.