agentmods.dev

tanstack-start

Rules for building TanStack Start applications, a web framework that provides file-based routing, data loading, and server-side functions.

In plain words
What is it for?
Creating routes and nested layouts, loading route data, guarding pages, validating search values, and connecting pages to backend functions.
Why use it?
They keep routes, data fetching, authentication checks, search parameters, and backend logic organised and consistently validated.

Cursor rule for Cursor

23 25d ago A scan 0 tokens original MIT
View the source file virastack/ai
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/virastack/ai/tanstack-start
Clone the repo
git clone --depth 1 https://github.com/virastack/ai

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,057 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.01057
Opus 5 $0.00000 $0.00528
Sonnet 5 $0.00000 $0.00211
Haiku 4.5 $0.00000 $0.00106

Measured yesterday against content hash 54bdedbcb46a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tanstack-start 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 yesterday.

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.

templates/tanstack/.cursor/rules/tanstack-start.mdc · 105 lines

How it starts

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

TanStack Start Constitution

Constraints

  • Route Definition: Always use createFileRoute. Path MUST strictly match the file system location.
  • Component Scope: Keep route files thin. Only orchestrate routing and data. Move UI and business logic to src/features.
  • Nested Layouts: Use the <Outlet /> component in parent routes to render child routes. If a route has children, the parent component MUST render <Outlet />.
  • Data Loading: Fetch all route-level data in loader. Consume via Route.useLoaderData or useSuspenseQuery.
  • Guards: Put auth, redirects, and preconditions in beforeLoad.
  • Hydration: Rely on loader prefetching for data hydration. Do not use Next.js-specific patterns like manual dehydration.
  • Server Functions: Wrap all backend-only logic in standalone serverFn. Functions MUST act as a bridge to the API layer; keep database orchestration and business logic inside src/features/api or helpers.
  • Search Params: Validate all search params with validateSearch using a Zod schema. Never trust raw search values.
  • i18n Implementation: Use paraglide-js for translations. Follow the patterns defined in i18n.mdc.
  • Error Handling: Provide errorComponent for failure states. Handle expected errors in the loader.
  • Loading UI: Provide pendingComponent for async states when needed.
  • Not Found: Provide notFoundComponent for missing resources.
  • Head/SEO: Define metadata with the head property. Keep it deterministic and typed.
  • Sync: Ensure route paths are kept in sync via tsr watch command.
  • Guard Security: Enforce session and permission checks within beforeLoad or dedicated middleware before serverFn execution.

Bans

  • Client-Side Fetching: Fetching data inside the component body via useEffect or useQuery (without loader prefetch) is FORBIDDEN.
  • Inline serverFn: Defining serverFn inside a component or route definition is FORBIDDEN. They MUST be exported as standalone constants.
  • Next.js Conventions: Using "use server" directives, page.tsx naming, or Next.js-specific hooks (useRouter from next/navigation) is STRICTLY FORBIDDEN.
  • Untyped Routes: Navigating via string paths without type-safety (using Link or Maps without the to property pointing to a valid route) is FORBIDDEN.
  • Insecure Env Vars: Forbidden to store secrets or private keys in environment variables with VITE_ prefixes.

Read the full file on GitHub · 105 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. yesterday First seen · 105 lines · 0 tokens per session scan A 54bdedbcb46a

Subscribe to this mod's changes

tanstack-start is a cursor rule published in the GitHub repository virastack/ai (23 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,057 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.

Backend and APIsResearchagent-skillsantigravityclaude-codecursorskillsvirastack
Related

Other cursor rules, from other repositories

marker-triage

Triage a Marker.io website-feedback backlog at scale. Use when asked to go through, categorize, prioritize, deduplicate, or make sense of many Marker.io issues at once. Splits content fixes from functional bugs, groups by page, rates criticality, flags duplicates and repeat reporters, surfaces quick wins, lists…

marker-io/mcp-skills · 85 tokens

marker-client-report

Turn a project's completed Marker.io work into a client-ready report. Use when asked to write a weekly or monthly recap for a client, summarize what was shipped or fixed this period, or produce a status update for a website project from Marker.io. Read-only: it reads issues and writes a markdown report, it does not…

marker-io/mcp-skills · 67 tokens

marker-insights

Aggregate Marker.io website feedback into recurring patterns. Use when asked to find the most common issues on a site, which pages get the most feedback, recurring content problems, or the content-vs-bug split across many Marker.io reports, and produce a prioritized brief for a website team or agency. Read-only: it…

marker-io/mcp-skills · 73 tokens

marker-bug-to-fix

Take one Marker.io bug report and produce a ready-to-review code fix. Use when asked to fix, investigate, reproduce, or find the root cause of a specific Marker.io issue in the current repository. Pulls the issue's screenshot, console errors, network requests and DOM, locates the cause in code, proposes a minimal…

marker-io/mcp-skills · 73 tokens

marker-sync

Keep Marker.io and your issue tracker (GitHub, Linear, Jira) in sync. Use when asked to pull new Marker.io issues into a tracker, enrich tracker tickets with Marker context, mark issues resolved or ready-to-test in both places, or reconcile status mismatches between Marker.io and the tracker.

marker-io/mcp-skills · 61 tokens

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens