> ## Documentation Index
> Fetch the complete documentation index at: https://extension.js.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations for Tailwind, ESLint, and more

> Connect Extension.js with Tailwind CSS, PostCSS, ESLint, Prettier, Stylelint, Babel, and shadcn/ui for a complete extension development workflow.

Connect Extension.js with formatting, linting, CSS tooling, and UI component workflows used in modern web projects.

## Choose by need

| Need | Start here |
| - | - |
| Add custom transforms beyond SWC (Speedy Web Compiler) | [Babel](/docs/integrations/babel) |
| Enforce code-quality rules | [ESLint](/docs/integrations/eslint) |
| Keep formatting consistent | [Prettier](/docs/integrations/prettier) |
| Transform CSS with plugins | [PostCSS](/docs/integrations/postcss) |
| Lint stylesheets in continuous integration (CI) | [Stylelint](/docs/integrations/stylelint) |
| Build composable UI primitives | [shadcn/ui](/docs/integrations/shadcnui) |
| Utility-first styling system | [Tailwind CSS](/docs/integrations/tailwindcss) |
| Atomic utility classes generated on demand | [UnoCSS](/docs/integrations/unocss) |
| Debug extensions with AI agents via Chrome DevTools | [Chrome DevTools MCP](/docs/integrations/chrome-devtools-mcp) |
| Let a coding agent drive the dev session | [extension.dev MCP server](/docs/integrations/extension-mcp) |

## Practical integration order

1. Add baseline quality tools: ESLint + Prettier.
2. Add style tooling: PostCSS + Stylelint (and Tailwind if needed).
3. Add framework-specific tooling only when required.

## Next steps

* Align project defaults in [Extension configuration](/docs/features/extension-configuration).
* Validate changes with [Workflows](/docs/workflows/index).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.