05 / Developer tooling · quality · evidence
Code Hygiene
Shared tools for keeping a growing portfolio of apps understandable and reviewable.
Code Hygiene is the public-facing story for Standards: a private shared-tooling repository that supports quality checks, error handling, and browser evidence across Terra Symposium projects.
Tooling designer and maintainer; developed the shared packages and their public documentation.
Built for Terra Symposium engineering work and its collection of Astro and React applications.
- 03
- complementary packages
- CI
- repeatable repository checks
- UI
- browser evidence for review
/01
The maintenance problem
When a group maintains several applications, conventions can drift. Quality checks, UI failure handling, and browser evidence tend to be rebuilt in slightly different ways, which makes it harder to compare results or keep a consistent baseline.
/02
Three reusable layers
Standards groups maintenance tasks into tools that can be reused by sibling projects. Code Hygiene groups them around the work they support, rather than presenting the private source repository as a public code sample.
- Quality tooling: configurable JavaScript and TypeScript checks with a maintenance CLI.
- Error boundaries: reusable React boundaries and framework helpers for handling UI failures.
- Playwright reporting: screenshots, diagnostics, timings, and evidence outputs assembled for review.
/03
Why evidence belongs in the workflow
A check result is more useful when a teammate can inspect what ran and what the browser showed. The reporting tools turn browser sessions into artifacts that can be discussed, compared, and kept with engineering work.
The aim is practical consistency: make the healthy path easy to repeat and the broken path easier to see.
/04
Public references
The Standards source repository is private. Public references are the documentation site and the published package listings below.
Go a little further
Explore the work.
Sources & further reading
Keep exploring