Intro to Fluent AI Skills
Essential knowledge
Changed on:
9 Mar 2026
Overview
[Warning: empty required content area]Key points
[Warning: empty required content area]AI coding assistants (Claude Code, Cursor, Copilot, etc.) are general-purpose, and are not Fluent Commerce specific. As such, commands and best practices may be missing when developing Fluent using AI-assisted tooling.This package injects Fluent-specific domain knowledge into your assistant so it understands workflows, events, rules, GraphQL patterns, CLI commands, and deployment procedures.
Who is this for?
T| Builders | Implementation consultants & developers building Fluent Commerce for clients. You touch workflows, rules, manifests, and deployments daily. Try these: `"Help me define use cases for return orders"` → interactive wizard producing spec.md`"Plan the return order feature"` → 18-section plan with diagrams, waits for approval`"Build an ORDER::RETURN workflow"` → scaffolds rules, builds JSON, compiles, deploys`"Add an appeasement form to the order page"` → builds manifest fragment, validates, deploys`"Deploy ORDER::HD to staging"` → 26 pre-flight gates, deploy, verify Your skills: The full lifecycle — `use-case-discover` → `feature-phase` (complex) → `feature-plan` → `rule-scaffold` → `workflow-builder` → `mystique-builder` → `module-deploy` → `e2e-test` |
| Investigator | Support engineers & debuggers troubleshooting production issues — stuck orders, failed events, missing buttons, broken workflows. Try these: `"Why is order HD-12345 stuck in BOOKED?"` → traces event history, finds root cause + fix`"Show event failure rates for the last hour"` → metrics anomaly detection with alerts`"The approve button is missing on credit memos"` → checks Transition API, modules, subtype`"Trace event ON_SEND_FULFILMENT for this order"` → rule-by-rule execution breakdown Your skills: `trace`, `transition-api`, `workflow-analyzer`, `system-monitoring`, MCP event & metrics tools |
| Reviewer | Tech leads & architects assessing quality, auditing implementations, and running go-live readiness checks. Try these: `"Run a Ready For Launch assessment"` → scored audit across workflows, rules, settings`"Map the entire implementation"` → feature inventory with dependency graphs`"Explain how Home Delivery works end-to-end"` → state diagrams, rules table, architecture.md`"Analyze workflow connection topology"` → cross-entity dependency maps Your skills: `rfl-assess`, `implementation-map`, `feature-explain`, `connection-analysis`, `custom-code` |
| New Starter | Just joined the project. Need to understand what's deployed before you can contribute. Don't know where anything is yet. Try these: `"Set up my workspace"` → connects account, downloads workflows, scans code`"What's deployed on this account?"` → full implementation inventory`"Explain the custom rules"` → annotated analysis of all plugin code`"Show me the feature dashboard"` → live status of all features in progress Your path: `/fluent-connect` → `implementation-map` → `feature-explain` → `custom-code` → start building |
