Pattern Library Curator
Turn repeated accepted solutions into reusable project patterns.
Current bounded implementation (0.3.0)
The automatic Foundation pack collects candidate compositions from the explicit parent-run chain (maximum 16). It checks canonical repository identity, current complete source/input snapshots, active acceptance, durable passing QA and original image hashes. A candidate needs multiple statically referenced child components, multiple static consumers and distinct declared root identities in the same route/device/action context. Device copies, selector aliases and repeated runs do not multiply uses. Older captures lacking structural root identity cannot be backfilled by inference.
The result remains needs-evidence: observed candidates are not inserted into Foundation.patterns. Professional review must still establish pattern role, when to use/avoid, exceptions and applicable states/variants. Historical image paths/hashes identify local evidence, not bundled originals; revalidate source runs before model curation. Missing accepted history is an evidence gap, not proof the product has no reusable patterns. See docs/accepted-pattern-candidates-2026-10-18.md for bounds and remaining work.
The local Workbench can optionally draft usage guidance from a single candidate. Its separate model adapter revalidates accepted history and current sources, delivers original PNGs plus bounded source context to a read-only Codex session, and validates a dedicated structured-output schema. All supplied image and source references must be cited. propose requires usage, avoidance, exception and limitation text; unresolved/non-reusable verdicts cannot supply usage rules. The saved record is always proposal-only, with frozen original images and input hashes. It does not replace this deterministic Skill result, modify approved Foundation, complete QA or record human acceptance. Governed pattern admission and professional case calibration remain open. See docs/pattern-guidance-review-2026-10-18.md.
Required evidence
- accepted runs
- component and token references
- documented exceptions
Decisions
- Require accepted evidence
- Describe when to use and avoid the pattern
- Link dependencies and examples
Boundary
A one-off solution is not automatically a reusable pattern.
Return structured evidence, findings, proposed updates and limitations. Use needs-evidence when required inputs or professional review are missing. Never invent an Experience Score or promote a project observation into a universal rule.