@webmcp-auto-ui/agent 2.5.8 → 2.5.10

package/src/recipes/_generated.ts

@@ -3,49 +3,49 @@
 export const RAW_RECIPES: Record<string, string> = {
   'afficher-oeuvres-art-collection-musee': `---
 id: afficher-oeuvres-art-collection-musee
-name: Afficher les oeuvres d'art d'une collection de musee en galerie visuelle
+name: Display artworks from a museum collection in a visual gallery
 components_used: [gallery, cards, kv, stat-card]
-when: l'utilisateur demande des oeuvres d'art, des collections de musee, des tableaux, sculptures ou objets d'art du Metropolitan Museum of Art
+when: the user asks for artworks, museum collections, paintings, sculptures, or art objects from the Metropolitan Museum of Art
 servers: [metmuseum]
 layout:
   type: grid
   columns: 2
-  arrangement: stats en haut, galerie pleine largeur au centre, details en bas
+  arrangement: stats at top, full-width gallery in the center, details at the bottom
 ---
 
-## Quand utiliser
+## When to use
 
-L'utilisateur s'interesse a des oeuvres d'art ou des collections de musee :
-- "Montre-moi des tableaux impressionnistes du Met Museum"
-- "Les sculptures grecques du Metropolitan"
-- "Quelles oeuvres de Van Gogh sont au Met ?"
-- "Les oeuvres d'art egyptien du musee"
-- "Cherche des estampes japonaises"
+The user is interested in artworks or museum collections:
+- "Show me Impressionist paintings from the Met Museum"
+- "Greek sculptures at the Metropolitan"
+- "What Van Gogh works are at the Met?"
+- "Egyptian art objects from the museum"
+- "Search for Japanese woodblock prints"
 
-Le serveur Met Museum donne acces a la collection du Metropolitan Museum of Art de New York (plus de 470 000 oeuvres, dont beaucoup avec images en domaine public).
+The Met Museum server provides access to the Metropolitan Museum of Art collection in New York (more than 470,000 objects, many with public domain images).
 
-## Comment
+## How to use
 
-1. **Rechercher les oeuvres** par theme, artiste ou departement :
+1. **Search for artworks** by theme, artist, or department:
    \`\`\`
    search_objects({query: "impressionism sunflower", hasImages: true})
    \`\`\`
-   Retourne une liste d'\`objectID\`s.
+   Returns a list of \`objectID\`s.
 
-2. **Recuperer les details** de chaque oeuvre (limiter a 5-10 pour la performance) :
+2. **Fetch the details** of each artwork (limit to 5-10 for performance):
    \`\`\`
    get_object({objectID: 436524})
    \`\`\`
-   Retourne : \`title\`, \`artistDisplayName\`, \`primaryImage\`, \`objectDate\`, \`medium\`, \`department\`, \`culture\`, etc.
+   Returns: \`title\`, \`artistDisplayName\`, \`primaryImage\`, \`objectDate\`, \`medium\`, \`department\`, \`culture\`, etc.
 
-3. **Afficher les statistiques** de la recherche :
+3. **Display search statistics**:
    \`\`\`
-   component("stat-card", {label: "Resultats", value: total, icon: "image"})
-   component("stat-card", {label: "Avec image", value: withImage, icon: "camera"})
-   component("stat-card", {label: "Domaine public", value: publicDomain, icon: "unlock"})
+   component("stat-card", {label: "Results", value: total, icon: "image"})
+   component("stat-card", {label: "With image", value: withImage, icon: "camera"})
+   component("stat-card", {label: "Public domain", value: publicDomain, icon: "unlock"})
    \`\`\`
 
-4. **Galerie des oeuvres** avec images haute definition :
+4. **Artwork gallery** with high-resolution images:
    \`\`\`
    component("gallery", {
      images: objects
@@ -58,124 +58,124 @@ Le serveur Met Museum donne acces a la collection du Metropolitan Museum of Art
    })
    \`\`\`
 
-5. **Fiches detaillees** en cards pour les oeuvres principales :
+5. **Detailed cards** for the main artworks:
    \`\`\`
    component("cards", {
      items: objects.map(o => ({
        title: o.title,
-       subtitle: o.artistDisplayName || "Artiste inconnu",
+       subtitle: o.artistDisplayName || "Unknown artist",
        image: o.primaryImageSmall,
        body: [o.objectDate, o.medium, o.department].filter(Boolean).join(" — ")
      }))
    })
    \`\`\`
 
-6. **Details d'une oeuvre specifique** en kv :
+6. **Details of a specific artwork** in kv:
    \`\`\`
    component("kv", {pairs: [
-     ["Titre", obj.title],
-     ["Artiste", obj.artistDisplayName],
+     ["Title", obj.title],
+     ["Artist", obj.artistDisplayName],
      ["Date", obj.objectDate],
      ["Medium", obj.medium],
      ["Dimensions", obj.dimensions],
-     ["Departement", obj.department],
+     ["Department", obj.department],
      ["Culture", obj.culture],
      ["Credit", obj.creditLine],
-     ["Domaine public", obj.isPublicDomain ? "Oui" : "Non"]
+     ["Public domain", obj.isPublicDomain ? "Yes" : "No"]
    ]})
    \`\`\`
 
-## Exemples
+## Examples
 
-### Tableaux de Van Gogh
+### Van Gogh paintings
 \`\`\`
-// 1. Recherche
+// 1. Search
 search_objects({query: "van gogh", hasImages: true})  // → [436532, 436529, ...]
 
-// 2. Details (premiers 8 resultats)
+// 2. Details (first 8 results)
 objectIDs.slice(0, 8).forEach(id => get_object({objectID: id}))
 
-// 3. Rendu
-component("stat-card", {label: "Oeuvres de Van Gogh", value: "8", icon: "palette"})
+// 3. Render
+component("stat-card", {label: "Van Gogh works", value: "8", icon: "palette"})
 component("gallery", {images: vanGoghWorks.map(w => ({src: w.primaryImageSmall, alt: w.title, caption: w.objectDate}))})
 component("cards", {items: vanGoghWorks.map(w => ({title: w.title, subtitle: w.objectDate, image: w.primaryImageSmall, body: w.medium}))})
 \`\`\`
 
-### Art egyptien
+### Egyptian art
 \`\`\`
-// 1. Recherche par departement
+// 1. Search by department
 search_objects({query: "egypt pharaoh", departmentId: 10, hasImages: true})
 
-// 2. Rendu avec metadonnees culturelles
+// 2. Render with cultural metadata
 component("gallery", {images: egyptWorks.map(w => ({src: w.primaryImageSmall, alt: w.title}))})
-component("table", {columns: ["Titre", "Periode", "Culture", "Medium"], rows: egyptDetails})
-component("kv", {pairs: [["Departement", "Egyptian Art"], ["Source", "Met Museum — Open Access"]]})
+component("table", {columns: ["Title", "Period", "Culture", "Medium"], rows: egyptDetails})
+component("kv", {pairs: [["Department", "Egyptian Art"], ["Source", "Met Museum — Open Access"]]})
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Trop d'appels \`get_object\`** : la recherche retourne parfois des centaines d'IDs — limiter a 5-10 appels detail pour la performance
-- **Oeuvres sans image** : beaucoup d'objets Met n'ont pas de \`primaryImage\` — toujours filtrer avec \`hasImages: true\` dans la recherche ou verifier le champ
-- **Images haute resolution cassees** : utiliser \`primaryImageSmall\` (web-large) pour la galerie et les cards — les URLs \`primaryImage\` (original) retournent souvent des 404
-- **Oublier la licence** : les oeuvres en domaine public (\`isPublicDomain: true\`) peuvent etre affichees librement, les autres ont un champ \`rights\` a respecter
-- **Artiste inconnu** : beaucoup d'oeuvres anciennes n'ont pas d'\`artistDisplayName\` — afficher "Artiste inconnu" ou la culture/periode a la place
+- **Too many \`get_object\` calls**: a search sometimes returns hundreds of IDs — limit to 5-10 detail calls for performance
+- **Artworks without images**: many Met objects have no \`primaryImage\` — always filter with \`hasImages: true\` in the search or check the field
+- **Broken high-resolution images**: use \`primaryImageSmall\` (web-large) for the gallery and cards — \`primaryImage\` (original) URLs often return 404s
+- **Forgetting the license**: works in the public domain (\`isPublicDomain: true\`) can be displayed freely; others have a \`rights\` field to respect
+- **Unknown artist**: many ancient works have no \`artistDisplayName\` — display "Unknown artist" or the culture/period instead
 `,
   'analyser-actualites-hacker-news': `---
 id: analyser-actualites-hacker-news
-name: Analyser les actualites et tendances Hacker News en tableau et graphiques
+name: Analyze Hacker News news and trends with tables and charts
 components_used: [table, chart, stat-card, cards]
-when: l'utilisateur demande les actualites tech, les tendances Hacker News, les top stories, ou une analyse des discussions et commentaires HN
+when: the user asks for tech news, Hacker News trends, top stories, or an analysis of HN discussions and comments
 servers: [hackernews]
 layout:
   type: grid
   columns: 2
-  arrangement: stats en ligne, table pleine largeur, chart en bas
+  arrangement: stats in a row, full-width table, chart at the bottom
 ---
 
-## Quand utiliser
+## When to use
 
-L'utilisateur s'interesse aux actualites technologiques ou aux tendances de la communaute Hacker News :
-- "Quelles sont les top stories Hacker News ?"
-- "Montre-moi les posts les plus commentes aujourd'hui"
-- "Les tendances tech de la semaine sur HN"
-- "Analyse les Ask HN recents"
-- "Quels sujets dominent Hacker News en ce moment ?"
+The user is interested in technology news or Hacker News community trends:
+- "What are the top Hacker News stories?"
+- "Show me the most commented posts today"
+- "This week's tech trends on HN"
+- "Analyze recent Ask HN posts"
+- "What topics are dominating Hacker News right now?"
 
-Le serveur Hacker News donne acces aux stories, commentaires, classements et metadonnees de posts.
+The Hacker News server provides access to stories, comments, rankings, and post metadata.
 
-## Comment
+## How to use
 
-1. **Recuperer les top stories** :
+1. **Fetch the top stories**:
    \`\`\`
    get_top_stories({limit: 30})
    \`\`\`
-   Retourne les IDs des stories les plus populaires.
+   Returns the IDs of the most popular stories.
 
-2. **Recuperer les details** de chaque story :
+2. **Fetch the details** of each story:
    \`\`\`
    get_item({id: storyId})
    \`\`\`
-   Retourne : \`title\`, \`url\`, \`score\`, \`by\` (auteur), \`descendants\` (nb commentaires), \`time\`, \`type\`.
+   Returns: \`title\`, \`url\`, \`score\`, \`by\` (author), \`descendants\` (comment count), \`time\`, \`type\`.
 
-3. **Afficher les KPIs** en stat-cards :
+3. **Display KPIs** in stat-cards:
    \`\`\`
    component("stat-card", {label: "Top Stories", value: "30", icon: "newspaper"})
-   component("stat-card", {label: "Score moyen", value: Math.round(avgScore), icon: "trending-up"})
-   component("stat-card", {label: "Commentaires moyen", value: Math.round(avgComments), icon: "message-circle"})
-   component("stat-card", {label: "Score max", value: maxScore + " pts", icon: "award"})
+   component("stat-card", {label: "Average score", value: Math.round(avgScore), icon: "trending-up"})
+   component("stat-card", {label: "Average comments", value: Math.round(avgComments), icon: "message-circle"})
+   component("stat-card", {label: "Max score", value: maxScore + " pts", icon: "award"})
    \`\`\`
 
-4. **Tableau des stories** trie par score :
+4. **Stories table** sorted by score:
    \`\`\`
    component("table", {
-     columns: ["#", "Titre", "Score", "Commentaires", "Auteur"],
+     columns: ["#", "Title", "Score", "Comments", "Author"],
      rows: stories.sort((a, b) => b.score - a.score).map((s, i) => [
        i + 1, s.title, s.score, s.descendants, s.by
      ])
    })
    \`\`\`
 
-5. **Graphique de distribution** des scores :
+5. **Score distribution chart**:
    \`\`\`
    component("chart", {
      type: "bar",
@@ -184,105 +184,105 @@ Le serveur Hacker News donne acces aux stories, commentaires, classements et met
    })
    \`\`\`
 
-6. **Cards pour les stories vedettes** (top 5) :
+6. **Cards for featured stories** (top 5):
    \`\`\`
    component("cards", {
      items: top5.map(s => ({
        title: s.title,
        subtitle: s.by + " — " + s.score + " points",
-       body: s.descendants + " commentaires | " + new Date(s.time * 1000).toLocaleDateString(),
+       body: s.descendants + " comments | " + new Date(s.time * 1000).toLocaleDateString(),
        url: s.url
      }))
    })
    \`\`\`
 
-## Exemples
+## Examples
 
-### Top 10 stories du moment
+### Top 10 stories right now
 \`\`\`
-// 1. Recuperer
+// 1. Fetch
 get_top_stories({limit: 10})
-// Pour chaque ID: get_item({id})
+// For each ID: get_item({id})
 
-// 2. Rendu
-component("stat-card", {label: "Score total", value: totalScore, icon: "zap"})
-component("stat-card", {label: "Commentaires total", value: totalComments, icon: "message-circle"})
+// 2. Render
+component("stat-card", {label: "Total score", value: totalScore, icon: "zap"})
+component("stat-card", {label: "Total comments", value: totalComments, icon: "message-circle"})
 component("table", {
-  columns: ["Rang", "Titre", "Score", "Commentaires", "Auteur", "Age"],
+  columns: ["Rank", "Title", "Score", "Comments", "Author", "Age"],
   rows: rankedStories
 })
 component("cards", {items: top3Stories})
 \`\`\`
 
-### Analyse Ask HN
+### Ask HN analysis
 \`\`\`
-// 1. Rechercher les Ask HN recents
+// 1. Fetch recent Ask HN posts
 get_ask_stories({limit: 20})
 
-// 2. Rendu
-component("stat-card", {label: "Ask HN recents", value: "20", icon: "help-circle"})
-component("stat-card", {label: "Reponses moyennes", value: avgReplies, icon: "message-circle"})
-component("table", {columns: ["Titre", "Reponses", "Score", "Auteur"], rows: askStories})
-component("chart", {type: "bar", labels: titles, datasets: [{label: "Reponses", data: replyCounts}]})
+// 2. Render
+component("stat-card", {label: "Recent Ask HN", value: "20", icon: "help-circle"})
+component("stat-card", {label: "Average replies", value: avgReplies, icon: "message-circle"})
+component("table", {columns: ["Title", "Replies", "Score", "Author"], rows: askStories})
+component("chart", {type: "bar", labels: titles, datasets: [{label: "Replies", data: replyCounts}]})
 \`\`\`
 
-### Tendances par domaine
+### Trends by domain
 \`\`\`
-// 1. Recuperer top stories et extraire les domaines des URLs
+// 1. Fetch top stories and extract domains from URLs
 get_top_stories({limit: 50})
 
-// 2. Grouper par domaine
+// 2. Group by domain
 const domains = groupBy(stories, s => new URL(s.url).hostname)
 
-// 3. Rendu
-component("stat-card", {label: "Domaines uniques", value: Object.keys(domains).length, icon: "globe"})
+// 3. Render
+component("stat-card", {label: "Unique domains", value: Object.keys(domains).length, icon: "globe"})
 component("chart", {type: "bar", labels: topDomains.map(d => d.name), datasets: [{label: "Stories", data: topDomains.map(d => d.count)}]})
-component("table", {columns: ["Domaine", "Stories", "Score total"], rows: domainStats})
+component("table", {columns: ["Domain", "Stories", "Total score"], rows: domainStats})
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Trop d'appels \`get_item\`** : chaque story necessite un appel individuel — limiter a 20-30 pour eviter la lenteur
-- **Timestamps non convertis** : HN retourne des timestamps Unix — convertir en dates lisibles
-- **Titres tronques dans les graphiques** : les titres HN sont longs — tronquer a 30-40 caracteres pour les labels de graphiques
-- **Oublier les stories sans URL** : les "Ask HN", "Show HN" et "Tell HN" n'ont pas toujours d'URL externe — gerer ce cas
-- **Ne pas distinguer les types** : HN a des stories, jobs, polls — filtrer par type si l'utilisateur demande un type specifique
+- **Too many \`get_item\` calls**: each story requires an individual call — limit to 20-30 to avoid slowness
+- **Unconverted timestamps**: HN returns Unix timestamps — convert them to human-readable dates
+- **Truncated titles in charts**: HN titles are long — truncate to 30-40 characters for chart labels
+- **Forgetting stories without a URL**: "Ask HN", "Show HN", and "Tell HN" posts don't always have an external URL — handle this case
+- **Not distinguishing types**: HN has stories, jobs, and polls — filter by type if the user asks for a specific type
 `,
   'cartographier-observations-biodiversite': `---
-id: cartographier-observations-biodiversite
-name: Cartographier les observations de biodiversite sur une zone geographique
+id: map-biodiversity-observations
+name: Map biodiversity observations on a geographic area
 components_used: [map, gallery, table, stat-card]
-when: l'utilisateur demande une carte des observations naturalistes, la biodiversite d'une zone, les especes presentes dans un lieu, ou les observations iNaturalist d'une region
+when: the user asks for a map of naturalist observations, the biodiversity of an area, the species present in a location, or iNaturalist observations in a region
 servers: [inaturalist]
 layout:
   type: grid
   columns: 2
-  arrangement: carte pleine largeur en haut, galerie + stats en dessous
+  arrangement: full-width map at top, gallery + stats below
 ---
 
-## Quand utiliser
+## When to use
 
-L'utilisateur pose une question sur la biodiversite d'un lieu ou demande une carte des observations :
-- "Quelles especes d'oiseaux observe-t-on a Paris ?"
-- "Montre-moi une carte des observations de papillons dans les Alpes"
-- "Quelle est la biodiversite autour du lac d'Annecy ?"
-- "Les especes menacees observees en Ile-de-France"
+The user asks a question about the biodiversity of a location or requests a map of observations:
+- "What bird species are observed in Paris?"
+- "Show me a map of butterfly observations in the Alps"
+- "What is the biodiversity around Lake Annecy?"
+- "Endangered species observed in Ile-de-France"
 
-Le serveur iNaturalist fournit des observations georeferencees avec photos, taxons, dates et observateurs.
+The iNaturalist server provides georeferenced observations with photos, taxa, dates, and observers.
 
-## Comment
+## How to use
 
-1. **Rechercher les observations** dans la zone cible :
+1. **Search for observations** in the target area:
    \`\`\`
    search_observations({lat: 48.85, lng: 2.35, radius: 10, taxon_name: "Aves", per_page: 50})
    \`\`\`
-   Parametres utiles :
-   - \`lat\`, \`lng\`, \`radius\` : centre et rayon de la zone en km
-   - \`taxon_name\` : filtre taxonomique ("Aves", "Lepidoptera", "Mammalia", etc.)
-   - \`quality_grade\` : "research" pour les observations verifiees
-   - \`per_page\` : nombre de resultats (max 200)
+   Useful parameters:
+   - \`lat\`, \`lng\`, \`radius\`: center and radius of the area in km
+   - \`taxon_name\`: taxonomic filter ("Aves", "Lepidoptera", "Mammalia", etc.)
+   - \`quality_grade\`: "research" for verified observations
+   - \`per_page\`: number of results (max 200)
 
-2. **Afficher la carte** avec les marqueurs d'observation :
+2. **Display the map** with observation markers:
    \`\`\`
    component("map", {
      center: [48.85, 2.35],
@@ -296,15 +296,15 @@ Le serveur iNaturalist fournit des observations georeferencees avec photos, taxo
    })
    \`\`\`
 
-3. **Statistiques de la zone** en stat-cards :
+3. **Area statistics** in stat-cards:
    \`\`\`
    component("stat-card", {label: "Observations", value: total_results, icon: "eye"})
-   component("stat-card", {label: "Especes uniques", value: uniqueSpecies.length, icon: "leaf"})
-   component("stat-card", {label: "Observateurs", value: uniqueObservers.length, icon: "users"})
-   component("stat-card", {label: "Grade recherche", value: researchGradeCount, icon: "check-circle"})
+   component("stat-card", {label: "Unique species", value: uniqueSpecies.length, icon: "leaf"})
+   component("stat-card", {label: "Observers", value: uniqueObservers.length, icon: "users"})
+   component("stat-card", {label: "Research grade", value: researchGradeCount, icon: "check-circle"})
    \`\`\`
 
-4. **Galerie des especes avec photos** :
+4. **Species gallery with photos**:
    \`\`\`
    component("gallery", {
      images: observations
@@ -317,105 +317,105 @@ Le serveur iNaturalist fournit des observations georeferencees avec photos, taxo
    })
    \`\`\`
 
-5. **Tableau recapitulatif** des especes :
+5. **Summary table** of species:
    \`\`\`
    component("table", {
-     columns: ["Espece", "Nom scientifique", "Observations", "Derniere obs."],
+     columns: ["Species", "Scientific name", "Observations", "Last obs."],
      rows: speciesSummary
    })
    \`\`\`
 
-## Exemples
+## Examples
 
-### Oiseaux de Paris
+### Birds of Paris
 \`\`\`
-// 1. Recherche
+// 1. Search
 search_observations({lat: 48.8566, lng: 2.3522, radius: 10, taxon_name: "Aves", quality_grade: "research", per_page: 100})
 
-// 2. Rendu
+// 2. Render
 component("map", {center: [48.8566, 2.3522], zoom: 12, markers: birdMarkers})
-component("stat-card", {label: "Especes d'oiseaux", value: "47", icon: "bird"})
-component("stat-card", {label: "Observations verifiees", value: "312", icon: "check"})
+component("stat-card", {label: "Bird species", value: "47", icon: "bird"})
+component("stat-card", {label: "Verified observations", value: "312", icon: "check"})
 component("gallery", {images: birdPhotos})
-component("table", {columns: ["Espece", "Observations", "Derniere"], rows: birdSummary})
+component("table", {columns: ["Species", "Observations", "Last"], rows: birdSummary})
 \`\`\`
 
-### Papillons des Alpes
+### Butterflies in the Alps
 \`\`\`
-// 1. Zone large autour de Chamonix
+// 1. Wide area around Chamonix
 search_observations({lat: 45.9237, lng: 6.8694, radius: 30, taxon_name: "Lepidoptera", per_page: 100})
 
-// 2. Rendu avec clustering sur la carte
+// 2. Render with clustering on the map
 component("map", {center: [45.9237, 6.8694], zoom: 10, markers: butterflyMarkers, cluster: true})
-component("stat-card", {label: "Especes de papillons", value: uniqueSpecies.length})
+component("stat-card", {label: "Butterfly species", value: uniqueSpecies.length})
 component("gallery", {images: butterflyPhotos})
-component("table", {columns: ["Espece", "Altitude", "Mois", "Observateur"], rows: enrichedData})
+component("table", {columns: ["Species", "Altitude", "Month", "Observer"], rows: enrichedData})
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Rayon trop large** : un rayon de 100 km retourne trop de resultats et noie l'information — preferer 5-20 km et augmenter si peu de resultats
-- **Thumbnails iNaturalist** : les URLs par defaut sont en format "square" (75x75) — remplacer "square" par "medium" (200px) ou "large" (500px)
-- **Pas de filtre taxonomique** : sans filtre, iNaturalist retourne plantes + animaux + champignons ensemble — toujours filtrer par groupe si l'utilisateur en mentionne un
-- **Oublier le grade de qualite** : les observations "casual" peuvent etre mal identifiees — preferer \`quality_grade: "research"\` pour des donnees fiables
-- **Carte sans zoom adapte** : ajuster le zoom en fonction du rayon de recherche (5 km → zoom 13, 20 km → zoom 11, 50 km → zoom 9)
+- **Radius too large**: a 100 km radius returns too many results and buries the information — prefer 5-20 km and increase if few results are found
+- **iNaturalist thumbnails**: default URLs are in "square" format (75x75) — replace "square" with "medium" (200px) or "large" (500px)
+- **No taxonomic filter**: without a filter, iNaturalist returns plants + animals + fungi together — always filter by group if the user mentions one
+- **Forgetting the quality grade**: "casual" observations may be misidentified — prefer \`quality_grade: "research"\` for reliable data
+- **Map with wrong zoom level**: adjust zoom based on the search radius (5 km → zoom 13, 20 km → zoom 11, 50 km → zoom 9)
 `,
   'cross-server': `---
-id: croiser-donnees-de-plusieurs-serveurs-mcp-connectes
-name: Croiser les donnees de plusieurs serveurs MCP connectes simultanement
+id: cross-reference-data-from-multiple-connected-mcp-servers
+name: Cross-reference data from multiple simultaneously connected MCP servers
 components_used: [map, gallery, table, kv, stat-card]
-when: la question de l'utilisateur necessite de combiner des donnees provenant de plusieurs serveurs MCP connectes, par exemple croiser geolocalisation et observations, ou enrichir des donnees parlementaires avec Wikipedia
+when: the user's question requires combining data from multiple connected MCP servers, for example cross-referencing geolocation and observations, or enriching parliamentary data with Wikipedia
 servers: []
 layout:
   type: grid
   columns: 2
 ---
 
-## Quand utiliser
+## When to use
 
-L'utilisateur pose une question qui ne peut etre satisfaite par un seul serveur MCP. Exemples :
-- "Quels oiseaux peut-on observer pres du Louvre ?" → geocoding + iNaturalist
-- "Montre-moi la meteo et les observations naturalistes a Marseille" → Open-Meteo + iNaturalist
-- "Compare les oeuvres du Met Museum sur le theme des fleurs avec les especes observees a New York" → Met Museum + iNaturalist
-- "Donne-moi le profil Wikipedia du depute qui a depose le plus d'amendements" → Tricoteuses + Wikipedia
+The user asks a question that cannot be answered by a single MCP server. Examples:
+- "What birds can be spotted near the Louvre?" → geocoding + iNaturalist
+- "Show me the weather and nature observations in Marseille" → Open-Meteo + iNaturalist
+- "Compare artworks from the Met Museum on the theme of flowers with species observed in New York" → Met Museum + iNaturalist
+- "Give me the Wikipedia profile of the MP who filed the most amendments" → Tricoteuses + Wikipedia
 
-La recette s'applique des que 2+ serveurs MCP sont necessaires pour repondre.
+This recipe applies whenever 2+ MCP servers are needed to answer the question.
 
-## Comment
+## How to use
 
-1. **Identifier quels serveurs MCP fournissent quelles donnees** :
-   - Serveur A fournit les donnees de reference (coordonnees, IDs, noms)
-   - Serveur B enrichit avec des donnees complementaires
-2. **Appeler le premier serveur** pour obtenir les donnees de base :
+1. **Identify which MCP servers provide which data**:
+   - Server A provides reference data (coordinates, IDs, names)
+   - Server B enriches with complementary data
+2. **Call the first server** to obtain the base data:
    \`\`\`
-   // Exemple : geocoder un lieu
+   // Example: geocode a location
    geocode({query: "Louvre, Paris"}) → {lat: 48.8606, lon: 2.3376}
    \`\`\`
-3. **Utiliser les resultats comme input** pour le deuxieme serveur :
+3. **Use the results as input** for the second server:
    \`\`\`
-   // Exemple : chercher les observations dans un rayon
+   // Example: search for observations within a radius
    search_observations({lat: 48.8606, lng: 2.3376, radius: 5, taxon: "Aves"})
    \`\`\`
-4. **Combiner les resultats** dans une visualisation coherente :
-   - \`component("map", ...)\` si des coordonnees sont impliquees (marqueurs des deux sources)
-   - \`component("table", ...)\` pour les resultats combines avec colonnes des deux sources
-   - \`component("gallery", ...)\` si les deux sources fournissent des images
-5. **Toujours citer les sources** avec un composant \`kv\` final :
+4. **Combine the results** in a coherent visualization:
+   - \`component("map", ...)\` if coordinates are involved (markers from both sources)
+   - \`component("table", ...)\` for combined results with columns from both sources
+   - \`component("gallery", ...)\` if both sources provide images
+5. **Always cite the sources** with a final \`kv\` component:
    \`\`\`
-   component("kv", {pairs: [["Source 1", "iNaturalist"], ["Source 2", "Open-Meteo"], ["Zone", "5 km autour du Louvre"]]})
+   component("kv", {pairs: [["Source 1", "iNaturalist"], ["Source 2", "Open-Meteo"], ["Area", "5 km around the Louvre"]]})
    \`\`\`
 
-## Exemples
+## Examples
 
-### Oiseaux pres d'un monument (geocoding + iNaturalist)
+### Birds near a landmark (geocoding + iNaturalist)
 \`\`\`
-// 1. Geocoder le lieu
+// 1. Geocode the location
 geocode({query: "Tour Eiffel, Paris"}) → lat: 48.8584, lon: 2.2945
 
-// 2. Chercher les observations d'oiseaux
+// 2. Search for bird observations
 search_observations({lat: 48.8584, lng: 2.2945, radius: 3, taxon_name: "Aves"})
 
-// 3. Rendu combine
+// 3. Combined render
 component("map", {
   center: [48.8584, 2.2945],
   zoom: 14,
@@ -423,164 +423,164 @@ component("map", {
     .concat(observations.map(o => ({lat: o.lat, lon: o.lon, label: o.species_guess})))
 })
 component("gallery", {images: observations.flatMap(o => o.photos.map(p => ({src: p.url, alt: o.species_guess})))})
-component("table", {columns: ["Espece", "Date", "Distance", "Observateur"], rows: formattedObs})
-component("stat-card", {label: "Especes distinctes", value: "23", icon: "bird"})
+component("table", {columns: ["Species", "Date", "Distance", "Observer"], rows: formattedObs})
+component("stat-card", {label: "Distinct species", value: "23", icon: "bird"})
 \`\`\`
 
-### Profil enrichi (Tricoteuses + Wikipedia)
+### Enriched profile (Tricoteuses + Wikipedia)
 \`\`\`
-// 1. Chercher le depute le plus actif
+// 1. Find the most active MP
 query_sql({sql: "SELECT depute, COUNT(*) as nb FROM amendements GROUP BY depute ORDER BY nb DESC LIMIT 1"})
 
-// 2. Enrichir avec Wikipedia
+// 2. Enrich with Wikipedia
 search_wikipedia({query: depute.nom})
 
-// 3. Rendu combine
+// 3. Combined render
 component("profile", {name: depute.nom, subtitle: depute.groupe, details: wikipedia.extract})
-component("stat-card", {label: "Amendements deposes", value: depute.nb})
-component("kv", {pairs: [["Source parlementaire", "Tricoteuses"], ["Biographie", "Wikipedia"]]})
+component("stat-card", {label: "Amendments filed", value: depute.nb})
+component("kv", {pairs: [["Parliamentary source", "Tricoteuses"], ["Biography", "Wikipedia"]]})
 \`\`\`
 
-### Meteo + Biodiversite dans une region
+### Weather + Biodiversity in a region
 \`\`\`
-// 1. Meteo pour Marseille
+// 1. Weather for Marseille
 get_forecast({latitude: 43.2965, longitude: 5.3698, daily: "temperature_2m_max"})
 
-// 2. Observations naturalistes
+// 2. Nature observations
 search_observations({lat: 43.2965, lng: 5.3698, radius: 20})
 
-// 3. Dashboard combine
-component("stat-card", {label: "Temperature max", value: "26°C", icon: "thermometer"})
-component("stat-card", {label: "Observations recentes", value: "412", icon: "eye"})
+// 3. Combined dashboard
+component("stat-card", {label: "Max temperature", value: "26°C", icon: "thermometer"})
+component("stat-card", {label: "Recent observations", value: "412", icon: "eye"})
 component("map", {center: [43.2965, 5.3698], markers: observations})
 component("chart", {type: "line", labels: dates, datasets: [{label: "Temperature", data: temps}, {label: "Observations", data: obsCounts}]})
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Faire plus de 3 appels DATA sans render intermediaire** : l'utilisateur attend des resultats visuels entre les etapes
-- **Ne pas expliquer quels serveurs sont utilises** : toujours afficher les sources avec un \`kv\`
-- **Melanger les donnees sans structure** : les resultats combines doivent etre dans un tableau ou une carte coherente, pas un dump brut
-- **Oublier de gerer les cas sans correspondance** : si le geocoding ne trouve rien, ou si iNaturalist n'a pas d'observations dans la zone, l'afficher clairement
+- **Making more than 3 DATA calls without an intermediate render**: the user expects visual results between steps
+- **Not explaining which servers are being used**: always display the sources with a \`kv\`
+- **Mixing data without structure**: combined results must be in a coherent table or map, not a raw dump
+- **Forgetting to handle no-match cases**: if geocoding finds nothing, or if iNaturalist has no observations in the area, display that clearly
 `,
   'dashboard-kpi': `---
-id: composer-tableau-de-bord-kpi-depuis-metriques-agregees
-name: Composer un tableau de bord KPI a partir de metriques agregees
+id: compose-kpi-dashboard-from-aggregated-metrics
+name: Compose a KPI dashboard from aggregated metrics
 components_used: [stat-card, chart, table, kv]
-when: les donnees MCP contiennent des metriques numeriques, compteurs, totaux, pourcentages ou statistiques agregees qui meritent un tableau de bord visuel
+when: MCP data contains numeric metrics, counters, totals, percentages, or aggregated statistics that warrant a visual dashboard
 servers: []
 layout:
   type: grid
   columns: 3
-  arrangement: stat-cards en ligne, chart + table en dessous
+  arrangement: stat-cards in a row, chart + table below
 ---
 
-## Quand utiliser
+## When to use
 
-Les resultats MCP contiennent des metriques numeriques qu'il faut presenter de facon synthetique. Cette recette est transversale : elle s'applique quel que soit le serveur MCP, des lors que les donnees contiennent :
-- Des totaux, compteurs ou moyennes (revenus, nombre d'articles, participation, etc.)
-- Des pourcentages ou ratios (taux de churn, participation electorale, etc.)
-- Des series temporelles de metriques (evolution mois par mois, trimestre par trimestre)
-- Des ventilations par categorie (par groupe politique, par pays, par type d'objet)
+MCP results contain numeric metrics that need to be presented concisely. This recipe is cross-cutting: it applies regardless of the MCP server, as long as the data contains:
+- Totals, counters, or averages (revenue, article count, participation, etc.)
+- Percentages or ratios (churn rate, voter turnout, etc.)
+- Time series of metrics (month-over-month, quarter-over-quarter trends)
+- Breakdowns by category (by political group, by country, by object type)
 
-## Comment
+## How to use
 
-1. **Identifier les 3-5 KPIs principaux** dans les donnees retournees par le serveur MCP
-2. **Afficher chaque KPI en stat-card** avec formatage soigne :
+1. **Identify the 3–5 main KPIs** in the data returned by the MCP server
+2. **Display each KPI as a stat-card** with clean formatting:
    \`\`\`
-   component("stat-card", {label: "Chiffre d'affaires", value: "45 230 EUR", trend: "+12.4%", trendDir: "up", icon: "trending-up"})
+   component("stat-card", {label: "Revenue", value: "45 230 EUR", trend: "+12.4%", trendDir: "up", icon: "trending-up"})
    \`\`\`
-   - Toujours formater les nombres : separateurs de milliers, unites, symboles
-   - Ajouter \`trend\` et \`trendDir\` si une comparaison est disponible (vs mois precedent, vs annee precedente)
-3. **Si des series temporelles existent**, ajouter un graphique :
+   - Always format numbers: thousands separators, units, symbols
+   - Add \`trend\` and \`trendDir\` if a comparison is available (vs. previous month, vs. previous year)
+3. **If time series exist**, add a chart:
    \`\`\`
-   component("chart", {type: "bar", labels: ["Q1", "Q2", "Q3", "Q4"], datasets: [{label: "CA", data: [98000, 112000, 128000, 142000]}]})
+   component("chart", {type: "bar", labels: ["Q1", "Q2", "Q3", "Q4"], datasets: [{label: "Revenue", data: [98000, 112000, 128000, 142000]}]})
    \`\`\`
-   - "bar" pour des comparaisons entre categories/periodes
-   - "line" pour des evolutions continues
-4. **Si des details tabulaires existent**, ajouter une table :
+   - "bar" for comparisons between categories/periods
+   - "line" for continuous trends
+4. **If tabular details exist**, add a table:
    \`\`\`
-   component("table", {columns: ["Categorie", "Valeur", "Evolution"], rows: [...]})
+   component("table", {columns: ["Category", "Value", "Change"], rows: [...]})
    \`\`\`
-5. **Pour les metadonnees complementaires**, utiliser kv :
+5. **For supplementary metadata**, use kv:
    \`\`\`
-   component("kv", {pairs: [["Source", "data.gouv.fr"], ["Derniere mise a jour", "2026-04-01"], ["Periode", "T1 2026"]]})
+   component("kv", {pairs: [["Source", "data.gouv.fr"], ["Last updated", "2026-04-01"], ["Period", "Q1 2026"]]})
    \`\`\`
 
-## Exemples
+## Examples
 
-### Dashboard parlementaire (Tricoteuses)
+### Parliamentary dashboard (Tricoteuses)
 \`\`\`
-// Apres query_sql sur les scrutins de la legislature
-component("stat-card", {label: "Scrutins publics", value: "1 247", icon: "vote"})
-component("stat-card", {label: "Amendements deposes", value: "42 831", icon: "file-text"})
-component("stat-card", {label: "Participation moyenne", value: "61.3%", trend: "-2.1%", trendDir: "down"})
-component("chart", {type: "bar", labels: mois, datasets: [{label: "Scrutins/mois", data: counts}]})
-component("table", {columns: ["Groupe", "Amendements", "Adoptes", "Taux"], rows: groupStats})
+// After query_sql on votes for the legislature
+component("stat-card", {label: "Public votes", value: "1 247", icon: "vote"})
+component("stat-card", {label: "Amendments filed", value: "42 831", icon: "file-text"})
+component("stat-card", {label: "Average participation", value: "61.3%", trend: "-2.1%", trendDir: "down"})
+component("chart", {type: "bar", labels: months, datasets: [{label: "Votes/month", data: counts}]})
+component("table", {columns: ["Group", "Amendments", "Adopted", "Rate"], rows: groupStats})
 \`\`\`
 
-### Dashboard biodiversite (iNaturalist)
+### Biodiversity dashboard (iNaturalist)
 \`\`\`
 component("stat-card", {label: "Observations", value: "3 412", icon: "eye"})
-component("stat-card", {label: "Especes uniques", value: "287", icon: "leaf"})
-component("stat-card", {label: "Observateurs", value: "156", icon: "users"})
-component("chart", {type: "line", labels: dates, datasets: [{label: "Observations/jour", data: dailyCounts}]})
+component("stat-card", {label: "Unique species", value: "287", icon: "leaf"})
+component("stat-card", {label: "Observers", value: "156", icon: "users"})
+component("chart", {type: "line", labels: dates, datasets: [{label: "Observations/day", data: dailyCounts}]})
 \`\`\`
 
-### Dashboard actualites (Hacker News)
+### News dashboard (Hacker News)
 \`\`\`
 component("stat-card", {label: "Top stories", value: "500", icon: "newspaper"})
-component("stat-card", {label: "Score moyen", value: "142", icon: "trending-up"})
-component("stat-card", {label: "Commentaires moyen", value: "87", icon: "message-circle"})
-component("table", {columns: ["Rang", "Titre", "Score", "Commentaires"], rows: topStories})
+component("stat-card", {label: "Average score", value: "142", icon: "trending-up"})
+component("stat-card", {label: "Average comments", value: "87", icon: "message-circle"})
+component("table", {columns: ["Rank", "Title", "Score", "Comments"], rows: topStories})
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Trop de stat-cards** : au-dela de 5, basculer vers un \`kv\` ou un \`table\` pour les metriques secondaires
-- **Nombres non formates** : afficher "45230" au lieu de "45 230" nuit a la lisibilite
-- **Oublier les unites** : "45 230" ne signifie rien sans "EUR", "%", "observations", etc.
-- **Graphique sans contexte** : toujours accompagner un graphique de stat-cards qui donnent les chiffres cles instantanement
+- **Too many stat-cards**: beyond 5, switch to a \`kv\` or \`table\` for secondary metrics
+- **Unformatted numbers**: displaying "45230" instead of "45 230" hurts readability
+- **Missing units**: "45 230" means nothing without "EUR", "%", "observations", etc.
+- **Chart without context**: always accompany a chart with stat-cards that surface key figures instantly
 `,
   'explorer-dossiers-legislatifs-parcours-texte': `---
-id: explorer-dossiers-legislatifs-parcours-texte
-name: Explorer les dossiers legislatifs et le parcours d'un texte entre Assemblee et Senat
+id: explore-legislative-files-text-journey
+name: Explore legislative files and the journey of a text between the Assembly and the Senate
 components_used: [timeline, table, kv, stat-card]
-when: l'utilisateur demande le parcours d'un projet ou proposition de loi, la navette parlementaire, les lectures successives, ou le suivi d'un dossier legislatif
+when: the user asks about the journey of a bill or legislative proposal, the parliamentary shuttle, successive readings, or the tracking of a legislative file
 servers: [tricoteuses]
 layout:
   type: grid
   columns: 2
-  arrangement: timeline pleine largeur en haut, stats + table en dessous
+  arrangement: full-width timeline at top, stats + table below
 ---
 
-## Quand utiliser
+## When to use
 
-L'utilisateur s'interesse au parcours d'un texte de loi a travers les institutions :
-- "Ou en est le projet de loi sur l'immigration ?"
-- "Montre-moi la navette parlementaire de la reforme des retraites"
-- "Combien de lectures a subi ce texte ?"
-- "Quels amendements ont ete adoptes en commission ?"
+The user is interested in the journey of a bill through the institutions:
+- "Where does the immigration bill currently stand?"
+- "Show me the parliamentary shuttle for the pension reform"
+- "How many readings did this text go through?"
+- "Which amendments were adopted in committee?"
 
-Le serveur Tricoteuses contient les dossiers legislatifs avec leurs etapes : depot, renvoi en commission, discussion en seance, vote, navette, promulgation.
+The Tricoteuses server contains legislative files with their stages: filing, referral to committee, floor debate, vote, shuttle, promulgation.
 
-## Comment
+## How to use
 
-1. **Rechercher le dossier legislatif** :
+1. **Search for the legislative file**:
    \`\`\`
    query_sql({sql: "SELECT * FROM assemblee.dossiers WHERE titre ILIKE '%immigration%' ORDER BY date_depot DESC LIMIT 5"})
    \`\`\`
-   Ou via les recettes Tricoteuses :
+   Or via Tricoteuses recipes:
    \`\`\`
    search_recipes({query: "dossier legislatif parcours"})
    \`\`\`
 
-2. **Recuperer les etapes du parcours** :
+2. **Retrieve the journey stages**:
    \`\`\`
    query_sql({sql: "SELECT etape, chambre, date, resultat FROM assemblee.dossier_etapes WHERE dossier_id = $id ORDER BY date"})
    \`\`\`
 
-3. **Afficher la timeline du parcours** :
+3. **Display the journey timeline**:
    \`\`\`
    component("timeline", {
      events: etapes.map(e => ({
@@ -592,77 +592,77 @@ Le serveur Tricoteuses contient les dossiers legislatifs avec leurs etapes : dep
    })
    \`\`\`
 
-4. **Statistiques du dossier** en stat-cards :
+4. **File statistics** in stat-cards:
    \`\`\`
-   component("stat-card", {label: "Lectures", value: "3", icon: "book-open"})
-   component("stat-card", {label: "Amendements deposes", value: "1 247", icon: "file-text"})
-   component("stat-card", {label: "Amendements adoptes", value: "312", icon: "check"})
-   component("stat-card", {label: "Duree totale", value: "14 mois", icon: "clock"})
+   component("stat-card", {label: "Readings", value: "3", icon: "book-open"})
+   component("stat-card", {label: "Amendments filed", value: "1 247", icon: "file-text"})
+   component("stat-card", {label: "Amendments adopted", value: "312", icon: "check"})
+   component("stat-card", {label: "Total duration", value: "14 months", icon: "clock"})
    \`\`\`
 
-5. **Details des amendements par etape** en table :
+5. **Amendment details by stage** in a table:
    \`\`\`
    component("table", {
-     columns: ["Etape", "Chambre", "Amendements deposes", "Adoptes", "Rejetes"],
+     columns: ["Stage", "Chamber", "Amendments filed", "Adopted", "Rejected"],
      rows: etapeStats
    })
    \`\`\`
 
-6. **Metadonnees du dossier** en kv :
+6. **File metadata** in kv:
    \`\`\`
    component("kv", {pairs: [
-     ["Titre", dossier.titre],
+     ["Title", dossier.titre],
      ["Nature", "Projet de loi"],
-     ["Auteur", "Gouvernement"],
-     ["Date de depot", dossier.date_depot],
-     ["Etat actuel", dossier.etat],
+     ["Author", "Gouvernement"],
+     ["Filing date", dossier.date_depot],
+     ["Current status", dossier.etat],
      ["Source", "Tricoteuses"]
    ]})
    \`\`\`
 
-## Exemples
+## Examples
 
-### Parcours complet d'un texte
+### Complete text journey
 \`\`\`
-// 1. Recuperer le dossier
+// 1. Retrieve the file
 query_sql({sql: "SELECT id, titre, date_depot, etat FROM assemblee.dossiers WHERE titre ILIKE '%retraites%2023%' LIMIT 1"})
 
-// 2. Etapes
+// 2. Stages
 query_sql({sql: "SELECT * FROM assemblee.dossier_etapes WHERE dossier_id = $id ORDER BY date"})
 
-// 3. Amendements par etape
+// 3. Amendments by stage
 query_sql({sql: "SELECT etape, COUNT(*) as total, COUNT(*) FILTER (WHERE sort='Adopte') as adoptes FROM assemblee.amendements WHERE dossier_id = $id GROUP BY etape"})
 
-// 4. Rendu
-component("kv", {pairs: [["Dossier", titre], ["Etat", etat]]})
+// 4. Render
+component("kv", {pairs: [["File", titre], ["Status", etat]]})
 component("timeline", {events: etapes})
-component("stat-card", {label: "Total amendements", value: totalAmendements})
-component("stat-card", {label: "Adoptes", value: totalAdoptes})
-component("table", {columns: ["Etape", "Deposes", "Adoptes", "Taux"], rows: etapeStats})
+component("stat-card", {label: "Total amendments", value: totalAmendements})
+component("stat-card", {label: "Adopted", value: totalAdoptes})
+component("table", {columns: ["Stage", "Filed", "Adopted", "Rate"], rows: etapeStats})
 \`\`\`
 
-### Comparaison entre chambres
+### Comparison between chambers
 \`\`\`
-// Amendements par chambre
+// Amendments by chamber
 query_sql({sql: "SELECT chambre, COUNT(*) as deposes, COUNT(*) FILTER (WHERE sort='Adopte') as adoptes FROM assemblee.amendements WHERE dossier_id = $id GROUP BY chambre"})
 
-component("stat-card", {label: "Assemblee — Adoptes", value: an_adoptes + "/" + an_deposes})
-component("stat-card", {label: "Senat — Adoptes", value: senat_adoptes + "/" + senat_deposes})
-component("chart", {type: "bar", labels: ["Assemblee", "Senat"], datasets: [{label: "Deposes", data: [an_deposes, senat_deposes]}, {label: "Adoptes", data: [an_adoptes, senat_adoptes]}]})
+component("stat-card", {label: "Assembly — Adopted", value: an_adoptes + "/" + an_deposes})
+component("stat-card", {label: "Senate — Adopted", value: senat_adoptes + "/" + senat_deposes})
+component("chart", {type: "bar", labels: ["Assemblee", "Senat"], datasets: [{label: "Filed", data: [an_deposes, senat_deposes]}, {label: "Adopted", data: [an_adoptes, senat_adoptes]}]})
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Confondre projet et proposition de loi** : un projet vient du gouvernement, une proposition vient d'un parlementaire — verifier le champ \`nature\`
-- **Ne pas suivre la navette** : un texte peut faire plusieurs allers-retours entre Assemblee et Senat — afficher TOUTES les etapes
-- **Oublier la CMP** : la Commission Mixte Paritaire est une etape cruciale entre les deux chambres, ne pas l'omettre dans la timeline
-- **Timeline non chronologique** : toujours trier les etapes par date croissante
+- **Confusing bill types**: a "projet de loi" comes from the government, a "proposition de loi" comes from a parliamentary member — check the \`nature\` field
+- **Not following the shuttle**: a text can make several back-and-forth trips between the Assembly and the Senate — display ALL stages
+- **Forgetting the CMP**: the Commission Mixte Paritaire (Joint Committee) is a crucial stage between the two chambers — do not omit it from the timeline
+- **Non-chronological timeline**: always sort stages by ascending date
 `,
   'gallery-images': `---
-id: afficher-galerie-images-depuis-urls-mcp
-name: Afficher une galerie d'images a partir d'URLs retournees par un serveur MCP
+id: display-image-gallery-from-mcp-urls
+name: Display an image gallery from URLs returned by an MCP server
 components_used: [gallery, carousel, cards]
-when: les donnees MCP contiennent des champs URL pointant vers des images (jpg, png, webp, svg) comme hdurl, primaryImage, image_url, photos[].url, ou tout champ similaire
+when: MCP data contains URL fields pointing to images (jpg, png, webp, svg) such as hdurl, primaryImage, image_url, photos[].url, or any similar field
 servers: [nasa, metmuseum, inaturalist]
 layout:
   type: grid
@@ -671,32 +671,32 @@ interactions:
   - source: gallery, target: lightbox, event: click, action: zoom
 ---
 
-## Quand utiliser
+## When to use
 
-Les resultats d'un appel MCP contiennent des URLs d'images reelles. Cela inclut :
-- **NASA** : champ \`hdurl\` ou \`url\` dans les reponses APOD, Earth, Mars Rover Photos
-- **Met Museum** : champ \`primaryImage\` ou \`primaryImageSmall\` apres \`get_object\`
-- **iNaturalist** : champ \`photos[].url\` dans les observations
+The results of an MCP call contain real image URLs. This includes:
+- **NASA**: \`hdurl\` or \`url\` field in APOD, Earth, and Mars Rover Photos responses
+- **Met Museum**: \`primaryImage\` or \`primaryImageSmall\` field after \`get_object\`
+- **iNaturalist**: \`photos[].url\` field in observations
 
-La recette s'applique des qu'au moins 2 images sont disponibles dans les donnees. Pour une seule image, preferer un composant \`card\` avec l'image en en-tete.
+This recipe applies whenever at least 2 images are available in the data. For a single image, prefer a \`card\` component with the image as a header.
 
-## Comment
+## How to use
 
-1. **Appeler l'outil DATA** du serveur MCP pour recuperer les donnees contenant les images
-2. **Extraire les URLs reelles** depuis les resultats — ne JAMAIS inventer d'URLs placeholder
-3. **Verifier que les URLs sont valides** : elles doivent pointer vers des domaines connus (apod.nasa.gov, images.metmuseum.org, inaturalist-open-data.s3.amazonaws.com, etc.)
-4. **Choisir le composant** :
-   - 2-5 images : \`component("gallery", {images: [{src, alt, caption?}]})\`
-   - 6+ images : \`component("carousel", {images: [{src, alt}]})\` pour eviter une page trop longue
-   - Images avec metadonnees riches : \`component("cards", {items: [{title, image, subtitle, body}]})\`
-5. **Toujours fournir un \`alt\` descriptif** pour chaque image (titre de l'oeuvre, nom de l'espece, titre APOD)
-6. **Ajouter un titre contextuel** avant la galerie avec \`component("text", {content: "..."})\`
+1. **Call the DATA tool** from the MCP server to retrieve the data containing the images
+2. **Extract the real URLs** from the results — NEVER invent placeholder URLs
+3. **Verify that the URLs are valid**: they must point to known domains (apod.nasa.gov, images.metmuseum.org, inaturalist-open-data.s3.amazonaws.com, etc.)
+4. **Choose the component**:
+   - 2-5 images: \`component("gallery", {images: [{src, alt, caption?}]})\`
+   - 6+ images: \`component("carousel", {images: [{src, alt}]})\` to avoid an overly long page
+   - Images with rich metadata: \`component("cards", {items: [{title, image, subtitle, body}]})\`
+5. **Always provide a descriptive \`alt\`** for each image (artwork title, species name, APOD title)
+6. **Add a contextual title** before the gallery with \`component("text", {content: "..."})\`
 
-## Exemples
+## Examples
 
 ### NASA APOD (Astronomy Picture of the Day)
-Outil : \`nasa_apod\` ou \`nasa_apod_range\`
-Reponse type : \`{hdurl: "https://apod.nasa.gov/apod/image/2401/...", title: "Horsehead Nebula", explanation: "..."}\`
+Tool: \`nasa_apod\` or \`nasa_apod_range\`
+Typical response: \`{hdurl: "https://apod.nasa.gov/apod/image/2401/...", title: "Horsehead Nebula", explanation: "..."}\`
 
 \`\`\`
 component("gallery", {
@@ -708,9 +708,9 @@ component("gallery", {
 })
 \`\`\`
 
-### Met Museum — Recherche d'oeuvres
-Etape 1 : \`search_objects({query: "impressionism sunflower"})\` → liste d'IDs
-Etape 2 : pour chaque ID, \`get_object({objectID: id})\` → \`{primaryImage, title, artistDisplayName}\`
+### Met Museum — Artwork search
+Step 1: \`search_objects({query: "impressionism sunflower"})\` → list of IDs
+Step 2: for each ID, \`get_object({objectID: id})\` → \`{primaryImage, title, artistDisplayName}\`
 
 \`\`\`
 component("gallery", {
@@ -722,9 +722,9 @@ component("gallery", {
 })
 \`\`\`
 
-### iNaturalist — Observations avec photos
-Outil : \`search_observations({taxon_name: "Parus major", lat: 48.85, lng: 2.35, radius: 10})\`
-Reponse type : \`{photos: [{url: "..."}], species_guess: "Mesange charbonniere", place_guess: "Paris"}\`
+### iNaturalist — Observations with photos
+Tool: \`search_observations({taxon_name: "Parus major", lat: 48.85, lng: 2.35, radius: 10})\`
+Typical response: \`{photos: [{url: "..."}], species_guess: "Mesange charbonniere", place_guess: "Paris"}\`
 
 \`\`\`
 component("gallery", {
@@ -738,49 +738,49 @@ component("gallery", {
 })
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Inventer des URLs placeholder** (\`https://example.com/image.jpg\`, \`via.placeholder.com\`, \`placehold.co\`, \`dummyimage.com\`, \`?text=...\`) — strictement INTERDIT. Si aucune image réelle n'est retournée par l'API, ne PAS afficher de galerie.
-- **Oublier de verifier** que le champ image existe dans les donnees retournees (certains objets Met Museum n'ont pas de \`primaryImage\`)
-- **Utiliser \`text\` pour afficher des URLs** au lieu de \`gallery\` — les images doivent etre rendues visuellement
-- **Ne pas adapter la taille** : iNaturalist retourne des thumbnails "square" par defaut, remplacer par "medium" ou "large" dans l'URL
+- **Inventing placeholder URLs** (\`https://example.com/image.jpg\`, \`via.placeholder.com\`, \`placehold.co\`, \`dummyimage.com\`, \`?text=...\`) — strictly FORBIDDEN. If no real image is returned by the API, do NOT display a gallery.
+- **Forgetting to check** that the image field exists in the returned data (some Met Museum objects have no \`primaryImage\`)
+- **Using \`text\` to display URLs** instead of \`gallery\` — images must be rendered visually
+- **Not adapting the size**: iNaturalist returns "square" thumbnails by default — replace with "medium" or "large" in the URL
 `,
   'parlementaire-profile': `---
-id: afficher-profil-parlementaire-avec-hemicycle-et-votes
-name: Afficher le profil d'un parlementaire avec hemicycle, votes et timeline des mandats
+id: display-parliamentary-profile-with-hemicycle-and-votes
+name: Display a parliamentary profile with hemicycle, votes and mandate timeline
 components_used: [profile, hemicycle, timeline, table, stat-card, kv]
-when: les donnees MCP concernent un depute, senateur, groupe parlementaire, scrutin ou amendement provenant d'une base de donnees parlementaire
+when: MCP data concerns a deputy, senator, parliamentary group, vote, or amendment from a parliamentary database
 servers: [tricoteuses]
 layout:
   type: grid
   columns: 2
-  arrangement: profile + stats en haut, hemicycle + timeline en bas
+  arrangement: profile + stats at top, hemicycle + timeline below
 ---
 
-## Quand utiliser
+## When to use
 
-Les resultats MCP proviennent du serveur Tricoteuses (base de donnees parlementaire francaise) et concernent :
-- Un **depute ou senateur** : fiche individuelle, mandats, activite
-- Un **groupe politique** : composition, votes, positionnement
-- Des **scrutins publics** : resultats de vote, repartition par groupe
-- Des **amendements** : texte, auteur, sort, article vise
-- Des **dossiers legislatifs** : parcours d'un texte, navette parlementaire
+MCP results come from the Tricoteuses server (French parliamentary database) and concern:
+- A **deputy or senator**: individual profile, mandates, activity
+- A **political group**: composition, votes, positioning
+- **Public votes**: vote results, breakdown by group
+- **Amendments**: text, author, outcome, targeted article
+- **Legislative files**: text journey, parliamentary shuttle
 
-La recette est specifique au serveur Tricoteuses et a ses outils : \`query_sql\`, \`search_recipes\`, \`list_tables\`, \`describe_table\`.
+This recipe is specific to the Tricoteuses server and its tools: \`query_sql\`, \`search_recipes\`, \`list_tables\`, \`describe_table\`.
 
-## Comment
+## How to use
 
-1. **Recuperer les informations du parlementaire** via les outils Tricoteuses :
+1. **Retrieve the parliamentary member's information** via the Tricoteuses tools:
    \`\`\`
    query_sql({sql: "SELECT * FROM acteurs WHERE nom ILIKE '%dupont%' AND type = 'depute'"})
    \`\`\`
-   Ou via les recipes Tricoteuses :
+   Or via Tricoteuses recipes:
    \`\`\`
    search_recipes({query: "profil depute"})
    get_recipe({name: "recipe-name"})
    \`\`\`
 
-2. **Afficher la fiche profil** :
+2. **Display the profile card**:
    \`\`\`
    component("profile", {
      name: "Jean Dupont",
@@ -790,15 +790,15 @@ La recette est specifique au serveur Tricoteuses et a ses outils : \`query_sql\`
    })
    \`\`\`
 
-3. **Afficher les statistiques d'activite** en stat-cards :
+3. **Display activity statistics** in stat-cards:
    \`\`\`
-   component("stat-card", {label: "Participation aux scrutins", value: "87%", trend: "+3%", trendDir: "up"})
-   component("stat-card", {label: "Amendements deposes", value: "42", icon: "file-text"})
-   component("stat-card", {label: "Questions ecrites", value: "18", icon: "help-circle"})
-   component("stat-card", {label: "Interventions hemicycle", value: "7", icon: "mic"})
+   component("stat-card", {label: "Vote participation", value: "87%", trend: "+3%", trendDir: "up"})
+   component("stat-card", {label: "Amendments filed", value: "42", icon: "file-text"})
+   component("stat-card", {label: "Written questions", value: "18", icon: "help-circle"})
+   component("stat-card", {label: "Hemicycle speeches", value: "7", icon: "mic"})
    \`\`\`
 
-4. **Si des donnees de vote par groupe sont disponibles**, afficher l'hemicycle :
+4. **If vote data by group is available**, display the hemicycle:
    \`\`\`
    component("hemicycle", {
      groups: [
@@ -810,219 +810,219 @@ La recette est specifique au serveur Tricoteuses et a ses outils : \`query_sql\`
    })
    \`\`\`
 
-5. **Pour l'historique des mandats ou votes cles**, utiliser la timeline :
+5. **For the mandate history or key votes**, use the timeline:
    \`\`\`
    component("timeline", {
      events: [
-       {date: "2022-06-19", title: "Elu depute", description: "3e circ. du Rhone"},
-       {date: "2023-03-16", title: "Vote 49.3 retraites", description: "Motion de censure rejetee"},
-       {date: "2024-07-07", title: "Reelu depute", description: "2e tour"}
+       {date: "2022-06-19", title: "Elected deputy", description: "3e circ. du Rhone"},
+       {date: "2023-03-16", title: "Vote 49.3 pensions reform", description: "Motion de censure rejetee"},
+       {date: "2024-07-07", title: "Re-elected deputy", description: "2nd round"}
      ]
    })
    \`\`\`
 
-6. **Pour les details des votes ou amendements**, utiliser une table :
+6. **For vote or amendment details**, use a table:
    \`\`\`
    component("table", {
-     columns: ["Date", "Scrutin", "Vote", "Resultat"],
+     columns: ["Date", "Vote", "Position", "Result"],
      rows: votes.map(v => [v.date, v.intitule, v.position, v.resultat])
    })
    \`\`\`
 
-7. **Completer avec les metadonnees** en kv :
+7. **Complete with metadata** in kv:
    \`\`\`
    component("kv", {pairs: [
      ["Legislature", "XVIe (2022-2027)"],
-     ["Groupe", "Renaissance"],
-     ["Commission permanente", "Lois"],
+     ["Group", "Renaissance"],
+     ["Standing committee", "Lois"],
      ["Source", "Tricoteuses — mcp.code4code.eu"]
    ]})
    \`\`\`
 
-## Exemples
+## Examples
 
-### Profil complet d'un depute
+### Complete deputy profile
 \`\`\`
-// 1. Chercher le depute
+// 1. Look up the deputy
 query_sql({sql: "SELECT * FROM acteurs WHERE nom ILIKE '%dupont%' LIMIT 1"})
 
-// 2. Ses amendements
+// 2. Their amendments
 query_sql({sql: "SELECT COUNT(*) as total, SUM(CASE WHEN sort='Adopte' THEN 1 ELSE 0 END) as adoptes FROM amendements WHERE auteur_id = $id"})
 
-// 3. Ses votes recents
+// 3. Their recent votes
 query_sql({sql: "SELECT s.date, s.intitule, v.position FROM scrutins s JOIN votes v ON s.id = v.scrutin_id WHERE v.acteur_id = $id ORDER BY s.date DESC LIMIT 10"})
 
-// 4. Rendu complet
+// 4. Full render
 component("profile", {name, subtitle, photo})
-component("stat-card", {label: "Amendements", value: total, icon: "file-text"})
-component("stat-card", {label: "Adoptes", value: adoptes, icon: "check"})
-component("stat-card", {label: "Taux d'adoption", value: Math.round(adoptes/total*100) + "%"})
-component("table", {columns: ["Date", "Scrutin", "Position"], rows: votes})
+component("stat-card", {label: "Amendments", value: total, icon: "file-text"})
+component("stat-card", {label: "Adopted", value: adoptes, icon: "check"})
+component("stat-card", {label: "Adoption rate", value: Math.round(adoptes/total*100) + "%"})
+component("table", {columns: ["Date", "Vote", "Position"], rows: votes})
 component("timeline", {events: mandats})
 \`\`\`
 
-### Resultat d'un scrutin avec hemicycle
+### Vote result with hemicycle
 \`\`\`
-// 1. Recuperer le scrutin
+// 1. Retrieve the vote
 query_sql({sql: "SELECT * FROM scrutins WHERE intitule ILIKE '%budget%' ORDER BY date DESC LIMIT 1"})
 
-// 2. Repartition par groupe
+// 2. Breakdown by group
 query_sql({sql: "SELECT g.nom, g.couleur, COUNT(*) FILTER (WHERE v.position='pour') as pour, COUNT(*) FILTER (WHERE v.position='contre') as contre FROM votes v JOIN groupes g ON v.groupe_id = g.id WHERE v.scrutin_id = $id GROUP BY g.nom, g.couleur"})
 
-// 3. Rendu
-component("stat-card", {label: "Pour", value: "312", trendDir: "up"})
-component("stat-card", {label: "Contre", value: "245", trendDir: "down"})
+// 3. Render
+component("stat-card", {label: "For", value: "312", trendDir: "up"})
+component("stat-card", {label: "Against", value: "245", trendDir: "down"})
 component("hemicycle", {groups: groupResults, result: {pour: 312, contre: 245, abstention: 18}})
-component("table", {columns: ["Groupe", "Pour", "Contre", "Abstention"], rows: groupDetails})
+component("table", {columns: ["Group", "For", "Against", "Abstention"], rows: groupDetails})
 \`\`\`
 
-## Composants specifiques au domaine parlementaire
+## Components specific to the parliamentary domain
 
-- **hemicycle** : arc de cercle montrant la repartition des votes par groupe politique, avec couleurs par parti
-- **profile** : fiche individuelle avec photo, nom, fonction, details structurees
-- **timeline** : chronologie des mandats, votes cles, evenements parlementaires
-- **trombinoscope** : grille de photos pour un groupe de parlementaires (utile pour les commissions)
+- **hemicycle**: semicircular arc showing vote distribution by political group, with party colors
+- **profile**: individual card with photo, name, role, structured details
+- **timeline**: chronology of mandates, key votes, parliamentary events
+- **trombinoscope**: photo grid for a group of parliamentary members (useful for committees)
 
-## Erreurs courantes
+## Common mistakes
 
-- **Requetes SQL trop larges** : toujours utiliser LIMIT et des filtres precis pour eviter de surcharger le serveur
-- **Confondre acteurs et mandats** : un depute peut avoir plusieurs mandats dans la base, filtrer par legislature courante
-- **Oublier la source** : toujours crediter "Tricoteuses" comme source dans un kv final
-- **Hemicycle sans contexte** : toujours accompagner le composant hemicycle de stat-cards avec les totaux pour/contre/abstention
+- **Overly broad SQL queries**: always use LIMIT and precise filters to avoid overloading the server
+- **Confusing actors and mandates**: a deputy can have multiple mandates in the database — filter by current legislature
+- **Forgetting the source**: always credit "Tricoteuses" as the source in a final kv
+- **Hemicycle without context**: always accompany the hemicycle component with stat-cards showing for/against/abstention totals
 `,
   'rechercher-textes-juridiques-legifrance': `---
-id: rechercher-textes-juridiques-legifrance
-name: Rechercher des textes juridiques, codes et lois via les donnees Legifrance
+id: search-legal-texts-legifrance
+name: Search legal texts, codes and laws via Legifrance data
 components_used: [table, text, kv, code]
-when: l'utilisateur demande des informations sur des lois, codes juridiques, articles de loi, decrets, ordonnances ou textes legislatifs francais disponibles dans la base Tricoteuses
+when: the user asks for information about French laws, legal codes, articles of law, decrees, ordinances or legislative texts available in the Tricoteuses database
 servers: [tricoteuses]
 layout:
   type: grid
   columns: 1
 ---
 
-## Quand utiliser
+## When to use
 
-L'utilisateur pose une question sur le droit francais, la legislation, ou un texte juridique specifique :
-- "Que dit l'article 49-3 de la Constitution ?"
-- "Quels decrets ont ete publies sur le droit du travail en 2025 ?"
-- "Montre-moi les articles du Code civil sur la filiation"
-- "Quelles lois ont ete promulguees ce mois-ci ?"
+The user asks a question about French law, legislation, or a specific legal text:
+- "What does article 49-3 of the Constitution say?"
+- "Which decrees were published on labour law in 2025?"
+- "Show me the articles of the Civil Code on filiation"
+- "Which laws were enacted this month?"
 
-La base Tricoteuses contient des donnees issues de Legifrance (textes consolides, codes, lois, decrets). Utiliser \`list_tables\` pour decouvrir les tables disponibles dans le schema legifrance, puis \`describe_table\` et \`query_sql\` pour extraire les textes.
+The Tricoteuses database contains data from Legifrance (consolidated texts, codes, laws, decrees). Use \`list_tables\` to discover the available tables in the legifrance schema, then \`describe_table\` and \`query_sql\` to extract the texts.
 
-## Comment
+## How to use
 
-1. **Decouvrir les tables disponibles** :
+1. **Discover available tables**:
    \`\`\`
    list_tables({schema: "legifrance"})
    \`\`\`
-   Tables typiques : \`textes_versions\`, \`articles\`, \`codes\`, \`sections\`
+   Typical tables: \`textes_versions\`, \`articles\`, \`codes\`, \`sections\`
 
-2. **Decrire la structure** d'une table pour comprendre les colonnes :
+2. **Describe the structure** of a table to understand the columns:
    \`\`\`
    describe_table({schema: "legifrance", table: "articles"})
    \`\`\`
 
-3. **Rechercher les textes** avec des requetes SQL :
+3. **Search for texts** with SQL queries:
    \`\`\`
    query_sql({sql: "SELECT titre, date_publi, nature FROM legifrance.textes_versions WHERE titre ILIKE '%travail%' ORDER BY date_publi DESC LIMIT 20"})
    \`\`\`
 
-4. **Afficher les resultats** :
-   - **Table** pour les listes de textes :
+4. **Display results**:
+   - **Table** for lists of texts:
      \`\`\`
-     component("table", {columns: ["Titre", "Nature", "Date", "Etat"], rows: textes})
+     component("table", {columns: ["Title", "Nature", "Date", "Status"], rows: textes})
      \`\`\`
-   - **Text** pour le contenu d'un article :
+   - **Text** for the content of an article:
      \`\`\`
      component("text", {content: "### Article 49-3 de la Constitution\\n\\n" + article.contenu})
      \`\`\`
-   - **Code** pour les extraits legislatifs avec mise en forme :
+   - **Code** for legislative excerpts with formatting:
      \`\`\`
      component("code", {language: "text", content: article.texte_integral})
      \`\`\`
-   - **KV** pour les metadonnees du texte :
+   - **KV** for text metadata:
      \`\`\`
-     component("kv", {pairs: [["Nature", "Loi organique"], ["Date", "2023-04-14"], ["NOR", "JUSX2300001L"], ["Etat", "En vigueur"]]})
+     component("kv", {pairs: [["Nature", "Loi organique"], ["Date", "2023-04-14"], ["NOR", "JUSX2300001L"], ["Status", "En vigueur"]]})
      \`\`\`
 
-## Exemples
+## Examples
 
-### Articles d'un code juridique
+### Articles from a legal code
 \`\`\`
-// 1. Trouver les articles du Code civil sur la filiation
+// 1. Find articles of the Civil Code on filiation
 query_sql({sql: "SELECT num_article, contenu, etat FROM legifrance.articles WHERE code = 'Code civil' AND section ILIKE '%filiation%' ORDER BY num_article"})
 
-// 2. Rendu
-component("kv", {pairs: [["Code", "Code civil"], ["Section", "De la filiation"], ["Articles trouves", results.length]]})
-component("table", {columns: ["Article", "Contenu (extrait)", "Etat"], rows: results.map(r => [r.num_article, r.contenu.slice(0, 200) + "...", r.etat])})
+// 2. Render
+component("kv", {pairs: [["Code", "Code civil"], ["Section", "De la filiation"], ["Articles found", results.length]]})
+component("table", {columns: ["Article", "Content (excerpt)", "Status"], rows: results.map(r => [r.num_article, r.contenu.slice(0, 200) + "...", r.etat])})
 \`\`\`
 
-### Textes recents par nature
+### Recent texts by nature
 \`\`\`
-// 1. Lois promulguees en 2026
+// 1. Laws enacted in 2026
 query_sql({sql: "SELECT titre, date_publi, nor FROM legifrance.textes_versions WHERE nature = 'LOI' AND date_publi >= '2026-01-01' ORDER BY date_publi DESC"})
 
-// 2. Rendu
-component("stat-card", {label: "Lois promulguees en 2026", value: results.length, icon: "scale"})
-component("table", {columns: ["Titre", "Date", "NOR"], rows: results})
+// 2. Render
+component("stat-card", {label: "Laws enacted in 2026", value: results.length, icon: "scale"})
+component("table", {columns: ["Title", "Date", "NOR"], rows: results})
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Confondre les schemas** : les donnees Legifrance sont dans le schema \`legifrance\`, pas dans \`assemblee\` — verifier avec \`list_tables\`
-- **Requetes trop larges** : toujours utiliser LIMIT et des filtres WHERE precis
-- **Afficher le texte integral brut** : utiliser le composant \`text\` avec formatage Markdown plutot que de dumper le JSON
-- **Oublier de preciser l'etat du texte** : un article peut etre abroge, modifie ou en vigueur — toujours l'indiquer
+- **Confusing schemas**: Legifrance data is in the \`legifrance\` schema, not in \`assemblee\` — verify with \`list_tables\`
+- **Overly broad queries**: always use LIMIT and precise WHERE filters
+- **Displaying raw full text**: use the \`text\` component with Markdown formatting rather than dumping the JSON
+- **Forgetting to specify the text status**: an article can be repealed, amended or in force — always indicate it
 `,
   'weather-viz': `---
-id: visualiser-previsions-meteo-avec-graphiques-et-kpi
-name: Visualiser des previsions meteo avec graphiques temporels et indicateurs cles
+id: visualize-weather-forecasts-with-charts-and-kpis
+name: Visualize weather forecasts with time series charts and key indicators
 components_used: [stat-card, chart-rich, map, kv]
-when: les donnees MCP contiennent des mesures meteorologiques (temperature, humidite, vent, precipitations) ou des previsions horaires/journalieres
+when: MCP data contains weather measurements (temperature, humidity, wind, precipitation) or hourly/daily forecasts
 servers: [openmeteo]
 layout:
   type: grid
   columns: 2
-  arrangement: stat-cards en haut, chart en bas sur toute la largeur
+  arrangement: stat-cards at the top, chart spanning full width at the bottom
 ---
 
-## Quand utiliser
+## When to use
 
-Les resultats MCP contiennent des donnees meteorologiques structurees. Typiquement :
-- **Open-Meteo** : previsions horaires (\`hourly.temperature_2m\`, \`hourly.precipitation\`), previsions journalieres (\`daily.temperature_2m_max/min\`), conditions actuelles (\`current.temperature_2m\`, \`current.wind_speed_10m\`)
-- Toute source retournant des series temporelles de mesures climatiques
+MCP results contain structured weather data. Typically:
+- **Open-Meteo**: hourly forecasts (\`hourly.temperature_2m\`, \`hourly.precipitation\`), daily forecasts (\`daily.temperature_2m_max/min\`), current conditions (\`current.temperature_2m\`, \`current.wind_speed_10m\`)
+- Any source returning time series of climate measurements
 
-La recette s'applique meme pour une seule ville : les stat-cards montrent les conditions actuelles, le graphique montre l'evolution.
+This recipe applies even for a single city: stat-cards show current conditions, the chart shows the trend over time.
 
-## Comment
+## How to use
 
-1. **Appeler l'outil meteo** avec les coordonnees ou le nom de la ville :
-   - Open-Meteo : \`get_forecast({latitude: 48.85, longitude: 2.35, hourly: "temperature_2m,precipitation", daily: "temperature_2m_max,temperature_2m_min"})\`
-2. **Extraire les KPIs actuels** et les afficher en stat-cards :
-   - Temperature actuelle : \`component("stat-card", {label: "Temperature", value: "18.5°C", icon: "thermometer"})\`
-   - Vent : \`component("stat-card", {label: "Vent", value: "12.3 km/h", icon: "wind"})\`
-   - Humidite : \`component("stat-card", {label: "Humidite", value: "72%", icon: "droplets"})\`
-   - Precipitations : \`component("stat-card", {label: "Pluie (24h)", value: "2.1 mm", icon: "cloud-rain"})\`
-3. **Construire le graphique temporel** a partir des series horaires ou journalieres :
+1. **Call the weather tool** with coordinates or city name:
+   - Open-Meteo: \`get_forecast({latitude: 48.85, longitude: 2.35, hourly: "temperature_2m,precipitation", daily: "temperature_2m_max,temperature_2m_min"})\`
+2. **Extract current KPIs** and display them as stat-cards:
+   - Current temperature: \`component("stat-card", {label: "Temperature", value: "18.5°C", icon: "thermometer"})\`
+   - Wind: \`component("stat-card", {label: "Wind", value: "12.3 km/h", icon: "wind"})\`
+   - Humidity: \`component("stat-card", {label: "Humidity", value: "72%", icon: "droplets"})\`
+   - Precipitation: \`component("stat-card", {label: "Rain (24h)", value: "2.1 mm", icon: "cloud-rain"})\`
+3. **Build the time series chart** from hourly or daily series:
    - \`component("chart-rich", {type: "line", labels: hourly.time, datasets: [{label: "Temperature °C", data: hourly.temperature_2m}]})\`
-   - Pour les precipitations, preferer un type "bar" superpose
-4. **Ajouter la carte** si des coordonnees sont disponibles :
+   - For precipitation, prefer an overlaid "bar" type
+4. **Add the map** if coordinates are available:
    - \`component("map", {center: [lat, lon], zoom: 10, markers: [{lat, lon, label: "Paris"}]})\`
-5. **Completer avec les details** en kv :
-   - \`component("kv", {pairs: [["Lever du soleil", "06:42"], ["Coucher", "20:15"], ["Indice UV", "5 (modere)"]]})\`
+5. **Complete with details** in kv:
+   - \`component("kv", {pairs: [["Sunrise", "06:42"], ["Sunset", "20:15"], ["UV Index", "5 (moderate)"]]})\`
 
-## Exemples
+## Examples
 
-### Previsions 7 jours pour Paris
+### 7-day forecast for Paris
 \`\`\`
-// Appel MCP
+// MCP call
 get_forecast({latitude: 48.8566, longitude: 2.3522, daily: "temperature_2m_max,temperature_2m_min,precipitation_sum"})
 
-// Rendu
-component("stat-card", {label: "Aujourd'hui", value: "22°C / 14°C", icon: "thermometer"})
-component("stat-card", {label: "Pluie prevue", value: "0 mm", icon: "sun"})
+// Render
+component("stat-card", {label: "Today", value: "22°C / 14°C", icon: "thermometer"})
+component("stat-card", {label: "Expected rain", value: "0 mm", icon: "sun"})
 component("chart-rich", {
   type: "line",
   labels: daily.time,  // ["2026-04-09", "2026-04-10", ...]
@@ -1033,23 +1033,23 @@ component("chart-rich", {
 })
 \`\`\`
 
-### Previsions horaires avec precipitations
+### Hourly forecast with precipitation
 \`\`\`
 component("chart-rich", {
   type: "line",
   labels: hourly.time.slice(0, 24),
   datasets: [
     {label: "Temperature °C", data: hourly.temperature_2m.slice(0, 24), yAxisID: "y"},
-    {label: "Pluie mm", data: hourly.precipitation.slice(0, 24), yAxisID: "y1", type: "bar"}
+    {label: "Rain mm", data: hourly.precipitation.slice(0, 24), yAxisID: "y1", type: "bar"}
   ]
 })
 \`\`\`
 
-## Erreurs courantes
+## Common mistakes
 
-- **Afficher les donnees brutes JSON** au lieu de les visualiser avec des composants
-- **Ne pas convertir les unites** : Open-Meteo retourne en unites SI par defaut (m/s pour le vent → convertir en km/h si l'utilisateur est francophone)
-- **Oublier les stat-cards** pour les KPIs principaux : un graphique seul ne donne pas les chiffres cles immediatement
-- **Trop de points sur le graphique** : pour des previsions horaires sur 7 jours (168 points), preferer un resample journalier ou limiter a 48h en mode horaire
+- **Displaying raw JSON data** instead of visualizing it with components
+- **Not converting units**: Open-Meteo returns SI units by default (m/s for wind → convert to km/h if appropriate for the user)
+- **Forgetting stat-cards** for the main KPIs: a chart alone does not surface key figures immediately
+- **Too many points on the chart**: for hourly forecasts over 7 days (168 points), prefer daily resampling or limit to 48h in hourly mode
 `,
 };