variations
Skill2 starsChanged 6 months agoMITView on GitHub
Génère N variations UI/UX d'un composant dans des fichiers séparés pour explorer visuellement les concepts. L'utilisateur ouvre son navigateur, compare, choisit, et supprime le reste.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- grechj/Australian-Builders-Braintheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- grechj/Australian-Builders-Brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apexSkill
- api-genSkill
- assets-pipelineSkill
- brainstormSkill
- debugSkill
- deep-updateSkill
- deploy-checkSkill
- depsSkill
- docs-genSkill
- e2e-testsSkill
- env-setupSkill
- featureSkill
- fixSkill
- forkSkill
- meta-promptSkill
- migrateSkill
- onboardSkill
- oneshotSkill
- perfSkill
- prdSkill
- qualitySkill
- refactorSkill
- reviewSkill
- saas-initSkill
- schema-genSkill
- scope-taskSkill
- session-startSkill
- stripeSkill
- ui-auditSkill
- uiSkill
The file
Files
Arguments
component: Quel composant ou quelle page à explorercount: Nombre de variations (défaut: 5, max: 10)
Instructions
1. Comprendre le Composant
- Lire le composant existant (si il existe)
- Identifier les props, le data model, les contraintes
- Lire le design system en place (shadcn, tailwind config, etc.)
2. Planifier les Variations
Avant de coder, lister les approches UX différentes. Exemples :
- Layout : Cards grid vs Table vs List vs Kanban vs Timeline
- Navigation : Tabs vs Accordion vs Wizard vs Split view vs Sidebar
- Interaction : Modal vs Inline edit vs Drawer vs Full page vs Popover
- Densité : Compact vs Comfortable vs Spacious
- Style : Minimal vs Rich vs Glassmorphism vs Brutalist
Chaque variation doit être fondamentalement différente en approche UX, pas juste une variation de couleur.
3. Générer les Fichiers
Créer un dossier temporaire :
src/components/_variations/
├── [component]-v1-cards-grid.tsx
├── [component]-v2-table-view.tsx
├── [component]-v3-kanban.tsx
├── [component]-v4-timeline.tsx
├── [component]-v5-split-view.tsx
└── _preview.tsx ← Page qui affiche toutes les variationsLe fichier _preview.tsx :
// Page de preview — accéder via /variations ou route temporaire
// Affiche toutes les variations côte à côte ou en tabs
// Avec des données mock réalistes4. Chaque Variation Doit
- Être un composant standalone fonctionnel
- Utiliser les mêmes props/données
- Avoir un titre visible indiquant le concept (ex: "V3 — Kanban Board")
- Être responsive
- Utiliser shadcn/ui et Tailwind
5. Présentation
Informer l'utilisateur :
5 variations générées dans src/components/_variations/
Ouvre [URL preview] pour les comparer visuellement.
V1 — Cards Grid : Layout classique en grille de cartes
V2 — Table View : Vue tabulaire dense avec tri et filtres
V3 — Kanban : Vue en colonnes draggable
V4 — Timeline : Vue chronologique verticale
V5 — Split View : Master-detail avec panneau latéral
Dis-moi laquelle tu préfères (ou un mix), et je supprime le reste.6. Après le Choix
- Copier la variation choisie vers l'emplacement final
- Adapter les imports et le naming
- Supprimer tout le dossier
_variations/ - Connecter au vrai data fetching (remplacer les mocks)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

