ブログ > Design
How do I customize shadcn and Tailwind so it does not look like every indie project?
Change shadcn and Tailwind tokens for radius, color, and type so a project does not keep the zinc, Inter, and pill-badge look.
- 著者
- Unslop UI
- 公開
- 2026年11月20日
- 更新
- 2026年11月20日
- 読了
- 6分
Customize shadcn and Tailwind by changing the theme tokens and the hero composition, not by swapping the library. The familiar indie page is zinc grays, Inter or Geist, a radius many existing setups still set to 0.5rem, and a badge pill over a centered title. Those are choices you can edit. They are not what the components require. The current shadcn docs theme uses --radius: 0.625rem with a neutral base color. 0.5rem is the number you will still see in a lot of older projects.
This post is the token pass. The reason those defaults spread is in "Why Do All v0, Lovable and Cursor Websites Look Exactly the Same? (And How to Make Yours Not)". Font pairings are in "What Are the Best Fonts and Colors to Avoid the AI Look on a SaaS Landing Page?".
What in a starter shadcn theme reads as the indie template?
Look at four values before you touch a card.
| Token or habit | Common value | What people see |
|---|---|---|
--radius | 0.5rem (8px at 16px root) | The same corner on every control |
| Color | zinc scale | A neutral app shell |
| Type | Inter or Geist on every line | No display voice |
| Hero | Badge pill, centered title | The standard opening |
None of these is a bug, and 0.5rem is not the only radius in circulation. The current docs theme uses --radius: 0.625rem and a neutral base color, while 0.5rem is familiar from many existing setups. Together, an untouched radius, zinc, Inter, and the pill are the page a generator emits when you do not name a theme. shadcn's own docs treat theming as CSS variables. Use that. Do not restyle Button in one file and Card in another with a new gray each time.
How do I set a theme that is not zinc and 8px corners?
Start with a small block and map your Tailwind theme to it.
:root {
--background: #F7F5F0;
--foreground: #252722;
--radius: 0rem;
}
#252722 on #F7F5F0 is about 13.85:1, so body text is fine. If you add #B46F4D, keep it off small text on that canvas (about 3.6:1). A sharp radius (0rem) is one direction. Another is a small radius on buttons only, and 0 on screenshots. The failure mode is one radius on everything.
Set the font in the same place. Newsreader or Instrument Serif for headings, Inter or DM Sans for body. If you choose Satoshi, it comes from Fontshare, not Google Fonts. Do not describe it as a Google Font in your prompt or your CSS comment.
Which Tailwind utilities should I stop repeating?
py-24 is 6rem, 96px above and below a section at a 16px root. One section can use it. Every section cannot, or the page is a stack of equal bands. Use py-12 (48px), py-16 (64px), and py-20 (80px) on purpose.
rounded-2xl is 16px. Combined with the 8px token, you get two different rounds and both look soft. Pick the system and delete the one-off classes.
bg-zinc-50 and border-zinc-200 are the gray kit. After the variables change, search the page for zinc and replace leftovers. A leftover zinc card on a warm canvas is how the default sneaks back.
What should I do with the badge component?
The badge component is useful for status inside an app. On a marketing hero it becomes the pill that says New or AI above the title. That pill is a layout tell, not a reason to delete the component.
Use the badge in the product UI if you need a status. On the marketing page, delete the pill and let the headline be the only title. The headline should name the action, not a mood. "Paste a URL. Get an AI-look score and the three fixes to make first" is specific. "The modern way to ship" is the pill's cousin.
Which files should I change, and what should I search for afterward?
Change the theme in one place, then search for leftovers. In a typical shadcn app that place is the global CSS file where --background, --foreground, and --radius are set, plus the font import in the layout. Do not start by editing the button component's class string.
After the variables change, search the marketing routes for:
zincInterandGeistif they are still hardcoded on the heropy-24rounded-2xlandrounded-3xl- The badge component used above an
h1
Each hit is a place the default survived. Fix the marketing page first. App screens can keep a denser radius if that is a separate decision. Write that split down: marketing radius 0, app controls 0.5rem, so the next edit does not "make them match."
Keep a note in the theme file of the four values you chose, so a later prompt can be told "do not change these." If a component needs a one-off color, stop and ask whether the token is wrong instead of adding a hex on the component. Search the marketing routes before you call the theme done. Skipping the search is how bg-zinc-950 stays on a footer while the hero is warm. Then load the deployed page at desktop and at 390px wide. A token that looks right in the component file can still lose on mobile if the hero stacks a pill, a title, and three cards in one column. The stack is the tell even when the hex values are yours.
How do I keep the next AI edit from reverting the theme?
Put the tokens and the refuse list where the editor will read them again. A short rules note is enough: canvas, text, radius, heading font, no pill, no purple glow, no py-24 on every section. The longer version is on the rules page. A paste-ready prompt is in "How do I make my website not look AI-generated? Prompts you can paste".
After the edit, look at the live page. The component gallery in your repo can be on-theme while the marketing route still has the pill. Unslop UI takes a URL or an uploaded screenshot and flags the patterns on that page, including default type and gradient fills. It does not edit your theme files.
Search the marketing routes for zinc and the pill before you add another component.
FAQ
Does using shadcn make my website look AI-generated?
No. shadcn is a set of components you own and can restyle. The familiar look comes from leaving one shared radius, the zinc scale, Inter, and a badge pill in place together.
What radius do most shadcn setups use?
Many existing setups set --radius to 0.5rem, which is 8px when the root font is 16px. The current shadcn docs theme uses --radius: 0.625rem with a neutral base color. There is nothing wrong with either number. The tell is using that same corner on buttons, cards, and images.
How do I change the gray without restyling every component?
Point the background and foreground variables at your own colors, such as #F7F5F0 and #252722, instead of the zinc scale. Components that use those variables pick up the change.
Should I remove Tailwind to look custom?
No. Tailwind is the styling layer. The defaults to change are the utilities you repeat, such as py-24 on every section and the same rounded class on every box.
How do I check that the theme actually changed on the live page?
Open the built page, not the component preview. If the hero still has a pill, a zinc page, and one sans everywhere, the tokens did not reach the layout. A free check of the URL or an uploaded screenshot lists the patterns that remain.
Is 0.5rem the radius in the current shadcn docs?
No. The current docs theme sets --radius to 0.625rem and uses a neutral base color. 0.5rem is familiar because many existing projects still ship with it.