Cortex Docs guide: One specification, two outputs, and a unit neither should drop
Use a fictional spec and two paper outputs to trace the number, its unit, and missing entries to the reader.
Producing documentation and developer references from one specification can reduce duplicate maintenance, but similar outputs may communicate different rules. In its September 2026 release, Cortex Docs said it generates browsable documentation and typed SDKs from specifications. This exercise checks only what the reader can see. No spec code, SDK use, or actual generation.
Check each output against one specification card
The paper spec says width is in grid units, an explicit “0” means no width, and blank means unconfirmed, not zero. Document A says all three. Reference B says “Width: number, default 0” and omits the unit. Give two readers the same blank entry, each with just one sample. Ask if blank means 0 and what the unit of “2” is.
A’s reader should say “unconfirmed, don’t enter 0” and “2 grid units.” B drops the unit and changes what blank means. Deleting “default 0” without adding the unit is only half a fix. Verify the unit, explicit zero, and blank separately against the spec. The shared label “width” does not suffice. The samples are invented; no interfaces, projects, or real files were accessed.
Clarify the rules before adding another output
If teams repeatedly maintain browsable docs and a developer reference, a shared starting spec makes Cortex Docs worth comparing. A single internal page is easier to maintain as the original table. Define the unit and blank meaning in the source first. Outputs cannot turn undefined details into facts. The exercise does not establish generation quality, behavior, compatibility, or accuracy.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:www.producthunt.com