To improve the look of a vibe-coded project, give the AI a visual direction rather than simply asking it to “make it look nice.” Abdul Osama (عبدول أسامة) recommends naming a design system and specifying the color palette and visual brand you want. Without those details, he says, the result can look much like other vibe-coded projects.
“To get something distinctive, you need to talk to the AI.” — Abdul Osama
The options Abdul names
Abdul lists these choices in order of his personal preference, from his least favorite of the group to his favorite. They can inform an interface’s visual direction, though they are not identical kinds of tools.
| Option | What it is | Abdul’s comment | | --- | --- | --- | | shadcn/ui | A collection of customizable interface components. | Popular and appealing. | | Material UI | A component library based on Material Design. | A strong open-source option. | | Chakra UI | A library of user-interface components. | Appealing. | | Radix UI | Foundational components for building customizable interfaces. | One of his recommended options. | | HeroUI | A library of user-interface components. | His favorite; he describes it as simple, elegant, and having a 2026-style look. |
How to use the idea
Tell the AI agent helping with your project the name of the option you want it to use. You can also give it a reference from the option’s website or GitHub, a platform that hosts software projects. Abdul notes that some of these options offer a shortcut that helps AI read and understand their design system, but he does not specify which ones.
In numbers
- Five options to try.
- 2026 describes the visual style Abdul associates with HeroUI; he does not present it as a version number.
Background
Vibe coding is a way of building software by describing what you want to an AI. A named visual reference makes that request more specific. Check each option’s current license before using it commercially.
What to do next
Pick an option and give your AI agent its name, along with the colors and visual identity you want. Review the result and refine the instructions instead of relying on a general request to make the interface look good.