Chrome Extension
The TailTrace Chrome Extension lets you inspect any element on any website and see its computed styles translated to Tailwind tokens.
Features
Section titled “Features”- Real-time Translation - Hover over any element to see styles
- Confidence Indicators - Know if matches are exact, fuzzy, or none
- One-Click Bug Reports - Send drift issues to Linear or Jira
- Screenshot Capture - Include visual context automatically
- Custom Config - Use your design system tokens
Installation
Section titled “Installation”Coming soon! The extension will be available on the Chrome Web Store.
-
Clone the repository
Terminal window git clone https://github.com/tailtrace/tailtracecd tailtrace -
Install dependencies and build
Terminal window bun installcd extension && bun run build -
Load in Chrome
- Open
chrome://extensions - Enable “Developer mode”
- Click “Load unpacked”
- Select the
extension/distfolder
- Open
Basic Inspection
Section titled “Basic Inspection”- Click the TailTrace icon in your toolbar
- Toggle “Enable Inspector”
- Hover over any element on the page
- See the overlay with translated styles
Reading the Overlay
Section titled “Reading the Overlay”The overlay shows:
| Column | Description |
|---|---|
| Property | CSS property name |
| Value | Computed CSS value |
| Token | Matching Tailwind class |
| Confidence | Match quality indicator |
Confidence Levels
Section titled “Confidence Levels”- ✓ Exact - Perfect token match (green)
- ~ Fuzzy - Close match within threshold (yellow)
- ✗ None - No matching token (red)
Bug Reporting
Section titled “Bug Reporting”Linear Integration
Section titled “Linear Integration”- Open the popup and go to Settings
- Enter your Linear API key
- Select your default team and project
- When inspecting, click “Report Bug”
- Add a title and description
- The issue is created with screenshot and metadata
Jira Integration
Section titled “Jira Integration”- Open the popup and go to Settings
- Enter your Jira domain and API token
- Select your default project
- When inspecting, click “Report Bug”
- The issue is created with full context
Configuration
Section titled “Configuration”Via Popup
Section titled “Via Popup”Click the gear icon in the popup to configure:
- Delta-E threshold for color matching
- Spacing threshold
- Linear/Jira credentials
Via Config File
Section titled “Via Config File”The extension will read tailtrace.json from the current page’s origin if available at /tailtrace.json.
Keyboard Shortcuts
Section titled “Keyboard Shortcuts”| Shortcut | Action |
|---|---|
Alt+T | Toggle inspector |
Escape | Close overlay |
Permissions
Section titled “Permissions”The extension requires:
activeTab- To read styles from the current tabstorage- To save your settingstabs- For screenshot capture (bug reports)
Troubleshooting
Section titled “Troubleshooting”Overlay Not Showing
Section titled “Overlay Not Showing”- Make sure the inspector is enabled (toggle in popup)
- Check if the page has a Content Security Policy blocking inline styles
- Try refreshing the page
Styles Not Translating
Section titled “Styles Not Translating”- Verify your config is loaded (check popup)
- The element may have no applicable CSS properties
- Try hovering over a different element
Screenshots Failing
Section titled “Screenshots Failing”- Ensure you’ve granted the
tabspermission - Check if the page blocks screenshots via CSP