Core Analyzer vs. Standalone Tools on Project Wallace

Updated

Project Wallace splits its offering into two layers: the core analyzer, which produces a full-codebase audit of your CSS, and a set of standalone tools, which are single-purpose utilities you run on a snippet of CSS. Choose the core analyzer when you need to understand systemic problems across an entire stylesheet — color drift, specificity creep, design token duplication. Choose the standalone tools when you just need one job done right now, like formatting, minifying, or diffing CSS. The standalone tools are described as requiring no signup and no paywall, so they work as quick, disposable utilities.

What the core analyzer does

The core analyzer takes a URL or raw CSS as input and returns a complete "x-ray" of the stylesheets, covering every selector, media query, and property. It surfaces, counts, and visualizes the structure and complexity of your CSS. Its purpose is the aerial view: the big picture that component-level review misses.

It bundles several analysis views:

View What it reveals
Full CSS analysis Every selector, media query, and property, counted and visualized
Code quality score A single score based on specificity distribution, redundancy, selector complexity, and best practices
Design token audit Every color, font-size, shadow, and spacing value, extracted and grouped to show consistency or drift
Custom property inspector Which custom properties are declared, used, or orphaned
Cascade layer visualizer Order, nesting, and specificity implications of @layer declarations

The problems it targets are the ones that accumulate invisibly: a palette that grows from clean to 140+ unique values, specificity that creeps upward with each quick fix, and design tokens that duplicate until the bundle balloons. These are system-level issues, which is why the analyzer works on the whole codebase rather than a single file.

What the standalone tools are

The standalone tools are one-off utilities for everyday CSS work. The site lists:

  • CSS prettifier
  • CSS minifier
  • CSS diff viewer
  • Coverage inspector
  • Specificity tool (listed as "Speci…" in the source)

Each does one thing. You paste CSS, you get a result. They are positioned explicitly as no-signup, no-paywall tools — the framing is "paste your CSS and get your job done," not "set up an account and run an audit."

How to choose

Use the core analyzer when:

  • You need to know whether your design system is drifting across the whole codebase.
  • You suspect specificity problems or redundant selectors but can't see the pattern locally.
  • You want a quality score or a token audit as a starting point for cleanup.

Use the standalone tools when:

  • You have a concrete, single-step task: format this CSS, shrink this file, compare two versions, check what's unused.
  • You don't want to sign up or commit to a workflow.
  • You're working on a snippet rather than a whole project.

The two layers don't compete. The standalone tools handle the routine edits; the core analyzer handles the diagnosis that routine edits can't reveal. A practical sequence is to run the standalone tools during day-to-day work, then run the core analyzer periodically to catch the drift those small edits introduce.