new-term-radar
Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.
Finds local businesses whose websites are broken, dated or missing entirely, proves what's wrong, and writes the first message for you.
MarketingJavaScript · CSSGitHub @7umerOnlineOwner 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.
Standalone marketing page for LeadForge. Deployed separately from the app
itself; every CTA links out to the app's own /register and /login.
React 18 + Vite + Tailwind CSS + lucide-react. No routing, no state
management, no backend — this is a static site once built.
Outputs static files to dist/.
Import this repo at vercel.com/new. It's a plain
Vite app at the repo root, so the defaults (build command npm run build,
output directory dist) work with no configuration. Set VITE_APP_URL in
the project's Environment Variables before the first deploy.Read the full README ↗Standalone marketing page for LeadForge. Deployed separately from the app
itself; every CTA links out to the app's own /register and /login.
React 18 + Vite + Tailwind CSS + lucide-react. No routing, no state
management, no backend — this is a static site once built.
npm install
cp .env.example .env # set VITE_APP_URL to the deployed app's origin
npm run dev
npm run build
Outputs static files to dist/.
Import this repo at vercel.com/new. It's a plain
Vite app at the repo root, so the defaults (build command npm run build,
output directory dist) work with no configuration. Set VITE_APP_URL in
the project's Environment Variables before the first deploy.