Oracle3
Open-source trading engine and MCP server for prediction markets. Fee-aware no-arbitrage trading across related contracts, live on Kalshi, Polymarket and Solana or on paper.
Budget app v.01
Translation pending
FinanceJavaScript · CSSGitHub @jffzln-aiOnlineOwner 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.
Personal finance dashboard, built on Vite + React + Supabase.
Import this repo into Vercel. Framework preset: Vite (should auto-detect).
Add the two environment variables from .env.example in Vercel's Project
Settings -> Environment Variables, using your real values - Vercel builds
on its own servers and won't see your local .env file.
Schema lives in supabase/migrations/. Run each file in order in your
Supabase project's SQL Editor (or via supabase db push if using the CLI).Read the full README ↗Personal finance dashboard, built on Vite + React + Supabase.
npm install
cp .env.example .env
# edit .env with your real Supabase Project URL and Publishable key
npm run dev
Import this repo into Vercel. Framework preset: Vite (should auto-detect).
Add the two environment variables from .env.example in Vercel's Project
Settings -> Environment Variables, using your real values - Vercel builds
on its own servers and won't see your local .env file.
Schema lives in supabase/migrations/. Run each file in order in your
Supabase project's SQL Editor (or via supabase db push if using the CLI).