Features

Five complementary surfaces, one simpler adoption path.

SimplicityTools works best when each surface reinforces the next one: CLI for the first read, filters for interpretation, analyzers for daily feedback, reports for communication, and TCA for business context.

Healthy adoption sequence
  • Learn the shape with analyze and budget
  • Protect the floor with baseline and diff
  • Share the story with report
  • Keep daily pressure low with analyzers
  • Translate drag into cost with TCA when needed

The five tool surfaces

Each surface can stand alone, but the real value shows up when the same contract survives from local runs to CI and architecture conversations.

Common team jobs

Use the page that matches the job. That keeps the docs honest and the architecture conversation concrete.

Protect pull requests

Use baseline + diff --fail-on-regression once the team agrees on the current floor.

Coach the team in the IDE

Use the analyzer package when feedback needs to arrive before a pull request review does.

Justify simplification work

Use report output and TCA estimates when architecture cleanup needs stakeholder language, not just developer intuition.

Design system

The site stays intentionally narrow: one dark canvas, one brand accent, readable code blocks, and explicit focus states that survive keyboard use on mobile, tablet, and desktop.

Background

#050816

Default canvas and page chrome.

Panel

#0B1222

Cards, sections, and elevated surfaces.

Text

#E5EEFB

Primary copy and headings.

Muted text

#9FB1CC

Body copy, metadata, and supporting labels.

Brand red

#E31B23

Primary action, active state, and key emphasis.

Warm accent

#FF6B72

Eyebrows, badges, and secondary emphasis.

Success

#62D39F

Positive status and validation cues.