irwebtools Backend (optional)
This skill is optional. Most Product-Skills work stays frontend-oriented. Load this skill only when the task needs a non-Supabase API, service, or server boundary.
When to use
- an existing backend must be integrated;
- the team chose a backend other than Supabase;
- contracts, auth, or server behavior are in scope for the current outcome.
When not to use
- UI-only or mock-data work;
- Supabase already covers the need — prefer
supabase; - the request is really architecture ownership for Solution Architects — surface that instead of inventing a platform.
Expectations
- Keep product UI free of provider leakage.
- Leave reproducible contracts, types, and setup notes in the repository.
- Verify the primary backend-dependent journey before delivery.
- Do not expand into a general DevOps or platform redesign unless asked.
Standard resources
Use templates, references, and evaluations for scope and exit evidence.