---
name: knowledge-index
description: "Registry of partner and client knowledge files for this project"
version: 1.0
---

# Knowledge Index

This directory contains project-specific knowledge that AI skills use to build better, more consistent artifacts. Files are created by the AI via `/fluent-knowledge-init` wizard, document ingestion, or progressive capture — not hand-authored.

## Always Loaded

These files are referenced from CLAUDE.md and apply to EVERY interaction:

| File | Purpose | Status |
|------|---------|--------|
| [partner/naming-conventions.md](partner/naming-conventions.md) | Entity, attribute, and ref naming rules | Template — run `/fluent-knowledge-init` to populate |
| [partner/coding-standards.md](partner/coding-standards.md) | Java, workflow, and manifest conventions | Template — run `/fluent-knowledge-init` to populate |

## On-Demand

Skills read these when relevant (based on `relevant-skills` in frontmatter):

| File | Load When | Relevant Skills | Status |
|------|-----------|-----------------|--------|
| [platform/domain-model.md](platform/domain-model.md) | Entity relationships, GraphQL edges, cross-domain maps. Schema-validated. | workflow-builder, mystique-builder, rule-scaffold, feature-plan, custom-code, settings, trace, implementation-map, feature-explain, connection-analysis, scope-decompose, inventory-catalog | **Active** |
| [platform/create-order-reference.md](platform/create-order-reference.md) | Building or validating `createOrder` payloads, especially `ORDER::MULTI`, `fulfilmentChoice(s)`, and item-to-FC linkage. | test-data, e2e-test, trace, event-api, workflow-builder, feature-plan, feature-explain | **Active** |
| [platform/rule-development-contract.md](platform/rule-development-contract.md) | Rubix rule annotation contract, input channels, reading patterns, enhancement protocol. Derived from OOTB analysis (103 rules). | rule-scaffold, custom-code, feature-plan, feature-explain, build, workflow-builder, workflow-analyzer, pre-deploy-check | **Active** |
| [platform/user-action-contract.md](platform/user-action-contract.md) | Canonical user action contract: visibility fields, rule mapping, FieldRegistry wiring, workflow-vs-manifest override precedence. | workflow-builder, workflow-analyzer, pre-deploy-check, workflow-deploy, mystique-builder, mystique-validate, settings | **Active** |
| [platform/permissions-and-contexts.md](platform/permissions-and-contexts.md) | RBAC model: users, roles, context types/IDs, accretive scoping, Rubix user, deployment permissions, debugging. | rule-scaffold, custom-code, feature-plan, workflow-builder, settings, trace, implementation-map, bootstrap, pre-deploy-check, module-deploy, workflow-deploy, retailer-config, e2e-test | **Active** |
| [platform/mystique-manifest-components.md](platform/mystique-manifest-components.md) | Core Mystique manifest components: fc.list attribute schema, fc.page, fc.card.attribute, Handlebars helpers, props reference. | mystique-builder, mystique-validate, mystique-analyze, mystique-diff, ui-test, feature-plan, implementation-map | **Active** |
| [platform/mystique-routing.md](platform/mystique-routing.md) | Mystique routing architecture: HashRouter URL mapping, manifest structure, page params (`{{params.id}}`), link patterns, backButtons, homePath. Manifest-evidenced. | mystique-builder, mystique-validate, mystique-preview, mystique-analyze, mystique-diff, ui-test, ui-record, feature-plan, implementation-map | **Active** |
| [platform/workflow-json-structure.md](platform/workflow-json-structure.md) | Canonical workflow JSON structure: field ordering, ruleset naming = event matching, multi-entity patterns, trigger conventions. Evidence-based from live workflows. | workflow-builder, feature-plan, workflow-deploy, workflow-analyzer, pre-deploy-check | **Active** |
| [platform/graphql-in-rules.md](platform/graphql-in-rules.md) | GraphQL in Rubix rules: decision framework, execution model, gotchas. ~120 lines. | rule-scaffold, custom-code, feature-plan, feature-explain, build, module-scaffold | **Active** |
| [platform/graphql-in-rules-reference.md](platform/graphql-in-rules-reference.md) | Full API reference: DynamicUtils methods, Apollo patterns, custom mutation classes, code examples. Companion to above. | rule-scaffold, custom-code, feature-plan, feature-explain, build, module-scaffold | **Active** |
| [platform/reusability-patterns.md](platform/reusability-patterns.md) | Reusability decision framework, naming, parameterization patterns for rules and components. | rule-scaffold, mystique-component, feature-plan, use-case-discover, mystique-scaffold, custom-code, feature-explain | **Active** |
| [platform/roles-and-permissions.md](platform/roles-and-permissions.md) | RBAC model: three-layer access control, context types, label-only roles, custom role checking in rules, feature design questions. | use-case-discover, feature-plan, rule-scaffold, workflow-builder, mystique-builder | **Active** |
| [platform/workflow-design.md](platform/workflow-design.md) | Workflow design principles: boundaries, versioning, flow control, cross-retailer/workflow communication, execution model, rulesets, settings. | workflow-builder, workflow-analyzer, workflow-deploy, feature-plan, use-case-discover, rule-scaffold, feature-explain, connection-analysis, pre-deploy-check | **Active** |
| [platform/create-order-reference.md](platform/create-order-reference.md) | createOrder mutation patterns: HD, CC, MULTI, mixed-fulfilment, fulfilmentChoice linking, orderItem wiring, return orders, financial transactions. Schema-validated against live introspection. | test-data, e2e-test, event-api, workflow-builder, feature-plan, trace, retailer-config, sourcing | **Active** |
| [client/business-rules.md](client/business-rules.md) | Building workflows, rules, or sourcing | workflow-builder, rule-scaffold, feature-plan, sourcing | Template |
| [client/data-model.md](client/data-model.md) | Creating entities, writing GraphQL, building manifests | workflow-builder, mystique-builder, settings | Template |
| [client/integrations.md](client/integrations.md) | Building rules that call external APIs | rule-scaffold, custom-code, feature-plan | Template |
| [client/test-data.md](client/test-data.md) | Running E2E tests or creating test entities | e2e-test, test-data, trace | Template |

## Skill-Triggered

| File | Triggered By | Status |
|------|-------------|--------|
| `templates/deploy-checklist.md` | `/fluent-pre-deploy-check` | Optional override — create to customize default checklist |
| `templates/test-plan-template.md` | `/fluent-e2e-test` | Optional override — create to customize default test plan |

## Vertical

Active vertical: `none` (set by `/fluent-knowledge-init`)

Available: `grocery`, `fashion`, `electronics`, `b2b`, `marketplace`

## Frontend / Mystique UI

| File | Loading | Description |
|------|---------|-------------|
| `frontend/mystique-components.md` | on-demand | Component configuration reference (fc.list, fc.card.attribute, fc.tabs, etc.) |
| `frontend/mystique-templates.md` | on-demand | Template helper reference (30+ helpers with syntax and examples) |
| `frontend/mystique-patterns.md` | on-demand | Practical patterns: query construction, fragment mechanics, troubleshooting |
| `frontend/mystique-sdk.md` | on-demand | Component SDK: hooks, registration, Jest/Storybook testing, Mystique Jest bootstrap, deployment |
| `frontend/mystique-advanced-sdk.md` | on-demand | Advanced SDK: category decision tree, field/entityContext patterns, hook mocks, Storyshots policy, advanced test fixtures |

For custom `FieldRegistry` work, also load `platform/user-action-contract.md` — it is the canonical dialog/attribute contract and explains why `entityContext` exists while `useData()` is empty in user action dialogs.

Skills that should load frontend knowledge in pre-flight:
- `fluent-mystique-builder` -- components, templates, patterns
- `fluent-mystique-validate` -- patterns (troubleshooting section)
- `fluent-mystique-scaffold` -- sdk, advanced-sdk, components
- `fluent-mystique-analyze` -- components, patterns
- `fluent-frontend-build` -- sdk (for build gate validation)
- `fluent-frontend-review` -- sdk, advanced-sdk (for code quality audit)
- `fluent-frontend-readme` -- sdk, advanced-sdk (for README generation)
- `fluent-ui-test` -- patterns (for verifying expected UI state, OMS DOM styling for Tier 1 injection)
- `fluent-ui-record` -- patterns (OMS DOM styling reference for annotated walkthroughs)

## Account Memory (auto-accumulated)

Skills automatically capture account-specific learnings to `accounts/<PROFILE>/memory/`. Unlike knowledge files (static, authored), memory files grow organically from user corrections, deploy failures, runtime evidence, and promoted feedback patterns.

| File | Purpose |
|------|---------|
| `index.md` | Always-loaded summary: key gotchas (top 10), cross-references |
| `learnings.md` | Full detail: entity patterns, manifest/UI, custom code, deployment, corrections |

Split `learnings.md` into topic files when it exceeds ~300 lines. See CLAUDE.md § "Three data layers" for the knowledge vs memory distinction.

## How to Populate

Run `/fluent-knowledge-init` — the AI will ask you questions and write these files for you. Or drop existing scope docs/PDFs and say "extract project knowledge from this".
