@valentia-ai-skills/framework 1.0.13 → 1.0.14

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@valentia-ai-skills/framework",
-  "version": "1.0.13",
-  "description": "AI development skills framework — centralized coding standards, security patterns, and SOPs for AI-assisted development. Works with Claude Code, Cursor, Copilot, Windsurf, and any AI coding tool.",
+  "version": "1.0.14",
+  "description": "AI development skills framework — centralized coding standards, security patterns, and SOPs for AI-assisted development. Works with Claude Code, Cursor, Copilot, Windsurf, and any AI coding tool.",
   "keywords": [
     "ai-skills",
     "claude-code",

package/skills/global/aisupportapp-project-architecture/SKILL.md

@@ -3,7 +3,7 @@ name: aisupportapp/project-architecture
 description: Auto-generated project-architecture for aisupportapp. Created by project-scanner.
 version: 1.0.0
 scope: project
-last_reviewed: 2026-03-19
+last_reviewed: 2026-03-27
 ---
 
 ---

package/skills/global/aisupportapp-project-conventions/SKILL.md

@@ -3,7 +3,7 @@ name: aisupportapp/project-conventions
 description: Auto-generated project-conventions for aisupportapp. Created by project-scanner.
 version: 1.0.0
 scope: project
-last_reviewed: 2026-03-19
+last_reviewed: 2026-03-27
 ---
 
 ---

package/skills/global/aisupportapp-project-workflows/SKILL.md

@@ -3,7 +3,7 @@ name: aisupportapp/project-workflows
 description: Auto-generated project-workflows for aisupportapp. Created by project-scanner.
 version: 1.0.0
 scope: project
-last_reviewed: 2026-03-19
+last_reviewed: 2026-03-27
 ---
 
 ---

package/skills/global/aisupportapp-test-installation/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: aisupportapp/test-installation
+description: No description
+version: 1.0.0
+scope: project
+last_reviewed: 2026-03-27
+---
+
+# Skill Name
+
+## Overview
+
+Describe what this skill covers and when it should be applied.
+
+## 1. First Rule
+
+- Rule details here
+- Use clear, actionable language
+
+```typescript
+// ✅ Good
+const example = 'good pattern'
+
+// ❌ Bad
+const example = 'bad pattern'
+```
+
+## Checklist
+
+- [ ] First check
+- [ ] Second check
+- [ ] Third check

package/skills/global/api-design/SKILL.md

@@ -3,7 +3,7 @@ name: api-design
 description: No description
 version: 1.0.0
 scope: global
-last_reviewed: 2026-03-19
+last_reviewed: 2026-03-27
 ---
 
 ---

package/skills/global/appointment-oas-app/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: appointment-oas-app
+description: No description
+version: 1.0.1
+scope: global
+last_reviewed: 2026-03-27
+---
+
+---
+name: appointment-booking-app
+description: >
+  Build a complete appointment booking web application in React JS (Vite + Tailwind + Redux Toolkit + React Query).
+  This skill handles TWO phases: (1) pixel-perfect UI replication from any design input — Figma exports, HTML/CSS mockups,
+  or screenshot images — auto-detecting whether the UI is a wizard/stepper, single-page form, tabbed layout, or other pattern;
+  and (2) full API integration with business rules across a 6-step booking flow including authentication, service/category
+  selection, clinic/location filtering, provider selection with first-available slots, calendar/slot picker, patient
+  registration with NZ address lookup (eSAM), and Stripe payment.
+
+  USE THIS SKILL whenever the user asks to: build an appointment booking app or flow, replicate a booking UI from a design,
+  wire up booking APIs, implement a multi-step scheduling wizard, create a date/time picker booking interface, or anything
+  involving appointment scheduling with API integration. Also trigger when the user shares a Figma link, HTML mockup,
+  or screenshot and says "build this" or "replicate this" and the context is a booking or scheduling flow.
+  Trigger even if they just say "booking app", "appointment page", "scheduling UI", or share a design with calendar/time elements.
+---
+
+# Appointment Booking App Skill
+
+This skill builds a production-grade appointment booking web application in two phases:
+- **Phase 1 — UI Replication**: Pixel-perfect reproduction of a provided design
+- **Phase 2 — API Integration**: 6-step API wiring with business rules
+
+## Tech Stack (Non-negotiable)
+
+| Layer             | Choice                        |
+|-------------------|-------------------------------|
+| Build tool        | Vite + React                  |
+| Styling           | Tailwind CSS                  |
+| State management  | Redux Toolkit (global state)  |
+| Server state      | React Query / TanStack Query  |
+| Routing           | React Router v6               |
+| HTTP client       | Axios (with interceptors)     |
+| Payment           | Stripe.js + @stripe/react-stripe-js |
+
+## Environment Variables (Vite standard)
+
+```env
+VITE_S_PRACTICE_ID=<encrypted practice ID>
+VITE_API_BASE_URL=https://bookinggateway.vitonta.com
+VITE_STRIPE_PUBLISHABLE_KEY=<stripe publishable key>
+```
+
+---
+
+## Phase 1 — UI Replication
+
+Read `references/ui-replication.md` for the full design-to-code workflow including:
+- Design input detection (Figma/HTML/screenshot)
+- UI pattern auto-detection (wizard, split-panel, calendar-first, etc.)
+- Design token extraction and Tailwind config mapping
+- Component patterns (stepper, calendar grid, provider cards, booking summary)
+
+---
+
+## Phase 2 — API Integration (6-Step Booking Flow)
+
+Read `references/api-contracts.md` for complete endpoint specs, payloads, and response shapes.
+Read `references/business-rules.md` for filtering logic, validation rules, and state transitions.
+
+### Flow Overview
+
+```
+Step 0: POST /PublicAccessToken → JWT token (Bearer auth for all calls)
+   ↓
+Step 1: GET /GetServiceCategory?practiceID={id} → User picks a category
+   ↓
+Step 2: GET /GetServiceMapping → Filter services by category keywords across `serviceName` and `indiciReasonForContactTitle`
+   ↓
+Step 3: GET /GetPracticeLocation → Filter locations by serviceID
+   ↓
+Step 4: GET /GetPracticeProvider + POST /GetFirstAvailableSlotforMultiProvider
+         → Filter providers by serviceID + locationID, show first available slots
+   ↓
+Step 5: POST /GetDayRoaster + POST /SearchListOfSlot
+         → Calendar on left, time slots on right
+   ↓
+Step 6: Patient Registration + Address Lookup + Booking + Payment
+         → Multiple sub-APIs (see api-contracts.md Step 6)
+```
+
+### Redux Slice Structure
+
+```javascript
+// store/bookingSlice.js
+const bookingSlice = createSlice({
+  name: 'booking',
+  initialState: {
+    currentStep: 0,
+    token: null,
+    selectedCategory: null,      // Step 1
+    selectedService: null,        // Step 2
+    selectedLocation: null,       // Step 3
+    selectedProvider: null,       // Step 4
+    firstAvailableSlots: [],      // Step 4
+    dayRoster: [],                // Step 5
+    selectedDate: null,           // Step 5
+    selectedSlots: [],            // Step 5 (array — may need 2+ for longer durations)
+    appointmentID: null,          // Step 6 (from AddAppointment)
+    invoiceID: null,              // Step 6
+    patient: null,                // Step 6
+    paymentIntent: null,          // Step 6
+  },
+  reducers: { /* one setter per field + resetBooking */ },
+});
+```
+
+### React Query Hook Pattern
+
+```javascript
+// Every API step gets a dedicated hook
+export const useServiceCategories = (practiceID) => useQuery({
+  queryKey: ['serviceCategories', practiceID],
+  queryFn: () => api.getServiceCategories(practiceID),
+  enabled: !!practiceID,
+  staleTime: 10 * 60 * 1000,
+});
+
+// Mutations for POST endpoints
+export const useAddAppointment = () => useMutation({
+  mutationFn: (payload) => api.addAppointment(payload),
+  onSuccess: (data) => { dispatch(setAppointmentID(data.appointmentID)); },
+});
+```
+
+### Slot Booking Duration Logic (CRITICAL)
+
+When booking, the number of slots to reserve depends on the service's `timeDuration` vs the slot `interval`:
+```
+slotsNeeded = Math.ceil(service.timeDuration / slot.interval)
+```
+Example: If `timeDuration` is 40 mins and slots are 20 min intervals → book 2 consecutive slots.
+The `SlotID` array in `AddAppointment` must contain that many consecutive slot IDs.
+
+### Error Handling
+
+- Every API call must have loading, success, and error states in UI.
+- Network failures → "Connection issue. Please try again."
+- 4xx → map to business rule messages per step.
+- 5xx → "Something went wrong on our end. Please try again later."
+- Slot conflict (409) → refresh available slots and notify user.
+
+### Checklist Before Delivering
+
+- [ ] All design tokens in `tailwind.config.js`
+- [ ] UI pattern correctly identified and implemented
+- [ ] All API steps wired with React Query hooks
+- [ ] Redux slice holds cross-step booking state
+- [ ] Service filtering uses meaningful category keywords against `serviceName` and `indiciReasonForContactTitle`
+- [ ] Location filtering by serviceID
+- [ ] Provider dual-filter: serviceID + locationID
+- [ ] Slot duration logic: consecutive slot booking
+- [ ] eSAM address autocomplete + detail fetch
+- [ ] Stripe payment integration with clientSecret
+- [ ] Loading spinners on every async operation
+- [ ] Error states handled for every API call
+- [ ] Client-side validation before each API call
+- [ ] Step 6 Mantine form initializes from a cloned draft object, not frozen Redux state
+- [ ] Step 6 does not use unconditional `form.setValues(...)` sync effects that can cause update-depth loops
+- [ ] Back navigation preserves state (React Query cache)
+- [ ] AddAppointment fires on Step 6 page mount (before patient registration)

package/skills/global/code-standards/SKILL.md

@@ -3,7 +3,7 @@ name: code-standards
 description: No description
 version: 1.0.0
 scope: global
-last_reviewed: 2026-03-19
+last_reviewed: 2026-03-27
 ---
 
 ---

package/skills/global/project-scanner/SKILL.md

@@ -11,7 +11,7 @@ description: Reverse-engineer any codebase into AI-ready skill files. Use this s
   auto-trigger.
 version: 1.0.0
 scope: global
-last_reviewed: 2026-03-19
+last_reviewed: 2026-03-27
 ---
 
 # Project Scanner

package/skills/global/viteapp-core-workflows/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: viteapp/core-workflows
+description: No description
+version: 1.0.0
+scope: project
+last_reviewed: 2026-03-27
+---
+
+# Skill Name
+
+## Overview
+
+Describe what this skill covers and when it should be applied.
+
+## 1. First Rule
+
+- Rule details here
+- Use clear, actionable language
+
+```typescript
+// ✅ Good
+const example = 'good pattern'
+
+// ❌ Bad
+const example = 'bad pattern'
+```
+
+## Checklist
+
+- [ ] First check
+- [ ] Second check
+- [ ] Third check