igrantio-business-wallet-portallisted

Umbrella recipe for building a CUSTOM European Business Wallet (EBW) portal on the iGrant.io Organisation Wallet Suite - the path most customers take. Orchestrates the holder skills end to end - deploy the tenant backend (igrantio-holder-backend), scaffold or hand-build the portal UI (igrantio-holder-frontend), run everything on the live notifications inbox (igrantio-holder-notifications), and look up exact endpoints in igrantio-api-holder - with the page-by-page build order (base configuration, received credentials, shared credentials, share wizard, notifications), EBW onboarding to a valid wallet unit, and DCQL test requests. Use when an organisation wants its own business wallet portal with only holder functions.
L3-iGrant/skills · ★ 1 · API & Backend · score 75

Install: claude install-skill L3-iGrant/skills

# iGrant.io business wallet portal (umbrella) ## When to use A customer organisation wants its **own** business wallet portal - their branding, their pages, only holder functions (receive, hold, present, notifications) - on the iGrant.io OWS APIs. This skill is the route map: it does not duplicate any contract; it tells you which skill to open for each part and in which order. For a single missing fact (a path, an enum, a payload), go straight to `igrantio-api-holder`. **Before you build**: run the integrator intake in `igrantio-ows-overview` - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each. Then add the portal questions below. ## Portal intake (ask after the overview intake) 1. **Stack** - which web stack? _Recommend **Next.js (App Router) + TypeScript** with **Better Auth** passwordless login (see "Recommended stack" below); accept the customer's standing stack if they have one._ 2. **Scope** - which pages? _Recommend all four: base configuration, received credentials, shared credentials, notifications._ 3. **Scaffold or custom** - start from the ready `HolderPortal` scaffold and restyle, or build custom views on the hooks + engines? _Recommend the scaffold first; every view works standalone._ 4. **Look** - the customer's design system, or the default iGrant.io look (`igrantio-usecase-ui`)? _The reference components are unstyled on purpose._ 5. **EBW onboarding state** - is the o