livemark 0.25.0 → 0.26.0

package/source/styles/markdown.css

@@ -2,6 +2,12 @@
 @reference "./general.css";
 
 @layer components {
+  /* A bare URL or long inline code is one unbreakable word that widens the whole
+     page on a phone, so it scrolls sideways. */
+  .prose {
+    overflow-wrap: break-word;
+  }
+
   .prose :is(h1, h2, h3, h4, h5, h6) {
     @apply scroll-mt-28 md:scroll-mt-20;
   }
@@ -43,29 +49,29 @@
   }
 
   .prose pre code .line[data-diff="add"] {
-    @apply bg-green-500/15;
+    @apply bg-positive/15;
   }
 
   .prose pre code .line[data-diff="remove"] {
-    @apply bg-red-500/15;
+    @apply bg-destructive/15;
   }
 
   .prose pre code .line[data-diff="add"]::before {
     content: "+";
-    @apply text-green-600 absolute left-1;
+    @apply text-positive-tint-foreground absolute left-1;
   }
 
   .prose pre code .line[data-diff="remove"]::before {
     content: "-";
-    @apply text-red-600 absolute left-1;
+    @apply text-destructive-tint-foreground absolute left-1;
   }
 
   .prose pre code .line[data-line-status="error"] {
-    @apply bg-red-500/15;
+    @apply bg-destructive/15;
   }
 
   .prose pre code .line[data-line-status="warning"] {
-    @apply bg-yellow-500/15;
+    @apply bg-warning/15;
   }
 
   .prose pre[data-has-focus] code .line:not([data-focus]) {
@@ -100,7 +106,7 @@
   }
 
   .prose pre code .twoslash-error-line {
-    @apply bg-red-500/10;
+    @apply bg-destructive/10;
   }
 
   .prose pre code .twoslash-tag-line {

package/source/styles/shape.css

@@ -0,0 +1,14 @@
+/* Elements name these, never a raw `rounded-md`: controls are pills, rows and cards 1rem,
+   panels 1.5rem. Pills ignore `--radius`; only the `sm`…`xl` scale follows it. */
+@theme inline {
+  --radius-control: 9999px;
+  --radius-control-sm: 9999px;
+  --radius-control-xs: 9999px;
+  --radius-control-inset: 9999px;
+  --radius-textarea: 1rem;
+  --radius-row: 1rem;
+  --radius-card: 1rem;
+  --radius-panel: 1.5rem;
+  --radius-menu: 1rem;
+  --radius-menu-item: calc(1rem - 4px);
+}

package/.agents/skills/change-review/SKILL.md

@@ -1,47 +0,0 @@
----
-name: change-review
-description: Review a pull request for correctness, security and repo conventions, posting findings as inline comments. Invoked by the review workflow and by a person; never fires on its own.
-disable-model-invocation: true
----
-
-# Review a pull request
-
-Read the diff, judge it, post findings as inline comments. Be useful, not thorough-looking:
-a review that flags twenty things teaches nothing, and the twenty-first — the real one — is lost
-in it.
-
-## What to look for
-
-**Correctness**
-
-- Logic that is wrong for an input the change makes reachable, not merely unusual.
-- Error handling that swallows a failure or reports success on a partial write.
-- Concurrency: two requests, two sessions, a retry, a replay.
-- Performance where the change makes it structurally worse (a query in a loop, an unbounded
-  scan), not where it is merely not optimal.
-
-**Security — OWASP-shaped, but reported only when reachable**
-
-- Injection (SQL and otherwise), XSS, SSRF, XXE, unsafe deserialisation.
-- Broken authentication or access control: a route that skips the permission it needs, a scope
-  resolved from user input, an id trusted because it came from the client.
-- Sensitive data exposure: secrets in code or logs, PII widening, a credential recoverable from
-  the database.
-- Insecure cryptography, race conditions and TOCTOU, missing logging on a security-relevant
-  action.
-
-**This repo's own conventions** — these are where a generic reviewer is blind, and they matter
-more than the generic checklist. Read `AGENTS.md` and the sibling skills before judging: a
-change that violates a documented invariant is a finding even when the code is otherwise
-correct.
-
-## How to report
-
-Rate each finding **CRITICAL / HIGH / MEDIUM / LOW**, and say what input or sequence produces
-the failure. A finding that cannot name the case that breaks is a hunch: either verify it or
-leave it out.
-
-Post specific issues as inline comments on the lines they concern. Keep the summary short.
-Silence on the parts that are fine is not laziness — it is what makes the flagged parts legible.
-
-If the change is good, say so briefly and stop. Do not manufacture findings to justify the run.

package/.agents/skills/livemark-customization/SKILL.md

@@ -1,118 +0,0 @@
----
-name: livemark-customization
-description: Use when overriding Livemark's built-in UI or adding custom routes — drop same-named files under .livemark/{components,elements,styles} to shadow defaults, author .livemark/routes/*.tsx for new pages, or copy defaults with the `livemark escape` command.
----
-
-# Livemark Customization
-
-Guidance for customizing the UI layer of a Livemark project beyond what `livemark.config.ts` exposes.
-
-## When to use this skill
-
-Invoke when the user asks to:
-
-- Change a built-in component's layout or markup (Footer, Sidebar, Banner, …).
-- Restyle a shared primitive (buttons, inputs, cards, sheet, …).
-- Rebrand via CSS tokens (colors, radii, typography).
-- Add a brand-new page that isn't a Markdown article (landing hero, pricing page, about page).
-- Replace Livemark's default landing page with a custom React component.
-- Serve a custom `favicon.svg`, `robots.txt`, `og-image.png`, or other static asset.
-
-## Three overlapping mechanisms
-
-| Goal                              | Mechanism                                             |
-| --------------------------------- | ----------------------------------------------------- |
-| Replace a default component/style | Drop a file at `.livemark/components/<Name>.tsx` etc. |
-| Add a new page at an exact URL    | Create `.livemark/routes/<path>.tsx`                  |
-| Serve a static asset at `/<path>` | Put the file in `.livemark/public/<path>`             |
-
-None require config changes. The Vite plugin (`website/plugins/vite-livemark.ts`) watches `.livemark/**` and hot-reloads.
-
-## Discovering what's overridable
-
-Run the `escape` command. No arg lists every overridable file:
-
-```bash
-livemark escape
-```
-
-Output is a flat `<subdir>/<file>` list across `components/`, `elements/`, and `styles/`. With an argument, the command copies the default into `.livemark/`:
-
-```bash
-livemark escape components/Footer.tsx   # → .livemark/components/Footer.tsx
-livemark escape elements/button.tsx     # → .livemark/elements/button.tsx
-livemark escape styles/general.css      # → .livemark/styles/general.css
-```
-
-The command refuses to overwrite an existing override. Delete the override first if you want a fresh start.
-
-## Typical workflow: override a component
-
-1. `livemark escape components/Footer.tsx` — copy the default.
-2. Edit `.livemark/components/Footer.tsx`. All the site's Footer renders shift to the new file on save.
-3. Inside the override, import other Livemark modules from the `livemark/<subdir>/*` subpath exports:
-   ```tsx
-   import { cn } from "livemark/helpers/style"
-   import { Button } from "livemark/elements/button"
-   ```
-
-## Typical workflow: rebrand
-
-1. `livemark escape styles/general.css`.
-2. Edit the `:root` and `.dark` blocks in `.livemark/styles/general.css`:
-   - `--primary` — brand accent (Tailwind-flavoured oklch values work).
-   - `--radius` — corner roundness base.
-   - Sidebar / chart tokens if you want deeper tweaks.
-3. Save — the dev server applies immediately.
-
-Whole-site contrast is audited: light mode targets blue-600, dark mode targets blue-500. Keep new token values AA-compliant on both backgrounds (≥4.5:1 for text).
-
-## Typical workflow: add a page
-
-Custom routes use [TanStack Router](https://tanstack.com/router). Minimal example:
-
-```tsx title=".livemark/routes/about.tsx"
-import { createFileRoute } from "@tanstack/react-router"
-
-export const Route = createFileRoute("/about")({
-  component: () => (
-    <main className="mx-auto max-w-3xl px-6 py-16 prose">
-      <h1>About</h1>
-      <p>Hello.</p>
-    </main>
-  ),
-})
-```
-
-Filename maps to URL path: `.livemark/routes/pricing.tsx` → `/pricing/`. Nested paths work via nested folders.
-
-An `index.tsx` in `.livemark/routes/` **replaces** Livemark's default landing at `/`.
-
-Custom routes win over the Markdown catch-all at exact URLs. Don't create a route that collides with an article URL unless you intend to hide the article.
-
-## Rules of thumb
-
-1. **Don't fork the repo** for routine customization. Use `.livemark/` first — it reliably survives Livemark upgrades.
-2. **Same filename, same path under `.livemark/`.** The override plugin is case-sensitive and mirrors the subdirectory structure exactly.
-3. **Override files are full replacements**, not diffs. Copy the default first (via `escape`), then edit.
-4. **Import Livemark internals via `livemark/*`**, not via relative paths — the plugin routes those through the override resolver, so chained overrides (e.g., your Layout using your Sidebar) compose correctly.
-5. **Static files belong in `.livemark/public/`**, which Vite exposes at the site root.
-
-## What's NOT overridable
-
-- `actions/`, `commands/`, `program.ts` — server/CLI code. Fork upstream if you need to change these.
-- `livemark.config.ts` schema — fixed.
-- Content-collections transform pipeline. Customize markdown via remark/rehype plugins in a fork (or PR upstream).
-
-## Verification
-
-- `pnpm type` — confirms overrides typecheck.
-- `pnpm docs:build` — smoke-test the override lands in the bundle.
-- Browser: load an article page with the dev server; custom Footer/Sidebar/etc. should render without a full reload.
-
-## References
-
-- Narrative docs: `docs/customization/file-overrides.md`, `docs/customization/custom-routes.md`.
-- Plugin implementation: `website/plugins/vite-livemark.ts`.
-- Escape command: `commands/escape.ts`.
-- Subpath exports: `package.json` `exports` block.