Tools I Built on the Side

• Git-backed Truth: The entire project state (roles, process, history, budget) is in the repo. Clone the repo, and the whole project comes with it.
• Granular Cost Tracking: Costs are tracked per task, role, and release, exposing what was spent on work that produced nothing.
• Resilient Execution: A run that dies resumes from its state inventory instead of restarting. Applied work is never redone.
• Earned Autonomy: Trust and autonomy move based on evidence in run records. Agents never loosen their own gates.
• Honest Enforcement: every gate names what holds it — validator, hook, git host, or prose-only, listed by name. The rules that mattered were measured from 0/5 as prose to hard refusals as hooks.
• One Repo, Every Runtime: installs as a plugin into Claude Code, Codex, Gemini CLI and more — the project travels with its repository, not with a tool.

• Computed Output: Low-level building blocks rather than a fixed high-level scheme — you set the model, the tokens follow.
• Multi-Agent AI: A built-in AI chat with dedicated personas handles audits, proposals, and hands-on theme editing.
• Full Token Coverage: Computes every token in the model across light/dark modes, conditions and interaction states, including inverse tokens.
• Built-in Accessibility: Contrast ratios are part of the model, and vision filters simulate how the system appears to users with color vision deficiencies.

• Closed-Loop Conveyor: A dedicated conductor runs every stage — discovery, design, parallel review gates, shipping, measuring — instead of stopping at a merge.
• Cost & Governance: Every release writes an itemised cost ledger — tokens, time and list-price dollars, per agent and per feature — from the platform's own counters, so "what did this cost" has an answer instead of a feeling. A declared budget shapes what gets proposed, not just what gets refused — and spending is one of four kinds that always route to you for a yes, however long the track record.
• Long-term Resilience: Session-limit recovery, health checks across the whole conveyor, and git-backed plugin & skill upgrades.
• Honest by Construction: Every rule states what actually enforces it — a request, a validator, branch protection, the platform, or prose-only, which means nothing does — and the prose-only rules are listed by name. Behaviour is measured against stratified scenarios, each release publishes its run record including what failed, and a coverage map says which scenarios are unmeasured rather than implying all of them pass.
• Autonomous Staffing: A built-in role-builder researches crafts, drafts skills, and hires specialized agents (or invites human teammates) to grow the team.

Preview how a numeric system behaves in the interface, export CSS, and share settings via a link — one source for design and development.

Fluid size systems scale without jumps, keeping numbers legible and predictable at any viewport.

878 people use the Figma plugin.

A grid tool for design systems: design grid behavior in the interface, export to CSS & Figma, and share settings via a link. It supports fluid-sized grids that hold their behaviour at any viewport.

6.4k people use the Figma plugin, including Hiroco and Javan Digital Agency.

Numbers frames and pages so a spec or a deck keeps its order — and keeps it after something is inserted in the middle, which is when hand-numbering falls apart.

10.8k people use it — the most-used of my Figma plugins. It also works in Figma Slides.

Preview typography behavior in the interface, export CSS, and share settings via a link — one source for design and development, fallbacks included. Fluid type systems scale without jumps, keeping type legible at every viewport.

7.1k people use the Figma plugin.

Leonardo generates colour themes from contrast ratios rather than from picked values. Getting one into Figma meant copying colours across one at a time; this plugin imports the theme whole.

3.2k people use the Figma plugin, including teams at TripAdvisor and Harvard University.

Story points are estimated for the work and then paid for everything around it — an unfamiliar area, a dependency, someone who is only half on the task. The calculator takes those factors as explicit inputs instead of leaving them in somebody's head.

Values that already exist in a stylesheet get retyped by hand on the design side. FromCSS reads the CSS and applies it as Figma styles, so the two sides start from the same numbers instead of converging on them. Useful too for shadows built in generators like neumorphism.io or brumm.af/shadows, which produce CSS and nothing else.

8.9k people use the Figma plugin, including teams at SimilarWeb and Podhero.

HSL treats lightness as arithmetic rather than as something the eye agrees with: two colours on the same L can look nothing alike in brightness, which is why palettes built in HSL need hand-correcting. HSLuv is the perceptually even alternative, and this plugin brings it into Figma.

3.9k people use it.

My version of the Leonardo Color tool, built for the parts I kept working around: lightness stops on a bezier curve instead of even steps, templates to start from, HEX import, and share links that survive being shared.