@dittowords/spec-cli 0.0.1-alpha.8 → 0.0.1-alpha.9

package/README.md

@@ -37,7 +37,6 @@ surfaces:
 rules:
   - name: Confirmation dialogs should be direct
     description: Keep confirmation copy terse and unambiguous
-    styleguide: Acme Inc.
     section: Voice & Tone
   - surface: actionText
     name: Calls to action should use active voice
@@ -45,20 +44,17 @@ rules:
     examples:
       - from: "Your settings"
         to: "Open settings"
-    styleguide: Acme Inc.
     section: Voice & Tone
   - term: sign up
     disallowed:
       - signup
       - sign-up
     description: Always use as two words (verb form)
-    styleguide: Acme Inc.
     section: Terminology
 locales:
   de-DE:
     - name: Use informal address
       description: Use "Du" instead of "Sie" for all user-facing copy
-      styleguide: German
       section: Formality
 ---
 ```
@@ -75,13 +71,11 @@ tags: [body, button, call-to-action, dialog-title, heading, nav]
 rules:
   - name: Write in active voice
     description: Lead with verbs, avoid passive constructions
-    styleguide: Acme Inc.
     section: Voice & Tone
 locales:
   de-DE:
     - name: Use informal address
       description: Use "Du" instead of "Sie" for all user-facing copy
-      styleguide: German
       section: Formality
 ---
 ```
@@ -181,7 +175,7 @@ When writing or editing user-facing text for a component:
 5. Rules come in two shapes:
    - **Style rules** have `name`, `description`, and optional `examples` (before/after pairs). Use `examples` as concrete tone/shape guidance.
    - **Terminology entries** have `term` and `disallowed`. Always use the `term` form; never use any of the `disallowed` alternatives.
-6. Each rule carries `styleguide` and `section` metadata indicating its source on the platform.
+6. Each rule carries a `section` field (e.g. "Voice & Tone", "Terminology") providing context for how to interpret it.
 7. If a `locales` key is present, it contains locale-scoped rules keyed by locale code (e.g. `de-DE`). When writing copy for a specific locale, follow the matching `locales.<code>` rules **in addition to** the base `rules`. When writing for the default/base locale, only follow `rules`. Locale-scoped rules never conflict — each locale is a separate boundary.
 
 ### Creating specs

package/dist/commands/init.js

@@ -43,7 +43,7 @@ When writing or editing text props for a component:
 3. Respect ${c("maxLength")} — it's a layout constraint, not a suggestion.
 4. Follow all rules in the ${c("rules")} key. Rules without a ${c("surface")} field apply to every surface; rules with ${c("surface")} apply only to that surface.
 5. Rules come in two shapes: style rules (${c("name")}, ${c("description")}, ${c("examples")}) and terminology entries (${c("term")}, ${c("disallowed")}). For terminology entries, always use the ${c("term")} form and never use the ${c("disallowed")} alternatives.
-6. Each rule carries ${c("styleguide")} and ${c("section")} metadata indicating its source.
+6. Each rule carries a ${c("section")} field (e.g. "Voice & Tone", "Terminology") providing context for how to interpret it.
 7. If a ${c("locales")} key is present, it contains locale-scoped rules keyed by locale code. When writing copy for a specific locale, follow the matching locale's rules in addition to the base ${c("rules")}. When writing for the default locale, only follow ${c("rules")}.
 
 ${h3} Creating specs

package/dist/commands/pull.js

@@ -157,7 +157,6 @@ function toRuleObj(rule) {
             out.examples = rule.examples.map((ex) => ({ from: ex.from, to: ex.to }));
         }
     }
-    out.styleguide = rule.styleguide;
     out.section = rule.section;
     return out;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dittowords/spec-cli",
-  "version": "0.0.1-alpha.8",
+  "version": "0.0.1-alpha.9",
   "description": "CLI for syncing .ditto.md content specs with the Ditto platform.",
   "main": "dist/cli.js",
   "bin": {