SMACSS — Complete Guide
SMACSS — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of CSS Tutorial on Toolliyo Academy.
On this page
CSS Tutorial · Lesson 52 of 100
SMACSS
Foundations & Layout ✓ → Responsive & Motion ✓ → Architecture & Perf → Projects
Architecture & Perf · 3 — Scale · ~15 min read · CSS — Architecture
1. Introduction
Level up: SMACSS. Think architecture, performance, and maintainable design systems.
SMACSS categorizes CSS into Base, Layout, Module, State, and Theme — organizing files by purpose rather than page. States use is- or js- prefixes.
2. Real-world story
Banking squad edits modules/button.css without touching layout shell.
Outcome: SMACSS structure reduces merge conflicts in monorepo.
3. Why it matters
StyleVerse enterprise repos split layout grids from button modules so teams edit without collision.
4. Visual understanding
Read this diagram — the mental model for SMACSS.
tokens (color, space, type) → components (.btn, .card) → patterns (forms, nav) → pages BEM/ITCSS/Tailwind = naming & layering systems
5. Key concepts (easy words)
| Idea | Meaning |
|---|---|
| What | SMACSS categorizes CSS into Base, Layout, Module, State, and Theme — organizing files by purpose rather than page. States use is- or js- prefixes. |
| Remember | Five SMACSS categories organize CSS. Layout separate from modules. State classes show interaction modes. |
| Practice tip | Change one property, refresh, watch DevTools Computed. |
6. How it works
- btn module defines button base. is-disabled state class toggles inactive look. l-sidebar layout class positions shell structure separately.
- Five SMACSS categories organize CSS.
- Layout separate from modules.
- Check the result in DevTools → Computed and the box model overlay.
7. Choose wisely
| Option | Notes |
|---|---|
| Do | Practice SMACSS on a small StyleVerse card |
| Avoid | Copying huge frameworks before learning core CSS |
8. Try this example
Paste into a <style> block (or use Run Example). Refresh to see StyleVerse UI changes.
/* Module: btn */
.btn { display: inline-flex; padding: 10px 20px; border-radius: 6px; }
.btn.is-disabled { opacity: 0.5; pointer-events: none; }
/* Layout: l-sidebar */
.l-sidebar { width: 240px; flex-shrink: 0; }Line walkthrough
| Code | What it means |
|---|---|
.btn { display: inline-flex; padding: 10px 20px; border-radius: 6px; } | Selector — picks which elements get these declarations. |
.btn.is-disabled { opacity: 0.5; pointer-events: none; } | Selector — picks which elements get these declarations. |
.l-sidebar { width: 240px; flex-shrink: 0; } | Selector — picks which elements get these declarations. |
Run Example »
Edit the code below and click Run to see the result in Toolliyo’s live editor.
9. Another real-world angle
10. Best practices checklist
- Prefer classes over ids for reusable StyleVerse components.
- Use design tokens (CSS variables) for color and spacing.
- Mobile-first media queries; test keyboard focus.
- Keep specificity low — avoid !important except rare overrides.
- Animate transform/opacity when you can; respect prefers-reduced-motion.
11. Common mistakes
- Mixing layout width rules inside button module file.
- State classes styled without is- prefix causing conflicts.
12. Practice in the browser
- Folder CSS into base/, layout/, modules/, states/, theme/.
- Prefix layout with l- and state with is-.
- Keep modules independent of page wrappers.
- Theme file overrides tokens for white-label.
Experiments
- Add theme-dark overrides in theme/ folder only.
- Create l-main module for content area flex rule.
13. FAQ
Where should I put CSS for SMACSS?
Start in a <style> block or styles.css linked from HTML. Later use CSS Modules, Tailwind, or tokens in a design system.
Why is my rule not applying?
Check selector match, typos, specificity, and whether a more specific rule or inline style wins. DevTools Computed tells the truth.
Flexbox or Grid for this?
Flex for one direction (toolbars, card rows). Grid for two-dimensional page frames. Many UIs use both.
14. Interview questions
Explain SMACSS simply.
SMACSS categorizes CSS into Base, Layout, Module, State, and Theme — organizing files by purpose rather than page. States use is- or js- prefixes.
How do you debug CSS?
Inspect element, toggle declarations, read Computed styles, outline the box model, and reduce specificity conflicts.
How does this show up in production UI?
SMACSS structure reduces merge conflicts in monorepo.
15. Remember
- Five SMACSS categories organize CSS.
- Layout separate from modules.
- State classes show interaction modes.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!
