ARCHETYPIC

Before the first framework, before the first function, there was a shape. An archetype is not merely a class or a template — it is the resonance that makes all instances recognizable to one another.

We descend into a forest of these shapes. Every interface you will write has been written before, in a language older than silicon. The work of archetypic.dev is to remember them.

What is a CSS selector but a glyph that binds a rule to a shape in the DOM? What is a dependency graph but a spell circle connecting the named to the named? In archetypic.dev, the metaphor isn't decoration — it's documentation.

• #hero .ascent > .glow — a binding across three layers
• @keyframes pulse-glow — an incantation on repeat
• --primary: #ff2d7b — the true name, held in a variable
• filter: drop-shadow() — the aura that follows contour

A pure function is a sigil without side effects. Input in, output out, and the world untouched. The mortal programmer calls it referential transparency; the fae name it by an older word.

Composition is inheritance; currying is the binding of a familiar; memoization is a memory charm. The practices persist; only the glossary changes.

Our work is an ongoing catalog of these archetypes — the fundamental patterns expressed as code artifacts you can read, fork, and invoke in your own rituals.

1. i

   The Observer & the Observed

   Subscriptions, signals, streams. An archetype of attention.

2. ii

   The Gate & the Key

   Authentication, capabilities, scoped tokens. The shape of permission.

3. iii

   The Mirror & the Memory

   Caching, reflection, metaprogramming. Surfaces that remember.

4. iv

   The Thread & the Loom

   Concurrency as weaving. The orchestrated cadence of parallel work.

archetypic.dev is maintained from a small studio between timezones. New entries to the grimoire appear irregularly, as they are remembered. There is no newsletter, no funnel, no checkout. Only the pattern, then the next pattern.