baldart 3.6.2

package/framework/.claude/skills/doc-writing-for-rag/references/schemas-and-errors.md

@@ -0,0 +1,129 @@
+# Schemas & Errors — Central Reference Files
+
+Protocollo per usare e estendere `${paths.api_schemas}` e `${paths.api_errors}` (typically `docs/references/api/schemas.md` and `docs/references/errors.md`).
+
+> **Note**: the schema names and domain sections below come from a real project (a multi-merchant fidelity/loyalty platform) and are kept as a concrete example. Replace them with your own domain entities when applying this skill to a new project — the project-specific domain vocabulary lives in `.baldart/overlays/doc-writing-for-rag.md`.
+
+## schemas.md — Struttura attuale
+
+File centrale con **80+ JSON schemas riusabili** organizzati per dominio:
+
+| Domain section | Esempi schemi |
+|----------------|---------------|
+| Booking | BookingRoom, BookingTable, BookingCombo, ReservationDocument, ReservationStatus |
+| Admin | Merchant, MerchantPublic, Store, MerchantEmailSettings, AdminCustomerProfile |
+| Customer | CustomerDashboard, CustomerProfile, Coupon, CustomerNotification, GamificationProfile |
+| Merchant | MerchantWithStores, BrandSettings, DashboardAnalytics, MerchantSession |
+| Stores | StoreLandingSettings, StoreWheelSettings, WheelStats, ActiveWheelToken |
+| Promos | Promo, PromoDetail, PromoToken, PromoAnalyticsDetail, DailyOffersSettings |
+| Membership | MembershipTier, MembershipBenefit, MembershipCard, BenefitToken |
+| Menu | MenuCategory, MenuItem, MenuVariant, NutritionalInfo, CustomerMenuPreference |
+| DIO | DioMeta, DioSignal, DioRankedItem, DioMerchantConfig, BeverageQuizAnswers |
+| Notifications | NotificationEventType, NotificationSubscription, NotificationDevice |
+| Survey | SurveyAnswer, SurveyLinkConfigResponse, SurveyCategoryProductsResponse |
+| Wallet | WalletPass, FavoriteStoreLocationSnapshot, MerchantPassSummary |
+
+### Path relativi per riferimenti
+
+| File scrittura | Link schemas.md |
+|----------------|-----------------|
+| `docs/references/api/*.md` (top level) | `./schemas.md#anchor` |
+| `docs/references/api/booking/*.md` | `../schemas.md#anchor` |
+| `docs/references/api/survey/*.md` | `../schemas.md#anchor` |
+| `docs/references/ui/*.md` | `../api/schemas.md#anchor` |
+| `docs/references/ui/merchant/*.md` | `../../api/schemas.md#anchor` |
+
+### Estendere schemas.md
+
+1. **Verifica prima**: `grep -i "SchemaName" docs/references/api/schemas.md` per evitare duplicati
+2. **APPEND alla domain section** esistente (o crea nuova sezione `## X Domain Schemas` alla fine)
+3. **Format tabella**:
+   ```markdown
+   ## SchemaName
+   | Field | Type | Notes |
+   |-------|------|-------|
+   | id | string | UUID |
+   | name | string | 1-120 chars |
+   | createdAt | string | ISO 8601 |
+   ```
+4. **Union types**: usa `\|` per separare (`"ACTIVE" \| "EXPIRED"`)
+5. **Nullable**: `string \| null`
+6. **Nested**: crea schema separato (es. `BookingPolicy`) e referenzialo nel field Notes
+
+### Quando NON estendere schemas.md
+
+- Schema usato UNA SOLA VOLTA in un endpoint molto specifico → inline nel file
+- Schema differisce significativamente da uno esistente (evita "BookingResponseV2" se è un alias di "BookingResponse")
+
+## errors.md — Struttura attuale
+
+File centrale con **300+ error codes** grouped per dominio:
+
+### Domain sections esistenti
+
+- Auth / Access Control
+- Generic Validation
+- Booking — Rooms / Tables / Combos / Policies / Availability / Customer Lookup / Hold / Reservations
+- No-Show / Blacklist
+- Tags / Email Templates / Floor Plan / Swap / Arrival Queue
+- Admin (Merchant Management, Stores, Staff, Points Rules, Customers, Membership, DORE)
+- Customer (Profile, Phone Change, Notifications, Reward, Referrals, Gamification, Wallet)
+- Merchant (Brand Settings, Points, Analytics, Ledger, Session)
+- Stores (Landing, Wheel, QR Codes, Pixels)
+- Promos (CRUD, Tokens, Time Slots)
+- Membership (Tiers, Benefits, Points, Analytics)
+- Menu (Categories, Items, Variants, Images, Inferred Orders)
+- DIO Menu (Ranking, Quiz, Behavior, Cron)
+- Notifications, Survey, Wallet Passes, Closure Days
+
+### Format entry
+
+```markdown
+| Code | HTTP | IT Message | Context |
+|------|------|------------|---------|
+| BOOKING_NOT_FOUND | 404 | Prenotazione non trovata | GET/PATCH /api/v1/merchant/booking/:id |
+```
+
+### Error code naming conventions
+
+- **UPPER_SNAKE_CASE**
+- Prefix con dominio quando ambiguo: `BOOKING_NOT_FOUND`, `STORE_NOT_FOUND`
+- Senza prefix per codes generici: `MISSING_FIELDS`, `INVALID_HEX_COLOR`, `MERCHANT_MISMATCH` (riusati in più domini)
+- Descrittivi: `NAME_REQUIRED` meglio di `ERR_001`
+
+### Riutilizzo error codes
+
+**RIUSA** i generic codes esistenti in più domini:
+- `MISSING_FIELDS`, `INVALID_FORMAT`, `MERCHANT_MISMATCH`, `STORE_NOT_FOUND`, `FORBIDDEN`
+
+**NON creare duplicati** con prefix non necessari: se `INVALID_HEX_COLOR` esiste in Admin, riusalo in Merchant Brand Settings.
+
+### Link dagli endpoint
+
+Dal file API:
+```markdown
+**Errors**: BOOKING_NOT_FOUND, BOOKING_CONFLICT ([errors.md](../errors.md#booking---reservations))
+```
+
+Il link anchor punta alla **domain section**, non al singolo code.
+
+### Anchor naming per domain sections
+
+Markdownlint genera anchor da heading: tutto lowercase, spazi → `-`, caratteri speciali → rimossi.
+
+Esempi:
+- `## Booking — Reservations` → `#booking--reservations`
+- `## Admin Domain` → `#admin-domain`
+- `## Merchant — Staff Management (FEAT-0119/0485/0486)` → `#merchant--staff-management-feat-01190485-0486`
+
+**Verifica sempre** l'anchor generato con `grep "^## " docs/references/errors.md` prima di committare.
+
+## Workflow estensione in sequenza
+
+Quando scrivi un nuovo endpoint che richiede nuovo schema + nuovo error code:
+
+1. **Grep** in schemas.md e errors.md (evita duplicati)
+2. **APPEND** schema in schemas.md (sezione dominio)
+3. **APPEND** error codes in errors.md (sezione dominio esistente o nuova)
+4. **Scrivi endpoint** con link ai nuovi anchor
+5. **Verify** link validity: grep gli anchor per confermare che esistono

package/framework/.claude/skills/find-skills/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** <https://skills.sh/>
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Search for Skills
+
+Run the find command with a relevant query:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+The command will return results like:
+
+```
+Install with npx skills add <owner/repo@skill>
+
+vercel-labs/agent-skills@vercel-react-best-practices
+└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 3: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install command they can run
+3. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "vercel-react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+
+To install it:
+npx skills add vercel-labs/agent-skills@vercel-react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 4: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```

package/framework/.claude/skills/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/framework/.claude/skills/frontend-design/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+## Project Context
+
+**Reads from `baldart.config.yml`:** `paths.design_system`, `paths.ui_guidelines`, `identity.design_philosophy`, `stack.charting.canonical`, `stack.animation.canonical`.
+**Gated by features:** `features.has_design_system` (when `true`, the BLOCKING reads in the next section are mandatory; when `false`, fall back to `paths.ui_guidelines` alone — the BOLD aesthetic direction is then driven by `identity.design_philosophy` only).
+**Overlay:** loads `.baldart/overlays/frontend-design.md` if present — project-specific aesthetic mandates, forbidden patterns, illustration-motion contract.
+**On missing/empty keys:** ask the user; do not assume defaults. See `framework/agents/project-context.md` § 3.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
+
+**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
+
+Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
+
+## MANDATORY Pre-Work Read (project design-system override)
+
+When operating inside a repo that ships a design-system SSOT, the generic
+creative guidance above is BLOCKED by the project design-system until the
+reads below are complete. MANDATORY pre-work reads (skipping any of them is
+a protocol violation when the docs exist):
+
+1. **MANDATORY / BLOCKING** — `${paths.design_system}/INDEX.md`. Authoritative component index + Canonical Authority Matrix. Discover existing primitives there BEFORE inventing new ones.
+2. **MANDATORY / BLOCKING** — `${paths.design_system}/tokens-reference.md`. Human-readable token contract (colors, spacing, radius, shadows, typography). Never hardcode hex colors, shadow pixel tuples, or border widths not defined in the design-system doc.
+3. **MANDATORY** — `${paths.design_system}/components/<Name>.md` for every primitive in scope, and `${paths.design_system}/patterns/*.md` (overlays, theming, animations, platform quirks) for the pattern involved.
+4. **MANDATORY / BLOCKING** — `${paths.ui_guidelines}`. Brand philosophy, aesthetic rules, SVG rules, accessibility constraints.
+5. **MANDATORY for generated marketing illustrations/videos** — `the project's illustration-motion pattern doc (listed in `.baldart/overlays/frontend-design.md` if present)` (if your project has one). Canonical illustration language, product-variant vocabulary, and surgical element-by-element video prompt contract.
+
+Non-negotiable constraints typical of mature design-system SSOTs (adapt to your project):
+
+- Token consumption: only via the project's design-token mechanism (e.g. CSS custom properties, Tailwind theme, Stitches tokens). Never hardcode values outside this contract.
+- **Themed-surface text/bg pairing rule (MANDATORY / BLOCKING)** when the design-system defines a primary theme color: any text rendered over the themed primary background MUST pair with the project's theme-primary-text token (e.g. `text-[var(--theme-primary-text,#000)]` on `bg-[var(--theme-primary)]`).
+- Do NOT create new overlay systems if the project already catalogs an overlay decision tree — pick from the existing options.
+- **Chart library (MANDATORY / BLOCKING)** when the project standardizes a chart stack: use only the approved library and the project's wrappers, never call the underlying chart library from feature code. Banned libraries (typical): `chart.js`, `echarts`, `victory`, `visx`, `d3` standalone, `observable-plot`, `tremor`. Exceptions require an ADR.
+
+Within those bounds, creative choices (typography nuance, composition, motion intensity) are welcome — but the design-system token contract and themed-surface pairing are non-negotiable.
+
+---
+
+## Prototipi Standalone e Demo
+
+Quando il task richiede un prototipo HTML interattivo, demo animata, slide deck, mockup iOS/app, o design exploration **NON legato alla codebase Next.js** (nessun contesto `src/app/`), invocare la skill `huashu-design` in aggiunta o al posto di questa skill. Essa fornisce:
+- App Prototype shell (AppPhone state manager, tappabile, iPhone frame)
+- Tweaks panel per varianti in-page
+- Export animazioni → MP4/GIF (25fps base, 60fps interpolato)
+- 5 flussi × 20 filosofie di design per design exploration
+- Validazione Playwright click-test prima della consegna
+
+**Regola del Filesystem (ASSOLUTA):** ogni output HTML/prototipo deve essere scritto su disco con il tool `Write` PRIMA di aprirlo in Safari o condividerlo con l'utente. Non è sufficiente outputtare blocchi di codice inline.

package/framework/.claude/skills/gamification-design/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: gamification-design
+version: 1.0.0
+description: Use when designing or analyzing points systems, reward loops, progression mechanics, engagement features, or loyalty programs. Triggers include "points system," "rewards design," "progression," "engagement loop," "battle pass," "loyalty mechanics," "gamification," or "retention hooks." For B2C customer-facing features in this codebase, this skill invokes the hyper-gamification-designer agent.
+---
+
+# Gamification Design
+
+Analyze and optimize gamification elements for maximum engagement and retention.
+
+## Project Context
+
+**Reads from `baldart.config.yml`:** `paths.design_system`, `paths.ui_guidelines`, `identity.audience_segments`, `identity.design_philosophy`, `stack.animation.canonical`.
+**Gated by features:** `features.has_design_system` (when `true`, design-system reads below are BLOCKING; when `false`, fall back to `paths.ui_guidelines` alone), `identity.audience_segments` non-empty (gamification surfaces target a specific segment — usually `customer` — which the user must confirm before any recommendation).
+**Overlay:** loads `.baldart/overlays/gamification-design.md` if present — project-specific reward economy facts (point name, tier ladder, lottery format), motion vocabulary, brand voice register for customer surfaces.
+**On missing/empty keys:** ask the user; do not assume defaults. See `framework/agents/project-context.md` § 3.
+
+## When to Use
+
+Invoke this skill when working on:
+- Points systems (earning, spending, expiring)
+- Reward mechanics (coupons, discounts, prizes)
+- Progression systems (tiers, levels, badges)
+- Engagement loops (streaks, daily rewards, challenges)
+- Loyalty mechanics (membership, VIP status)
+- Social features (referrals, leaderboards, sharing)
+- Retention mechanics (notifications, reminders)
+
+## MANDATORY Design System Reads (BLOCKING before any visual recommendation)
+
+Gamification features are typically customer-facing — their visual expression MUST conform to the project design-system SSOT (when one exists). The reads below are BLOCKING when `features.has_design_system: true`. Skipping any of them in that case is a protocol violation.
+
+1. **MANDATORY / BLOCKING** — `${paths.design_system}/INDEX.md`. Component index and Canonical Authority Matrix. Entry point.
+2. **MANDATORY / BLOCKING** — `${paths.design_system}/areas/<customer-segment>.md` (segment name comes from `identity.audience_segments` — typically `customer`). Surface guidance for badges, progress bars, reward cards, lottery tickets, etc.
+3. **MANDATORY / BLOCKING** — the project's motion patterns doc (typically `${paths.design_system}/patterns/animations.md`; exact path listed in `.baldart/overlays/gamification-design.md`). Approved motion patterns (confetti, level-ups, wheel spin, progress pulses) must be specified against this registry.
+4. **MANDATORY** — `${paths.design_system}/tokens-reference.md`. Colors, spacing, radii, shadows. Never invent new palettes that bypass this token contract.
+5. **MANDATORY** — `${paths.ui_guidelines}` (brand voice + interaction-state sections). The project's brand voice pillars are listed in `.baldart/overlays/gamification-design.md` if it overrides the defaults.
+
+If `stack.animation.canonical` is set, motion recommendations target those libraries.
+
+Do NOT invent new color palettes, shadow recipes, or token names for gamification elements. Re-use the existing semantic tokens and component primitives defined in the design-system SSOT.
+
+## Agent Delegation
+
+This skill delegates to the `hyper-gamification-designer` agent for comprehensive analysis.
+
+**To invoke the agent**, use the Task tool:
+```
+Task tool:
+- subagent_type: hyper-gamification-designer
+- prompt: [Feature description with details below]
+```
+
+## Required Context for Analysis
+
+Provide the agent with:
+
+1. **Feature Name**: What you're building/analyzing
+2. **Target Behavior**: What users should do repeatedly
+3. **Core Action**: The repeatable action (e.g., "scan receipt", "visit store")
+4. **Reward Structure**: How users are rewarded
+5. **Progression**: How users advance/progress
+6. **Economy**: Points, tokens, currencies involved
+7. **Social Elements**: Referrals, leaderboards, sharing (if any)
+8. **Current KPI Concerns**: Drop-off points, churn, conversion issues
+
+## Agent Output
+
+The `hyper-gamification-designer` agent provides:
+
+### A) TL;DR Verdict
+- What works
+- What is broken/weak
+- Single highest-leverage change
+
+### B) Gamification Scorecard (0-10)
+| Dimension | Score | Notes |
+|-----------|-------|-------|
+| Core loop clarity | | |
+| Reward design | | |
+| Progression pacing | | |
+| Meaningful goals | | |
+| Social stickiness | | |
+| Economy balance | | |
+| Retention hooks | | |
+| Agency & choice | | |
+| Fairness | | |
+| Ethical safety | | |
+
+### C) MDA Map
+- Mechanics: Concrete rules/systems
+- Dynamics: Emerging behaviors
+- Aesthetics: Player feelings
+
+### D) Failure Modes
+- Exploit vectors
+- Churn triggers
+- Pay-to-win risks
+
+### E) Prioritized Improvements
+| # | Change | Rationale | Complexity | KPI Impact |
+|---|--------|-----------|------------|------------|
+
+### F) Validation Plan
+- Events to track
+- Funnels/cohorts
+- A/B test design
+
+### G) Ethical Check
+- Dark patterns detected
+- Risk level
+- Safer alternatives
+
+## Quick Self-Check
+
+Before invoking the agent, verify you have:
+- [ ] Clear description of the feature
+- [ ] Target user behavior defined
+- [ ] Reward/progression structure outlined
+- [ ] Any current metrics or concerns noted
+
+## Related Skills
+
+- `prd-planning`: For full PRD with gamification section
+- `copywriting`: For reward/achievement messaging
+- `ui-ux-pro-max`: For gamification UI patterns
+
+## Project Integration
+
+In this codebase, the `prd` agent automatically invokes `hyper-gamification-designer` for B2C features touching gamification areas. This skill provides direct access for standalone analysis.