Style Guide or Pattern Library¶
Document — instantiates Slot-Template Design
A curated collection of reusable patterns, allowed variants, and usage rules.
A style guide or pattern library is a curated catalog of sanctioned patterns, their permitted variants, and the rules for choosing among them. Its defining move is that it is not an instance to fill but the reference other instances draw from: it publishes which options are eligible, offers a recommended default for the common case, and tells a user which variant to reach for in which situation. It governs no single document or product of its own; it supplies the vocabulary — the approved fills and the swap rules — that document templates, components, and authors consume. Where a policy binds one intent, a style guide offers a menu; its power is in curation and guidance, not enforcement of a protected core.
Example¶
A national magazine maintains a house style guide. On the question of numerals, it curates the eligible set — spell out one through nine, use figures for 10 and up — and marks the spelled-out form as the default an editor applies without deliberating. That is membership: "twelve" is not an approved variant in body copy; "12" is. For quotation, it gives a substitution rule tied to context: use double quotes in running text, but switch to single quotes for a quote-within-a-quote, and to italics (no quotes) for a defined term on first use. An editor working a feature doesn't invent these calls; she looks up which sanctioned variant the situation calls for and applies it.
A staff writer drafts a piece using logical (British) quotation-mark placement picked up from a UK outlet. It isn't in the library's eligible set for this publication, so a copy editor swaps it to the house American convention per the substitution rule. The guide didn't forbid the writer's choice through review or escalation — it simply is not among the catalog's members, and the default plus the swap rule resolve it quietly at the desk.
How it works¶
The library is built by curation: someone decides which patterns and variants are in, writes the usage rule that distinguishes when each applies, and designates the default for the unmarked case. It is consumed by reference rather than executed — writers, designers, and downstream templates look up the sanctioned option and the swap rule rather than being gated by a runtime check. This is the same discipline as a design pattern catalog[1]: each entry names a recurring problem, the approved solution, and its variants, so that reuse means selecting a vetted pattern instead of reinventing one. The guide's authority is soft — it standardizes by being the obvious place to look, and by feeding the defaults that templates ship with.
Tuning parameters¶
- Catalog breadth — how many patterns and variants the library sanctions. A rich catalog covers more cases but is harder to keep coherent and current.
- Rule prescriptiveness — hard "always/never" rules versus contextual guidance. Prescription yields consistency; guidance respects judgment.
- Default opinionatedness — how strongly a recommended variant is pushed. Strong defaults speed decisions but can ossify house style.
- Update cadence — how often the catalog is revised as usage evolves. Frequent updates stay current but destabilize what "approved" means.
When it helps, and when it misleads¶
It shines wherever many people produce similar work and need a shared, lookup-able vocabulary of approved choices — editorial houses, design systems, brand teams. Its honest failure mode is staleness: a catalog that isn't maintained keeps blessing variants the house has quietly abandoned and omits the patterns people now actually use, so the guide and practice drift apart until no one consults it. The classic misuse is treating a soft reference as a hard gate — assuming that because a pattern is "in the library" every use of it is automatically correct, skipping the judgment the usage rule was meant to inform. The guarding discipline is to keep the catalog pruned and dated, and to remember it advises selection rather than certifying any particular instance.
How it implements the components¶
membership_criteria— the catalog defines exactly which patterns and variants are sanctioned, so an unlisted option is simply not eligible.substitution_rule— each entry's usage rule says which approved variant applies in which context, and how to swap a non-house choice for the sanctioned one.default_fill— every pattern designates a recommended default for the common case, which downstream templates and authors adopt without deliberation.
It does not stamp a protected non-negotiable core or route out-of-bounds requests to an adjudicator — that invariant_specification and escape_or_review_path machinery is Policy Template with Local Options's; a style guide advises selection rather than binding and enforcing an intent.
Related¶
- Instantiates: Slot-Template Design — a style guide is the catalog instance: it publishes the eligible fills, defaults, and swap rules that other slot-templates consume.
- Sibling mechanisms: Policy Template with Local Options · Curriculum Template · Document Template · Recipe Pattern · Design System Component Slot · Plugin Slot Registration · Product Configuration Matrix · Modular Form Schema
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Style Guide Or Pattern Library is defined in the frozen evidence as: A curated collection of reusable patterns, allowed variants, and usage rules. Its operative deployed or enacted form is therefore Representation, Specification & Plan.
Nearest alternative: Record, Log & Register — Record, Log & Register can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: A reusable catalog of interface patterns, components, content rules, and accessibility behaviors is a design-system artifact in HCI. The U.S. Web Design System publishes components, patterns, tokens, and guidance as a maintained library; other design fields contribute parallel style guides.
Related originating lineages:
- Art & Aesthetics — Visual art, composition, and design practice supplies a parallel or contributing lineage for the mechanism's defining operation: a curated collection of reusable patterns, allowed variants, and usage rules.
- Communication & Media Studies — communication_media_studies contributes communication and media research to this mechanism's defining operation—A curated collection of reusable patterns, allowed variants, and usage rules—without displacing the selected primary historical lineage.
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: a curated collection of reusable patterns, allowed variants, and usage rules.
- Engineering & Design — Engineering design, reliability, and systems-safety practice supplies a parallel or contributing lineage for the mechanism's defining operation: a curated collection of reusable patterns, allowed variants, and usage rules.
- Library & Information Science — Curation organizes variants.
Review resolution: The blind reviewers disagree on primary lineage (art_aesthetics versus human_computer_interaction). Authoritative or primary research supports human_computer_interaction as the best historical origin: A reusable catalog of interface patterns, components, content rules, and accessibility behaviors is a design-system artifact in HCI. The U.S. Web Design System publishes components, patterns, tokens, and guidance as a maintained library; other design fields contribute parallel style guides. The cited U.S. Web Design System directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=single_lineage records lineage, while domain_reach=universal records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Gamma, E., Helm, R., Johnson, R., & Vlissides, J. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley Professional (1994). Catalogs named recurring design problems, their reusable solution structures and variants, so designers can select established patterns rather than rediscover solutions. registry ↩