@honeydeck/honeydeck 0.1.0

package/skills/presentation-writing/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: presentation-writing
+description: Opinionated help for writing excellent slide decks and delivering strong presentations. Use for talk strategy, audience analysis, storylines, slide outlines, headlines, narrative flow, speaker notes, timing, rehearsal, visual clarity, progressive disclosure, and presentation reviews.
+---
+
+# Presentation Writing
+
+You help the user create clear, memorable presentations. Optimize for audience understanding, speaker confidence, and a strong narrative arc.
+
+## First clarify the brief
+
+If missing, ask concise questions about:
+
+- Audience: who they are, what they know, what they care about
+- Goal: inform, persuade, teach, align, sell, decide, or inspire
+- Desired outcome: what should the audience think, feel, or do afterward
+- Context: venue, format, stakes, speaker role, cultural constraints
+- Duration: total time, Q&A time, and expected depth
+- Material: existing notes, data, demos, examples, or required messages
+
+## Opinionated slide principles
+
+- One slide, one job. If a slide has two points, split it.
+- Headlines should say the point, not just label the topic.
+- Keep text sparse. Prefer short phrases over paragraphs. Prose belongs in speaker notes, not on slides.
+- Build a storyline before polishing individual slides.
+- Start with the audience problem, tension, or opportunity.
+- Use evidence after the claim, not instead of the claim.
+- Prefer concrete examples over abstract explanation.
+- Use diagrams for relationships, flows, systems, and tradeoffs.
+- Use charts only when the takeaway is obvious in seconds.
+- Use progressive disclosure when complexity would overwhelm.
+- Remove decoration that does not support comprehension.
+- Speaker notes should contain the talk track, transitions, timing cues, and optional details.
+- Good story over tell everything. You might need to kill a darling to get your main point across.
+
+## Useful story shapes
+
+Choose a simple shape and make it explicit:
+
+- Problem → insight → solution → proof → ask
+- Situation → pain → outcome → path → decision
+- Question → exploration → answer → implication
+- Before → after → bridge
+- Myth → reality → what changes
+- Demo setup → demo → interpretation → next step
+
+## How to draft
+
+1. Write the audience promise in one sentence.
+2. Draft a slide-by-slide headline outline.
+3. Check that the outline tells a story without body text.
+4. Add only the minimum supporting content for each headline.
+5. Add speaker notes for delivery, transitions, and emphasis.
+6. Add visuals, code, diagrams, data, or reveals only where they improve understanding.
+7. Review for pacing: roughly 1–2 minutes per content slide, less for section breaks.
+
+## Review checklist
+
+- Can the main message be summarized in one sentence?
+- Does every slide earn its place?
+- Are the opening and closing memorable?
+- Is the call to action or decision explicit?
+- Does each slide have one clear takeaway?
+- Are dense slides split or simplified?
+- Are jargon and acronyms explained for this audience?
+- Are notes useful for speaking, not just duplicated slide text?
+- Is there a plan for questions, objections, or demos failing?
+
+## Output style
+
+- Be direct and practical.
+- Prefer outlines, rewritten headlines, and concrete slide edits.
+- When writing slides, keep visible text short and put details in speaker notes.
+- This skill is presentation-framework agnostic. If the user is using Honeydeck, pair this guidance with the Honeydeck skill for valid MDX syntax.

package/skills/slidev-migration/SKILL.md

@@ -0,0 +1,153 @@
+---
+name: slidev-migration
+description: Migrate presentations from Slidev (sli.dev) to Honeydeck. Use when the user has a Slidev project, slides.md, Slidev Markdown, Vue components/layouts, v-click/v-clicks, Slidev themes/addons, or asks to move from sli.dev/Slidev to Honeydeck.
+---
+
+# Slidev to Honeydeck Migration
+
+You help users move Slidev presentations to Honeydeck. Slidev is the framework at `sli.dev`; it uses Markdown plus Vue conventions. Honeydeck uses MDX plus React, Vite, Tailwind v4, explicit imports, and Honeydeck layouts/components.
+
+Start by reading all Honeydeck related skills available. Alternatively you can check in the honeydeck node_modules folder and read the docs/skills there.
+
+## Source of truth
+
+Before changing files, read the available project/package docs:
+
+- `Readme.md`, `docs/getting-started.md`, root `SPEC.md`, linked colocated `SPEC.md` files, and `docs/slides.md` for Honeydeck deck structure
+- `docs/configuration.md` for Honeydeck frontmatter
+- `docs/steps-and-reveals.md` for Reveal/RevealGroup/code steps
+- `docs/kits.md` and `docs/kit-authoring.md` for layouts/themes/components
+- Existing Slidev files: `slides.md`, `pages/**/*.md`, `components/**/*.vue`, `layouts/**/*.vue`, `styles/**`, `public/**`, `package.json`, `vite.config.*`, and local theme/addon packages
+
+If Honeydeck docs are not nearby, package docs may be in `node_modules/@honeydeck/honeydeck`, or the user can use the public docs site. A migrated deck's runtime reference pages cover active theme tokens, layouts, and built-in components.
+
+## Migration goal
+
+Create a working Honeydeck presentation that preserves the talk's structure, content, assets, notes, and important reveals. Favor a clear first working migration over a perfect one-to-one port of every Slidev feature.
+
+## First pass workflow
+
+1. Inspect the repository.
+   - Detect Slidev by `slides.md`, `slidev` scripts, `@slidev/cli`, `theme:` frontmatter, `components/*.vue`, or `layouts/*.vue`.
+   - Detect Honeydeck by `deck.mdx`, `honeydeck` dependency/scripts, and `styles.css` importing Honeydeck CSS.
+2. Confirm source and target.
+   - Default source: `slides.md`.
+   - Default Honeydeck target: current repository if it is already a Honeydeck project; otherwise ask whether to migrate in-place or into a new sibling directory.
+3. Initialize Honeydeck if needed.
+   - For a new empty/sibling target, run `npx @honeydeck/honeydeck init --name <target-name>` unless the user asked to avoid commands.
+   - For an existing Slidev repo migrated in-place, create or merge the Honeydeck starter files manually: `deck.mdx`, `styles.css`, `package.json` scripts/dependencies, `public/`, and `components/`. Do not delete the Slidev source until the user approves.
+   - If using a temporary starter (`.honeydeck-migration-starter`), copy only the generated starter patterns you need, then remove the temp directory after asking or when it is clearly safe.
+4. Convert Slidev Markdown to Honeydeck MDX.
+5. Port or stub components/layouts/theme code.
+6. Run validation: `npm install` if needed, then `npm run dev` or at least `npm run build`/`npx honeydeck build` when feasible.
+7. Report what was migrated, what was approximated, and what still needs manual React/visual polish.
+
+## File mapping
+
+| Slidev | Honeydeck |
+| --- | --- |
+| `slides.md` | `deck.mdx` |
+| `pages/*.md` with `src:` includes | imported `.mdx` slide groups, rendered as `<ImportedSlides />` |
+| `public/**` | `public/**` copied unchanged; root-relative `/assets/...` paths usually keep working |
+| `components/*.vue` | `components/*.tsx` React components |
+| `layouts/*.vue` | React layouts plus a layout map selected with deck frontmatter `layouts: "./layouts"` |
+| Slidev theme package | Honeydeck kit/theme/layout map, or local React layouts + CSS |
+| `styles/style.css` or `styles/index.*` | `styles.css` imported from `deck.mdx` |
+| `slidev`, `slidev build`, `slidev export` scripts | `honeydeck dev`, `honeydeck build`, `honeydeck pdf` scripts |
+
+## Syntax conversion checklist
+
+### Deck/head frontmatter
+
+- Keep useful shared metadata: `title`, `description`, `author`, `info` content if relevant.
+- Remove or comment Slidev-only keys unless you map them: `theme`, `addons`, `highlighter`, `lineNumbers`, `drawings`, `download`, `record`, `monaco`, `routerMode`, `selectable`, etc.
+- Add Honeydeck settings when useful: `defaultLayout`, `layouts`, `colorMode`, `pdfSteps`, `showSlideNumbers`.
+- If the first Slidev headmatter also configures the first slide layout/background, preserve slide-specific values in the first slide's frontmatter where Honeydeck supports them.
+
+### Slide separators and frontmatter
+
+- Both frameworks use `---` slide separators. Preserve exact standalone separators.
+- Convert Slidev layout names to Honeydeck names where possible.
+
+### Notes
+
+Slidev uses trailing HTML comments as presenter notes. Honeydeck uses `<Notes>`:
+
+```mdx
+import { Notes } from '@honeydeck/honeydeck'
+
+<Notes>
+This is a presenter note.
+</Notes>
+```
+
+Move only trailing note comments into `<Notes>`. Keep non-note comments as comments or remove if they are implementation noise.
+
+### Clicks and reveals
+
+- `<v-click>...</v-click>` -> `<Reveal>...</Reveal>`
+- `<v-clicks>...</v-clicks>` -> `<RevealGroup>...</RevealGroup>`
+- `v-click` directives on HTML elements -> wrap the element with `<Reveal>`
+- Slidev click positioning (`at`, `v-after`, `.hide`, `v-switch`, `$clicks`) may need custom React state, `TimelineSteps`, or simplified sequential reveals. Do not pretend these are exact if they are not.
+- Add imports as needed:
+
+```mdx
+import { Reveal, RevealGroup, TimelineSteps, Notes, BrowserFrame } from '@honeydeck/honeydeck'
+```
+
+### Code blocks
+
+- Keep normal fenced code blocks.
+- Convert common Slidev stepped highlights like `{1|2|3}` to Honeydeck-supported code step metadata when possible. If unsure, preserve the fence and leave a TODO comment near the block.
+- Slidev Monaco/live-code features need manual React components or simplified static code.
+
+### Vue to React conversion
+
+- Convert `.vue` single-file components to `.tsx` only when they are actually used.
+- Use React props and children instead of Vue props/slots.
+- Use Tailwind v4 utilities or CSS variables instead of Slidev/UnoCSS-specific shortcuts where practical.
+- Use `lucide-react` suffixed `...Icon` imports for icons; do not use inline SVG helpers or unsuffixed lucide aliases.
+- If conversion is large, create a simple placeholder React component first and list it in the migration report.
+
+### Layouts and themes
+
+- Prefer built-in Honeydeck layouts for the first migration.
+- If the Slidev deck depends heavily on a custom theme, create local Honeydeck layouts and a layout map instead of trying to emulate Slidev internals.
+- Put global theme imports in `styles.css`, and import `./styles.css` at the top of `deck.mdx`.
+- Avoid leaking broad CSS into runtime UI. Scope deck-specific CSS to slide content/classes where possible.
+
+## Package migration
+
+For migrated projects, package scripts should look like:
+
+```json
+{
+  "scripts": {
+    "dev": "honeydeck dev",
+    "build": "honeydeck build",
+    "pdf": "honeydeck pdf"
+  }
+}
+```
+
+Keep unrelated project scripts. Remove Slidev dependencies only after the Honeydeck migration builds or after asking the user.
+
+## Quality bar
+
+A good migration result:
+
+- Starts with `npm run dev`.
+- Has `deck.mdx` with valid MDX and explicit imports.
+- Preserves slide order and visible text.
+- Preserves assets and root-relative asset paths.
+- Converts basic notes and reveals.
+- Clearly marks advanced Slidev features that need manual React/Honeydeck follow-up.
+
+## Final response
+
+Summarize:
+
+- Files created/changed.
+- Commands run and whether they passed.
+- Slidev features migrated exactly vs approximated.
+- Manual follow-ups, especially Vue component/layout/theme ports.

package/src/SPEC.md

@@ -0,0 +1,89 @@
+# Honeydeck Public Source Surface Specification
+
+> Observable behavior for public imports and exported types spanning source subpackages.
+
+## Public Imports & Types
+
+### Import Patterns
+
+```ts
+// Core components
+import { Reveal, RevealGroup, TimelineSteps, ListStyle, Keyboard, BrowserFrame, Notes, ColorModeImage } from '@honeydeck/honeydeck'
+
+// Types for kit authors
+import type { LayoutProps, LayoutMap, LayoutDemo } from '@honeydeck/honeydeck/types'
+
+// Theme CSS
+import '@honeydeck/honeydeck/theme.css'
+import '@honeydeck/honeydeck/themes/base.css' // alias for honeydeck/theme.css
+import '@honeydeck/honeydeck/themes/clean.css'
+import '@honeydeck/honeydeck/themes/bee.css'
+
+// Individual layouts and layout-specific slot components
+import BlankLayout from '@honeydeck/honeydeck/layouts/Blank'
+import { Left, Right } from '@honeydeck/honeydeck/layouts/TwoCol'
+import { ColorModeImage as LayoutColorModeImage } from '@honeydeck/honeydeck/layouts/ColorModeImage'
+
+// Named clean layout map, layout imports, and slot components
+import cleanLayouts from '@honeydeck/honeydeck/layouts/clean'
+import CleanBlankLayout from '@honeydeck/honeydeck/layouts/clean/Blank'
+import { Left as CleanLeft, Right as CleanRight } from '@honeydeck/honeydeck/layouts/clean/TwoCol'
+
+// Bee layout map, layout imports, and slot components
+import beeLayouts from '@honeydeck/honeydeck/layouts/bee'
+import BeeBlankLayout from '@honeydeck/honeydeck/layouts/bee/Blank'
+import { Left as BeeLeft, Right as BeeRight } from '@honeydeck/honeydeck/layouts/bee/TwoCol'
+
+// Built-in placeholder image URLs for custom layouts
+import {
+  imagePlaceholder,
+  imagePlaceholderDark,
+  verticalImagePlaceholder,
+  verticalImagePlaceholderDark,
+} from '@honeydeck/honeydeck/layouts/placeholders'
+
+// Public component barrel
+import {
+  Reveal as BarrelReveal,
+  RevealGroup as BarrelRevealGroup,
+  TimelineSteps as BarrelTimelineSteps,
+  ListStyle as BarrelListStyle,
+  Keyboard as BarrelKeyboard,
+  BrowserFrame as BarrelBrowserFrame,
+  Notes as BarrelNotes,
+  ColorModeCycleButton,
+} from '@honeydeck/honeydeck/components'
+import type { ColorMode } from '@honeydeck/honeydeck/components'
+
+// Reserved injected component (generated by Honeydeck remark plugins; not intended for manual slide author use)
+import { HoneydeckCodeBlock } from '@honeydeck/honeydeck/components/code-block'
+```
+
+### Type Definitions
+
+```ts
+import type { ComponentType, ReactNode } from 'react'
+
+/**
+ * Props passed to layout components.
+ * Generic parameter F types the accepted frontmatter fields.
+ */
+type LayoutProps<F extends Record<string, unknown> = Record<string, unknown>> = {
+  title: ReactNode | null // currently a plain text string or null
+  children: ReactNode
+  rawChildren: ReactNode // currently same compiled content as children
+  frontmatter: F
+}
+
+/**
+ * A map of layout names to layout components.
+ */
+type LayoutMap = Record<string, ComponentType<LayoutProps<any>>>
+
+/**
+ * Demo data for the docs reference page.
+ */
+type LayoutDemo<F extends Record<string, unknown> = Record<string, unknown>> = {
+  mdx: string
+}
+```

package/src/assets.d.ts

@@ -0,0 +1,30 @@
+// Type declarations for static image assets handled by Vite bundler
+declare module "*.webp" {
+	const src: string;
+	export default src;
+}
+
+declare module "*.png" {
+	const src: string;
+	export default src;
+}
+
+declare module "*.jpg" {
+	const src: string;
+	export default src;
+}
+
+declare module "*.jpeg" {
+	const src: string;
+	export default src;
+}
+
+declare module "*.svg" {
+	const src: string;
+	export default src;
+}
+
+declare module "*.gif" {
+	const src: string;
+	export default src;
+}

package/src/cli/SPEC.md

@@ -0,0 +1,230 @@
+# Honeydeck CLI Specification
+
+> Observable behavior for CLI commands, build command, and PDF export.
+
+## CLI Commands
+
+### `honeydeck`
+
+Shows help text listing available commands and usage.
+
+Subcommand help:
+
+```bash
+honeydeck help init
+honeydeck dev --help
+honeydeck pdf -h
+```
+
+Behavior:
+
+- `honeydeck`, `honeydeck --help`, `honeydeck -h`, and `honeydeck help` show top-level help
+- `honeydeck help <command>`, `honeydeck <command> --help`, and `honeydeck <command> -h` show a command-specific help page owned by that subcommand for `init`, `skill`, `dev`, `build`, or `pdf`
+- Subcommand help exits successfully without starting the requested command
+- Unknown help targets show top-level help and exit with an error
+
+### `honeydeck init`
+
+Creates a new Honeydeck project interactively.
+
+```bash
+honeydeck init                         # prompts for deck name and optional agent skill installer
+honeydeck init --name awesome-talk     # skip deck name prompt
+honeydeck init --skip-install          # write files without installing dependencies
+honeydeck init --skip-skill            # do not prompt/open the Honeydeck agent skills installer
+honeydeck init --install-skill         # open the Honeydeck agent skills installer without prompting first
+```
+
+Behavior:
+
+- Prompts for project name using clack (skippable with `--name` flag)
+- Validates the project name and creates a directory with that name
+- Prompts before continuing if the target directory already exists
+- Generates starter files, including `deck.mdx`, `styles.css`, `.gitignore`, `package.json`, `public/`, and `components/SparkleButton.tsx`
+- Renders `deck.mdx` and `styles.css` from real template files that can also run as a development demo
+- Installs dependencies with npm unless `--skip-install` is used
+- Asks whether to open the Honeydeck agent skills installer unless `--skip-skill` or `--install-skill` is used, and makes clear that accepting runs `npx skills add`
+- Cancelling any `honeydeck init` prompt or interrupting the spawned skills installer aborts the init flow instead of continuing
+- If cancellation or interruption happens after `honeydeck init` created a new project directory, Honeydeck cleans up that generated project directory before exiting; it never deletes a directory that existed before init started
+- Opens the same interactive `npx skills add <honeydeck-package-source> --copy` flow as `honeydeck skill`, so the `skills` CLI owns skill selection, scope selection, and agent selection
+- `--install-skill` opens the Honeydeck agent skills installer without the preceding Honeydeck confirmation prompt
+- The success outro lists `cd <project>` and `npm run dev` as next steps; it does not include `npm install` because init already attempted dependency installation unless `--skip-install` was used
+- Terminal output is clean, guided, and tasteful with emojis
+
+### `honeydeck skill`
+
+Installs Honeydeck agent skills into the current project.
+
+```bash
+honeydeck skill
+```
+
+Behavior:
+
+- Starts the normal interactive `npx skills add` flow from the local Honeydeck package source and tells users this before launching it
+- Lets the `skills` CLI prompt for bundled skill selection, scope (project/global), and agent selection
+- Uses copy mode so generated projects do not depend on a symlink to the installed Honeydeck package
+- Prints a clear failure message and a manual `npx skills add <honeydeck-repo-url> --copy` fallback if installation fails
+
+### `honeydeck dev`
+
+Starts the development server.
+
+```bash
+honeydeck dev                # default port 4200
+honeydeck dev --port 8080    # custom port
+honeydeck dev -p 8080        # custom port alias
+honeydeck dev --open         # auto-open browser
+honeydeck dev -o             # auto-open alias
+honeydeck dev --deck talk.mdx # use a different deck entry file
+```
+
+Behavior:
+- Starts internal Vite dev server
+- Binds the dev server to all local network interfaces so other devices on the same LAN can open the printed Network URL
+- HMR enabled for MDX/components/styles
+- Does not auto-open browser unless `--open` flag is used
+
+Terminal output:
+
+```txt
+
+  ✨ Honeydeck v0.1.0
+
+  🚀 Local:   http://localhost:4200/
+  🌐 Network: http://192.168.1.42:4200/
+  🎨 Theme:   http://localhost:4200/#/theme
+
+  👀 Watching for changes...
+
+```
+
+### `honeydeck build`
+
+Builds a static SPA.
+
+```bash
+honeydeck build
+honeydeck build --deck talk.mdx
+```
+
+Output structure (Vite default asset names):
+
+```txt
+dist/
+  index.html
+  assets/
+    index-[hash].js
+    index-[hash].css
+  (contents of project public/ copied to dist root)
+```
+
+Deployable to any static host without server-side routing (hash-based URLs).
+
+Terminal output:
+
+```txt
+
+  ✨ Honeydeck v0.1.0
+
+  📦 Build complete!
+  📁 Output: dist/
+  📄 12 slides
+
+```
+
+### `honeydeck pdf`
+
+Exports the deck to PDF.
+
+```bash
+honeydeck pdf                          # output: deck.pdf in current working directory
+honeydeck pdf -o my-talk.pdf           # custom filename
+honeydeck pdf --output my-talk.pdf     # custom filename alias
+honeydeck pdf --steps final            # one page per slide at final state (default)
+honeydeck pdf --steps all              # include all steps as pages
+honeydeck pdf --mode dark              # force dark mode
+honeydeck pdf --mode light             # force light mode
+honeydeck pdf --parallel 6             # capture up to 6 pages at a time
+honeydeck pdf --deck talk.mdx          # use a different deck entry file
+```
+
+Behavior:
+
+- Does not pollute `dist/`
+- Builds an ordered capture plan from the deck and renders one rasterized page per captured state
+- May capture planned pages with bounded parallelism, but final PDF page order must follow the capture plan regardless of screenshot completion order
+- CLI flags override frontmatter (`--mode` over `pdfColorMode`, `--steps` over `pdfSteps`)
+- Effective PDF color mode is `--mode` > `pdfColorMode` > pinned `colorMode` (`light`/`dark`) > `light`
+- Default output: `deck.pdf` resolved relative to the current working directory
+- Default capture parallelism: detected CPU count, capped at `16`; `--parallel` accepts integers from `1` to `16`
+
+Terminal output:
+
+```txt
+
+  ✨ Honeydeck v0.1.0
+
+  🖨️  Exporting PDF...
+  🧵 Capturing 12 pages with N workers...
+  📄 Rendering page 1/12 (slide 1/12)...
+  📄 Rendering page 2/12 (slide 2/12)...
+  ...
+  ✅ Done! deck.pdf (12 pages)
+
+```
+
+---
+
+---
+
+## PDF Export
+
+### Output Format
+
+PDF export preserves browser rendering fidelity by exporting rasterized slide pages. PDF text is not selectable/searchable.
+
+### Behavior
+
+- Does not require a pre-existing production build and does not write to the normal `dist/` output
+- One rendered slide/state per PDF page
+- PDF page dimensions follow deck-level `aspectRatio`: width is fixed at 1920 and height is derived from the ratio (`16:9` → 1920×1080, `4:3` → 1920×1440, etc.). Invalid or missing ratios fall back to 1920×1080.
+- Default output: `deck.pdf` in the current working directory
+- Default steps: final state only
+
+### Color Mode Resolution
+
+PDF color mode resolves in this order:
+
+1. CLI `--mode` (`light` or `dark`)
+2. `pdfColorMode` frontmatter
+3. Deck-level `colorMode` when pinned to `light` or `dark` (not `system`)
+4. `light` (ultimate default)
+
+### Settings
+
+| Setting | CLI Flag | Frontmatter | Default |
+|---------|----------|-------------|---------|
+| Steps | `--steps final` / `--steps all` | `pdfSteps: final` / `pdfSteps: all` | `final` |
+| Color mode | `--mode dark` / `--mode light` | `pdfColorMode: dark` / `pdfColorMode: light` | unset; falls back to pinned `colorMode`, then `light` |
+| Output | `-o file.pdf` / `--output file.pdf` | — | `deck.pdf` |
+| Deck entry | `--deck file.mdx` | — | `deck.mdx` in current directory |
+| Capture parallelism | `--parallel 1` through `--parallel 16` | — | CPU count, capped at `16` |
+
+### Step Handling
+
+- `pdfSteps: final` — each slide appears once, all reveals visible, code at final highlight
+- `pdfSteps: all` — step `0` through final step state are separate PDF pages
+- Capture order is slide order first; in `pdfSteps: all`, step states ascend within each slide. Parallel capture must not change this final PDF page order.
+- During `pdfSteps: final`, `useTimeline()` and `useTimelineSteps()` expose
+  `isPdfFinalRender: true` so custom step-driven components can render an
+  all-open/all-visible PDF state. During `pdfSteps: all`, this flag remains
+  false because components are rendered at their normal step states.
+
+### Interactive Components in PDF
+
+Interactive components (like `SparkleButton`) render their current timeline-driven state. Component mount JavaScript still runs, but no user interactions are simulated during PDF capture.
+
+### Notes in PDF
+
+`<Notes>` content is excluded from normal PDF output.

package/src/cli/args.ts

@@ -0,0 +1,3 @@
+export function hasHelpFlag(args: string[]): boolean {
+	return args.some((arg) => arg === "--help" || arg === "-h");
+}

package/src/cli/banner.ts

@@ -0,0 +1,9 @@
+import packageJson from "../../package.json" with { type: "json" };
+
+export function formatTopLevelBanner(): string {
+	return `  ✨ honeydeck v${packageJson.version} — MDX presentation toolkit`;
+}
+
+export function formatCommandBanner(): string {
+	return `  ✨ Honeydeck v${packageJson.version}`;
+}

package/src/cli/bin.js

@@ -0,0 +1,5 @@
+#!/usr/bin/env node
+import { register } from "tsx/esm/api";
+
+register();
+await import("./index.ts");