@equal-experts/kuat-react 0.13.1 → 0.14.0-beta.0

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/marketing → reference/media-types/web-marketing}/website.md

@@ -4,24 +4,9 @@ Guidelines for Equal Experts marketing websites and landing pages.
 
 ---
 
-**Prerequisites:** Load [foundations](../../../foundations/) first
-
----
-
 ## Overview
 
-Marketing websites are public-facing pages designed to inform, engage, and convert visitors. They use light backgrounds with full-color branding.
-
----
-
-## When to Use Marketing Layout
-
-Use marketing layout when:
-- Creating public-facing website content
-- Building landing pages
-- External audience (customers, prospects, public)
-- Content-focused pages (blog, documentation)
-- No complex navigation or application features
+Marketing websites are public-facing pages designed to inform, engage, and convert visitors. They use light backgrounds with full-color branding. They are public-facing, target external audiences (customers, prospects, public), and are content-focused without complex navigation or application features.
 
 ---
 
@@ -74,7 +59,7 @@ Use marketing layout when:
 | Header | Full-color | 120-150px |
 | Footer | Full-color | 100-120px |
 
-See [foundations/logo.md](../../../foundations/logo.md) for logo guidelines.
+See [logo](../../brand/logo.md) for logo guidelines.
 
 ---
 
@@ -90,7 +75,7 @@ See [foundations/logo.md](../../../foundations/logo.md) for logo guidelines.
 
 ## Content Guidelines
 
-Follow [foundations/content/](../../../foundations/content/) for writing style.
+Follow [content](../../content/) for writing style.
 
 ### Marketing Content Should:
 
@@ -162,8 +147,8 @@ Follow [foundations/content/](../../../foundations/content/) for writing style.
 
 ## Related Documentation
 
-- [Foundations](../../../foundations/) - Brand and design language
-- [Foundations Accessibility](../../../foundations/accessibility.md) - Accessibility principles
-- [Web Foundations](../README.md) - Common web principles
+- [Reference home](../../README.md) - Brand and design language
+- [Accessibility](../../accessibility/accessibility.md) - Accessibility principles
+- [Web marketing overview](./README.md) - Common web principles
 - [Marketing Emails](./emails.md) - Email guidelines
-- [Marketing Scenarios](./scenarios/) - Patterns for marketing pages
+- [Marketing Patterns](./patterns/) - Patterns for marketing pages

package/agent-docs/external/kuat-agent-rules/reference/media-types/web-product/README.md

@@ -0,0 +1,16 @@
+# Web Product
+
+Reference for Equal Experts web applications, dashboards, internal tools, and product emails.
+
+| File | Scope |
+|------|-------|
+| [design.md](./design.md) | Layout, navigation, product visual patterns |
+| [accessibility.md](./accessibility.md) | Product accessibility requirements |
+| [emails.md](./emails.md) | Transactional / product email patterns |
+| [component-decision-tree.md](./component-decision-tree.md) | Which component source to use (Blocks → Kuat → shadcn → custom) |
+| [component-registry.md](./component-registry.md) | Stable component IDs → overlay/package guides |
+| [content/](./content/) | UX copy (actions, errors, forms, confirmations, empty states) |
+| [patterns/](./patterns/) | Page-type patterns (auth, dashboards, documentation, forms) |
+| [examples/](./examples/) | Framework code samples (React, Vue, CSS) |
+
+Per-component usage, variants, and API live in the implementation overlay or npm package `agent-docs/components/`, resolved via the IDs in [component-registry.md](./component-registry.md) — not in this upstream tree.

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/accessibility.md

@@ -1,19 +1,9 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations/accessibility.md
----
-
 # Technical Accessibility
 
 Implementation rules for WCAG 2.2 AA compliance in web applications.
 
 ---
 
-**Prerequisites:** Load [foundations accessibility](../../../foundations/accessibility.md) first.
-
----
-
 ## Quick reference
 
 - **Semantic HTML:** Use `<button>`, `<a href>`, `<input>`, headings, lists, tables; avoid div/span for interactive or structural meaning.
@@ -396,7 +386,7 @@ Kuat components automatically respect `prefers-reduced-motion`. When building cu
 
 ## Related Documentation
 
-- [Foundations Accessibility](../../../foundations/accessibility.md) - Principles and guidelines
+- [Accessibility foundations](../../accessibility/accessibility.md) - Principles and guidelines
 - [Component Decision Tree](./component-decision-tree.md) - Component selection and patterns
 - [Product Design](./design.md) - Layout patterns
-- [Product Scenarios](./scenarios/) - Applied patterns for specific page types
+- [Product Patterns](./patterns/) - Applied patterns for specific page types

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/component-decision-tree.md

@@ -1,19 +1,9 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations
----
-
 # Component Decision Tree
 
 Component selection and development patterns for Equal Experts web applications.
 
 ---
 
-**Prerequisites:** Load [foundations](../../../foundations/) first.
-
----
-
 ## Overview
 
 When building UI for web applications, follow this priority order to ensure consistency and reduce maintenance burden.
@@ -72,7 +62,7 @@ Build from scratch only when:
 
 ## Per-component guides
 
-Usage, variants, API, and accessibility for each primitive are **not** duplicated in this upstream file. Resolve by stable ID:
+Usage, variants, API, and accessibility for each primitive are **not** duplicated in this upstream file. They live as `components/{slug}.md` in the consumer package `agent-docs/` or overlay, resolved by stable ID via [component-registry.md](./component-registry.md):
 
 | ID | Guide location |
 |----|----------------|
@@ -80,11 +70,7 @@ Usage, variants, API, and accessibility for each primitive are **not** duplicate
 | `kuat:button-group` | `components/button-group.md` |
 | `kuat:kuat-header` | `components/kuat-header.md` |
 
-1. Look up IDs in [component-registry.md](./component-registry.md).
-2. Resolve path via `COMPONENT_MANIFEST` (`ensure-rules.sh` output) or `{RULES_ROOT}/agent-docs/components.manifest.json`.
-3. Load only the component docs referenced by the current task or artifact.
-
-Architecture: [consumption-architecture.md](../../../../setup/consumption-architecture.md).
+See [consumption-architecture.md](../../../kuat-docs/setup/consumption-architecture.md) for the resolution architecture.
 
 ---
 
@@ -191,7 +177,7 @@ Always specify `defaultVariants`:
 
 ### Design Tokens
 
-- Use semantic color tokens (`bg-primary`, not `#0066CC`)
+- Use semantic color tokens (`bg-primary`, not a raw hex)
 - Use spacing scale (`p-4`, not `padding: 17px`)
 - Use border radius rules (0px/4px/6px)
 
@@ -258,6 +244,5 @@ Before shipping a component, verify:
 ## Related Documentation
 
 - [Accessibility](./accessibility.md) - Technical accessibility implementation
-- [Technical Guidelines](./technical.md) - Setup and integration
 - [Design Rules](./design.md) - Layout and visual design
 - [Examples](./examples/) - Framework-specific code examples

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/component-registry.md

@@ -1,24 +1,6 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations, component-decision-tree.md
----
-
 # Component registry
 
-Stable IDs link upstream scenarios and checklists to per-component guides in the implementation overlay or npm `agent-docs/`.
-
----
-
-## How to use
-
-1. Scenario or checklist cites an ID (e.g. `shadcn:button`).
-2. Resolve via `components.manifest.json`:
-   - Package: `node_modules/@equal-experts/kuat-react/agent-docs/components.manifest.json`
-   - Overlay: `{KUAT_RULES_OVERLAY_PATH}/components.manifest.json`
-3. Load `components/{slug}.md` from the manifest `path` field.
-
-**Slug:** ID without namespace prefix (`shadcn:button` → `button`).
+Stable IDs link patterns and checklists to per-component guides in the implementation overlay or npm `agent-docs/`. Component docs live as `components/{slug}.md` in the consumer package `agent-docs/` or overlay, resolved via `components.manifest.json`. The slug is the ID without its namespace prefix (`shadcn:button` → `button`).
 
 ---
 
@@ -26,7 +8,7 @@ Stable IDs link upstream scenarios and checklists to per-component guides in the
 
 | ID | Display name | Source | Overlay / package doc | Upstream refs |
 |----|--------------|--------|----------------------|---------------|
-| `shadcn:button` | Button | shadcn CLI + `kuat-core` theme | `components/button.md` | [forms](./scenarios/forms.md), [authentication](./scenarios/authentication.md), [content/actions](./content/actions.md) |
+| `shadcn:button` | Button | shadcn CLI + `kuat-core` theme | `components/button.md` | [forms](./patterns/forms.md), [authentication](./patterns/authentication.md), [content/actions](./content/actions.md) |
 | `kuat:button-group` | ButtonGroup | `@equal-experts/kuat-react` / `kuat-vue` | `components/button-group.md` | [component-decision-tree](./component-decision-tree.md) |
 | `kuat:kuat-header` | KuatHeader | `@equal-experts/kuat-react` / `kuat-vue` block | `components/kuat-header.md` | [component-decision-tree](./component-decision-tree.md), [design](./design.md) |
 
@@ -64,5 +46,4 @@ Authoritative manifest lives in `kuat-mono` and is published inside each package
 ## Related
 
 - [component-decision-tree.md](./component-decision-tree.md)
-- [consumption-architecture.md](../../../../setup/consumption-architecture.md)
-- [DEPRECATIONS.md](./DEPRECATIONS.md)
+- [consumption-architecture.md](../../../kuat-docs/setup/consumption-architecture.md)

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/content/README.md

@@ -6,7 +6,7 @@ UX writing and content patterns for Equal Experts web applications.
 
 ## Overview
 
-Product content is the text inside product interfaces: buttons, errors, forms, confirmations, empty states. Load [foundations content](../../../../foundations/content/voice-and-tone.md) first, then [product-content.md](./product-content.md).
+Product content is the text inside product interfaces: buttons, errors, forms, confirmations, empty states. The [voice and tone](../../../brand/voice-and-tone.md) foundation and [product-content.md](./product-content.md) cover the core principles.
 
 ---
 
@@ -25,5 +25,5 @@ Product content is the text inside product interfaces: buttons, errors, forms, c
 
 ## Related
 
-- [Foundations content](../../../../foundations/content/README.md)
+- [Writing style](../../../content/writing-style.md)
 - [Product design](../design.md)

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/content/actions.md

@@ -1,9 +1,3 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations, foundations/content/voice-and-tone.md, product/content/product-content.md
----
-
 # Actions (Buttons and Links)
 
 Guidance for button labels and link text in product interfaces.
@@ -41,7 +35,7 @@ Guidance for button labels and link text in product interfaces.
 
 - Use descriptive link text that states the destination or action
 - Avoid "click here", "read more", or "learn more" without context
-- See [foundations content formatting](../../../../foundations/content/formatting.md) for link guidelines
+- See [content formatting](../../../content/formatting.md) for link guidelines
 
 ---
 

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/content/confirmations.md

@@ -1,9 +1,3 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations, product/content/product-content.md
----
-
 # Confirmations
 
 When and how to write confirmation dialogs for destructive or high-impact actions.

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/content/empty-states.md

@@ -1,9 +1,3 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations, product/content/product-content.md
----
-
 # Empty States
 
 How to write copy when there's no data or content to show yet.

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/content/errors.md

@@ -1,9 +1,3 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations, product/content/product-content.md
----
-
 # Errors
 
 How to write error messages that help users fix the problem.

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/content/forms.md

@@ -1,9 +1,3 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations, product/content/product-content.md
----
-
 # Forms
 
 Content guidance for forms: labels, placeholders, helper text, validation, and structure.
@@ -71,4 +65,4 @@ Content guidance for forms: labels, placeholders, helper text, validation, and s
 
 - [Product content](./product-content.md)
 - [Errors](./errors.md)
-- [Foundations accessibility](../../../../foundations/accessibility.md)
+- [Accessibility foundations](../../../accessibility/accessibility.md)

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/content/product-content.md

@@ -1,19 +1,9 @@
----
-scope: type
-platform: web_product
-prerequisites: foundations, foundations/content/voice-and-tone.md
----
-
 # Product Content Guidelines
 
 UX writing and content guidelines for Equal Experts web applications.
 
 ---
 
-**Prerequisites:** Load [foundations](../../../../foundations/) first, especially [voice and tone](../../../../foundations/content/voice-and-tone.md).
-
----
-
 ## Overview
 
 Product content is the text inside product interfaces, designed to help users complete tasks. It's more concise than marketing content and action-oriented.
@@ -128,7 +118,7 @@ Before writing, know:
 
 ## Related Documentation
 
-- [Foundations content](../../../../foundations/content/README.md) - Voice, tone, style
+- [Voice and tone](../../../brand/voice-and-tone.md) - Voice, tone, style
 - [Actions](./actions.md) - Buttons and links
 - [Confirmations](./confirmations.md) - Confirmation dialogs
 - [Empty states](./empty-states.md) - Empty state copy

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/design.md

@@ -1,38 +1,9 @@
----
-scope: type
-platform: web_product
-prerequisites: general
----
-
 # Product Design Rules
 
 Design guidelines for Equal Experts web applications and product interfaces.
 
 ---
 
-**Prerequisites:** Load [foundations](../../../foundations/) first.
-
-**Intent:** Use skill [kuat-review](../../../../skills/kuat-review/SKILL.md) or [kuat-create](../../../../skills/kuat-create/SKILL.md) first.
-
----
-
-## Before you review
-
-1. Run [kuat-review](../../../../skills/kuat-review/SKILL.md) intake (depth, artifacts, output format).
-2. Gather product context per [review-context.md](./review-context.md) when depth is `product_ux` or `full`.
-3. Apply [review-checklist.md](./review-checklist.md).
-4. **Do not load** [examples/](./examples/) for review-only tasks.
-
----
-
-## Before you create
-
-1. Run [kuat-create](../../../../skills/kuat-create/SKILL.md).
-2. Load this file, relevant [scenarios/](./scenarios/), and [content/](./content/) as needed.
-3. Load [examples/](./examples/) when implementing UI in React, Vue, or CSS.
-
----
-
 ## Overview
 
 Product layouts are for web applications, dashboards, and internal tools. They use **dark navigation** for clear visual hierarchy, distinguishing them from marketing layouts.
@@ -137,7 +108,7 @@ For dark navigation (horizontal or sidebar):
 
 **Never use full-color logo on dark backgrounds.**
 
-See [foundations/logo.md](../../../foundations/logo.md) for logo guidelines.
+See [logo guidelines](../../brand/logo.md).
 
 ---
 
@@ -172,8 +143,8 @@ See [foundations/logo.md](../../../foundations/logo.md) for logo guidelines.
 ### Cards and Panels
 
 - Use `bg-card` token for card backgrounds
-- Follow [foundations/design/borders.md](../../../foundations/design/borders.md) for border styling
-- Follow [foundations/design/spacing.md](../../../foundations/design/spacing.md) for padding
+- Follow [borders](../../design-language/borders.md) for border styling
+- Follow [spacing](../../design-language/spacing.md) for padding
 
 ---
 
@@ -199,9 +170,8 @@ See [foundations/logo.md](../../../foundations/logo.md) for logo guidelines.
 
 ## Related Documentation
 
-- [Foundations](../../../foundations/) - Brand and design language
+- [Reference home](../../README.md) - Brand and design language
 - [Accessibility](./accessibility.md) - Technical accessibility implementation
 - [Component Decision Tree](./component-decision-tree.md) - Component selection
-- [Technical Guidelines](./technical.md) - Implementation details
-- [Product Content](./content.md) - UX writing guidelines
-- [Scenarios](./scenarios/) - Applied patterns for specific page types
+- [Product Content](./content/product-content.md) - UX writing guidelines
+- [Patterns](./patterns/) - Applied patterns for specific page types

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product → reference/media-types/web-product}/emails.md

@@ -4,12 +4,6 @@ Guidelines for Equal Experts transactional and product-related emails.
 
 ---
 
-**Status:** Placeholder - details to be defined
-
-**Prerequisites:** Load [foundations](../../../foundations/) first
-
----
-
 ## Overview
 
 Product emails are transactional communications sent from web applications, including confirmations, notifications, and system messages.
@@ -36,7 +30,7 @@ Product emails are transactional communications sent from web applications, incl
 
 ## Content Guidelines
 
-Follow [foundations/content/](../../../foundations/content/) and [product content](./content/product-content.md) for writing style.
+Follow [content foundations](../../content/writing-style.md) and [product content](./content/product-content.md) for writing style.
 
 ### Subject Lines
 - Be specific about the content
@@ -66,6 +60,6 @@ Follow [foundations/content/](../../../foundations/content/) and [product conten
 
 ## Related Documentation
 
-- [Foundations](../../../foundations/) - Brand and design language
+- [Reference home](../../README.md) - Brand and design language
 - [Product Content](./content/product-content.md) - UX writing guidelines
-- [Marketing Emails](../marketing/emails.md) - Marketing email guidelines
+- [Marketing Emails](../web-marketing/emails.md) - Marketing email guidelines

package/agent-docs/external/kuat-agent-rules/reference/media-types/web-product/patterns/README.md

@@ -0,0 +1,10 @@
+# Web Product Patterns
+
+Applied layout and design patterns for web-application page types.
+
+| Pattern | For | Base layout |
+|---------|-----|-------------|
+| [authentication.md](./authentication.md) | Login, registration, password flows, MFA | Single column |
+| [dashboards.md](./dashboards.md) | Analytics, data tables, metrics, reporting | Sidebar navigation |
+| [forms.md](./forms.md) | Settings, multi-step forms, data entry | Varies |
+| [documentation.md](./documentation.md) | Docs sites, knowledge bases, API reference | Sidebar + split |

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product/scenarios → reference/media-types/web-product/patterns}/authentication.md

@@ -192,7 +192,7 @@ Authentication pages should minimise distraction and focus users on the task.
 
 ## Accessibility
 
-**Base requirements:** See [foundations accessibility](../../../../foundations/accessibility.md) and [web accessibility](../accessibility.md)
+**Base requirements:** See [accessibility foundations](../../../accessibility/accessibility.md) and [web accessibility](../accessibility.md)
 
 **Scenario-specific:**
 
@@ -221,7 +221,7 @@ Follow the standard validation pattern:
 
 ### Button Placement
 
-**Component guide:** `shadcn:button` — see [component-registry.md](../component-registry.md); load `components/button.md` from package or overlay.
+**Component guide:** `shadcn:button` — the `components/button.md` guide lives in the consumer package or overlay (see [component-registry.md](../component-registry.md)).
 
 | Button | Position | Variant |
 |--------|----------|---------|
@@ -300,4 +300,4 @@ Follow the standard validation pattern:
 
 - [Product Design](../design.md) - Layout patterns
 - [Web Accessibility](../accessibility.md) - Form validation pattern
-- [Forms Scenario](./forms.md) - General form patterns
+- [Forms Pattern](./forms.md) - General form patterns

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product/scenarios → reference/media-types/web-product/patterns}/dashboards.md

@@ -188,7 +188,7 @@ Dashboards benefit from persistent navigation and maximum content width.
 
 ## Accessibility
 
-**Base requirements:** See [foundations accessibility](../../../../foundations/accessibility.md) and [web accessibility](../accessibility.md)
+**Base requirements:** See [accessibility foundations](../../../accessibility/accessibility.md) and [web accessibility](../accessibility.md)
 
 **Scenario-specific:**
 
@@ -310,4 +310,4 @@ Use for complex filtering (10+ filter options):
 ## Related Documentation
 
 - [Product Design](../design.md) - Sidebar Navigation layout
-- [Foundations Accessibility](../../../../foundations/accessibility.md) - Color and contrast
+- [Accessibility foundations](../../../accessibility/accessibility.md) - Color and contrast

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product/scenarios → reference/media-types/web-product/patterns}/documentation.md

@@ -190,7 +190,7 @@ Docs / Components / Button / Variants
 
 ## Accessibility
 
-**Base requirements:** See [foundations accessibility](../../../../foundations/accessibility.md) and [web accessibility](../accessibility.md)
+**Base requirements:** See [accessibility foundations](../../../accessibility/accessibility.md) and [web accessibility](../accessibility.md)
 
 **Scenario-specific:**
 
@@ -329,5 +329,5 @@ Docs / Components / Button / Variants
 ## Related Documentation
 
 - [Product Design](../design.md) - Sidebar and Split layouts
-- [Foundations Accessibility](../../../../foundations/accessibility.md) - Structure and headings
-- [Foundations Typography](../../../../foundations/design/typography.md) - Type scale and hierarchy
+- [Accessibility foundations](../../../accessibility/accessibility.md) - Structure and headings
+- [Typography](../../../design-language/typography.md) - Type scale and hierarchy

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/types/web/product/scenarios → reference/media-types/web-product/patterns}/forms.md

@@ -166,7 +166,7 @@ We'll send your receipt to this address.
 
 ## Accessibility
 
-**Base requirements:** See [foundations accessibility](../../../../foundations/accessibility.md) and [web accessibility](../accessibility.md)
+**Base requirements:** See [accessibility foundations](../../../accessibility/accessibility.md) and [web accessibility](../accessibility.md)
 
 **Scenario-specific:**
 
@@ -235,7 +235,7 @@ Best for: Related fields (names, addresses)
 
 ### Button Placement
 
-**Component guide:** `shadcn:button` — load `components/button.md` from package `agent-docs/` or `KUAT_RULES_OVERLAY_PATH` when implementing or reviewing button behaviour (see [component-registry.md](../component-registry.md)).
+**Component guide:** `shadcn:button` — the `components/button.md` guide for button behaviour lives in the consumer package `agent-docs/` or overlay (see [component-registry.md](../component-registry.md)).
 
 **Single Form:**
 
@@ -358,4 +358,4 @@ Multiple card sections, each independently saveable:
 
 - [Product Design](../design.md) - Layout options
 - [Web Accessibility](../accessibility.md) - Form validation pattern
-- [Authentication Scenario](./authentication.md) - Login/registration forms
+- [Authentication Pattern](./authentication.md) - Login/registration forms