AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
A curated AI tool library, role-aware guides, and a place to keep what works. Everything a vibe coder needs to ship something real.
Translation pending
Developer toolsTypeScript · PLpgSQLGitHub @viberation-devOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
The AI coding tool directory, Learn hub and guided walkthroughs. Next.js App
Router, Supabase, Tailwind.
Against the shared Supabase project, which is what .env.local points at by
default:
Everything a visitor can see works this way. What does not is anything behind
a session: /account, onboarding and /admin all need a signed-in user, and
the shared project is production data.
Use this when the change is behind a login. It runs Postgres, GoTrue and the
rest in Docker, applies the migrations in supabase/migrations, and seeds a
staff account that exists only on your machine.Read the full README ↗The AI coding tool directory, Learn hub and guided walkthroughs. Next.js App Router, Supabase, Tailwind.
Against the shared Supabase project, which is what .env.local points at by
default:
npm run dev
Everything a visitor can see works this way. What does not is anything behind
a session: /account, onboarding and /admin all need a signed-in user, and
the shared project is production data.
Use this when the change is behind a login. It runs Postgres, GoTrue and the
rest in Docker, applies the migrations in supabase/migrations, and seeds a
staff account that exists only on your machine.
npx supabase start # once per machine, pulls images
npx supabase db reset # applies migrations + seeds
Point the app at it by replacing the two values in .env.local with the
API_URL and ANON_KEY that npx supabase status prints, then restart
npm run dev. Keep the shared values somewhere; swapping back is the same two
lines.
Then sign in:
npm run dev:login # prints a one-time link, open it
The seeded account ([email protected]) has no password. The script mints a
login link through the local stack's service-role key, so there is no
credential in the repo to leak and nothing to type into a form. It refuses to
run against any host but localhost.
npx supabase db reset reseeds and clears anything you did locally. The seed
lives in supabase/seed-dev-staff.sql, deliberately outside seed.sql so the
shared project can never pick it up.
npm run typecheck
npm run lint
npm test
npm run build
Conventions, architecture and what is deliberately out of scope live in
CLAUDE.md.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
To learn more about Next.js, take a look at the following resources:
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.