StyleSort
A design-system style linter that lets a design team declare their preferred CSS property ordering rules once, then auto-flags drift across Figma libraries, code repos and Storybook — so every component stays consistently ordered.
Design system leads and senior designers at product teams who enforce style consistency
- Visual rule editor where designers (no code) declare preferred property order via drag-and-drop
- Figma plugin that flags components whose styles are out of order, with one-click auto-fix
- CI hook for code repos that comments on PRs with out-of-order declarations
- Shareable team style-guide page auto-generated from the canonical ordering rules
The Royal Order of Operations post (even at 3 HN points) shows there is no consensus canonical CSS ordering — designers and engineers waste hours arguing about it on every project.
stylelint-order has 1,563 dependent npm projects and was updated within 2 months, showing real underlying need for CSS property-ordering enforcement; however the cited HN source had only 3 points / 0 comments, signaling a niche rather than mainstream pain.stylelint-order - npm ↗The Royal Order of Operations ↗
At least three direct or near-direct competitors already scan Figma libraries against codebases for design drift: Revilo.design, DesignGuard AI (Figma+GitHub+Storybook), and Buoy.design; stylelint-order already solves the pure-CSS ordering half for free.Revilo — Design System Alignment Platform ↗Design-Code Drift Detection | DesignGuard AI ↗Pricing | Buoy - Design Drift Detection ↗
Stylelint, stylelint-order, and prettier are free OSS and dominate dev-side linters; design-system budgets at the target persona typically go to broader platforms (zeroheight, Supernova) or visual regression (Chromatic), leaving a narrow property-ordering linter hard to monetize.Plans & Pricing | Figma ↗stylelint-order - npm ↗
Design systems and CSS remain durable (zeroheight, Supernova, Figma all growing), but the specific 'human-argued property order' pain may erode as AI code generators and formatters (Prettier, stylelint autofix) handle ordering automatically, slightly capping upside.Rules - Stylelint ↗Design System Parity: Figma vs Code Sync in 2026 - atomize.tools ↗
Each integration (Figma REST API, GitHub PR checks, Storybook addons) is well-documented and a property-ordering engine already exists in stylelint-order, but stitching three platforms with auth, webhooks, and a unified reporting surface is non-trivial engineering.Storybook and Figma - Figma Learn ↗stylelint-order/rules/properties-order/README.md ↗