coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A Christopher Alexander style pattern language for frontend architecture and design.
32 commits 1 branch 0 tags 2.9 MiB
Find a file
tegwick 85ae4f62af Isolate nested dismissal ownership across browsers and builds 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-26 22:35:12 +02:00
architectures Preserve initial frontend pattern language research scaffold 2026-09-24 07:55:34 +02:00
canon Reconcile pattern metadata and prepare contrasting primary-source inputs 2026-09-24 15:23:06 +02:00
patterns Preserve initial frontend pattern language research scaffold 2026-09-24 07:55:34 +02:00
research Isolate nested dismissal ownership across browsers and builds 2026-09-26 22:35:12 +02:00
scripts Reduce research calls with screened reuse and draft VC-02 walkthrough 2026-09-25 08:43:32 +02:00
sequences Preserve initial frontend pattern language research scaffold 2026-09-24 07:55:34 +02:00
technologies Preserve initial frontend pattern language research scaffold 2026-09-24 07:55:34 +02:00
templates Reduce research calls with screened reuse and draft VC-02 walkthrough 2026-09-25 08:43:32 +02:00
tests Reduce research calls with screened reuse and draft VC-02 walkthrough 2026-09-25 08:43:32 +02:00
workplans Isolate nested dismissal ownership across browsers and builds 2026-09-26 22:35:12 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-24 15:23:46 +02:00
.gitignore Exercise Matrix SDK recovery under controlled transport failures 2026-09-25 11:02:03 +02:00
.repo-classification.yaml Record classification provenance and State Hub identifiers 2026-09-23 22:44:39 +02:00
AGENTS.md Reconcile pattern metadata and prepare contrasting primary-source inputs 2026-09-24 15:23:06 +02:00
INTENT.md Register frontend pattern research and establish preliminary intent 2026-09-23 22:44:01 +02:00
Makefile Screen research evidence and record bounded llm-connect refinement 2026-09-25 01:43:16 +02:00
README.md Set up source-grounded frontend research workflows with infospace-bench 2026-09-24 09:47:22 +02:00
REVIEW.md Register frontend pattern research and establish preliminary intent 2026-09-23 22:44:01 +02:00
SCOPE.md Broaden pattern hypotheses across presentation composition and quality 2026-09-26 21:46:28 +02:00
TREE.md Isolate nested dismissal ownership across browsers and builds 2026-09-26 22:35:12 +02:00
WORK-RECORDS.md Refresh index for completed schema and active source review 2026-09-24 15:24:02 +02:00

README.md

frontend-patterns

A coherent, generative pattern language for frontend architecture and design.

The project treats frontend architecture not as a choice among frameworks or named styles, but as the progressive resolution of recurring forces concerning:

  • authority,
  • addressability,
  • projection,
  • interaction,
  • mutation,
  • synchronization and reconciliation,
  • composition,
  • execution and delivery,
  • quality boundaries.

The repository is intended as an infospace for both human and agentic reference.

Its goal is to make frontend architecture:

  1. understandable as a set of recurring design problems,
  2. navigable as a connected language of patterns,
  3. generative rather than merely taxonomic,
  4. explicit about trade-offs and failure modes,
  5. independent of framework fashion,
  6. grounded in known implementations and sources,
  7. machine-readable enough for agents to reason over.

Core proposition

Frontend architecture is the progressive resolution of forces concerning authority, addressability, projection, interaction, synchronization, composition, and execution. A frontend pattern language captures recurring resolutions of those forces and the contexts they create for subsequent design decisions.

Repository map

  • canon/ — normative vocabulary and structure of the language.
  • patterns/ — individual frontend architecture and design patterns.
  • sequences/ — generative sequences for common frontend situations.
  • architectures/ — named architectural configurations expressed through patterns.
  • technologies/ — mappings from technologies/frameworks to the patterns they implement.
  • research/ — research material, source reconciliation, concepts, catalogues, and cases.
  • templates/ — authoring templates for new patterns and mappings.

Design principles

Patterns before products

React, Solid, HTMX, Astro, LiveView, Vue, Svelte and similar technologies are treated as implementations and examples, not as the ontology.

Forces before preferences

A pattern should be selected because of the forces present in a context, not because a framework community considers it idiomatic.

Relations before lists

Patterns form a graph. Important relations include:

  • requires
  • enables
  • refines
  • generalizes
  • complements
  • alternative-to
  • conflicts-with
  • commonly-combined-with
  • creates-context-for
  • implemented-by
  • observed-in

Sequences before checklists

A pattern language should help generate architecture through an ordered sequence of decisions.

Failure modes are part of the pattern

Software patterns must describe when they become harmful, misleading, expensive or fragile.

Status

This repository begins as a v0.1 research scaffold with evidence collection still pending. The first research case is Ryan Carniato's "The Grand Unifying Architecture of Frontend", used as a starting point for decomposing modern frontend architectures into deeper responsibilities and forces.

Research entry point

Start with the research program, its protocol and validation cases. The first cycle is ready in FEP-WP-0002: resolve the metadata contract, review contrasting sources and test a connected seed corpus. Later phases broaden coverage and evaluate retrieval against real systems.

The research bench now provides executable source investigations through infospace-bench. Run make bench-test to verify the adapter and make bench-plan to inspect the synthetic pilot. Real source review is pending.