Controlling child-card renders from the parent — fitted vs embedded format choice, the host-injected CardContainer chrome, and the plural-field/atom/stagger/divider traps. Use when embedding cards via or when an embedded/fitted child looks wrong (empty boxes, collapsed grids, double borders, invisible atoms).
Fetch contexts — who carries auth where in Boxel (card code vs prerenderer vs CLI/orchestrator), and why raw fetch() from card code 401s on private realms. Use when card code needs to load cards, files, or external APIs, or when a fetch returns 401/unauthenticated data.
Live, self-updating card lists via @context.searchResultsComponent — the SearchEntryWireQuery contract, query traps, clickable tiles, and live activity feeds. Use when a card needs to list other cards in the realm (home/dashboard sections, feeds, grids) or when a search section renders nothing.
Map of everything Boxel card code can reach — base card-api, host tools, boxel-ui components/helpers, runtime-common, CardContext, AI services, BFM. Use when writing card code that needs an import you don't know the path for, or before reaching for raw fetch / a CDN / a hand-rolled capability.
Lean V2 factory loop — design-first workflow, on-demand skills, no tests until hardening. Use when implementing cards in a target realm through the V2 factory execution loop.
Use when working a software factory run from inside an interactive Claude Code session — picking the next unblocked Issue from a target realm, transitioning its status through the lifecycle, and recording progress as the agent works through the issue backlog. Replaces the orchestrator's issue-scheduler +…
★not rated 27 todayA75 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: