Loading...
Loading...
Found 1,952 Skills
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.
Provides rules for handling multi-language documentation. Use this when configuring agent skill documents using starlight-skills on an i18n-enabled project. Do not use this for standard single-language sites or plugin configuration options.
[Documentation] Create or update business feature documentation in docs/business-features/{Module}/. Generates comprehensive 26-section docs with verified code evidence and AI companion files. Triggers on: feature docs, business feature documentation, module documentation, document feature, update feature docs, ai companion, ai context file, quick feature docs, feature readme, single file docs, verified documentation.
Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting. Use when users request technical documentation, API docs, API references, code examples, or developer documentation.
When the boundaries are clear, directly implement code, tests and necessary documentation, and complete the implementation and closure with minimal interruptions
Maintains persistent codebase knowledge across sessions through a structured knowledge graph stored in a local Obsidian vault (.doctrack/). Use this skill whenever you have just made meaningful code changes (new features, modified components, refactoring, bug fixes) to update the project's documentation. Also use it when the user asks to document code, update docs, sync documentation, initialize documentation for an existing project, or when you want to understand the existing codebase structure at the start of a session. This skill should be used proactively after any significant code modification — don't wait for the user to ask. If you changed code, update the docs. Think of it as your long-term memory system: read before working, write after changing. Also use this when a user says "doctrack init", "doctrack refresh", "refresh docs", "update docs", "sync docs", "initialize docs", "document this project", or wants to bootstrap documentation for a codebase that has no .doctrack/ vault yet.
Progressive Domain Crystallization (PDC) — a skill for building and maintaining a living domain knowledge base for any custom business application. Use this skill whenever the user is developing a business application and wants the AI to accumulate understanding of internal terminology, entities, relationships, and business rules over time — especially when that knowledge is not fully defined upfront and grows across sessions. Trigger on any of: "remember how our system works", "learn our domain", "track business entities", "build domain knowledge", "understand our terminology", "grow AI context over time", "domain model", "business rules documentation", or whenever a user says the AI doesn't understand their business-specific language or data model. Also use at the start of any session where a DOMAIN.md file exists in the project — always read it before doing any work.
Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state—Anchor/native programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.
Process and transform markdown documents. Convert to HTML, extract headings, generate TOC, check links. Use when working with documentation or markdown content.