§ Diagnostic
/critique
An opinionated design-director read.
What it does
The design-director read. /critique engages the work at the level of design feel: does this feel like what it’s trying to be, does it have a point of view, does the whole add up to more than the sum of the parts. It speaks with the willingness to make a claim — willing to say something doesn’t land, willing to name when a design is hedging, willing to question direction — but always tied to specific observations and the product’s stated context. Opinionated, not imperious.
/critique doesn’t modify code. It produces feedback in narrative form — overall take, character and point of view, coherence across the work, specific moments, brief direction forward. The format is essay, not punch list; the value is in seeing the work at the level of design feel rather than at the level of cataloged issues.
A critique
Subject · Stillpoint home page
The overall take
Stillpoint’s home is in strong directional shape. The character — warm, grounded, quietly confident, unhurried — comes through in the typography pair, the warm-neutral palette, the natural-light meditation photography, and the line iconography. The work isn’t hedging on what Stillpoint is. The remaining concerns are voice and craft details, not direction. A few rough edges are slips rather than character problems.
Character and point of view
The combination of Söhne for body and UI with Lora for the editorial moments expresses what the .spruce.md described — modern human warmth paired with content-first restraint. The warm cream and sand neutrals, anchored by sage and deep indigo, read as committed to a specific palette character rather than as the AI-default cool-blue-with-purple-accent the moodboard warned against.
When you read the surfaces without context, you imagine a thoughtful product made by someone who has actually meditated. That matches what the .spruce.md describes — “mindfulness for real life” over performance. The signature moment is the hero pairing of the indoor-soft-light meditation photograph with “Find your stillpoint.” in Lora display. That single composition does the work the rest of the page builds on.
Coherence across the work
Internal coherence is in good shape. Every section reads from the same foundation — same primitives, same tokens, same scope. The hero, practices grid, how-it-works steps, pull quote, and signup all use Stillpoint’s sage-and-indigo register consistently. The voice is mostly aligned to the calm encouraging direction the .spruce.md specifies — except in two spots where it slips into SaaS register. Those slips are visible because the rest is so committed; in a more generic page they wouldn’t register.
Specific moments
The strongest moment is the hero — the indoor-soft-light photograph paired with “Find your stillpoint.” in Lora at 48px. The pairing carries the case study’s argument in a single composition: real-life imagery (not wellness-influencer photography), editorial typography (not generic geometric sans), restrained palette. This is what the rest of the page should feel like, and mostly does.
The pull quote with the candle still-life is the second strongest moment. The two-column composition (image left, quote right) breaks the page’s vertical rhythm with an editorial moment that grounds an abstract sentence in a material image. The kind of small move that separates considered work from default output.
The practices grid is the moment where the design hedges. The three-equal-cards layout is exactly the pattern the moodboard’s anti-references named — “asymmetric balance over rigid symmetry” was the direction; three identical cards in a uniform grid is the opposite. The cards themselves are clean and the content is good; the layout archetype underweights what the moodboard committed to.
The signup section is the moment where the design fails its intent. “Join 10,000+ people finding their stillpoint” is the performative social-proof copy the moodboard’s anti-references explicitly excluded. Same for the “Get Started” CTA copy in both the hero and the signup form — the friendly-professional SaaS default rather than the calm-supportive-friend voice the .spruce.md establishes. These are voice slips, fixable with /voice.
Direction forward
Three small moves would tighten the work without changing direction. Run /voice on the hero and signup CTAs plus the social-proof line — they’re the most visible character slips. Run /typeface on the practices eyebrow (apostrophe + letter-spacing) and any other craft details. Reconsider the practices grid layout — the three-equal-cards pattern is the clearest hedge in the page; an asymmetric arrangement matches the moodboard’s direction. Once those land, /finish for the polish pass before ship.
— by Spruce
/critique speaks at the level of design feel — opinionated, grounded in specifics, willing to make a claim. The format is essay, not punch list; the value is seeing the whole.
When to use it
- The interface is functionally sound but something about it feels off, generic, or undercommitted.
- You want feedback on whether the design has a point of view, not just whether it’s technically correct.
- The product’s emotional register or brand coherence is in question.
- A /survey returned few issues but the work still doesn’t feel right — the problems may be directional rather than technical.
- You’re evaluating whether to continue a direction or pivot and want a design-minded take.
- You’re asking “what do you think,” “does this feel right,” or “does this have a point of view.”
How to use it
By default /critique addresses the full project. Pass a page or area to focus the critique on a specific surface. Unlike /survey and /uxreview, /critique doesn’t accept domain-specific scope (no /critique typography) — its value is in looking at the whole, not the parts. A domain-specific critique would collapse into the perspective of a dedicated corrective command.
- /critique pricing page
- /critique onboarding
Anti-patterns it addresses
- Producing a structured finding report with severity tiers and bulleted findings. /critique is narrative, not punch-list — that format belongs to /survey.
- Hedging on every claim. The value of critique is its willingness to make a claim. “This might be too cool, or it might be right” is not useful. Make the claim, acknowledge the counterargument if one exists, move on.
- Padding with generic design wisdom. Every observation should be specific to this work — sentences that could apply to any product belong on a blog post, not in a critique.
- Inventing problems to look thorough. When the work is in strong shape, a short confident critique is the right output. A critique that fabricates concerns to fill space is worse than a brief honest one.
- Lecturing rather than offering perspective. The user has context the critique doesn’t; /critique offers a perspective, not a verdict.