Angle
Every prompt library starts as a folder of markdown files. STRATT starts with a schema. Before a single prompt is written, the system knows what a valid prompt unit looks like — its identity, its contract, its lifecycle state, and its binary wire format.Key Messages
For the design journal (stratt.engineer):@stratt/schema is now live — 87 tests, zero type errors, covering all 5 unit types, a 128-bit binary protocol header, URI addressing, and a full validation pipeline. This is Layer 1 of 7. The CLI cannot scaffold, validate, or publish a prompt unit without it. Schema first means the foundation is verifiable before anything is built on top.
For developer audiences (Show HN / dev community):
Most prompt engineering tools treat prompts as strings. STRATT treats them as typed, versioned, fingerprinted protocol units with explicit contracts (inputs/outputs/failure modes), CRDT merge semantics, and a 128-bit binary header. The schema package validates all of this at parse time using Zod discriminated unions — zero runtime surprises.
For LinkedIn / professional network:
Week 1 of building STRATT in public: shipped the schema layer. Five unit types. Nine domains. Six lifecycle states. A binary protocol header. 87 tests. No CLI yet — because the schema has to be right first. This is what “schema-first” means in practice.
Content Opportunities
- Design journal entry: “Why the schema comes before the CLI” — reference the learning, show the 7-layer diagram, explain CON-010 draft isolation
- Technical post: Deep dive on the SPUH binary header — 128 bits that encode everything about a prompt unit’s identity
- Thread/short-form: The CRDT merge ordering correction — finding a spec gap during implementation and why that matters for distributed prompt versioning