Getting Started
First successful audit in 4 steps
- Install and pin Palext in Chrome.
- Run a scan on any production page.
- Inspect key components and verify spacing/contrast.
- Export tokens or generate a report for handoff.
Audit Playbook
Run a repeatable UI quality cycle
Discovery (Free)
Capture baseline tokens and inspect visual system consistency.
Triage (Free + Pro)
Use contrast checks and Pro insights to prioritize the highest impact fixes.
Delivery (Free + Pro)
Ship with export formats for code and reports for stakeholder communication.
Export Reference
Choose the right output for each workflow
Output
Plan
Best used for
CSS variables, SCSS, JSON
Free
Core implementation and baseline audits
Tailwind, JS, TS, Less, Stylus
Pro
Framework and token pipeline integration
React UI (MUI, Chakra, Ant)
Pro
Component library implementation
Figma Tokens + DTCG
Pro
Design tool and token standard alignment
Audit report (.md + .html)
Pro
Stakeholder-ready communication
Plan Matrix
Free vs Pro at a glance
Capability
Free
Pro
Monthly scans
10
Unlimited
Saved snapshots
3
Unlimited
Insights analyzer + recommendations
Pro only
Included
Audit report downloads
Pro only
Markdown + Visual HTML
Design tools + React export families
Pro only
Included
FAQ
Common implementation questions
Do we need to read all docs before using Palext?
No. Start with Getting Started, then return here only for workflow-specific guidance.
What is the fastest way to explain Pro value internally?
Share the Plan Matrix and Export Reference sections first.
Should docs and pricing contain the same details?
Keep pricing concise and let docs hold the full operational detail.