Breakpoint prefixes

Last reviewed Jun 1, 2026 Content v20260601

Track mode

iframe_html

Means

HTML preview sandbox

Reading

~1 min

Level

intermediate

This lesson

This lesson teaches Breakpoint prefixes—the ideas, syntax, and habits you need before moving on in Utility CSS.

Without a solid grasp of Breakpoint prefixes, you will repeat mistakes in Utility CSS exercises and on real pages or scripts.

You will apply Breakpoint prefixes in contexts like: Product UIs, internal tools, and teams that want rapid layout iteration without a heavy component library.

Read the lesson, edit HTML/CSS in the playground, press Run to preview, then answer the lesson MCQs.

When the previous lesson's MCQs feel easy and you can explain Breakpoint prefixes in your own words.

Prefix convention in this track: tu-md- ≥ 48rem, tu-lg- ≥ 64rem. Document breakpoints in one file so utilities stay predictable.

Going deeper

In production utility-first CSS work, Breakpoint prefixes matters when documents, stylesheets, or apps must stay maintainable across teams and releases—not only in isolated demos.

Common pitfalls

Watch for copy-paste configs, skipping validation or tests, and mixing concerns (structure vs presentation vs behavior) in one layer.

Practice

Apply one technique from this lesson in the playground.
Write one interview-style sentence explaining when you would use breakpoint prefixes on a real project.

Interview prep

What does tu-md- mean in this track?: Utilities inside a min-width: 48rem media query—applied from that breakpoint upward (mobile-first).

Playground

Runs in your browser in a sandboxed frame. Backend runners appear when this track’s profile allows them.

Discussion

Past discussion is visible to everyone. Only logged-in users can post comments and replies.

Starter discussion topics

What utility pattern confused you here?
How would you rebuild this layout with fewer classes?

No discussion yet. Be the first to ask a question.