BreizhVibe is my set of vibe-coding skills and tools for web development for associations, festivals, clubs and small businesses wavedevsimpl is my basic specification for quick and reliable app prototyping.
Methodology
- start simple with wavedevsimpl skill - keep track of modifications via code tracking tool, - keep history of prompts and detailed answers in md. Prompts name should follow rule : YMD-AIprovider-n.md
folder to upload by FTP. Changing host means copying it
1
SQLite file holds the whole database
What we’ve already built
Real tools, coded with Claude, each on the stack that suits it.
Youl Vat
Live
“Good will” in Breton.
Volunteer scheduling for festive events, first built for the Fest-noz Vras Kalanna in Quimper. The public reads the planning, volunteers sign up for a free slot, organisers run the whole day from it.
A mobile app for stock spread over several sites, warehouses and shops. Everything fits in one grid: products as rows, locations as columns, quantities where they meet.
Product × location grid with totals
Move stock between sites with a tap, or drag and drop
An admin interface for Supabase databases, free plan included: browse, filter and edit your tables, and back up your data. Essential when you code with AI.
Tables, filters and pagination
“Glass” theme, light and dark
Backup from the menu
Vanilla JavaScript, no runtime framework
Tailwind CSS compiled once, nothing to build in production
Vibe coding is fast, but left alone an AI happily reaches for frameworks, cloud services and build pipelines that break in three years. For web tools, the wavedevsimpl skill is the packaged set of instructions Claude follows on every project, so each app comes out the same simple, durable shape.
1
Describe the need
A festival’s volunteer rota, a stock list, a website to edit. Plain words, real constraints, who’s public and who’s admin.
2
Claude builds it
With the wavedevsimpl skill loaded: same layout, same libraries, same security rules, and decisions recorded in the project’s CLAUDE.md.
3
Test on a copy
Never on the real database. Public pages checked at 375 px wide, export working before go-live.
4
Upload one folder
FTP it to any shared PHP host. The database creates itself on first launch. Nothing to install.
PHP 8 + SQLite + vanilla HTML, CSS and JS
Boring on purpose. PHP runs on every cheap host, SQLite turns the database into a file, and no dependency means nothing to update.
PHP first, JavaScript second
Pages are rendered by PHP; JavaScript is only a small add-on for filtering, confirmations or a rich-text editor. One language to read, so the people who maintain the tool can open a file and understand it.
Cheapest possible hosting
Any shared PHP host. Nothing to install server-side.
Change host painlessly
The database is a file. Migrating is copying the folder.
Maintained for years
No npm install, no build that breaks. Fine for non-specialists.
No external service
No Firebase or Supabase quotas, paused free tiers or changing terms.
Rules every app follows
SQLite in WAL mode, foreign keys on, busy timeout set on every connection.
Zero-install schema: created on first run, migrated automatically when it changes.
Business rules where concurrency matters live in SQL, not in PHP.
One JSON API with whitelisted tables and columns; private fields stripped for visitors.
Shared admin password, CSRF token on every POST, everything escaped.
Mobile first, relative paths everywhere, and a CSV/JSON export before go-live.
When it’s the wrong tool
BreizhVibe says so honestly and proposes something else when a project needs:
several servers behind a load balancer
dozens of concurrent writes per second
real per-user accounts with fine roles
a real-time collaborative interface
Useful tips
Tutorials, step by step
Three small tools we use on every project, each on one page: try a site on your Mac, log in to your server with a key, and publish with one command while you watch the deployment.