The estate’s workshop
Every tool, documented — edge cases included.
The Flashy estate builds record formats, verifiers, scaffolds and instruments the way other companies build products. This is their one home: what each tool does, how to run it, and the failures it exists to prevent — written down where the main sites no longer have to carry them.
38 tools catalogued · 22 on npm · 63 documented edge cases · audit of 2026-09-01
Record formats
12 catalogued — the /1 family: append-only records with refusal-first parsers
Packages
12 catalogued — SDKs, verifiers and gateways published for anyone to embed
Scaffolds
2 catalogued — one-command on-ramps, maintained like products
Vendored checks
1 catalogued — dependency-free scripts that run before an install
Estate instruments
10 catalogued — how the estate measures its own condition
Shared configs
1 catalogued — the shared bases every property extends
Why a whole property for tooling
Documentation that lives on a product’s marketing site competes with the product — and loses, page by page, until an integrator finds out what shipped by reading source. flashy.tools moves the deep material here: complete command references, the contracts each format enforces, and the edge cases the estate paid to learn, each one a production incident distilled to the rule that now prevents it.
Everything documented here is pinned by tests in its home repository, and this property passes the standards it documents in its own suite — the doctrine page explains how, and the demo runs a published validator in your browser.