web-vanilla-supabase-pwa

Builds mobile-first vanilla JavaScript apps on Supabase with RLS and PWA packaging.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill web-vanilla-supabase-pwa-codjeremias-cell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-vanilla-supabase-pwa
Source: https://github.com/codjeremias-cell/Orquestrador-fable/tree/main/skills/web-vanilla-supabase-pwa
Command: npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill web-vanilla-supabase-pwa-codjeremias-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a web app without a framework often means reinventing auth, database security, and offline installability from scratch, and getting Supabase security wrong by hiding screens instead of enforcing Row Level Security. This Skill encodes a proven production stack (HTML, CSS, vanilla ES6 JavaScript, Supabase, PWA) so every table ships with RLS policies and every app ships installable. ## Core Features & Use Cases - Framework-free app generation: Creates or evolves apps with a three-file architecture (index.html, style.css, app.js), CDN-loaded libraries, and no build toolchain. - Supabase backend with RLS-first security: Generates tables with row level security enabled, per-owner policies via auth.uid(), email/password auth, and private Storage with signed URLs. - PWA and Play Store packaging: Produces manifest.json with maskable icons and .well-known/assetlinks.json for TWA publication, deployable to Vercel. - Use Case: Ask to add an owner-only "monthly goals" table to an existing app and receive the SQL with four RLS policies, a new screen section wired into navigation, and CRUD logic that trusts the RLS instead of re-filtering in JavaScript. ## Quick Start Ask the assistant to create a mobile-first web app without a framework, using Supabase for auth and database, packaged as an installable PWA.

Frequently Asked Questions about web-vanilla-supabase-pwa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a web app with Supabase without a framework?▼

Use plain HTML, CSS, and ES6 JavaScript with the Supabase client loaded via CDN, organized as index.html, style.css, and app.js. Create a single client with supabase.createClient and keep the anon key in a gitignored config.js file.

Is it safe to expose the Supabase anon key in frontend code?▼

Yes, the anon key is designed to be public in frontend code. Real security comes from Row Level Security policies on the server that restrict rows by auth.uid(), not from hiding keys or hiding screens in the UI.

How do I make a vanilla JavaScript app installable as a PWA?▼

Add a manifest.json with standalone display, theme color, and 192/512/maskable icons, then serve it over HTTPS. For Play Store distribution, wrap it as a TWA and serve an assetlinks.json file at /.well-known/.

When should I use vanilla JavaScript instead of React for a web app?▼

Vanilla fits solo-developer, mobile-first apps with one user per account that need auth, database, and photo storage without maintaining a server or build pipeline. Choose React or Next when you need SEO, a component ecosystem, or a larger team codebase.

Why is hiding a screen not enough to secure Supabase data?▼

Hidden screens are cosmetic because anyone can call the Supabase API directly with the exposed anon key. Only Row Level Security policies enforced on the Postgres server actually block unauthorized reads and writes.