EqualExperts

Create EE-branded slides, web UI, marketing content, graphics, or copy using kuat-agent-docs rules. Use when building or generating new Equal Experts branded artifacts. Always resolves up-to-date rules before creating.

Review EE-branded work against kuat-agent-docs rules. Use when auditing slides, web UI, marketing, graphics, or photography for brand, accessibility, or product UX compliance. Always resolves up-to-date rules before reviewing.

Use when a request needs new visual design concepts or mockups — screens, components, or layouts — before any code or Figma work starts. Determines (1) whether to produce a single design or multiple concept directions, (2) the fidelity level and how strictly Kuat design-system compliance applies at that fidelity, and (3) whether the output route is Figma or Claude Design (inline mockup). Hands off to figma-build-intake or mockup-build-intake accordingly. Not for code implementation (see create-web-app) or slides/imagery (see create-presentation, create-imagery).

Build or modify Equal Experts web application UI — forms, dashboards, app screens, navigation, settings, tables, product flows. Use when creating product UI (React/Vue/HTML) that should follow EE brand, design tokens, accessibility, and the Kuat component system. Not for marketing pages (use web-marketing reference) or slides.

Run before generating or updating any Figma design, screen, or component (before figma-generate-design or use_figma). Confirms whether the work is Equal Experts/Kuat or a different client's own design system, and produces a short build plan. Deliberately separate from Figma's own skills — it does not customise figma-generate-design, figma-use, or any other Figma-provided skill, so Figma's own updates to those skills are never affected.

Run before building a design mockup with the Claude Design inline-mockup tool (show_widget / visualize). Confirms design-system context (EE/Kuat vs. a different client), resolves the fidelity level's compliance bar, and — for Kuat work — pulls real token values and component visual specs live from kuat-agent-rules rather than generic Claude Design tokens, so the mockup is as spec-accurate as the fidelity level requires instead of only directionally similar.

Use when a request needs new visual design concepts or mockups — screens, components, or layouts — before any code or Figma work starts. Determines (1) whether to produce a single design or multiple concept directions, (2) the fidelity level and how strictly Kuat design-system compliance applies at that fidelity, and (3) whether the output route is Figma or Claude Design (inline mockup). Hands off to figma-build-intake or mockup-build-intake accordingly. Not for code implementation (see create-web-app) or slides/imagery (see create-presentation, create-imagery).

Build or modify Equal Experts web application UI — forms, dashboards, app screens, navigation, settings, tables, product flows. Use when creating product UI (React/Vue/HTML) that should follow EE brand, design tokens, accessibility, and the Kuat component system. Not for marketing pages (use web-marketing reference) or slides.

Write a new entry in "The Satsuma Diaries" — a funny, tongue-in-cheek project changelog written by Pip, a junior intern AI with strong SE London energy. Run this after a coding session or on a schedule. The skill decides whether the day merits its own entry or should be rolled into a quiet-days summary. Files entries under satsuma-diaries/yyyy/mm/yyyy-mm-dd.md and tracks progress in satsuma-diaries/.progress.json.

Generate OpenLineage events from Satsuma (.stm) mapping specs. Use this skill whenever the user wants to export Satsuma lineage to OpenLineage, integrate Satsuma with Marquez or DataHub, generate OpenLineage JSON from .stm files, create lineage events for a data catalog, or bridge Satsuma specs into an OpenLineage-compatible lineage backend. Also trigger for requests like "export lineage to OpenLineage", "generate Marquez events", "create column-level lineage JSON", "integrate Satsuma with DataHub/Atlan/OpenMetadata", or "publish lineage from my mapping spec". Requires the `satsuma` CLI for structural extraction. Generates spec-compliant OpenLineage 2-0-2 RunEvents with standard and custom facets.

Convert Excel mapping spreadsheets into idiomatic Satsuma .stm files. Use when the user has an .xlsx file containing source-to-target data mapping definitions and wants to generate Satsuma output. Three-phase workflow: survey the spreadsheet structure, generate Satsuma with chunked extraction, then critique and refine.

Explain Satsuma (.stm) data mapping files in plain English for business stakeholders, analysts, and non-technical reviewers. Use this skill whenever the user asks to explain, summarize, review, walk through, or describe a Satsuma file or workspace — including requests like "what does this mapping do", "explain this to my PM", "review this spec", "what are the risks", "is anything missing", "onboarding summary", or "walk me through this". Also trigger when users ask for a data quality assessment, PII audit summary, coverage check, or impact analysis of a .stm file. This skill requires the `satsuma` CLI to be installed and available on PATH.

Reverse-engineer Satsuma (.stm) mapping specs from an existing dbt project. Use this skill whenever the user wants to generate Satsuma from dbt, convert a dbt project to Satsuma, extract mapping specs from dbt models, document dbt transformations in Satsuma format, or create a Satsuma workspace from their existing dbt codebase. Also trigger when the user says things like "I have a dbt project and want to try Satsuma", "convert my dbt models to .stm", or "reverse-engineer my dbt lineage into Satsuma". Requires access to the dbt project files on disk. The `satsuma` CLI should be installed for validation and formatting of the output.

Generate realistic synthetic test data from Satsuma (.stm) schema definitions. Use this skill whenever the user wants to create test data, sample data, fake data, seed data, mock data, or synthetic data from a Satsuma spec. Also trigger for requests like "generate CSV from this schema", "create test fixtures for my mapping", "I need sample data to test my pipeline", "mock up some data for this spec", or "seed data for my warehouse". Generates data that respects all schema constraints (types, enums, required, PII patterns, formats, defaults, filters) and maintains referential integrity across schemas connected by mappings. Supports CSV, JSON/JSONL, SQL INSERT, and Parquet output. For exotic source formats (COBOL copybooks, HL7, EDI, ISO 8583, etc.), this skill generates the logical data and suggests the user create a format-specific skill for physical serialisation. Requires the `satsuma` CLI.

Generate idiomatic dbt project scaffolds from Satsuma (.stm) mapping specs. Use this skill whenever the user wants to create a dbt project from Satsuma, generate dbt models from .stm files, scaffold a dbt pipeline from a mapping spec, or convert Satsuma to dbt. Also trigger for requests like "generate dbt from this spec", "create staging and mart models from this mapping", "scaffold a dbt project for this Satsuma file", or "turn my .stm into dbt SQL". Handles Kimball star schemas, Data Vault 2.0, merge strategies, governance metadata, and consumer schemas (reports/models → dbt exposures). Requires the `satsuma` CLI for structural extraction. Generates dbt projects that use {{ ref() }} and {{ source() }} throughout — never hardcoded table names.

Convert Satsuma .stm files into professional, stakeholder-ready Excel workbooks. Deterministic, parser-backed export using the satsuma CLI for structural extraction and openpyxl for workbook generation. Produces Overview, Issues, Mapping, Schema, and Lookup tabs with full styling.

Scaffold a new Kuat design-system component end-to-end in kuat-mono — React + Vue implementations, the React Figma Code Connect mapping, Storybook stories, tests, the component doc, the manifest entry, the regenerated component registry, and the agent-docs bundle. Use when a DS-team contributor is adding (or renaming) a component to @equal-experts/kuat-react / kuat-vue. Repo-local contributor skill — never packaged or distributed.

Regenerate the brand-colour block of @equal-experts/kuat-core src/variables.css from the upstream colour token source-of-truth, and run the drift gate. Use when colours changed upstream (Run A) and the downstream CSS needs refreshing, or to check variables.css hasn't drifted. Repo-local contributor skill — never packaged or distributed. Downstream half of Phase 7's generate-tokens.