Générer des composants
Boutons, cartes et formulaires à la demande.
Générer des composants est une leçon Vibe Coding gratuite sur CoddyKit. Ceci est la leçon 2 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Vibe Coding, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Vibe Coding comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
Build in Pieces, Not All at Once
A full page can feel overwhelming to prompt. The pro move is to generate one component at a time: a button, a card, a form, a navbar. Each is a small, reusable building block.
In this lesson you'll prompt v0, Lovable, and Bolt to produce clean components on demand — and learn how to combine them into a real interface.
What Is a Component?
A component is a self-contained piece of UI you can reuse: one button definition, used 50 times across your app. Change it once, it updates everywhere.
Thinking in components keeps your prompts focused and your app consistent. Most AI UI tools output components in React, the most popular way to build modern interfaces.
Common components you'll prompt for:
- Button (primary, secondary, ghost)
- Card (image + title + text + action)
- Form input (label + field + validation)
- Navbar / Footer
- Modal / Dialog
- Avatar, Badge, TabsPrompting a Button
Start tiny. Ask for a button and describe every state: default, hover, disabled. Naming states tells the AI you care about polish.
The more variants you request up front, the more reusable the result.
"Create a reusable primary Button component in React.
Rounded corners, a bold accent-blue background, white text.
Include hover (slightly darker) and disabled (greyed out) states.
Accept the label as a prop so I can reuse it."Prompting a Card
Cards are everywhere — products, blog posts, profiles. Describe the slots: what goes in the card and in what order.
Tell the AI which parts are images, headings, and actions so the layout comes out right.
"Create a product Card component: a square image on top,
then a bold product title, a short description, a price in the
bottom-left, and an 'Add to cart' button in the bottom-right.
Subtle shadow, rounded corners, lifts slightly on hover."Prompting a Form
Forms are where details matter most: labels, placeholders, required fields, and error messages. Spell them out.
Good forms also include validation — telling the user when something is wrong. Ask for it explicitly.
"Create a contact form with three fields: Name, Email, and Message.
Each has a label above it. Email shows a red error if it's not valid.
A 'Send' button at the bottom, disabled until all fields are filled.
Clean, modern styling with generous spacing."Reading the Output (Lightly)
You don't need to write React, but recognizing its shape builds confidence. A component is a function that returns markup. Below is the kind of simple, framework-free version of a button the AI might explain to you.
You can run this snippet — it just logs the label, simulating what a button 'does' when clicked.
function Button(label) {
return {
label: label,
click: function () {
console.log(label + ' was clicked!');
}
};
}
const saveBtn = Button('Save');
saveBtn.click();Make It Reusable With Props
The word that turns a one-off design into a reusable component is prop (short for 'property') — a value you pass in to customize it.
Ask the AI to make things configurable: label, color, size, icon. Then one Button component covers every button in your app.
"Refactor my Button so it accepts props: label, variant
('primary' | 'secondary' | 'ghost'), size ('sm' | 'md' | 'lg'),
and an optional left icon. Give each variant distinct styling."Generating Variants in One Shot
Need a whole set? Ask for all variants at once and request a preview gallery so you can see them side by side. Tools like v0 will render every option for you to compare.
"Generate a Badge component with 4 color variants:
success (green), warning (yellow), error (red), and info (blue).
Then show all four side by side in a small preview gallery
so I can compare them."Combining Components Into a Page
Once you have buttons, cards, and forms, assemble them. Reference the components you already made by name so the AI reuses them instead of inventing new ones.
This keeps your design consistent — the same button everywhere, the same card style across sections.
"Build a product listing page that uses my existing Card component
in a 3-column responsive grid, with my primary Button as the
'Load more' action at the bottom. Reuse the components — don't
create new styles."Use a Component Library as a Base
Many tools build on top of polished libraries like shadcn/ui. You can lean on these to get accessible, professional components instantly, then restyle them by prompt.
You don't install anything manually in v0 or Lovable — just ask for it.
"Use shadcn/ui components as the foundation. Build a settings panel
with a Card containing toggle switches, a Select dropdown for language,
and a Save button. Match the rest of my app's spacing and colors."Practice the Component Workflow
Try this loop in v0 or Lovable: generate a single Card, refine it until you love it, then ask for a grid of them. Building bottom-up — small pieces first — gives you far more control than prompting a whole page blindly.
Save prompts that work well; they become your personal component toolkit.
"Create a testimonial Card: a round avatar, the person's name and
role, a star rating, and a quote. Then generate a 3-column grid of
three of these cards with placeholder testimonials."Quick Check
Why is asking the AI to make a component accept props so useful?
Recap: Components on Demand
You learned to build interfaces in reusable pieces. Prompt for one component at a time — button, card, form — and describe its slots and states. Make components flexible with props, generate variants in one shot, and lean on libraries like shadcn/ui as a base.
Then assemble components into pages by referencing them by name so the AI reuses, not reinvents. Next: making everything beautiful with colors, spacing, and dark mode — all by prompt.
Questions Fréquemment Posées
La leçon « Générer des composants » est-elle gratuite ?
Oui — le texte complet de « Générer des composants » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Vibe Coding, passe à CoddyKit PRO. Le cours Vibe Coding comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Générer des composants » ?
Boutons, cartes et formulaires à la demande. Tu pratiques Vibe Coding avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer Vibe Coding ?
Aucune expérience préalable n'est requise. Vibe Coding sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 2 sur 4.
Combien de temps prend la leçon « Générer des composants » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon Vibe Coding ?
Oui. Chaque leçon Vibe Coding inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Décrire une interface en mots
- Générer des composants
- Styles et thèmes
- Rendre l’interface adaptative