@liebstoeckel/cli 0.3.7

package/LICENSE

@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+    means each individual or legal entity that creates, contributes to
+    the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+    means the combination of the Contributions of others (if any) used
+    by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+    means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+    means Source Code Form to which the initial Contributor has attached
+    the notice in Exhibit A, the Executable Form of such Source Code
+    Form, and Modifications of such Source Code Form, in each case
+    including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+    means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+    means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+    means a work that combines Covered Software with other material, in
+    a separate file or files, that is not Covered Software.
+
+1.8. "License"
+    means this document.
+
+1.9. "Licensable"
+    means having the right to grant, to the maximum extent possible,
+    whether at the time of the initial grant or subsequently, any and
+    all of the rights conveyed by this License.
+
+1.10. "Modifications"
+    means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+    means any patent claim(s), including without limitation, method,
+    process, and apparatus claims, in any patent Licensable by such
+    Contributor that would be infringed, but for the grant of the
+    License, by the making, using, selling, offering for sale, having
+    made, import, or transfer of either its Contributions or its
+    Contributor Version.
+
+1.12. "Secondary License"
+    means either the GNU General Public License, Version 2.0, the GNU
+    Lesser General Public License, Version 2.1, the GNU Affero General
+    Public License, Version 3.0, or any later versions of those
+    licenses.
+
+1.13. "Source Code Form"
+    means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+    means an individual or a legal entity exercising rights under this
+    License. For legal entities, "You" includes any entity that
+    controls, is controlled by, or is under common control with You. For
+    purposes of this definition, "control" means (a) the power, direct
+    or indirect, to cause the direction or management of such entity,
+    whether by contract or otherwise, or (b) ownership of more than
+    fifty percent (50%) of the outstanding shares or beneficial
+    ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+    Licensable by such Contributor to use, reproduce, make available,
+    modify, display, perform, distribute, and otherwise exploit its
+    Contributions, either on an unmodified basis, with Modifications, or
+    as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+    for sale, have made, import, and otherwise transfer either its
+    Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+    or
+
+(b) for infringements caused by: (i) Your and any other third party's
+    modifications of Covered Software, or (ii) the combination of its
+    Contributions with other software (except as part of its Contributor
+    Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+    its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+    Form, as described in Section 3.1, and You must inform recipients of
+    the Executable Form how they can obtain a copy of such Source Code
+    Form by reasonable means in a timely manner, at a charge no more
+    than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+    License, or sublicense it under different terms, provided that the
+    license for the Executable Form does not attempt to limit or alter
+    the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+*                                                                      *
+*  6. Disclaimer of Warranty                                           *
+*  -------------------------                                           *
+*                                                                      *
+*  Covered Software is provided under this License on an "as is"       *
+*  basis, without warranty of any kind, either expressed, implied, or  *
+*  statutory, including, without limitation, warranties that the       *
+*  Covered Software is free of defects, merchantable, fit for a        *
+*  particular purpose or non-infringing. The entire risk as to the     *
+*  quality and performance of the Covered Software is with You.        *
+*  Should any Covered Software prove defective in any respect, You     *
+*  (not any Contributor) assume the cost of any necessary servicing,   *
+*  repair, or correction. This disclaimer of warranty constitutes an   *
+*  essential part of this License. No use of any Covered Software is   *
+*  authorized under this License except under this disclaimer.         *
+*                                                                      *
+************************************************************************
+
+************************************************************************
+*                                                                      *
+*  7. Limitation of Liability                                          *
+*  --------------------------                                          *
+*                                                                      *
+*  Under no circumstances and under no legal theory, whether tort      *
+*  (including negligence), contract, or otherwise, shall any           *
+*  Contributor, or anyone who distributes Covered Software as          *
+*  permitted above, be liable to You for any direct, indirect,         *
+*  special, incidental, or consequential damages of any character      *
+*  including, without limitation, damages for lost profits, loss of    *
+*  goodwill, work stoppage, computer failure or malfunction, or any    *
+*  and all other commercial damages or losses, even if such party      *
+*  shall have been informed of the possibility of such damages. This   *
+*  limitation of liability shall not apply to liability for death or   *
+*  personal injury resulting from such party's negligence to the       *
+*  extent applicable law prohibits such limitation. Some               *
+*  jurisdictions do not allow the exclusion or limitation of           *
+*  incidental or consequential damages, so this exclusion and          *
+*  limitation may not apply to You.                                    *
+*                                                                      *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+  This Source Code Form is subject to the terms of the Mozilla Public
+  License, v. 2.0. If a copy of the MPL was not distributed with this
+  file, You can obtain one at https://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+  This Source Code Form is "Incompatible With Secondary Licenses", as
+  defined by the Mozilla Public License, v. 2.0.

package/README.md

@@ -0,0 +1,74 @@
+# @liebstoeckel/cli
+
+> The `liebstoeckel` command. Scaffold, develop, build, and present decks.
+
+Part of [liebstoeckel](https://liebstoeckel.app), a code-first presentation framework. You write decks in MDX and TSX and build them into a single self-contained HTML file with no server or runtime dependencies. The same file works offline, and when you host it the deck runs a live session between the presenter and the audience. Built on Bun, React 19, Motion, and Tailwind v4.
+
+> **Status: experimental, pre-1.0.** liebstoeckel is an evolving experiment, not yet production-ready. Before 1.0, breaking changes can land in any release without a major-version bump, so pin an exact version if you depend on it.
+
+This is the umbrella CLI. One binary scaffolds a deck, runs a hot-reloading dev server, builds the single-file HTML, captures thumbnails, and drives live presenter mode.
+
+## Install
+
+> It isn't on the public npm registry yet. The commands below are how it will install once it ships. For now, run it from a checkout of the repo (`bun run live|relay|thumbs …`) or from a workspace that links the packages.
+
+```sh
+bun add -d @liebstoeckel/cli
+# …or run it without installing:
+bunx @liebstoeckel/cli <command>
+```
+
+> Requires **Bun ≥ 1.3**.
+
+## Commands
+
+```sh
+liebstoeckel new <name>          # scaffold a new deck in ./<name>
+liebstoeckel add <name>...       # copy registry items (charts, …) into a deck as owned source
+liebstoeckel registry list|view  # browse the chart/component registry (--json for agents)
+liebstoeckel build [dir]         # build a deck into one self-contained .html (+ thumbnails)
+liebstoeckel eject <deck.html>   # recover a built deck's editable source
+liebstoeckel pack [dir]          # inspect or emit the source a build embeds
+liebstoeckel licenses [dir]      # report the third-party licenses bundled into a deck
+liebstoeckel live <deck|dir>     # present live (LAN, or through a --relay)
+liebstoeckel relay               # run a public relay server for WAN presenting
+liebstoeckel thumbs <deck.html>  # (re)generate thumbnails for a built deck
+liebstoeckel export [deck|dir]   # export slides to PNG or PDF
+liebstoeckel skill install       # install the agent skill for deck authoring
+liebstoeckel login|push|orgs|decks|brand   # liebstoeckel cloud (coming soon)
+
+liebstoeckel <deck|dir>          # shorthand for: liebstoeckel live <deck>
+```
+
+There's no `dev` subcommand. For the hot-reloading dev server, run `bun run dev` inside the deck (the scaffold wires the script), or use `liebstoeckel live`.
+
+The bin is installed as both `liebstoeckel` and the short alias `lst`. `live`, `relay`, `thumbs`, and `export` hand off to a sibling package; the rest are implemented here. Every command has its own `--help`. The authoritative command and flag reference lives at [docs.liebstoeckel.app/reference/cli](https://docs.liebstoeckel.app/reference/cli/).
+
+## Architecture
+
+The CLI is a [citty](https://github.com/unjs/citty) dispatcher. `src/cli.ts` defines one root command whose `subCommands` are lazy `() => import(…)` thunks, so a command only pulls in what it needs. `build` never loads the live server, and `live` never loads the bundler. The CLI itself holds almost no logic. It routes, and each command module does the work or hands off to a sibling package.
+
+| File | Role |
+|---|---|
+| `src/cli.ts` | The `liebstoeckel`/`lst` bin. It builds the root citty command, prints best-effort update and skill reminders, and resolves the bare-path shorthand (`liebstoeckel <deck>` becomes `live`) before calling `runMain`. |
+| `src/targeting.ts` | `looksLikeDeck()` decides whether a leading positional is a deck path, so the shorthand kicks in instead of citty reporting an unknown command. |
+| `src/new.ts` | `new` scaffolds a deck from a template (`index.html`, `main.tsx`, `build.ts`, `server.ts`, `bunfig.toml`, `slides/01-intro.tsx`) and bakes in the org's default brand when you're logged in. |
+| `src/build.ts` | Holds `build`, `eject`, `pack`, and `licenses`. Each one calls into `@liebstoeckel/engine` or `@liebstoeckel/thumbnails`. |
+| `src/add.ts`, `src/registry.ts` | Copy registry items into a deck as owned source, and browse the registry. |
+| `src/skill.ts` | `skill install` and `skill update` write the version-pinned agent skill into a deck for each agent target. |
+| `src/cloud.ts`, `src/creds.ts` | The cloud commands (`login` over the RFC 8628 device flow, plus `push`, `orgs`, `decks`, `brand`) and credential storage. |
+| `src/update.ts` | The once-a-day update check and the "deck skill older than the CLI" reminder. Both write to stderr only, and stay quiet for `--json`, pipes, and CI. |
+
+Where each command runs:
+
+- Local commands are implemented in this package: `new`, `add`, `registry`, `skill`, the cloud commands, and `build`/`eject`/`pack`/`licenses`. `build` drives `buildDeck` from `@liebstoeckel/thumbnails/build`; `--check` uses `checkDeck`, `eject` and `pack` use `@liebstoeckel/engine/build/source-package`, and `licenses` reads `collectDeckLicenses` and `extractLicenses`.
+- Delegated commands re-export a citty command straight out of a sibling package, so that package owns its own flags and `--help`: `live` (and the bare-deck shorthand) and `thumbs`/`export` come from `@liebstoeckel/live-server` and `@liebstoeckel/thumbnails`, and `relay` comes from `@liebstoeckel/present-relay`.
+
+## Links
+
+- [CLI reference](https://docs.liebstoeckel.app/reference/cli/) lists every command and flag
+- [Getting started](https://docs.liebstoeckel.app/guides/getting-started/)
+- [Homepage](https://liebstoeckel.app)
+- [Source and issues](https://github.com/liebstoeckel/liebstoeckel-app)
+
+Licensed under [MPL-2.0](https://github.com/liebstoeckel/liebstoeckel-app/blob/main/LICENSE).

package/package.json

@@ -0,0 +1,60 @@
+{
+  "name": "@liebstoeckel/cli",
+  "version": "0.3.7",
+  "description": "The liebstoeckel CLI to scaffold, develop, build, and present code-first decks.",
+  "keywords": [
+    "liebstoeckel",
+    "slides",
+    "presentation-slides",
+    "ai-agents",
+    "ai",
+    "skills",
+    "cli",
+    "mdx",
+    "react"
+  ],
+  "homepage": "https://liebstoeckel.app",
+  "bugs": "https://github.com/liebstoeckel/liebstoeckel-app/issues",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/liebstoeckel/liebstoeckel-app.git",
+    "directory": "packages/cli"
+  },
+  "license": "MPL-2.0",
+  "author": "Leon Kaucher <contact@liebstoeckel.app>",
+  "publishConfig": {
+    "access": "public"
+  },
+  "files": [
+    "src",
+    "!src/**/*.test.ts",
+    "!src/**/*.test.tsx",
+    "skill",
+    "LICENSE"
+  ],
+  "engines": {
+    "bun": ">=1.3"
+  },
+  "type": "module",
+  "bin": {
+    "liebstoeckel": "./src/cli.ts",
+    "lst": "./src/cli.ts"
+  },
+  "exports": {
+    ".": "./src/cli.ts",
+    "./new": "./src/new.ts"
+  },
+  "dependencies": {
+    "@liebstoeckel/engine": "^0.3.5",
+    "@liebstoeckel/live-server": "^0.3.5",
+    "@liebstoeckel/present-relay": "^0.3.5",
+    "@liebstoeckel/registry": "^0.3.4",
+    "@liebstoeckel/theme": "^0.3.3",
+    "@liebstoeckel/thumbnails": "^0.3.5",
+    "citty": "^0.2.2"
+  },
+  "peerDependencies": {
+    "react": "^19.2.7",
+    "react-dom": "^19.2.7"
+  }
+}

package/skill/AGENTS.md

@@ -0,0 +1,18 @@
+<!-- liebstoeckel:start -->
+## Presentations (liebstoeckel)
+
+This project builds presentation decks with **liebstoeckel** (code-first slides → one
+self-contained HTML). To create or edit a deck, drive the `liebstoeckel` CLI:
+
+- Discover charts: `liebstoeckel registry list --json`, then `liebstoeckel registry view <name> --json` for a component's exact `exports`, `props`, and `dataShape`.
+- New deck: `liebstoeckel new <name> --dir presentations [--brand <brand>]` (creates `./presentations/<name>`; without `--dir`, `new` creates `./<name>` in the cwd).
+- Scaffold a chart into a deck (owned source + deps): `liebstoeckel add <name> --dir <deck>`.
+- Validate (run in a loop until `ok:true`): `liebstoeckel build --check --dir <deck>`.
+- Build / export: `liebstoeckel build <deck>` · `liebstoeckel export <deck> --format pdf -o deck.pdf`.
+- Live plugins (not in the registry): `bun add @liebstoeckel/plugin-poll` (or `-qa`/`-reactions`), register on `<Present plugins={[poll]}>`, place `<Plugin id="poll" props={{ … }} />`; present with `liebstoeckel live <deck>`.
+
+Slides are MDX/TSX files in `<deck>/slides/`, listed in order in `main.tsx`; charts are
+owned source in `<deck>/charts/`. Never invent component names or data shapes — read
+them from `registry view`. Don't hand-write the final HTML; author slides and let
+`build` render. Full guide: the `liebstoeckel-deck` skill, or https://docs.liebstoeckel.app/llms.txt
+<!-- liebstoeckel:end -->

package/skill/SKILL.md

@@ -0,0 +1,144 @@
+---
+name: liebstoeckel-deck
+description: >-
+  Create and edit liebstoeckel presentation decks from source material (reports,
+  notes, data). Scaffolds a deck, adds visx chart components from the registry,
+  wires in real data, validates, and builds to a single self-contained HTML or
+  exports PNG/PDF. Use when the user asks to turn a document into slides, build or
+  edit a presentation/deck, add a chart to a slide, or mentions liebstoeckel.
+metadata:
+  version: 0.0.0
+license: MPL-2.0
+---
+
+# General
+
+- **Environment** — liebstoeckel is a framework written in Bun; it requires the **Bun
+  runtime** (not Node). Drive everything through the `liebstoeckel` CLI via bash.
+- **Structure**
+  - A deck is authored as an **npm package** (its own `package.json`) of MDX/TSX slide
+    files.
+  - A deck compiles to **one self-contained `.html`** — JS, CSS, fonts, and assets all
+    inlined; no server, CDN, or runtime deps.
+  - That same `.html` **renders standalone** (open it directly, offline — plugins show a
+    fallback), or can be **hosted live** with
+    `liebstoeckel live [deck|dir|--dir <deck>] [opts]`, which enables the Yjs plugins
+    (poll, Q&A, reactions) for a full presenter/audience session.
+
+# Authoring liebstoeckel decks
+
+liebstoeckel is a code-first presentation framework: a deck is a project of
+**MDX/TSX slide files** that builds to **one self-contained `.html`**. You author it
+by writing slides and scaffolding chart components from a registry — the same code a
+human writes. The `liebstoeckel` CLI does the scaffolding, building, and validating;
+you write content and wire data. Drive everything through the CLI via bash.
+
+**Always prefer the CLI's `--json` output** (it's the machine contract) and **run
+`liebstoeckel build --check` in a loop until it passes** before declaring done — that
+is your correctness signal.
+
+## Create a deck from a source document
+
+1. **See what charts exist** (do this first — never guess component names or data shapes):
+   ```bash
+   liebstoeckel registry list --json
+   ```
+   This returns every component with its `name`, `type`, and `dataShape`.
+
+2. **Scaffold the deck:**
+   ```bash
+   liebstoeckel new <name> --dir presentations [--brand <brand>]   # creates ./presentations/<name>
+   # without --dir, `new` creates ./<name> in the current directory
+   ```
+
+3. **Outline the slides** from the source: a title, then one slide per key point.
+   Decide which points are best shown as a chart and what data each needs.
+
+4. **For every chart slide**, inspect the exact contract, scaffold it, then use it:
+   ```bash
+   liebstoeckel registry view bar-chart --json    # exports, props, dataShape, example
+   liebstoeckel add bar-chart --dir ./presentations/<name>
+   ```
+   Then write a slide that imports the component (from where `add` wrote it) and passes
+   data **matching its `dataShape`** — see `references/components.md`.
+
+   The scaffolded `.tsx` is now **owned source in the deck** — it belongs to the deck,
+   not to a package. Passing data via props is the common path, but when the slide needs
+   something the props don't expose (a different palette, an extra series, an annotation,
+   dropping the legend, a layout or motion tweak), **edit `charts/<Name>.tsx` directly to
+   fit the use case.** That is the whole point of scaffolding owned source; don't work
+   around a chart's limits when you can change the chart.
+
+5. **Write prose slides** as MDX/TSX following `references/authoring.md`.
+
+6. **Validate and fix in a loop:**
+   ```bash
+   liebstoeckel build --check --dir ./presentations/<name>   # JSON: { ok, diagnostics[] }
+   ```
+   If `ok` is false, fix each diagnostic (it carries `file`/`line`/`message`) and
+   re-run until `ok` is true.
+
+7. **Build or export:**
+   ```bash
+   liebstoeckel build ./presentations/<name>                 # → dist/<name>.html
+   liebstoeckel export ./presentations/<name> --format pdf -o deck.pdf
+   ```
+   Report the output path.
+
+## Edit an existing deck
+
+Decks live under `presentations/<name>/` (or the project root). Slides are the files
+in `slides/`, listed in order by the entry. To add/replace a slide, swap a chart, or
+re-theme, see `references/editing.md`. Always finish with the `build --check` loop.
+
+Only have a built `.html`? Recover the editable project first with
+`liebstoeckel eject <deck.html> [outdir]`, then edit and rebuild as usual (details and
+the rebuild's trust caveat in `references/editing.md`).
+
+Building a deck runs its code on this machine, so a deck you did **not** scaffold here
+is untrusted and `build`/`build --check` on it fails with an `untrusted deck` error.
+**Never** pass `--trust` (or set `LIEBSTOECKEL_TRUST_BUILD=1`) on your own — relay the
+trust question to the user and only proceed once they explicitly confirm. See the trust
+note in `references/editing.md`.
+
+## Make a deck interactive (live plugins)
+
+Plugins add live, synced audience interaction; offline the deck still builds and shows
+a static fallback. They are **not in the registry** — don't `registry list` for them.
+The built-ins:
+
+- **poll** (`@liebstoeckel/plugin-poll`) — live voting; results update in real time.
+- **qa** (`@liebstoeckel/plugin-qa`) — audience asks + upvotes questions from any slide;
+  presenter moderates.
+- **reactions** (`@liebstoeckel/plugin-reactions`) — ephemeral floating emoji over the deck.
+
+Adding one is: `bun add` the package, register it on `<Present plugins={[…]}>`, and place
+`<Plugin id="…" props={…} />` on a slide — see `references/plugins.md`. To author a new
+plugin, see `references/build-plugins.md`.
+
+## Rules
+
+- **Never invent component names, props, or data shapes** — read them from
+  `registry list/view --json`. The registry is the source of truth.
+- **Charts are owned source — adjust them to fit the use case.** After `add`, the
+  `.tsx` lives in the deck's `charts/` and is the deck's code, not a package API.
+  Prefer props for data, but freely edit the component itself (palette, series,
+  annotations, labels, layout, motion) whenever the slide needs it — re-running `add`
+  won't clobber your edits unless `--force`. Never import a chart from a package, and
+  never treat its props as a hard limit.
+- **Don't hand-write the final HTML** — author slides + components; let `build` render.
+- **Never trust a deck on the user's behalf.** Building runs the deck's code; if a
+  build fails with `untrusted deck`, do not blindly add `--trust` or
+  `LIEBSTOECKEL_TRUST_BUILD=1` — ask the user, and only proceed once they confirm.
+- Keep going until `build --check` passes; that is the definition of done.
+
+## References
+
+- `references/components.md` — component types in the registry, using scaffolded components/charts, data shapes, the `add` workflow.
+- `references/authoring.md` — slide file conventions (MDX/TSX, notes, steps, layout, brands).
+- `references/editing.md` — editing decks: add/replace slides, swap charts, re-theme, eject.
+- `references/plugins.md` — add live plugins (poll/qa/reactions): register, place, present live.
+- `references/build-plugins.md` — author a custom plugin (`definePlugin`, state, surfaces, server).
+- `references/troubleshooting.md` — the `build --check` loop and common errors.
+
+Full reference docs: https://docs.liebstoeckel.app/llms.txt