cursorrules

Cursor Rules: webjs app

You are working on a webjs app, an AI-first, no-build, web-components-first framework. Read AGENTS.md for the full API reference and CONVENTIONS.md for project-specific conventions before writing any code. When AGENTS.md doesn't cover what you need, the full hosted docs are at https://webjs.dev/docs.

Persistence + scaffold rules (non-negotiable)

• Use Drizzle + SQLite for data, never JSON files. It's already wired up (db/schema.server.ts, db/connection.server.ts, npm run db:generate + npm run db:migrate). For ANY data the app stores (todos, posts, messages, products, comments…), define a Drizzle table. NEVER create data/*.json, db.json, or any JSON file as a fake database. NEVER use module-scope arrays / Maps as a substitute. NEVER use localStorage for app data. These are project conventions in CONVENTIONS.md (a JSON file used as a database resets on reload and cannot scale).
• The scaffold is reference, not the final product. Replace app/page.ts, the example User model, the example users module, etc. with the app the user actually asked for. Don't ship "Hello from " as the deliverable.
• Only three templates exist: webjs create <name> (default full-stack), --template api, --template saas. The CLI rejects any other --template value. Pick:
  • Any product UI (todo, blog, dashboard, marketplace, social…) → default
  • HTTP/JSON API only, no UI → --template api
  • Auth / login / signup / SaaS → --template saas

Before starting ANY work

FIRST, before writing any code:

1. Run git branch --show-current to check the branch.
   • If on main/master: STOP. Ask the user which branch to use, or create one with git checkout -b feature/<name>.
   • If on a feature branch: verify it matches the current task. Ask if unsure.
2. Sync with parent: git fetch origin && git log HEAD..origin/main --oneline
   • If upstream has new commits: git rebase origin/main before starting.
   • Resolve any conflicts before proceeding with the task.