@fluentcommerce/ai-skills 0.1.0 → 0.3.0

package/content/dev/skills/fluent-custom-code/SKILL.md

@@ -53,6 +53,8 @@ fluent workflow download -p <PROFILE> -r <RETAILER_REF> -w all --json > accounts
 
 Then split into one file per workflow with sanitized names, and persist `workflow-file-map.json` (original workflow name -> sanitized filename).
 
+> **If `workflow-file-map.json` is missing**, generate it from the workflow directory before proceeding. See `/fluent-workflow` for the generation script. Without the map, workflow name resolution may fail on Windows.
+
 If `RETAILER_REF` is omitted and multiple retailer folders exist under `accounts/<PROFILE>/workflows/`, require explicit retailer selection before analysis.
 
 ### Account intake contract
@@ -82,7 +84,7 @@ The analysis objective is a holistic inventory:
 **Check module inventory:** Before scanning source, check if a module inventory exists:
 
 ```
-accounts/<PROFILE>/analysis/module-validate/module-inventory.json
+accounts/<PROFILE>/analysis/modules/module-inventory.json
 ```
 
 If found, read it to identify:
@@ -375,12 +377,12 @@ For each option include:
 
 At the end of every run, write or refresh the full artifact bundle (or the incremental subset when freshness rules allow):
 
-- `accounts/<PROFILE>/analysis/custom-code/source-map.json`
-- `accounts/<PROFILE>/analysis/custom-code/workflow-rule-map.json`
-- `accounts/<PROFILE>/analysis/custom-code/constraints.json`
-- `accounts/<PROFILE>/analysis/custom-code/behavior-map.md`
-- `accounts/<PROFILE>/analysis/custom-code/extension-plan.md`
-- `accounts/<PROFILE>/analysis/custom-code/fingerprint.json`
+- `accounts/<PROFILE>/analysis/code/source-map.json`
+- `accounts/<PROFILE>/analysis/code/workflow-rule-map.json`
+- `accounts/<PROFILE>/analysis/code/constraints.json`
+- `accounts/<PROFILE>/analysis/code/behavior-map.md`
+- `accounts/<PROFILE>/analysis/code/extension-plan.md`
+- `accounts/<PROFILE>/analysis/code/fingerprint.json`
 
 Also persist installed rule evidence:
 
@@ -414,7 +416,7 @@ If source is incomplete or unavailable:
 
 Always write analysis artifacts to:
 
-`accounts/<PROFILE>/analysis/custom-code/`
+`accounts/<PROFILE>/analysis/code/`
 
 Required files:
 
@@ -457,7 +459,7 @@ For markdown artifacts (`behavior-map.md`, `extension-plan.md`), include a short
 
 Do not mark analysis as complete until all checks pass:
 
-1. All six required artifacts exist in `accounts/<PROFILE>/analysis/custom-code/`.
+1. All six required artifacts exist in `accounts/<PROFILE>/analysis/code/`.
 2. `source-map.json`, `workflow-rule-map.json`, `constraints.json`, and `fingerprint.json` include `sourceInputHash` + `contentHash`.
 3. `workflow-rule-map.json` mappings use `source` (`custom` | `reference` | `unresolved`) and avoid legacy `unmapped` buckets.
 4. If decompiled evidence is used, impacted mappings include confidence text that indicates decompile-derived evidence.
@@ -884,6 +886,10 @@ Reference module knowledge is also available to all skills:
 
 If artifacts are stale (hash mismatch) or objective changed, regenerate and keep the same file names.
 
+## Learning Capture
+
+This is an analysis skill — follow the **Learning Capture Protocol** (see CLAUDE.md Cross-Skill Conventions). After analysis, when the user confirms or corrects findings about rule behavior, module architecture, or runtime quirks, write the confirmed learning to the `implementation-learnings.md` auto-memory file under the relevant account heading.
+
 ## Output Template
 
 Use this structure:

package/content/dev/skills/fluent-data-module-scaffold/SKILL.md

@@ -14,7 +14,7 @@ Generate a complete Fluent Commerce data module skeleton with no Java plugins, n
 
 **Before scaffolding, write a plan and get approval.** This is mandatory for all non-trivial module creation.
 
-**Plan file path:** `accounts/<PROFILE>/plans/<YYYY-MM-DD>-data-module-scaffold-<slug>.md`
+**Plan file path:** `accounts/<PROFILE>/tasks/<YYYY-MM-DD>-data-module-scaffold-<slug>.md`
 
 The plan should cover:
 1. **Purpose** -- what data this module will contain and why it is a separate module
@@ -25,7 +25,24 @@ The plan should cover:
 
 Write the plan file, present it to the user, and wait for explicit approval ("yes", "go ahead", "approved", "do it") before generating any files. On approval, update the plan status to `APPROVED`.
 
-**Skip the gate** when: the user says "just do it" or "skip planning", or a pre-approved plan already exists in `accounts/<PROFILE>/plans/`.
+**Skip the gate** when: the user says "just do it" or "skip planning", or a pre-approved plan already exists in `accounts/<PROFILE>/features/*/status.json` or `accounts/<PROFILE>/tasks/`.
+
+## Handoff Protocol
+
+### Signals emitted by this skill
+
+| Signal | Condition | Example |
+|--------|-----------|---------|
+| `-> READY: <path>` | Data module scaffolded | `-> READY: accounts/HMDEV/SOURCE/fc-data-locations/` |
+| `-> NEXT: /fluent-<skill>` | Ready for build or deploy | `-> NEXT: /fluent-module-deploy` |
+| `-> BLOCKED: <reason>` | Cannot proceed | `-> BLOCKED: PLAN_REQUIRED — Write a plan via /fluent-feature-plan` |
+
+### Error codes
+
+| Code | Condition | Recovery |
+|------|-----------|----------|
+| `PLAN_REQUIRED` | Scaffolding attempted without approved plan | Run `/fluent-feature-plan` first |
+| `VALIDATION_FAILED` | Module name conflicts or missing required assets | Fix input and retry |
 
 ## When to Use