Pattern drafting · browser-local pleat arithmetic · 2026 · Solo — product framing, test-first drafting logic, interaction design, accessibility, responsive verification, production deployment

Pleat Draft

A pattern-room instrument that turns two fabric widths into marks a maker can carry to the cutting table.

The problem

Sewing makers drafting a run of equal knife pleats often move between raw width, finished width, seam allowances, pleat take-up, and a handwritten sequence of marks. A correct total can still leave the physical fold-to-placement order hard to inspect at the cutting table. Pleat Draft keeps that bounded transformation causal: enter raw and finished panel widths, equal edge allowances, and two to twenty-four pleats; inspect a proportional opened-fabric tape where every fold and placement line shares the same geometry as the arithmetic; choose a visual pressing direction; then copy the visible sequence as a plain-text ticket. It deliberately models equal knife pleats on one rectangular panel only. It does not account for grain, fabric thickness, turn-of-cloth, pattern matching, pressing loss, drape, or construction suitability, and it asks the maker to proof one repeat on an offcut. Inputs stay in the tab; there is no upload, account, persistence, paid API, tracking SDK, email, payment, advertising, or destructive operation. Production deployment dpl_FKHUiGGc6gNPYxN2KBKjbGZdpiKc reached READY before independent Foundry artifact, HTTPS deploy, and nine-step behavior checks passed at the stable alias.

Architecture

Key decisions

01

Make the unfolded cloth the diagram

The central tape is not decorative. Its pleat cycles, seam bands, fold lines, placement lines, and grainline are positioned from the same tested measurements that produce the ticket.

02

Separate arithmetic from construction judgment

The core proves equal-width geometry only. Press direction is a visual switch, not hidden in the calculation, and the interface repeatedly names fabric behavior and proofing as maker responsibilities.

03

Use one pattern-room Configure bench

Ledger paper, sage cloth, selvedge red, Georgia drafting copy, and Courier evidence labels create dimensions-to-tape-to-ticket causality without feature tiles, a center stack, blur, icon toppers, or dashboard data slop.

04

Repair what real gates exposed

The first production audit found vulnerable transitive packages and the first behavior contract carried one incorrect expected mark. Dependencies were upgraded to a zero-vulnerability result and the contract was corrected against the tested geometry before publication.

Metrics

4
pure pleat-planning tests passing
9
production golden-path steps passing
2
desktop and mobile viewports verified without overflow
0
production dependency vulnerabilities