Open-Source Cold Email & Warmup Platform
Warmbly is the open-source platform for cold email: warm your mailboxes, send campaigns, and triage every reply. Run it on our cloud or self-host the whole thing.
NFC/QR devices and a dashboard to track scans, rank employees, and grow your Google reviews.
MarketingTypeScript · CSSGitHub @taptapstarusa-gifOnlineOwner 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
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗This folder is the project root where the actual Next.js codebase gets scaffolded (starting
at Build Step 0.5). It is intentionally empty of documentation — all planning/reference docs
live one level up, in ../AgentGuide/, so they stay separate from the code tree.
TAPTAP/
AgentGuide/ ← all planning docs (scope, theme, flow, architecture, build guide, etc.)
Refrence/ ← raw client source material (SRS PDF, chat log, plate artwork)
Taptapstar/ ← THIS folder — the actual project root / codebase (currently empty, gets
scaffolded in Build Step 0.5 of ../AgentGuide/05_MASTER_BUILD_GUIDE.md)
Run the coding agent (Claude Code, etc.) with this folder (Taptapstar/) as its working
directory — that's where package.json, app/, etc. will live once scaffolded. Every
Master Prompt in ../AgentGuide/05_MASTER_BUILD_GUIDE.md refers to the planning docs by bare
filename (e.g. 04_PROJECT_STATE.md) for readability — when pasting a prompt into the agent,
those filenames resolve at ../AgentGuide/<filename> relative to this folder. If your
agent/tool requires the full relative path spelled out, prefix each reference with
../AgentGuide/ before pasting.
Start here: open ../AgentGuide/README.md for the full documentation index and reading order.