doc:rtfm
Lit la documentation technique - RTFM (Read The Fucking Manual)
What this skill does
# Configuration de sortie ## Instructions à Exécuter **IMPORTANT : Exécute ce workflow étape par étape :** **IMPORTANT** : Cette skill génère une synthèse de documentation structurée et nécessite un format de sortie spécifique. Lis le frontmatter de cette skill. Si un champ `output-style` est présent, exécute immédiatement : ``` /output-style <valeur-du-champ> ``` *Note : Une fois que le champ `output-style` sera supporté nativement par Claude Code, cette instruction pourra être supprimée.* **Output-style requis** : `markdown-focused` # Documentation Reader - RTFM ## Purpose Force Claude à lire et comprendre la documentation technique fournie, que ce soit via une URL directe ou en recherchant une documentation par nom. ## Variables DOC_SOURCE: L'URL ou le nom de la documentation à lire ## Instructions - Si une URL est fournie directement, utilise WebFetch pour la lire - Si un nom de documentation est fourni, utilise WebSearch pour la trouver puis WebFetch pour la lire - Force Claude à lire complètement la documentation avant de répondre - Fournis un résumé structuré des points clés ## Relevant Files - Documentation externe via WebFetch/WebSearch ## Codebase Structure Cette commande ne modifie pas le codebase, elle lit uniquement la documentation externe. ## Workflow - Si DOC_SOURCE commence par http/https, utilise directement WebFetch - Sinon, recherche la documentation avec WebSearch puis lis le résultat avec WebFetch - Parse et structure l'information de la documentation - Fournis un résumé concis et actionnable ## Expertise - Lecture et analyse de documentation technique - Extraction d'informations clés - Synthèse et structuration de contenu ## Template ``` # Documentation: [NOM] ## Résumé [Résumé concis en 2-3 phrases] ## Points clés - Point important 1 - Point important 2 - Point important 3 ## Exemples pratiques [Exemples d'usage si disponibles] ## Liens utiles [Références additionnelles si pertinentes] ``` ## Examples - `/rtfm https://docs.anthropic.com/claude/reference` - Lit directement la documentation Claude - `/rtfm symfony doctrine` - Recherche et lit la documentation Symfony Doctrine - `/rtfm php 8.3 new features` - Recherche les nouvelles fonctionnalités PHP 8.3 ## Report Résumé structuré de la documentation lue avec points clés et exemples pratiques.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.