Spruce.

§ Corrective

/finish

Final polish before shipping.

What it does

/finish is the last corrective run before deployment. It addresses the small details that accumulate into perceived quality across all seven Spruce dimensions — straight quotes still in prose, headlines that would benefit from text-wrap: balance, hover darkening that drifted between similar components, an accent that crept back where it shouldn’t be — and produces an honest ship-readiness assessment with any remaining concerns identified.

/finish is deliberately scoped to polish. It does not swap typefaces, shift palettes, build missing states, or restructure layouts — those are the dedicated correctives’ work, and if they’re needed, /finish flags them and recommends running them first. The whole point is that by the time /finish runs, the heavy work has been done; only the final tightening and the verdict remain.

Output

/finish · Stillpoint home

Verdict

Ready to ship. With minor items noted.

Polish applied (8 items)

  • Verified prefers-reduced-motion handling across .stp-card--interactive hover, the personalization banner, and the pull-quote rendering — every transition collapses to 0.01ms when the system pref is set.
  • Confirmed AA contrast across all surfaces in both light and dark — including the pull-quote attribution eyebrow on the warm-cream surface and the footer tagline against the page bg.
  • Caught two remaining straight quotes in the practices section description and how-it-works step copy; converted to smart curly form. /typeface had handled the pull quote and practices eyebrow; this swept through the rest.
  • Applied text-wrap: balance to the hero display heading and the practices section title so line breaks respect editorial cadence rather than hitting the column edge mid-phrase.
  • Optical centering nudge on practice card icons — the sage icon glyphs sit visually centered with the duration label baseline now, with a 1px adjustment to compensate for stem weight.
  • Tracking calibrated on the footer wordmark and tagline so the all-caps rhythm reads consistent with the rest of the page's eyebrow rhythm. Was rendering at default tracking; now uses --stp-tracking-wide.
  • Verified focus ring offsets at 2px across every interactive element — Stillpoint primitives (button, input, link), the theme toggle in the case-study header, and the practice card hover affordance.
  • Removed an accidental sage tint on a hairline divider in the how-it-works section — should be neutral border, was reading as a subtle accent line.

Remaining concerns

Ship-blockers

None identified.

Substantial

  • Signup form is missing error / success / client-side validation states. Per /fortify's findings on this surface — the form looks the same after submit as before, with no feedback. Implementation belongs in the next iteration; not a deploy-blocker for the marketing home but worth addressing before launch. Run /fortify.

Minor

  • Personalization banner has no fallback state when no time-of-day recommendation lands. Per /uxreview's polish-tier finding — quiet fallback or hidden treatment to be designed. Run /design.
  • The asymmetric practices grid only activates at md+ breakpoint; below 768px the three cards stack vertically without the featured/supporting hierarchy. Acceptable but tighter responsive treatment is possible. Run /refine.

Ship as-is if the substantial item is acceptable for this release, or address it first. Minor items can land in the next iteration without affecting deployment.

The live artifact

The cumulative result of every command in the catalog — Stillpoint home as it stands after the full workflow — lives at /case-study.

End of output

/finish closes out the work. By this point the heavy correctives have run; what remains is the final tightening and an honest signal about whether the project is genuinely ready to deploy.

When to use it

  • The interface is approaching deployment and needs a final quality pass.
  • Substantial corrective work is complete (typography, color, components, states) and what remains is small refinements.
  • You want a confidence signal about ship-readiness plus any last concerns identified before deploying.
  • The project is being handed off, submitted, or published and deserves a final craft pass.

How to use it

/finish

By default /finish runs a full polish pass across every dimension and produces a ship-readiness assessment. Pass a page or area to narrow scope when shipping a specific surface. /finish does not accept domain-specific scopes (like /finish typography) — domain polish belongs to the domain commands; /finish is explicitly the cross-domain final pass.

  • /finish home page
  • /finish onboarding

Anti-patterns it addresses

  • Substantial work disguised as polish — swapping a typeface, rewriting error messages systemically, establishing states where none exist. If the work requires a dedicated corrective, /finish flags it rather than absorbing it.
  • A ship-ready verdict on a project that isn’t ship-ready. The verdict’s value depends on its honesty; padded confidence is worse than acknowledged remaining work.
  • Padded polish reports — minor tweaks invented to make the change list look substantial. A short report on a strong project is a strong report.
  • Re-running other correctives’ work. If /typeface or /colorgrade have already run, trust their work; polish any small drift since, but don’t repeat the substantial decisions.
  • Introducing new patterns under the guise of polish. Polish is tightening existing patterns, not introducing new tokens, conventions, or approaches.

See also