55 skills pour piloter Claude Code.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Modélisation business générique tout secteur : business model canvas, market sizing TAM/SAM/SOM, financial modeling pour un objectif de CA, plan de conquête, économie par canal, pricing, P&L cible, BFR, scénarios de trajectoire, stress-test, états financiers, modèle financier startup 3-5 ans. Agnostique, pose les questions de cadrage avant de modéliser. Charge-le pour chiffrer, modéliser, projeter ou planifier un business : 'modèle économique', 'BMC', 'comment atteindre X€', 'TAM SAM SOM', 'P&L', 'point mort', 'pricing', 'pitch chiffré'.

Trame pour construire un skill de connaissance d'entreprise : positionnement, produit, équipe, ICP, ton de marque, processes. Charge ce skill quand tu veux créer un skill dédié à une boîte (la tienne, un client, un partenaire) qui devient la source de vérité pour tout draft (email, pitch, contenu, propale) dans son contexte. Couvre la structure type, les sections à remplir, les sources à connecter (Notion, site, Drive), et le mode d'invocation. À forker pour chaque boîte que tu suis sérieusement.

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

Veille concurrentielle et de marché générique, tout secteur : profilage de concurrents depuis leurs URLs (offres, positionnement, pricing) et routine de veille (signaux, mouvements marché). Charge ce skill pour profiler des concurrents ou faire de la veille, hors contexte Exoteach.