レガシー CSS との共存
レガシー CSS や別のフレームワークを含む既存プロジェクトに Tailwind を統合し、詳細度の競合を管理しながら段階的に移行します。
「レガシー CSS との共存」はCoddyKit上の無料Tailwind CSS Academyレッスンです。 これはレッスン2/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはTailwind CSS Academy学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Tailwind CSS Academyコースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
The Coexistence Challenge
Many real-world projects cannot rewrite all existing styles at once. You might inherit a project using Bootstrap, a homegrown CSS framework, or thousands of lines of plain CSS. Introducing Tailwind into such a project means both systems must coexist without breaking each other. Understanding specificity, class naming collisions, and layer ordering is essential for a smooth incremental migration.
Understanding CSS Specificity Conflicts
Tailwind utilities use single-class selectors with specificity 0,1,0. Legacy CSS often uses descendant selectors like .header .nav a with higher specificity. When both styles target the same element, the higher-specificity legacy rule wins regardless of source order. This means a Tailwind utility like text-blue-600 may appear to do nothing if a legacy descendant rule overrides it.
/* Legacy CSS — specificity 0,2,1 */
.header .nav a {
color: #333333;
}
/* Tailwind utility — specificity 0,1,0 */
/* .text-blue-600 { color: #2563eb; } */
<!-- This Tailwind class LOSES because legacy has higher specificity -->
<header class="header">
<nav class="nav">
<a class="text-blue-600">Will still be #333333</a>
</nav>
</header>Using @layer to Manage Specificity
Tailwind's @layer directive places rules inside CSS Cascade Layers. Styles in @layer base and @layer utilities have lower priority than unlayered (legacy) styles, even if the utility has the same specificity. This means legacy styles naturally win without needing !important. Conversely, new Tailwind utilities you add via @layer utilities will not accidentally break the existing CSS.
/*
Order of precedence (highest to lowest):
1. !important declarations
2. Unlayered styles (legacy CSS)
3. @layer utilities
4. @layer components
5. @layer base
Legacy CSS in a separate file wins by default over Tailwind layers.
*/
/* legacy.css — unlayered, wins over Tailwind layers */
.btn { background-color: navy; }
/* tailwind output — in @layer components, loses to legacy */
/* @layer components { .btn { ... } } */Importing Tailwind Alongside Legacy CSS
Import both Tailwind and legacy CSS in the correct order. In the main entry file, import Tailwind's output first (via PostCSS), then import legacy CSS. This way legacy styles are declared after the Tailwind output in the stylesheet, giving them precedence when specificity is equal. Never import legacy before Tailwind unless you intend Tailwind to override it.
/* main.css */
@tailwind base;
@tailwind components;
@tailwind utilities;
/* Import legacy styles AFTER Tailwind so they can override when needed */
@import './legacy/reset.css';
@import './legacy/typography.css';
@import './legacy/components.css';
/* New component styles using @apply where needed */
@import './components.css';Avoiding Class Name Collisions
Tailwind's utility names rarely conflict with typical legacy class names, but collisions can occur. Common examples: a legacy .container class clashes with Tailwind's .container utility. Prefixing is the official solution — add a prefix in tailwind.config.js so all Tailwind classes become tw-flex, tw-bg-blue-500, etc., completely avoiding name overlap with legacy styles.
// tailwind.config.js
module.exports = {
prefix: 'tw-', // All Tailwind classes prefixed with 'tw-'
content: ['./src/**/*.{html,js}'],
theme: { extend: {} },
};
<!-- In HTML: use tw- prefix on all Tailwind classes -->
<div class="tw-flex tw-items-center tw-gap-4 tw-bg-blue-500">
<!-- Legacy classes work normally alongside -->
<div class="legacy-card header-title tw-text-white">
</div>Incremental Migration Strategy
Migrate component by component rather than attempting a full rewrite. Pick a low-risk component — perhaps a new button or badge — and style it entirely with Tailwind. Leave surrounding legacy code unchanged. Once the pattern proves stable, gradually replace legacy components one at a time. This approach limits the blast radius of any issues and keeps the project deployable throughout the migration.
<!-- BEFORE: legacy button -->
<button class="btn btn-primary btn-lg">Save</button>
<!-- AFTER: new Tailwind button (legacy .btn class removed) -->
<button class="rounded-lg bg-blue-600 px-6 py-3 font-semibold text-white
transition hover:bg-blue-700">Save</button>
<!-- DURING MIGRATION: both can coexist temporarily -->
<button class="btn btn-primary tw-ring-2 tw-ring-offset-2">Save</button>Disabling Tailwind's Preflight
Tailwind's Preflight (a CSS reset based on normalize.css) resets browser defaults aggressively. In a legacy project, these resets can break existing styles — removing heading sizes, clearing list styles, collapsing margins. You can disable Preflight in the config to preserve legacy browser defaults while still using all of Tailwind's utilities.
// tailwind.config.js
module.exports = {
corePlugins: {
preflight: false, // Disable the CSS reset
},
content: ['./src/**/*.{html,js}'],
theme: { extend: {} },
plugins: [],
};Selectively Scoping Tailwind
If only part of a legacy page should use Tailwind utilities, you can scope Tailwind's output to a specific CSS selector. Wrap the three @tailwind directives in a selector scope using PostCSS. All generated utilities will be nested under that selector, preventing them from leaking into the rest of the legacy page. This is the most surgical integration possible.
/* Using postcss-scopify or similar — scope Tailwind to .tw-scope */
.tw-scope {
@tailwind base;
@tailwind components;
@tailwind utilities;
}
<!-- In HTML: only elements inside .tw-scope use Tailwind -->
<div class="tw-scope">
<div class="flex items-center gap-4 bg-blue-500">
<!-- Tailwind works here -->
</div>
</div>
<!-- Outside .tw-scope: legacy CSS only -->
<div class="old-header"><!-- legacy --></div>Testing After Each Migration Step
After migrating each component, run a visual regression test to confirm nothing broke. Browser-based tools like Playwright's screenshot comparison or Chromatic catch unintended style changes automatically. At minimum, manually review the migrated component in all supported browsers and at key breakpoints before moving to the next migration target. Automated testing pays dividends in a long migration.
// Playwright visual regression example
import { test, expect } from '@playwright/test';
test('button renders correctly', async ({ page }) => {
await page.goto('/components/button');
await expect(page.locator('.btn-primary')).toHaveScreenshot('button.png');
});
// Run comparison:
npx playwright test --update-snapshots // First run: capture baseline
npx playwright test // Subsequent: compareRemoving Legacy CSS Safely
Once a component is fully migrated to Tailwind, delete the legacy CSS rules. Use browser DevTools' Coverage tab to identify CSS rules that receive zero hits on a given page — strong evidence they are unused. PurgeCSS can also report which selectors in your legacy file never matched any content, guiding the safe removal of dead CSS.
# Check CSS coverage in Chrome DevTools:
# 1. Open DevTools > Coverage tab (Ctrl+Shift+P → 'Show Coverage')
# 2. Start recording, interact with the page
# 3. Red bars indicate unused CSS rules — safe to delete if confirmed
# PurgeCSS analysis:
npx purgecss --css legacy.css --content 'src/**/*.html'
# Rules absent from the output were matched — keep
# Rules still in output were never matched — remove candidatesCommunicating Migration Progress
In team projects, track migration progress visibly. A simple spreadsheet or project board listing every component with status (Not started, In progress, Migrated, Legacy deleted) helps the team coordinate. Document any legacy classes still in use with a comment marking them for future deletion so they are not accidentally reintroduced or depended upon by new features.
/* MIGRATION STATUS: IN PROGRESS
Component: .header-nav
Tailwind replacement: planned in Sprint 12
Owner: @alice
Note: Used in _header.html and email-template.html
*/
.header-nav {
display: flex;
align-items: center;
gap: 1rem;
}Quick Check
Test your understanding of Tailwind CSS Mastery concepts from this lesson.
Lesson Recap
In this lesson you learned: managing specificity conflicts between Tailwind and legacy CSS using cascade layers, disabling Preflight and adding a prefix to avoid breaking or colliding with existing styles, and incrementally migrating components with visual regression testing and tracked progress. Next up we explore CSS Modules combined with Tailwind.
よくある質問
「レガシー CSS との共存」レッスンは無料ですか？
はい。「レガシー CSS との共存」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Tailwind CSS Academyコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Tailwind CSS Academyコースには全4レッスンが含まれています。
「レガシー CSS との共存」で何を学びますか？
レガシー CSS や別のフレームワークを含む既存プロジェクトに Tailwind を統合し、詳細度の競合を管理しながら段階的に移行します。 ブラウザで直接実行するハンズオンコードでTailwind CSS Academyを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
Tailwind CSS Academyを始めるのに経験は必要ですか？
事前経験は必要ありません。CoddyKitのTailwind CSS Academyは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン2/4です。
「レガシー CSS との共存」レッスンにはどのくらい時間がかかりますか？
ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このTailwind CSS Academyレッスンでコードを書いて実行できますか？
はい。すべてのTailwind CSS Academyレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。