netlify-tanstack-deploy

Deployment rules for a TanStack Start React site on Netlify, a service that builds and hosts websites. They define the repository build file and require Netlify's dashboard build fields to remain empty.

In plain words
What is it for?
Use them when configuring, reviewing, or fixing Netlify deployment for a TanStack Start project in a web subdirectory.
Why use it?
They prevent path mistakes and incomplete server-side deployments that can leave a site showing a generic 404 page.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/dmenchaca/webflow-to-react/netlify-tanstack-deploy
Clone the repo
git clone --depth 1 https://github.com/dmenchaca/webflow-to-react
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 901 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00901
Opus 5 $0.00000 $0.00451
Sonnet 5 $0.00000 $0.00180
Haiku 4.5 $0.00000 $0.00090

Measured 2d ago against content hash 0680f0b83d0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

netlify-tanstack-deploy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/netlify-tanstack-deploy.mdc · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Netlify + TanStack Start (Webflow migration)

These mistakes were hit on real deploys. Follow shipping.md and gotchas.md § Netlify — especially § Mission critical: Netlify UI build settings must stay empty.

1. Use repo-root netlify.toml with [build] base = "web"

  • command and publish run relative to base after Netlify cds into web/.
  • publish = "dist/client" — not web/dist/client when base is already web (that would resolve to web/web/dist/client).

2. Do not deploy with only npm --prefix web from repo root

Prefer [build] base = "web" + npm ci && npm run build in the file. The @netlify/vite-plugin-tanstack-start plugin expects the build to run inside web/ so .netlify/ (SSR serverless function, redirects) is produced and deployed. A prefix-only build can leave dist/client on disk but still yield Netlify’s generic 404 (“Page not found”).

3. Mission critical: Netlify UI Build settings must stay empty

Do not fill Site configuration → Build & deploy → Build settings (Configure builds). Every override risks a broken deploy:

  • Base directory — empty (not /, not web); [build] base = "web" in the file already cds into web/.
  • Build command — empty; non-empty replaces TOML command. Never type netlify.toml here.
  • Publish directory — empty; TOML publish = "dist/client" is relative to base.
  • Package directory — empty unless a documented monorepo exception.
  • Functions directory — empty; not netlify/functions. SSR functions come from web/.netlify/ after vite build, not repo-root netlify/functions.
  • Runtime — leave default / unset unless you have a documented Node pin in TOML.

Re-check the UI after Save — Netlify sometimes restores Functions directory or Base. Full table: gotchas.md § Mission critical: Netlify UI.

If you truly cannot clear a field, mirror templates/netlify.toml exactly — the skill’s default is file-only + empty UI.

Read the full file on GitHub · 46 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 46 lines · 0 tokens per session scan A 0680f0b83d0d

Subscribe to this mod's changes

netlify-tanstack-deploy is a cursor rule published in the GitHub repository dmenchaca/webflow-to-react (27 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 901 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.