Engram
Catalog

Components

66 components across 13 domains — atoms and the composed widgets that build on them. Each ships as a shadcn registry item you install and own. Press ⌘K to jump to any of them.

Primitives

7

Layout

4

Items

11

Cost chip

atom

A currency/cost token: an amount + its currency icon. Used for vendor costs, build/material requirements, and rewards.

Item grid

component

The fundamental inventory/collection container: a CSS grid that lays out item tiles (passed as `children`).

Item hover card

component

Reveals an inspect popup for the trigger (e.g. an ItemTile / gear slot) — the in-game "hover gear to inspect" flyout.

Item image

component

The layered Destiny item square: rarity-colored base, the item art, the season/tier watermark assembly (TierWatermark), the intrinsic glyph, then state chrome (masterwork frame + glow, crafted marker).

Item popup

component

The item inspect flyout — a dark glass panel modeled on the in-game tooltip: a rarity header band, a damage-type + power/ammo readout, flavor, an optional kill tracker, the stat block, the intrinsic frame row, a perk band (`children`, e.g. a `SocketGrid`), and an action `footer` (e.g. Apply).

Item popup header

component

The rarity-gradient header band: name on top, type + rarity on the lower line, and a top-right tier strip (TierWatermark) with the season glyph flush in the corner — the same assembly the item tile composites.

Item stats

component

The Destiny stat block: an aligned grid of right-labeled stat rows.

Item tile

component

A full item tile: the layered ItemImage with a bottom element+power foot, and the signature Destiny white outline on hover.

Power badge

component

The power/light readout: the angular power glyph + the value in gold, with an optional `cap`.

Rarity gem

atom

A small diamond gem in the rarity's token color.

Tier watermark

component

The season/tier corner assembly shared by the item tile and the inspect popup header: a soft scrim, the season crest, and a colored diamond per gear tier — the diamonds and gradient are drawn in CSS (no baked-in Bungie asset margins), so the whole stack aligns precisely.

Sockets & perks

6

Loadout

10

Ability slot

component

A single subclass/loadout socket — an ability, aspect, fragment, super, or class ability.

Artifact perk

component

A seasonal-artifact perk tile — one square cell of the in-game artifact grid: teal-filled when the perk is active, teal-outlined when it's unlocked but unpicked, and dimmed while its tier is still locked.

Energy meter

component

The armor energy capacity readout: a row of pips where `used` are filled, the rest of `total` are empty sockets, and any headroom up to `max` shows as faint upgrade ghosts.

Loadout card

component

A compact build summary: the subclass diamond + name, the equipped item tiles, an optional mod row, the stat tiers, and an action footer.

Mod popup

component

The armor-mod inspect flyout — the in-game mod tooltip, the mod counterpart to PlugPopup.

Mod slot

component

One armor mod socket: a square plug with its energy-cost pip in the corner, or an empty "+" placeholder.

Mod tray

component

A row of ModSlots with an energy-budget meter — the armor mod loadout for one piece. `used` defaults to the summed energy costs; the meter turns over-budget red when the slots exceed `capacity`.

Plug popup

component

The subclass-plug inspect flyout — the in-game tooltip for abilities, aspects, fragments, supers, and subclasses, the counterpart to ItemPopup for non-gear plugs.

Slot row

component

A fixed-count row of AbilitySlots — the aspect or fragment block of a subclass, where the subclass fixes how many slots exist and some may be empty.

Subclass diamond

component

The signature subclass node: a 45°-rotated diamond frame tinted by its damage type, with the subclass icon upright inside and an optional super overlay.

Identity & nameplates

4

Stats

7

Inventory

2

Triumphs

2

Quests

1

Tables

2

Crucible

2

Interaction

8

For agents

llms.txt · MCP

Every component is published to a shadcn registry, so coding agents can discover and install them by name. Point an agent at /llms.txt for the catalog (/llms-full.txt adds every component's props), or wire up the shadcn MCP server and ask it to add @engram/<name>. See Get started for the registry config.