Capacity guide: Separate an empty list from a filter with no results before designing the UI

Give two colleagues the same fictional requirement on paper to expose ambiguity. Assess Capacity as a way to clarify requirements, not as a finished deliverable.

Source: www.producthunt.com
September 20, 2026
2 min

If people interpret the same UI requirement differently, Capacity's spec-first approach is worth comparing. Its January 2026 release page describes Spec Coding as planning first, and a co-creator's public explanation describes clarifying requirements before forming a specification. This guide compares how a specification might help a review. An announcement isn't proof the spec is correct, and this is not about building an app.

What do two different zeroes look like on paper?

Write a fictional requirement: “Show a message when the internal display board's card list has no results.” Ask two colleagues to sketch it independently. Then introduce two fictional input cards: A is a list that has never had any entries. B started with two paper sample cards, but shows zero after filtering by “Blue.” If both say “No entries,” the message incorrectly implies that B's existing items do not exist. Agree on “This list has no entries yet” for A and “No results for this filter” for B, with the active filter still visible on the drawing.

Shuffle the two inputs and the two drawings. Ask someone who hasn't seen them to match the pairs and explain why B's two original entries still exist. If you need to explain it aloud, write the condition, the message, and the visible filter term on the same page. The test is whether different people reach the same answer, not how long your spec is. Paper only: no input or upload of data, code generation, building, installation, execution, account or interface connections.

When one handwritten page is a better choice

If these two drawings are the only dispute and a page gets both colleagues to the same answer, stay with paper or a shared document. If frequent handoffs make teams debate the same condition repeatedly, compare Capacity's approach. Include review and revision time and check whether you can keep an independent copy. Don't assume export in the format you need or count a clear spec as an accepted result.

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