feat(wix-manage): add layered ecommerce skill references#171
Open
itayhewix wants to merge 18 commits into
Open
feat(wix-manage): add layered ecommerce skill references#171itayhewix wants to merge 18 commits into
itayhewix wants to merge 18 commits into
Conversation
itayhewix
force-pushed
the
feat/ecommerce-recipes
branch
2 times, most recently
from
6d6d9ae to
10a313d
Compare
Add goals, flows, guardrails, troubleshooting, setup, and recommendation recipes for the ecommerce domain under wix-manage. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…tics API The GetCatalogAnalytics API rejects UPPER_CASE enum values — it expects lowercase camelCase (e.g. ordersCount, profitMargin, sum, quantiles). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…xt-based gate Adds api-recommendation-tracking.md (L3 CRUD API reference) and recipe-recommendation-tracking.md (L4 standalone skill with SKIP_TRACKING gate, history loading, and state transition tracking). Domain skills stay clean — no tracking logic embedded. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…odies The frontmatter references are stripped by the parser, so the LLM never sees them. This adds visible reference sections in the markdown body so the LLM can self-resolve dependencies using ReadFullDocsArticle — works with the production MCP without code changes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace L3-L6 numbered layers with descriptive types: goal, flow, config, guardrail, troubleshoot, tracking. Guardrails and tracking are cross-cutting concerns, not hierarchical layers. Fix broken reference chains: recommend-discount-strategy now loads matching goal skill after intent classification, recommend-shipping-health loads goal-reduce-cart-abandonment upfront and flows after checks. Simplified skill-graph to 8 group-level edges. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Holiday/event mentions now always classify as SEASONAL, even when combined with generic signals like "boost sales". Prevents misrouting to BUNDLE_AND_SAVE or UPSELL_BOOST when a holiday is clearly stated. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…xecuting Add rule 1: "Do NOT ask clarifying questions — start executing immediately from Step 0." The LLM was asking about goals, scope, and mechanism before calling any APIs. The only allowed question is Step 4 (automatic vs coupon). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The tracking skill was never loaded because no skill referenced it. Added recipe-recommendation-tracking to the "Before executing" block in both recommend-discount-strategy and recommend-shipping-health so the LLM loads it via ReadFullDocsArticle. The tracking skill's own activation gate handles SKIP_TRACKING. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The tracking skill was loaded but never executed because the recommend skills' step-by-step flow never referenced it. Added explicit hooks: - Step 0a (before execution): execute tracking Phase 1 (load history) - Step 8 / post-validation: execute tracking Phase 2 (persist to DB) Also removed duplicate Output Format section in recommend-shipping-health. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The LLM was asking clarifying questions because all 20+ ecommerce skills were listed at the same level. Restructured to put entry points at top with explicit routing rules (discounts → Recommend: Discount Strategy, shipping → Recommend: Shipping Health). Internal skills (goals, flows, guardrails, config) collapsed into a details block marked as auto-loaded. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…datory The LLM was cherry-picking from the "Before executing" bullet list and skipping the tracking reference. Fix: moved tracking out of the shared list into Step 0a as an explicit mandatory ReadFullDocsArticle call with the URL inline. The LLM now must call it as part of the step flow, not as optional pre-reading. Same treatment for the persist step (Step 8). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Added api-recommendation-tracking.md and recipe-recommendation-tracking.md to the documentation.yaml so they get published to dev.wix.com and are accessible via ReadFullDocsArticle. Without this, the tracking skill URL returned 404 and the LLM couldn't load it. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The tracking service REST gateway is at manage.wix.com/_api/agentic-recommendations, not wixapis.com. Confirmed via fqdn_service lookup: server mapping shows manage._base_domain_ with sourcePath /_api/agentic-recommendations. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Single entry point for all business improvement requests. Analyzes across ALL domains (discounts + shipping, future: gift cards, taxes) instead of forcing a single-domain path. Tracking inlined (no separate ReadFullDocsArticle call). Generates up to 5 cross-domain recommendations. The old domain-specific skills (recommend-discount-strategy, recommend-shipping-health) remain for explicit single-domain requests. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Merge shipping health logic into recommend-ecommerce-strategy.md and remove the old domain-specific entry points: - Deleted: recommend-discount-strategy.md, recommend-shipping-health.md, recipe-recommendation-tracking.md - Shipping section expanded to full 11-rule analysis table - Single-domain focus rule: when user asks for specific domain, use all 5 slots for that domain only - Tracking inlined (no separate ReadFullDocsArticle) - Updated documentation.yaml and SKILL.md routing Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…skill Added Step 4b that MANDATORILY loads the matching goal skill via ReadFullDocsArticle after domain classification. The goal skill cascades to flow and guardrail skills, providing detailed margin tiers, campaign windows, coverage checks, and conflict rules. With tracking inlined, the ReadFullDocsArticle budget now goes to: unified skill (1st) → goal (2nd) → flow (3rd) → guardrails (4th). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Unified skill (recommend-ecommerce-strategy.md): - Added: unsupported request validation (Step 3b) - Added: mechanism determination - auto vs coupon (Step 4c) - Added: goal-specific aggregates per discount strategy - Added: GetCategoryIds step (5b) for GUID conversion - Added: scope selection rules (CATEGORY > ITEMS > SITE) - Added: performance signals table - Added: conflict check, rounding, mechanism match in validation - Added: body blockquote URLs matching all frontmatter references - Fixed: api-recommendation-tracking set to load:false (inlined) Connected 4 orphaned files to the chain: - recipe-apply-shipping-recommendations → goal-reduce-cart-abandonment - setup-store-pickup-location → goal-reduce-cart-abandonment - troubleshoot-discount-not-applying → guardrail-discount-conflicts - troubleshoot-checkout-delivery-dropoff → guardrail-shipping-health Updated skill-graph.md to reflect unified architecture. Zero orphans across all 28 files. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
LLM was sending all 12 categories from analytics instead of just the targeted ones. Added explicit instruction: send only the categories you plan to target, max 10 per call. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
itayhewix
force-pushed
the
feat/ecommerce-recipes
branch
from
cabce58 to
61e6347
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
skills/wix-manage/references/ecommerce/Test plan
🤖 Generated with Claude Code