boxel-skills

Plugin boxel-skills from marketplace cardstack-boxel in cardstack/boxel. Commands read from the repo's manifest — today.

Skills (27)

• api-integrations

  Use when a card needs data from, or sends data to, a third-party API — "show my GitHub pull requests in a card", "pull my open issues", "a card that calls the weather API with my key", "integrate with Stripe/Twilio/OpenAI", "how often can this card poll", "build a PR inbox". Takes a card author from

• api-keys

  Use when a card or the AI assistant needs a user''s API key, or a key shared into a workspace — "this card needs my GitHub token", "the forecast operation was refused binding-not-approved", "let the user add their key", "share my key with this workspace", "add a key button". Also "sign in to GitHub

• boxel-create-edit-cards

  Use when choosing the realm.* calls in a run-realm-code script that create new cards or edit existing instances from the AI assistant.

• boxel-design

  Use when DECIDING a Boxel card's visual language — mood, palette, typography direction, asset direction, one visual signature, the design-playbook process. This is the taste/decision layer. NOT for implementing tokens or CSS inside templates (that's boxel-ui-guidelines) and NOT for creating/editing

• boxel-environment

  Use when running, navigating, or orchestrating tasks inside the live Boxel application — switching between Code Mode and Interact Mode, searching and editing cards, indexing, or any operation that drives the Boxel UI, all through `realm.*` and `room.*` calls in a run-realm-code script. Activates for

• boxel-file-def

  Use when adding or working with file-typed fields (FileDef, ImageDef, MarkdownDef, PngDef, CsvFileDef). Activates when a card needs to reference an image, document, or other file asset.

• boxel-flavored-markdown

  Use when authoring or editing Boxel Flavored Markdown (BFM) content — content fields rendered as rich markdown with :card/::card directives, mermaid diagrams, etc.

• boxel-markdown-format

  Use when authoring a `markdown` template (static markdown format) on a CardDef or FieldDef — defaults, markdownEscape, and markdown helpers.

• boxel-patterns

  Use when the user names an outcome ("show a chart", "let users pick a color", "build a dashboard", "summarize comments", "embed AI image generation", "lay out a moodboard") and you need a working code example to start from. This skill is the bridge between user intent and the existing patterns in Bo

• boxel-skill-authoring

  Use when creating or editing a user-authored Boxel skill — a markdown file whose `boxel.kind: skill` frontmatter makes it loadable by AI assistant rooms. Covers the SKILL.md format contract, the frontmatter schema, tool declarations (codeRef forms, requiresApproval), placement conventions, and how t

• boxel-theme-development

  Use when the deliverable is a theme ARTIFACT — creating, converting, auditing, or patching Theme, StructuredTheme, StyleReference, DetailedStyleReference, or BrandGuide cards; importing/exporting Google DESIGN.md design-system briefs; logo/mark usage and functional palettes. NOT for deciding a card'

• boxel-ui-component-discovery

  MANDATORY before writing any UI in a `.gts` template, including a quick fix to an existing card (turning a styled span or div into a button, wiring a dead control, a design-review fix) and the reuse search design-review runs for each gap. Search the catalog for a component Spec and reuse it — Pret U

• boxel-ui-guidelines

  Use when IMPLEMENTING or REVIEWING UI in Boxel templates (writing a template, or reviewing a change, diff or pull request that touches one) — applying var(--*) theme tokens in <style scoped>, choosing between @fields and @model, using Pret UI components (Button, Chip, Avatar, Select) and the boxel-u

• boxel-workspace-cardinal-rules

  Silent-failure traps in Boxel card authoring — rules that pass lint and often indexing, then corrupt the realm index, crash at render, or drop data with no error (DateField vs DateTimeField formats, external URLs in relationship links, and more). Check every card and field against this list before f

• boxel

  Use whenever creating, reading, or editing Boxel cards (.gts files), card instances (.json), fields, templates, queries, or anything in a Boxel realm. Required for any Boxel coding work — covers CardDef, FieldDef, contains/linksTo, templates, formats, queries, and core patterns. Companion skills - b

• bxl-authoring

  Use when writing or reviewing a BXL expression in a Boxel card — a computeVia built from expression(), the fx / jq tags, spreadsheet-formula fields, aggregations over linked or query-backed collections. Covers which tag to reach for, what the derive profile refuses outright, the silent traps (a stre

• card-motion

  Use when a card should animate: elements entering and leaving, a list or grid rearranging, a tile opening into a detail view, drag and reorder, scroll-linked effects, or several elements moving in a sequenced scene. Covers which of glimmer-motion''s patterns to reach for ({{motion}}, <Presence>, lay

• card-operations-authoring

  Use when adding an operation to a card — "let users add a comment / invite a guardian / create a linked X from this card", "batch create and link", "append to a log without loading the card", "a saved search on this card type", "hide the button if they can''t". Covers declaring `@operation` as data

• catalog-listing

  Use when installing, browsing, remixing, updating, or submitting catalog listings (Apps, Cards, Fields, Skills, Themes) from a Boxel catalog realm. Includes the submission workflow that creates a SubmissionWorkflowCard and GitHub PR.

• catalog-reuse

  MANDATORY before writing any `.gts`. Boxel ships a curated catalog; search it before you author. Classify what you need, then apply the matching reuse operation: a **Spec** when you need building blocks (a CardDef to link, a FieldDef to contain, a component or command to import — catalog modules imp

• design-review

  Score the taste and coherence of a built Boxel screen, card or whole app against its brief and an aesthetic bar, from captures. Runs only when asked (`/design-review`, optionally as a mode, `set`, `card <CardDef>` or `refine`, scoped with `--layout`, `--typo`, `--colour` or `--coherence`, anchored w

• domain-interview

  Use when the user asks for a spec or a brief ("spec this out", "help me think this through"), says they want to plan before building, or asks for an app, kit or card in a domain with rules a builder would not know ("build me a scheduling app for salons"). Not when the user wants a quick mockup of so

• ember-best-practices

  Ember.js performance optimization and accessibility guidelines. This skill should be used when writing, reviewing, or refactoring Ember.js code to ensure optimal performance patterns and accessibility. Triggers on tasks involving Ember components, routes, data fetching, bundle optimization, or acces

• query-backed-relationships

  Use when declaring or reviewing a query-backed `linksTo`/`linksToMany` — the `{ query }` form that resolves by running a search instead of holding authored links. Covers the one thing that surprises everyone (the field holds a bounded page of its query, not the whole match set), reading `totalMatchC

• realm-policy-authoring

  Use when writing, linking, or debugging a realm policy — "let teachers read their own classrooms", "let anyone signed in create a ticket", "why does this grant admit nobody", "point this realm at a policy", "anyone may read", "a public form", "why was this caller refused", "should I grant update", "

• rich-markdown-reports

  Use when a request calls for a report, summary, briefing, or dashboard-style document — especially when you'd otherwise define a new card type to present it. Compose it as a rich Boxel markdown (.md) file that embeds the relevant cards (custom or off-the-shelf) instead of authoring a bespoke CardDef

• source-code-editing

  Use the run-realm-code tool to create and edit source files in a Boxel realm.

Similar plugins