vite-ts-react-template architecture.instructions.md

A set of architecture rules for a Vite and React TypeScript project. It defines where features, API access, shared code, pages, application setup, and end-to-end tests belong, and which layers may depend on one another.

In plain words
What is it for?
Use it when adding or reviewing features, deciding where files belong, enforcing import rules, structuring API logic, or checking that React Query and similar library code stays in the data-access layer.
Why use it?
It reduces tangled dependencies and keeps data-access details from spreading through the application. Clear boundaries make feature code easier to change and review.

Instructions file for GitHub Copilot

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 instructions/bartstc/vite-ts-react-template/architecture
Clone the repo
git clone --depth 1 https://github.com/bartstc/vite-ts-react-template

Made for: GitHub Copilot.

Per session 411 This file is loaded in full into every session.
When invoked 411 The same file — it is already loaded in full.
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.00411 $0.00411
Opus 5 $0.00205 $0.00205
Sonnet 5 $0.00082 $0.00082
Haiku 4.5 $0.00041 $0.00041

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

Security

Grade A, and why

vite-ts-react-template architecture.instructions.md 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.

.github/instructions/architecture.instructions.md · 38 lines

What it actually says

Architecture Rules

Project Structure

  • src/features/ — feature modules using feature slice architecture
  • src/lib/api/ — centralized API layer: queryOptions factories, mutations, DTOs by resource
  • src/lib/ — shared utilities, components, HTTP client, i18n, routing, theme
  • src/pages/ — route-level page components composing features
  • src/app/ — app-level config (App.tsx, Providers.tsx)
  • e2e/ — Playwright end-to-end tests
  • test-lib/ — test utilities, MSW handlers, fixtures

Feature Slice Layers

Each feature has four layers: components/, application/, providers/, models/.

Dependency rule

Layer May import from
components/ application/, providers/, models/, lib/*
application/ providers/, models/, lib/*
providers/ models/, lib/api/, lib/*
models/ lib/api/, lib/*

Cross-slice primitives: features/auth/ and features/authv2/ are cross-cutting concerns. Any feature slice may import from them.

Additional rules

  • providers/ is the data access gateway — library-specific code (React Query, etc.) stays inside this layer and never leaks beyond it
  • API logic starts in src/lib/api/ (queryOptions factories, mutations, DTOs by resource), then gets exposed through the relevant feature's providers/
  • Query files expose queryOptions factories — hook composition belongs in providers/, not in API files
  • Co-locate related files: component + story + test together
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 · 38 lines · 411 tokens per session scan A 5e603055bfb8

Subscribe to this mod's changes

vite-ts-react-template architecture.instructions.md is an instructions file published in the GitHub repository bartstc/vite-ts-react-template (121 stars, last pushed 1mo ago), licensed MIT. It adds 411 tokens to every session, about $0.0021 per session on Opus 5. 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.