vite-flare-starter

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill vite-flare-starter
0 commentsdiscussion
summary

Scaffold a production-ready full-stack Cloudflare app with React, Hono, D1, and better-auth in minutes.

  • 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
skill.md

Vite Flare Starter

Clone and configure the batteries-included Cloudflare starter into a standalone project. Produces a fully rebranded, deployable full-stack app.

Stack

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

Cloudflare Bindings

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

Project Structure

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

Key Commands

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

Workflow

Step 1: Gather Project Info

Ask for:

Required Optional
Project name (kebab-case) Admin email
Description (1 sentence) Google OAuth credentials
Cloudflare account Custom domain

Step 2: Clone and Configure

2a. Clone and clean

git clone https://github.com/jezweb/vite-flare-starter.git PROJECT_DIR --depth 1
cd PROJECT_DIR
rm -rf .git
git init

2b. Find-replace targets

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:

  • Remove hardcoded account_id line (let wrangler prompt or use env var)
  • Replace database_id value with REPLACE_WITH_YOUR_DATABASE_ID

Reset package.json version to "0.1.0".

Use the Edit tool for replacements (preferred over sed to avoid macOS/GNU differences).

2c. Generate auth secret

BETTER_AUTH_SECRET=$(openssl rand -hex 32 2>/dev/null || python3 -c "import secrets; print(secrets.token_hex(32))")

2d. Create .dev.vars

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

2e. Create Cloudflare resources (optional)

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

2f. Install and migrate

pnpm install
pnpm run db:migrate:local

2g. Initial commit

git add -A
git commit -m "Initial commit from vite-flare-starter"

Step 3: Manual Configuration

  1. Google OAuth (if using): Go to Google Cloud Console, create OAuth 2.0 Client ID, add redirect URI http://localhost:5173/api/auth/callback/google, copy Client ID and Secret to .dev.vars
  2. Favicon: Replace public/favicon.svg
  3. CLAUDE.md: Update project description, remove vite-flare-starter references
  4. index.html: Update <title> and meta description

Step 4: Verify Locally

pnpm dev

Check: http://localhost:5173 loads, shows YOUR app name, sign-up/sign-in works (if OAuth configured).

Step 5: Deploy to Production

# 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.

Security Fingerprints

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

Environment Variables

Branding (VITE_ prefix = available in frontend)

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"

Auth

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

Email (Optional)

Variable Purpose Notes
EMAIL_FROM Sender address For verification/password reset
EMAIL_API_KEY Email service API key Resend recommended

Common Customisations

Adding a New Database Table

  1. Add schema in src/server/db/schema.ts
  2. Generate migration: pnpm db:generate
  3. Apply locally: pnpm db:migrate:local
  4. Apply to production: pnpm db:migrate:remote

Adding a New API Route

  1. Create route file in src/server/routes/
  2. Register in src/server/index.ts
  3. Add TanStack Query hook in src/client/hooks/

Changing Auth Providers

Edit src/server/auth.ts: add provider to socialProviders, add credentials to .dev.vars and production secrets, update client-side login buttons.

Feature Flags

Control features via environment variables: VITE_FEATURE_STYLE_GUIDE=true, VITE_FEATURE_COMPONENTS=true. Add your own in src/client/lib/features.ts.

Troubleshooting

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

Production Deployment Checklist

  • BETTER_AUTH_SECRET set (different from dev!)
  • BETTER_AUTH_URL matches actual Worker URL
  • TRUSTED_ORIGINS includes all valid URLs
  • Google OAuth redirect URI includes production URL
  • Remote database migrated (pnpm db:migrate:remote)
  • No vite-flare-starter references in config files
  • Favicon replaced
  • CLAUDE.md updated
  • .dev.vars is NOT committed (check .gitignore)
how to use vite-flare-starter

How to use vite-flare-starter on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add vite-flare-starter
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill vite-flare-starter

The skills CLI fetches vite-flare-starter from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/vite-flare-starter

Reload or restart Cursor to activate vite-flare-starter. Access the skill through slash commands (e.g., /vite-flare-starter) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.653 reviews
  • Kofi Sanchez· Dec 24, 2024

    Keeps context tight: vite-flare-starter is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Aditi Huang· Dec 20, 2024

    Registry listing for vite-flare-starter matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sakura Harris· Dec 16, 2024

    vite-flare-starter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Neel Smith· Dec 4, 2024

    We added vite-flare-starter from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kofi Ramirez· Nov 23, 2024

    vite-flare-starter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Valentina Bhatia· Nov 15, 2024

    Registry listing for vite-flare-starter matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Mei Garcia· Nov 11, 2024

    Keeps context tight: vite-flare-starter is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Harper Khanna· Nov 7, 2024

    We added vite-flare-starter from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Harper Thompson· Oct 26, 2024

    vite-flare-starter reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aditi Kim· Oct 14, 2024

    vite-flare-starter has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 53

1 / 6