Scaffold a production-ready full-stack Cloudflare app with React, Hono, D1, and better-auth in minutes.
Works with
Clones and rebrands the vite-flare-starter template into a standalone project with automated find-replace across wrangler.jsonc, package.json, and index.html
Includes React 19, Vite, Tailwind v4, shadcn/ui frontend; Hono backend on Workers; D1 SQLite with Drizzle ORM; better-auth for Google OAuth; R2 storage; and Workers AI binding
Generates secrets, creates .dev.vars template, run
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionvite-flare-starterExecute the skills CLI command in your project's root directory to begin installation:
Fetches vite-flare-starter from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate vite-flare-starter. Access via /vite-flare-starter in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
695
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
695
stars
Clone and configure the batteries-included Cloudflare starter into a standalone project. Produces a fully rebranded, deployable full-stack app.
| Layer | Technology | Version |
|---|---|---|
| Frontend | React, Vite, Tailwind CSS, shadcn/ui | 19, 6.x, v4, latest |
| Backend | Hono (on Cloudflare Workers) | 4.x |
| Database | D1 (SQLite at edge) + Drizzle ORM | 0.38+ |
| Auth | better-auth (Google OAuth + email/password) | latest |
| Storage | R2 (S3-compatible object storage) | — |
| AI | Workers AI binding | — |
| Data Fetching | TanStack Query | v5 |
| Binding | Type | Purpose |
|---|---|---|
DB |
D1 Database | Primary application database |
AVATARS |
R2 Bucket | User avatar storage |
FILES |
R2 Bucket | General file uploads |
AI |
Workers AI | AI model inference |
src/
├── client/ # React frontend
│ ├── components/ # UI components
│ ├── hooks/ # Custom hooks + TanStack Query
│ ├── pages/ # Route pages
│ ├── lib/ # Utilities (auth client, etc.)
│ └── main.tsx # App entry point
├── server/ # Hono backend
│ ├── index.ts # Worker entry point
│ ├── routes/ # API routes
│ ├── middleware/ # Auth, CORS, etc.
│ └── db/ # Drizzle schema + queries
└── shared/ # Shared types between client/server
| Command | Purpose |
|---|---|
pnpm dev |
Start local dev server |
pnpm build |
Production build |
pnpm deploy |
Deploy to Cloudflare |
pnpm db:migrate:local |
Apply migrations locally |
pnpm db:migrate:remote |
Apply migrations to production |
pnpm db:generate |
Generate migration from schema changes |
Ask for:
| Required | Optional |
|---|---|
| Project name (kebab-case) | Admin email |
| Description (1 sentence) | Google OAuth credentials |
| Cloudflare account | Custom domain |
git clone https://github.com/jezweb/vite-flare-starter.git PROJECT_DIR --depth 1
cd PROJECT_DIR
rm -rf .git
git init
Replace vite-flare-starter with the project name in these locations:
| File | Target | Replace with |
|---|---|---|
wrangler.jsonc |
"vite-flare-starter" (worker name) |
"PROJECT_NAME" |
wrangler.jsonc |
vite-flare-starter-db |
PROJECT_NAME-db |
wrangler.jsonc |
vite-flare-starter-avatars |
PROJECT_NAME-avatars |
wrangler.jsonc |
vite-flare-starter-files |
PROJECT_NAME-files |
package.json |
"name": "vite-flare-starter" |
"name": "PROJECT_NAME" |
package.json |
vite-flare-starter-db |
PROJECT_NAME-db |
index.html |
<title> content |
App display name (Title Case) |
Also in wrangler.jsonc:
account_id line (let wrangler prompt or use env var)database_id value with REPLACE_WITH_YOUR_DATABASE_IDReset package.json version to "0.1.0".
Use the Edit tool for replacements (preferred over sed to avoid macOS/GNU differences).
BETTER_AUTH_SECRET=$(openssl rand -hex 32 2>/dev/null || python3 -c "import secrets; print(secrets.token_hex(32))")
Convert kebab-case project name: my-cool-app becomes Display My Cool App, ID my_cool_app.
# Local Development Environment Variables
# DO NOT COMMIT THIS FILE TO GIT
# Authentication (better-auth)
BETTER_AUTH_SECRET=<generated>
BETTER_AUTH_URL=http://localhost:5173
# Google OAuth (optional)
GOOGLE_CLIENT_ID=
GOOGLE_CLIENT_SECRET=
# Email Auth Control (disabled by default)
# ENABLE_EMAIL_LOGIN=true
# ENABLE_EMAIL_SIGNUP=true
# Application Configuration
APP_NAME=<Display Name>
VITE_APP_NAME=<Display Name>
VITE_APP_ID=<app_id>
VITE_TOKEN_PREFIX=<app_id>_
VITE_GITHUB_URL=
VITE_FOOTER_TEXT=
NODE_ENV=development
npx wrangler d1 create PROJECT_NAME-db
# Extract database_id from output, update wrangler.jsonc
npx wrangler r2 bucket create PROJECT_NAME-avatars
npx wrangler r2 bucket create PROJECT_NAME-files
pnpm install
pnpm run db:migrate:local
git add -A
git commit -m "Initial commit from vite-flare-starter"
http://localhost:5173/api/auth/callback/google, copy Client ID and Secret to .dev.varspublic/favicon.svg<title> and meta descriptionpnpm dev
Check: http://localhost:5173 loads, shows YOUR app name, sign-up/sign-in works (if OAuth configured).
# Set production secrets
openssl rand -base64 32 | npx wrangler secret put BETTER_AUTH_SECRET
echo "https://PROJECT_NAME.SUBDOMAIN.workers.dev" | npx wrangler secret put BETTER_AUTH_URL
echo "http://localhost:5173,https://PROJECT_NAME.SUBDOMAIN.workers.dev" | npx wrangler secret put TRUSTED_ORIGINS
# If using Google OAuth
echo "your-client-id" | npx wrangler secret put GOOGLE_CLIENT_ID
echo "your-client-secret" | npx wrangler secret put GOOGLE_CLIENT_SECRET
# Migrate remote database
pnpm run db:migrate:remote
# Build and deploy
pnpm run build && pnpm run deploy
Critical: After first deploy, update BETTER_AUTH_URL with your actual Worker URL. Add the production URL to Google OAuth redirect URIs.
Change all of these so attackers cannot identify your site uses this starter:
| Location | Default Value | How to Change |
|---|---|---|
| Page title | "Vite Flare Starter" | index.html |
| App name in UI | "Vite Flare Starter" | VITE_APP_NAME env var |
| localStorage keys | vite-flare-starter-theme |
VITE_APP_ID env var |
| API tokens | vfs_ prefix |
VITE_TOKEN_PREFIX env var |
| GitHub links | starter repo | VITE_GITHUB_URL (set empty to hide) |
| Worker name | vite-flare-starter |
wrangler.jsonc |
| Database name | vite-flare-starter-db |
wrangler.jsonc |
| R2 buckets | vite-flare-starter-* |
wrangler.jsonc |
| Variable | Purpose | Example |
|---|---|---|
VITE_APP_NAME |
Display name in UI | "My Cool App" |
VITE_APP_ID |
localStorage prefix, Sentry | "mycoolapp" |
VITE_TOKEN_PREFIX |
API token prefix | "mca_" |
VITE_GITHUB_URL |
GitHub link (empty = hidden) | "" |
VITE_FOOTER_TEXT |
Footer copyright text | "2026 My Company" |
APP_NAME |
Server-side app name | "My Cool App" |
| Variable | Purpose | Notes |
|---|---|---|
BETTER_AUTH_SECRET |
Session encryption | openssl rand -hex 32 |
BETTER_AUTH_URL |
Auth base URL | Must match actual URL exactly |
TRUSTED_ORIGINS |
Allowed origins | Comma-separated, include localhost + prod |
GOOGLE_CLIENT_ID |
Google OAuth | From Google Cloud Console |
GOOGLE_CLIENT_SECRET |
Google OAuth | From Google Cloud Console |
ENABLE_EMAIL_LOGIN |
Enable email/password | "true" to enable |
ENABLE_EMAIL_SIGNUP |
Enable email signup | Requires ENABLE_EMAIL_LOGIN |
| Variable | Purpose | Notes |
|---|---|---|
EMAIL_FROM |
Sender address | For verification/password reset |
EMAIL_API_KEY |
Email service API key | Resend recommended |
src/server/db/schema.tspnpm db:generatepnpm db:migrate:localpnpm db:migrate:remotesrc/server/routes/src/server/index.tssrc/client/hooks/Edit src/server/auth.ts: add provider to socialProviders, add credentials to .dev.vars and production secrets, update client-side login buttons.
Control features via environment variables: VITE_FEATURE_STYLE_GUIDE=true, VITE_FEATURE_COMPONENTS=true. Add your own in src/client/lib/features.ts.
| Symptom | Cause | Fix |
|---|---|---|
| Auth redirects to homepage silently | Missing TRUSTED_ORIGINS | Set TRUSTED_ORIGINS with all valid URLs |
| "Not authorized" on deploy | Wrong account_id | Remove account_id from wrangler.jsonc or set yours |
| Database 500 errors | Missing migrations | Run pnpm db:migrate:local and pnpm db:migrate:remote |
| localStorage shows "vite-flare-starter" | Missing VITE_APP_ID | Set VITE_APP_ID=yourapp in .dev.vars |
| Auth fails in production only | BETTER_AUTH_URL mismatch | Must match actual Worker URL exactly (https, no trailing slash) |
| "redirect_uri_mismatch" on Google sign-in | OAuth redirect URI missing | Add production URL to Google Cloud Console OAuth redirect URIs |
| Secret changes have no effect | Not redeployed | wrangler secret put does NOT redeploy. Run pnpm deploy after |
BETTER_AUTH_SECRET set (different from dev!)BETTER_AUTH_URL matches actual Worker URLTRUSTED_ORIGINS includes all valid URLspnpm db:migrate:remote)vite-flare-starter references in config files.dev.vars is NOT committed (check .gitignore)Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
jezweb/claude-skills
asyrafhussin/agent-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
Keeps context tight: vite-flare-starter is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for vite-flare-starter matched our evaluation — installs cleanly and behaves as described in the markdown.
vite-flare-starter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added vite-flare-starter from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
vite-flare-starter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for vite-flare-starter matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: vite-flare-starter is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added vite-flare-starter from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
vite-flare-starter reduced setup friction for our internal harness; good balance of opinion and flexibility.
vite-flare-starter has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 53