ADR 0014 — A template is a seed prompt, and the seed is derived not stored

ga · floor-software-engineer

Decision

A template is a seed prompt, and the seed is derived not stored

Why

Clicking a tile on claude.ai/design preloads a prompt into the chat box -- that is the whole observable behaviour -- so a template is a seed prompt plus an inherited design system. Deriving the seed from the skill's capability declaration is what stops it drifting: a stored prompt is a copy of the declaration, and the copy goes on showing a connector the skill stopped using with nothing to disagree. Every seed requires a degraded state, because a surface that renders only the complete answer is the silent-degradation defect in pixel form.

Measured

13 managed templates, verbatim from the picker; blank excluded so a skill that has not chosen one cannot pass a coverage count. 5 of 92 bound, 4 of 13 templates used. Bindings in one table rather than 92 sibling files, because the failure this invites is uniformity by default and one table shows it at a glance. The existing 2e14b7eb floors board predates the design system and does not inherit it -- recorded rather than quietly reused.

Inputs and outputs

This decision declares none. Every name in this section, when present, resolves against the capability vocabulary or the floor registry -- a typo fails the generator rather than rendering.

Where it is