More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    CSS to Tailwind — First-Pass Converter

    1

    Converts a plain CSS or Sass site to Tailwind v4 classes as a fast first pass, checks every class against Tailwind's own scale, and lists exactly what you still have to fix by hand.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    CSS to Tailwind — First-Pass Converter

    CSS to Tailwind — First-Pass Converter

    Example session with this skill installed

    /css-to-tailwind Migrate this site's styles to Tailwind. I only want to see what converts cleanly and what I'd have to fix by hand.

    • Read your context and instructions
    • Compiled the css to tailwind
    • Generated the app files

    Sample project: a three-page cafe site (index, menu, about) with one Sass-built stylesheet, about 50 selectors, BEM naming, media queries, hover states and a few things Tailwind has no direct class for.

    Conversion mode

    Tool-assisted: 42 converter calls, and every result checked against Tailwind's own scale and color tables.

    Migrated

    FileSelectors convertedStylesheetBackup
    index.html22kept, 5 rules flaggedindex.html.bak
    menu.html19kept, 5 rules flaggedmenu.html.bak
    about.html15kept, 5 rules flaggedabout.html.bak

    Across the three pages that is 32 selector blocks, including their hover and media-query variants and the active-link compound selector. The original Sass and CSS files are untouched.

    Flagged for manual review

    • .menu__item + .menu__item (the divider line between menu items): sibling combinator, not converted.
    • .about__quote::before (the opening quote mark): generated content, not converted.
    • @keyframes fade-in: no utility class.
    • The animation on .notice: depends on the keyframes above; the rest of .notice was converted.
    • @supports (display: grid) block: not converted.

    While the old stylesheet stays linked, its rules win every conflict, so the page looks right mostly because of the old CSS. To see what the Tailwind classes do on their own, comment out that link. The flagged rules then visibly change, and that is your to-do list.

    What the check caught in the converter's output

    SelectorConverter saidCorrected toWhy
    .containermax-w-24max-w-275max-width: 1100px; max-w-24 is 96px
    .containermy-0 for margin: 0 automx-autothe auto horizontal margin was lost, which would break centering
    .hero (768px and up)py-24md:py-28padding: 112px; py-24 is 96px
    bodytext-4text-base16px; text-4 is not a font-size class
    .site-header__logotext-6text-2xl24px
    .card__titletext-5text-xl20px
    .notice, footertext-3.5text-sm14px
    brand colorsbg-f7f1e8, text-3b2a20bg-[#f7f1e8], text-[#3b2a20]not real classes; kept as exact hex
    .cardsgrid columns unsupportedgrid-cols-1 md:grid-cols-3standard utilities preferred over arbitrary ones
    .menu__listlist-style unsupportedlist-noneone-to-one literal match

    Most converter calls had at least one wrong or missing declaration. The check corrected them before anything reached your HTML.

    Values left as arbitrary (no standard step)

    Font sizes 13, 15, 32, 40 and 56px, line heights 1.2 and 1.7, letter spacing 0.08em and 0.2em, one shadow, the font stack, and eight brand colors from the Sass variables. They are listed for a visual check. One near-miss color was snapped: #fff7e6 became bg-yellow-50, flagged for confirmation.

    Tailwind preflight differences

    Tailwind resets browser defaults that the original CSS never set, so a page can differ slightly even where every rule converted. The report lists what applies here, with the fix.

    • index.html: the hero title and the three card titles lose their default bold (add font-bold).
    • menu.html: the page heading loses its default bold (add font-bold).
    • All pages: the unclassed paragraph in the footer loses its top and bottom margins, and footer links lose their underline (add my-4 and underline).

    Tailwind runtime

    No Tailwind build was found, so a version-pinned CDN script with an integrity hash was added to each page so the classes render right away. This is a preview convenience, not a production setup.

    Before you trust this

    This is a best-effort mechanical conversion. Nothing was checked in a browser by the agent. Compare the pages visually, including hover states and the md breakpoint.

    index.html

    ZIP · project files

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Moving a hand-written CSS or Sass site to Tailwind usually means finding out the hard way what does not translate. This skill gives you that answer first. It converts what converts cleanly, checks each class against Tailwind's own scale, and tells you plainly what it left alone, so you can see whether Tailwind will cause problems on your site before you commit to it.

    It is a first pass, not a promise of a perfect replacement. If the result looks right, keep it and fix only the spots the report lists. If it does not, your originals are untouched and every edited page has a backup.

    What it does

    • Compiles Sass (nesting, variables, mixins, partials) to plain CSS in a temporary file, so your .scss source is never touched
    • Converts your stylesheet selector by selector, including hover and focus states and media queries as Tailwind variants
    • Checks every class against the bundled Tailwind scale and color tables, and corrects the ones that do not match your CSS. For example a 320px width comes out as w-80, never w-24
    • Leaves anything that needs judgment for you instead of guessing: selector combinators, keyframe animations, @supports blocks, pseudo-element content, approximate colors and off-scale values
    • Keeps your old stylesheet linked while any rule is still unconverted, so nothing silently loses its styling, and tells you how to comment the link out to see what the Tailwind classes do on their own
    • Saves a .bak copy of each HTML file before editing it, and never overwrites an existing backup
    • Adds a short Tailwind rules section to CLAUDE.md, creating the file if needed
    • If the project has no Tailwind at all, adds a version-pinned CDN script with an integrity hash so the classes render right away for preview
    • Ends with a report: what was converted, what needs a manual fix, what the check corrected, and which values stayed arbitrary

    How it works

    1. Finds your HTML pages and the stylesheets they link, and asks which to migrate
    2. Compiles Sass to flat CSS if needed and splits it into rules
    3. Converts each rule to a candidate class list, using the optional converter tool when it is connected or Tailwind knowledge when it is not
    4. Verifies every candidate against the scale and color tables and records each correction
    5. Applies the classes to your HTML, backs up each file first, and unlinks the old stylesheet only when every rule was converted
    6. Reports the result, including what to check by eye

    What it is not

    It does not guarantee a pixel-identical page. Tailwind resets some browser defaults, such as heading weight, paragraph margins and link underlines, so a page can differ slightly even where every rule converted. The report names the elements affected. It handles plain HTML files; Vue single-file components, CSS Modules and styled-components are out of scope.

    Requirements

    Node.js, used once to compile Sass with npx. A TailwindCSS MCP server is optional: if it is connected the skill uses it as a starting point, and if not the skill carries on without it. Either way every class is verified against the bundled tables. Network access is used only to fetch the Sass compiler and, for a project with no Tailwind, to pin the CDN script version.

    Try it free first

    Try it Free runs on Agensi's servers with a 5,000-character input limit, so it previews part of a page (for example one body and its stylesheet). The installed skill handles whole sites locally.

    Works well with

    Tailwind Review, the free companion skill, for ongoing checks once your markup is on Tailwind.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    A fast first pass, not a guaranteed complete replacement. Selector combinators, keyframe animations, @supports blocks and pseudo-element content are flagged, not converted. Tailwind's preflight can change default heading weight, margins and link underlines. Values with no standard step stay as arbitrary values. Plain HTML only; component frameworks are out of scope. Output targets Tailwind CSS v4.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Software
    sassNode.js

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Write Files

    Allowed Hosts

    registry.npmjs.org

    File Scopes

    **/*.html
    **/*.scss
    **/*.sass
    **/*.css
    CLAUDE.md

    Reads the project's HTML and stylesheet files and edits the HTML pages in place, after saving a .bak copy of each. The original stylesheets are never modified. It also creates or appends to CLAUDE.md. The terminal is used to compile Sass with npx sass into a temporary file and, only when the project has no Tailwind at all, to compute an integrity hash for a version-pinned CDN script (curl and openssl). Network access is limited to the npm registry (fetching the Sass compiler and resolving the Tailwind version) and the jsDelivr CDN. The optional third-party TailwindCSS MCP server, if the user has it connected, receives only CSS rules from the project. No environment variables or credentials are read.

    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    It edits your HTML pages in place, but it saves a .bak copy of each one first, never touches your original stylesheet, and keeps the old stylesheet linked while any rule is still unconverted.

    No. It converts what maps cleanly and lists the rest for you, such as selector combinators, keyframe animations and @supports blocks. That list is the point of the first pass.

    No. It is optional. If it is connected the skill uses it as a starting point, and if not the skill converts from the bundled tables and its own knowledge. Either way each class is checked against the tables, because that converter can be wrong.

    Tailwind resets some browser defaults, such as heading weight, paragraph margins and link underlines. The report names the elements affected so you can add classes where you want the old look back.

    Yes. It compiles your Sass to plain CSS in a temporary file and converts that. Your .scss files are never changed.

    Yes, for preview. If no Tailwind build is found, it adds a version-pinned CDN script with an integrity hash. That is a quick way to see the result, not a production setup, so set up a real build before shipping.

    New in Frontend & Web Apps