@vibes.diy/prompts 12.3.2 → 13.0.0

package/llms/access.md

@@ -551,7 +551,7 @@ export default function App() {
           <button type="submit">Post</button>
         </form>
       ) : (
-        viewer && <p style={{ color: "var(--muted, #888)" }}>{canPost.reason}</p>
+        viewer && <p style={{ color: "var(--text-secondary, #888)" }}>{canPost.reason}</p>
       )}
 
       {/* owner-only management — gated on can.* */}

package/llms/use-viewer.md

@@ -208,7 +208,7 @@ Key points:
 
 **Anonymous & always-safe.** `ViewerTag` never throws regardless of login state. A no-prop `<ViewerTag />` would render a "Sign in" button for anonymous viewers, but you don't need to place one for sign-in — the logo's Vibes Switch already offers it.
 
-**Theming.** `ViewerTag` reads `--accent`, `--accent-text`, `--card-bg`, `--border`, `--text`, and `--muted` from the app's CSS variables with sensible fallbacks. If your app defines these on `:root` (which most generated themes do), `ViewerTag` inherits the theme automatically with no extra props.
+**Theming.** `ViewerTag` reads the canonical palette variables — `--surface`, `--text-primary`, `--border`, and `--accent` (plus optional `--accent-text` to override the on-accent text color) — from the app's CSS with sensible fallbacks. If your app defines these on `:root` (which every generated theme does), `ViewerTag` inherits the theme automatically with no extra props. The one exception is the signed-out **Sign in** CTA, which deliberately stays the Vibes brand blue: it is a platform affordance matched to the Vibes Switch shown to the same visitor, so it is not theme-inherited.
 
 Pass `<ViewerTag userHandle={...} />` to render other people. The no-prop `<ViewerTag />` (current user) covers identity and sign-in too, but the logo's Vibes Switch already does that — reach for it only when you specifically want inline avatar self-edit for any signed-in member.
 
@@ -231,7 +231,7 @@ How it behaves:
 - **Raw entry always works.** Pressing Enter commits the sanitized typed text even when nothing matched, so users can reference someone brand-new.
 - `onChange` fires with the picked handle string (or `null` on clear). **Persist only the handle** on your docs — render it later with `<ViewerTag userHandle={...} />`, exactly like `authorHandle`.
 - Works uncontrolled too (omit `value`) when you only need the `onChange` events.
-- Theming matches `ViewerTag` — it reads the same CSS variables (`--accent`, `--card-bg`, `--border`, `--text`, `--muted`).
+- Theming matches `ViewerTag` — it reads the same canonical CSS variables (`--surface`, `--text-primary`, `--text-secondary`, `--border`, `--accent`).
 
 ```jsx
 // Typical write pattern: stash the picked handle on a doc.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "12.3.2",
+  "version": "13.0.0",
   "type": "module",
   "main": "./index.js",
   "description": "",
@@ -24,9 +24,9 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/call-ai-v2": "^12.3.2",
-    "@vibes.diy/identity": "^12.3.2",
-    "@vibes.diy/use-vibes-types": "^12.3.2",
+    "@vibes.diy/call-ai-v2": "^13.0.0",
+    "@vibes.diy/identity": "^13.0.0",
+    "@vibes.diy/use-vibes-types": "^13.0.0",
     "arktype": "~2.2.3",
     "json-schema-faker": "~0.6.3"
   },