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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@equal-experts/kuat-react",
-  "version": "0.13.1",
+  "version": "0.14.0-beta.1",
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.js",
@@ -107,7 +107,7 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/your-org/kuat-mono.git",
+    "url": "https://github.com/equalexperts/kuat-mono.git",
     "directory": "packages/kuat-react"
   },
   "scripts": {

package/agent-docs/external/kuat-agent-rules/kuat-docs/rules/LOADING.md

@@ -1,166 +0,0 @@
-# Agent Rules Loading Index
-
-**Canonical reference** for which rule files to load for each task type. Use this index to resolve "task X" → exact list of files. All paths are relative to `kuat-docs/rules/`.
-
----
-
-## Intent (review | create)
-
-Determine intent before loading type rules. If unclear, ask: *Are you reviewing existing work or creating something new?*
-
-| Intent | Load first | Then |
-|--------|------------|------|
-| **review** | Skill [kuat-review](../../skills/kuat-review/SKILL.md) — run [ensure-rules](../../skills/scripts/ensure-rules.sh) | foundations → [roles/brand-reviewer.md](./roles/brand-reviewer.md) → type rules (see [Review load notes](#review-load-notes)) |
-| **create** | Skill [kuat-create](../../skills/kuat-create/SKILL.md) — run [ensure-rules](../../skills/scripts/ensure-rules.sh) | foundations → create role card if any → type rules → scenarios/examples as needed |
-
----
-
-## Load order
-
-1. **Determine intent** (review | create) and load the matching [skill](../../skills/) (`kuat-review` or `kuat-create`); resolve rules via [skills/shared/resolve-rules.md](../../skills/shared/resolve-rules.md).
-2. **Always load foundations** (see [Foundations](#foundations) below).
-3. **Load the role card** for the intent: [brand-reviewer](./roles/brand-reviewer.md) for review; task-specific role for create when listed in [Role cards](#role-cards).
-4. **Then load type-specific rules** for the task (see [Task → rules](#task--rules)).
-5. **Optionally** add scenarios or examples when relevant (see [Optional paths](#optional-paths)).
-
-**Platform isolation:** Type-specific rules must not reference other types. Foundations are shared; types only reference foundations.
-
-## Entry points
-
-| Entry | Audience | Start | Index file |
-|-------|----------|-------|------------|
-| **Org** | Brand, slides, all platforms | [AGENTS.md](../../AGENTS.md) | This file (`LOADING.md`) |
-| **Library** | `kuat-mono` contributors | Mono `AGENTS.md` | This file + mono `kuat-docs/LOADING.md` overlay |
-| **App** | npm consumers | `node_modules/@equal-experts/kuat-react/agent-docs/AGENTS.md` | `agent-docs/rules/LOADING-consumer.md` (generated on publish) |
-
-Full architecture: [setup/consumption-architecture.md](../setup/consumption-architecture.md).
-
-Run [ensure-rules.sh](../../skills/scripts/ensure-rules.sh) — emits `RULES_SOURCE=git|package` and optional `OVERLAY_DIR`.
-
-## Cross-repo consumption contract
-
-When these rules are used from a consumer implementation repo (for example `kuat-mono`) or via npm packages:
-
-1. Resolve rules: git `kuat-agent-docs` or bundled `agent-docs` in `@equal-experts/kuat-react` / `kuat-vue`.
-2. Load local implementation overlay second when `KUAT_RULES_OVERLAY_PATH` is set.
-
-Conflict policy:
-- Design/structure/content guidance -> upstream rules or bundled snapshot at package version.
-- Implementation/API/testing/build -> local implementation repo or package component docs.
-- If implementation behavior remains ambiguous, trust runtime evidence in this order: tests, Storybook, package exports, source code.
-
-Ownership: [setup/ownership-matrix.md](../setup/ownership-matrix.md).
-
----
-
-## Foundations
-
-**Path:** `foundations/`
-
-**Shared (top level):**
-| File | Description |
-|------|-------------|
-| `foundations/brand.md` | Brand principles and identity |
-| `foundations/logo.md` | Logo variants, sizing, placement |
-| `foundations/accessibility.md` | Accessibility principles and guidelines |
-
-**Design** (`foundations/design/`):
-| File | Description |
-|------|-------------|
-| `foundations/design/design-language.md` | Design principles |
-| `foundations/design/colours.md` | Brand color palette |
-| `foundations/design/typography.md` | Fonts and type scale |
-| `foundations/design/spacing.md` | Spacing system |
-| `foundations/design/borders.md` | Border philosophy |
-
-**Content** (`foundations/content/`):
-| File | Description |
-|------|-------------|
-| `foundations/content/voice-and-tone.md` | Voice, tone, audience, quality checklist |
-| `foundations/content/writing-style.md` | Active voice, plain language, conciseness |
-| `foundations/content/formatting.md` | Capitalisation, headings, links, lists |
-| `foundations/content/numbers.md` | Dates, times, currency, units |
-| `foundations/content/punctuation.md` | Punctuation conventions |
-
-**When to load:** For minimal context, load only the foundation file(s) relevant to the task. For standard or full context, load all of `foundations/` (shared + design + content as needed, ~800+ lines).
-
----
-
-## Role cards
-
-**Path:** `roles/`
-
-Load after foundations (or inject as the first instruction block). Task → role mapping: [roles/README.md](./roles/README.md).
-
-| Intent | Role card |
-|--------|-----------|
-| **review** (all task types) | [roles/brand-reviewer.md](./roles/brand-reviewer.md) |
-
-| Task type (create) | Role card |
-|--------------------|-----------|
-| infographics | [roles/technical-illustrator.md](./roles/technical-illustrator.md) |
-| icons | [roles/icon-designer.md](./roles/icon-designer.md) |
-
----
-
-## Task → rules
-
-| Task type | Required foundations | Required type-specific | Notes |
-|-----------|----------------------|------------------------|--------|
-| **slides** | All foundations (or: brand, logo, design, content) | `types/slides/` | Full rule set: brand-compliance, styling, layouts, content, imagery-and-diagrams, data, checklist; scenarios when deck type is known. |
-| **photography** | brand (or all foundations) | `types/photography/` | Full rule set: principles, diversity-inclusion, style-and-sources, quality-validation. |
-| **icons** | brand, design/colours (or all foundations) | `types/graphics/icons.md` | Single file. |
-| **illustrations** | brand, design/colours, design/typography (or all foundations) | `types/graphics/illustrations.md` | Single file. |
-| **infographics** | brand, design/colours, design/typography, design/spacing (or all foundations) | `types/graphics/infographics.md` | Single file. |
-| **charts_data** | design/colours, design/typography (or all foundations) | `types/charts-data/` | Placeholder/skeleton; has minimal chart-type guidance. |
-| **web_marketing** | All foundations | `types/web/marketing/` | Include scenarios when designing specific marketing page types; content in `types/web/marketing/content/`. |
-| **web_product** | All foundations | `types/web/product/` | Include scenarios for docs, forms, dashboards, auth; content in `types/web/product/content/`; include examples when implementing in React/Vue/CSS. |
-
----
-
-## Review load notes
-
-When intent is **review**, use these load deltas (in addition to skill [kuat-review](../../skills/kuat-review/SKILL.md)):
-
-| Task type | Load | Skip |
-|-----------|------|------|
-| **slides** | All `types/slides/` core files + [checklist.md](./types/slides/checklist.md); scenario if deck type known | — |
-| **web_product** | [design.md](./types/web/product/design.md), [accessibility.md](./types/web/product/accessibility.md), [component-decision-tree.md](./types/web/product/component-decision-tree.md), [review-context.md](./types/web/product/review-context.md), [review-checklist.md](./types/web/product/review-checklist.md); relevant scenario if flow type known | `types/web/product/examples/` |
-| **Others** | Foundations + type README + any validation checklist (e.g. photography `quality-validation.md`) | Implementation examples unless reviewing code |
-
----
-
-## Optional paths
-
-| Path | When to include |
-|------|------------------|
-| `types/slides/scenarios/` | Deck type known (sales, knowledge sharing, case study, reporting). |
-| `types/photography/` | Selecting or reviewing slide photography beyond placement rules. |
-| `types/charts-data/` | Building or restyling complex charts for slides. |
-| `types/web/marketing/scenarios/` | Task involves specific marketing page types (see scenarios README). |
-| `types/web/marketing/content/` | Task involves marketing copy, blog, or SEO. |
-| `types/web/product/scenarios/` | Task involves documentation pages, forms, dashboards, or authentication flows. |
-| `types/web/product/content/` | Task involves product UX writing (actions, errors, forms, etc.). |
-| `types/web/product/examples/` | **Create only:** implementing web product UI in React, Vue, or vanilla CSS. **Do not load for review.** Prefer component IDs + package/overlay docs (see [DEPRECATIONS.md](./types/web/product/DEPRECATIONS.md)). |
-| Component guides (`components/{slug}.md`) | Artifact or scenario cites a component ID ([component-registry.md](./types/web/product/component-registry.md)). Resolve via `COMPONENT_MANIFEST` from package `agent-docs/` or `KUAT_RULES_OVERLAY_PATH`. Load on demand, not the full catalog. |
-
----
-
-## Context size reference
-
-| Level | What to load | Approx. size |
-|-------|----------------|--------------|
-| Minimal | Single foundation file (e.g. `foundations/design/colours.md`) | ~100 lines |
-| Standard | All `foundations/` | ~800 lines |
-| Full (web product) | `foundations/` + `types/web/product/` | ~2000 lines |
-| Full (web product + examples) | Above + `types/web/product/examples/` | ~3500 lines |
-
----
-
-## Related
-
-- [skills/](../../skills/) – Review and create skills (orchestration)
-- [workflows/](./workflows/) – Pointer to skills (legacy path)
-- [rules/README.md](./README.md) – Structure and overview
-- [AGENTS.md](../../AGENTS.md) – Agent entry point and behaviour guidelines
-- [setup/integration.md](../../setup/integration.md) – IDE integration

package/agent-docs/external/kuat-agent-rules/kuat-docs/rules/foundations/content/README.md

@@ -1,28 +0,0 @@
-# Content Rules
-
-Writing style, voice, tone, and usage for Equal Experts. Apply to all content before platform-specific guidance.
-
----
-
-## Overview
-
-These rules cover how we write: voice and tone, style principles, formatting, numbers, and punctuation. Load [voice-and-tone.md](./voice-and-tone.md) first; use the others as needed for the task.
-
----
-
-## Files
-
-| File | Description |
-|------|-------------|
-| [voice-and-tone.md](./voice-and-tone.md) | Voice, tone, audience, quality checklist, AI content |
-| [writing-style.md](./writing-style.md) | Active voice, plain language, contractions, conciseness |
-| [formatting.md](./formatting.md) | Capitalisation, bold/italic, headings, links, lists, acronyms |
-| [numbers.md](./numbers.md) | Dates, times, currency, percentages, units |
-| [punctuation.md](./punctuation.md) | Commas, dashes, apostrophes, quotation marks |
-
----
-
-## Related
-
-- [Foundations](../README.md) – Brand, logo, accessibility
-- [Design](../design/README.md) – Visual design and tokens

package/agent-docs/external/kuat-agent-rules/kuat-docs/rules/foundations/content/formatting.md

@@ -1,93 +0,0 @@
-# Formatting
-
-How to use bold, capitalisation, headings, links, lists, and abbreviations in Equal Experts content.
-
----
-
-## Quick Reference
-
-- **Capitalisation:** Sentence case for headings, buttons, and body copy; title case only for proper nouns and product names
-- **Bold:** Use sparingly for emphasis or key terms
-- **Links:** Descriptive link text, not "click here" or raw URLs
-- **Lists:** Use when items are parallel; keep items concise
-- **Acronyms:** Spell out on first use, then use the short form
-
----
-
-## Capitalisation
-
-### Sentence case
-
-Use sentence case for:
-- Headings and subheadings
-- Button and link labels
-- List items
-- Body copy
-
-**Examples:**  
-"Getting started"  
-"Save and continue"  
-"Contact the team"
-
-### Title case
-
-Reserve for:
-- Proper nouns (Equal Experts, product names)
-- Official titles when they are the full name of something
-
-Do not use title case for general headings or UI labels.
-
----
-
-## Bold and Italic
-
-- **Bold:** Use for a small number of key terms or one-off emphasis. Don't bold whole sentences or paragraphs.
-- *Italic:* Use for titles of works, technical terms on first use if needed, or subtle emphasis. Use sparingly in UI copy.
-
----
-
-## Headings
-
-- One H1 per page or screen (the main title)
-- Use a logical hierarchy: H1 → H2 → H3; don't skip levels
-- Make headings descriptive so they work as a scan of the content
-- Prefer sentence case
-
----
-
-## Links
-
-- Link text should describe the destination or action
-- Avoid "click here", "read more", "learn more" without context
-
-| Prefer | Avoid |
-|--------|--------|
-| Read the accessibility guidelines | Click here for guidelines |
-| Pricing plans | Learn more |
-| Contact the team | https://example.com/contact |
-
----
-
-## Lists
-
-- Use bullet lists for unordered items
-- Use numbered lists for steps or ranked items
-- Keep list items parallel in structure
-- Start with a lead-in sentence if it helps; don't repeat the same lead-in word in every item when not needed
-- Prefer sentence case and consistent punctuation (full stops only if items are full sentences)
-
----
-
-## Abbreviations and Acronyms
-
-- Spell out on first use with the short form in parentheses: "Application Programming Interface (API)"
-- Use the short form consistently after that
-- For well-known terms in your audience (e.g. API, UX), first-use expansion is still helpful in public-facing or mixed-audience content
-
----
-
-## Related Documentation
-
-- [Voice and tone](./voice-and-tone.md)
-- [Writing style](./writing-style.md)
-- [Numbers](./numbers.md) - Dates, currency, units

package/agent-docs/external/kuat-agent-rules/kuat-docs/rules/foundations/content/numbers.md

@@ -1,69 +0,0 @@
-# Numbers
-
-Guidance for dates, times, currency, and other numbers in Equal Experts content.
-
----
-
-## Quick Reference
-
-- **Dates:** Use a clear, unambiguous format; prefer written or ISO (YYYY-MM-DD) depending on context
-- **Times:** Use 24-hour or am/pm consistently; specify time zone when relevant
-- **Currency:** Use symbol or code (e.g. £, GBP) as appropriate; be consistent within a document
-- **Percentages:** Use the % symbol with the number (e.g. 45%)
-- **Large numbers:** Use commas (or spaces in some locales) for thousands
-
----
-
-## Dates
-
-- Prefer a format that avoids ambiguity (e.g. 24 March 2025 or 2025-03-24)
-- In UK-facing content, day–month–year is standard (24 March 2025)
-- In technical or international contexts, ISO 8601 (YYYY-MM-DD) is often clearer
-- Spell out month names in body copy when space allows; abbreviate only in tables or tight UI (e.g. Mar 2025)
-
----
-
-## Time
-
-- Be consistent within a document: either 24-hour (14:30) or 12-hour with am/pm (2:30 pm)
-- Specify time zone when the reader needs to act or compare across regions (e.g. "2:30 pm GMT")
-- Use "midday" and "midnight" where they're clearer than 12:00
-
----
-
-## Currency
-
-- Use the appropriate symbol (£, $, €) or ISO code (GBP, USD, EUR) as fits the context
-- Be consistent: don't mix "£10" and "10 GBP" in the same piece unless one is clearly a label
-- For whole amounts, no decimal places unless it's pence/cents (e.g. £10 not £10.00 for ten pounds)
-
----
-
-## Percentages
-
-- Use the % symbol with the number: 45%, 12.5%
-- In body copy, "45%" is usually preferable to "45 percent" unless you're writing for voice or very formal copy
-- For a range, "40–60%" (en dash, no space)
-
----
-
-## Units of Measure
-
-- Use metric by default in UK/international content unless the audience or product uses imperial
-- Abbreviate when standard: kg, m, km, cm. Spell out in prose when it reads more naturally
-- Leave a space between number and unit: "5 kg", "12 cm"
-
----
-
-## Large Numbers
-
-- Use commas as thousand separators in English (1,000,000) or a thin space where that's the convention
-- Keep formatting consistent in tables and lists
-- For very large numbers, consider "1.5 million" or "2.3 billion" in body copy
-
----
-
-## Related Documentation
-
-- [Formatting](./formatting.md) - Capitalisation, lists
-- [Punctuation](./punctuation.md) - Dashes, spaces

package/agent-docs/external/kuat-agent-rules/kuat-docs/rules/foundations/content/punctuation.md

@@ -1,75 +0,0 @@
-# Punctuation
-
-Guidance for commas, dashes, apostrophes, and other punctuation in Equal Experts content.
-
----
-
-## Quick Reference
-
-- **Commas:** Use to separate clauses and items in a list; avoid comma splices
-- **Apostrophes:** Use for possessives and contractions; don't use for plurals
-- **Dashes:** Use en dash for ranges (40–60); use em dash sparingly for a break in a sentence
-- **Hyphens:** Use in compound modifiers before a noun (e.g. well-known); follow standard compound rules
-- **Exclamation points:** Use rarely; one is enough
-
----
-
-## Commas
-
-- Use a comma before "and" or "or" in a list of three or more items (Oxford comma) for clarity when it avoids ambiguity
-- Use commas to set off non-essential clauses
-- Don't join two independent clauses with only a comma (use a full stop, semicolon, or conjunction)
-
----
-
-## Apostrophes
-
-- **Possessives:** Add 's for singular (team's, user's); add ' for plural already ending in s (users', teams')
-- **Contractions:** Use for standard contractions (don't, it's, we're)
-- **Plurals:** Do not use an apostrophe for plurals: "1990s" not "1990's"; "APIs" not "API's"
-
----
-
-## Dashes and Hyphens
-
-- **En dash (–):** Use for ranges (40–60%, March–May, 9–5). Use unspaced in British style.
-- **Em dash (—):** Use sparingly for a strong break or aside. Prefer one em dash per sentence.
-- **Hyphen (-):** Use in compound modifiers before a noun: "well-known result", "up-to-date report". Don't hyphenate after the noun when the modifier follows: "the result is well known".
-- **Hyphen in compounds:** Follow standard usage (e.g. "email", "multi-factor", "read-only" as per common style)
-
----
-
-## Colons and Semicolons
-
-- **Colon:** Use to introduce a list or an explanation that follows from the main clause. One space after a colon.
-- **Semicolon:** Use to link closely related independent clauses, or to separate list items that already contain commas. Use sparingly; often a full stop is clearer.
-
----
-
-## Ellipses
-
-- Use for omitted words in a quote (three dots: …)
-- Avoid in UI or body copy to indicate "more" or trailing thought; rewrite so the sentence is complete
-
----
-
-## Exclamation Points
-
-- Use rarely; reserve for genuine emphasis or short, positive confirmation
-- One exclamation point is enough; never use multiple (!!)
-
----
-
-## Quotation Marks
-
-- Use double quotation marks for direct speech and short quoted phrases
-- Put full stops and commas inside the closing quote when they apply to the quoted matter; outside when they apply to the whole sentence (British style)
-- For terms or "scare quotes", use sparingly
-
----
-
-## Related Documentation
-
-- [Writing style](./writing-style.md)
-- [Formatting](./formatting.md)
-- [Numbers](./numbers.md) - Ranges, decimals