uniweb 0.7.9 → 0.8.0

package/README.md

@@ -250,12 +250,13 @@ npx uniweb add site main --from marketing --foundation marketing
 
 The workspace grows organically. `add` handles placement, wires dependencies, updates workspace globs, and generates root scripts. Use `--path` to override default placement, or `--project` for co-located layouts (e.g., `marketing/foundation/` + `marketing/site/`).
 
+> `npx uniweb` works before and after install. Once dependencies are installed, you can also use `pnpm uniweb` directly since `uniweb` is a project dependency.
+
 **Or start blank and build up:**
 
 ```bash
 pnpm create uniweb acme --template blank
 cd acme
-pnpm install
 npx uniweb add foundation
 npx uniweb add site
 pnpm install

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.7.9",
+  "version": "0.8.0",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,9 +41,9 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/kit": "0.6.1",
-    "@uniweb/build": "0.7.5",
+    "@uniweb/build": "0.8.0",
     "@uniweb/core": "0.5.1",
+    "@uniweb/kit": "0.7.0",
     "@uniweb/runtime": "0.6.1"
   }
 }

package/partials/agents-md.hbs

@@ -200,14 +200,19 @@ CCA separates theme from code. Components use **semantic CSS tokens** instead of
 |-------|---------|
 | `text-heading` | Headings |
 | `text-body` | Body text |
-| `text-muted` | Secondary text |
-| `bg-surface` | Section background |
-| `bg-surface-subtle` | Slightly offset surface |
-| `border-edge` | Borders |
-| `border-edge-muted` | Subtle borders |
+| `text-subtle` | Secondary/de-emphasized text |
+| `bg-section` | Section background |
+| `bg-card` | Card/panel background |
+| `bg-muted` | Hover states, zebra rows |
+| `border-border` | Borders |
 | `text-link` | Link color |
-| `text-on-primary` | Text on primary-colored backgrounds |
-| `bg-primary` | Brand primary color |
+| `bg-primary` | Primary action background |
+| `text-primary-foreground` | Text on primary background |
+| `bg-secondary` | Secondary action background |
+| `text-success` / `bg-success-subtle` | Status: success |
+| `text-error` / `bg-error-subtle` | Status: error |
+| `text-warning` / `bg-warning-subtle` | Status: warning |
+| `text-info` / `bg-info-subtle` | Status: info |
 
 **Content authors control context** in frontmatter:
 
@@ -376,7 +381,7 @@ When given a monolithic React file (AI-generated or hand-built), don't port line
 
 1. **Name by purpose** — `Institutions` → `Testimonial`, `WorkModes` → `FeatureColumns`. Components render a *kind* of content, not specific content.
 2. **Separate content from code** — Hardcoded strings → markdown. Layout/styling stays in JSX. Content authors edit words without touching code.
-3. **Use semantic tokens** — Replace `text-slate-900` with `text-heading`, `bg-white` with `bg-surface`. Component works in any context and any brand.
+3. **Use semantic tokens** — Replace `text-slate-900` with `text-heading`, `bg-white` with `bg-section`. Component works in any context and any brand.
 4. **UI components → `components/`** — Buttons, badges, cards go in `src/components/` (no `meta.js` needed).
 
 You don't have to convert everything at once. Each section is independent — one can use hardcoded content while another reads from markdown.

package/src/index.js

@@ -501,7 +501,6 @@ async function main() {
   if (templateType === 'blank') {
     log(`Next steps:\n`)
     log(`  ${colors.cyan}cd ${projectName}${colors.reset}`)
-    log(`  ${colors.cyan}${installCmd(pm)}${colors.reset}`)
     log(`  ${colors.cyan}npx uniweb add foundation${colors.reset}`)
     log(`  ${colors.cyan}npx uniweb add site${colors.reset}`)
     log(`  ${colors.cyan}${installCmd(pm)}${colors.reset}`)