Why no type-check command?
The site uses plain JavaScript, so there is nothing to type-check. If you add TypeScript, choose it in the generator and add tsc as the type-check command.
A static, multi-page marketing or documentation site built with plain HTML, Vite and Tailwind CSS v4. With no framework to lean on, the rules focus on design tokens, accessibility and keeping pages light.
# AGENTS.md
Project: static-site. A static multi-page website built with Vite and Tailwind CSS v4.
This file is the single source of truth for every coding agent working in this repository. The tool-specific files (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md and .cursor/rules/project.mdc) point here. Edit this file, not those.
## Stack
- Languages: JavaScript, HTML and CSS
- Hosting: Netlify
- Tests: Playwright
- Package manager: npm
## Commands
Run these from the repository root.
- Install dependencies: `npm ci`
- Run locally: `npm run dev`
- Build: `npm run build`
- Run all tests: `npx playwright test`
- Run one test file: `npx playwright test tests/home.spec.js`
- Lint: `npx eslint .`
- Format: `npx prettier --write .`
## Project layout
- `index.html`: Home page (one HTML file per page)
- `pages/`: Other pages
- `src/style.css`: Tailwind entry: @import "tailwindcss" and @theme tokens
- `src/main.js`: Small progressive-enhancement scripts
- `public/`: Images, fonts and files copied as-is
## Code style
- Indent with 2 spaces. Never tabs.
- Match the style and patterns of the surrounding code, even where you would personally choose differently.
- Commit messages follow Conventional Commits: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, with an imperative summary under 72 characters.
- Delete code you make unused, including imports, flags and files. Do not leave commented-out code behind.
- Every new UI control works with a keyboard, has a visible focus state and an accessible name.
## Working rules
- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
## Product constraints
- Design and test every screen at phone width first, then scale up.
- Watch the performance budget: no new blocking requests on page load, and justify any bundle-size increase in the change description.
- Public pages must render their main content as HTML on the server, with a unique title, meta description and one h1.
## Project-specific notes
- Style with Tailwind utility classes in the markup. Add custom CSS only for things utilities cannot express.
- Colors, fonts and spacing come from the `@theme` tokens in `src/style.css`; do not use arbitrary values like `text-[#3b82f6]`.
- Tailwind v4 is configured in CSS with `@theme`; do not create a `tailwind.config.js` unless the project already has one.
- Pages must work without JavaScript; scripts only enhance.
- Every page has one `h1`, a unique title and meta description, and images with `alt`, `width` and `height`.
- Register every new HTML page in the Vite build inputs so it is included in the production output.
## Project phase
This project is in active development. Follow the patterns that already exist; consistency beats novelty.
# CLAUDE.md
@AGENTS.md
## Claude Code
- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file, so every agent stays in sync.
- Put Claude-only preferences below this line. Personal, uncommitted notes belong in CLAUDE.local.md.
# GEMINI.md
@./AGENTS.md
## Gemini CLI
- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file.
- Alternative: delete this file and set "context": { "fileName": ["AGENTS.md"] } in .gemini/settings.json so Gemini CLI reads AGENTS.md directly.
# Copilot instructions
Project: static-site. A static multi-page website built with Vite and Tailwind CSS v4.
The full instructions are in AGENTS.md at the repository root. Read it before you change code; if anything here disagrees with it, AGENTS.md wins. The essentials are repeated below for Copilot surfaces that only read this file.
## Stack
- Languages: JavaScript, HTML and CSS
- Hosting: Netlify
- Tests: Playwright
- Package manager: npm
## Commands
- Install dependencies: `npm ci`
- Run locally: `npm run dev`
- Build: `npm run build`
- Run all tests: `npx playwright test`
- Run one test file: `npx playwright test tests/home.spec.js`
- Lint: `npx eslint .`
- Format: `npx prettier --write .`
## Working rules
- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
---
description: Project instructions for every task (mirrors AGENTS.md)
globs:
alwaysApply: true
---
# Project rules
The project instructions live in @AGENTS.md at the repository root, which Cursor loads automatically. They are not repeated here, so they cost context only once. Edit AGENTS.md, not this rule.
Before you change code, check the Commands and Working rules sections of AGENTS.md, and run its test and lint commands before you say a task is done.
Put Cursor-only rules below, or add scoped rules as more .mdc files with `globs` (for example `src/components/**/*.tsx`).
These are the exact files the generator writes for this preset. Change any command or rule in the generator and download your own set.
The preset describes a a static multi-page website built with Vite and Tailwind CSS v4. Its AGENTS.md is 47 non-empty lines with 7 exact commands, 5 key directories, and 6 stack-specific rules on top of the shared working rules.
npm ci, npm run dev, npm run build, npx playwright test, npx playwright test tests/home.spec.js, npx eslint ., npx prettier --write ..index.html, pages/, src/style.css, src/main.js, public/.Most examples online are Tailwind v3 with a JavaScript config file. In v4 the theme lives in CSS. Agents that create a config file add a second source of truth that may be ignored entirely.
Bracket values are convenient, so agents use them for every color. After a few weeks the site has fifteen blues. Tokens keep the palette consistent.
Vite builds only the entry points it knows about. A new HTML file works in dev and then silently disappears from the production build unless it is registered.
There is no component library enforcing accessible patterns, so the basic page rules matter more.
@theme tokens in src/style.css; do not use arbitrary values like text-[#3b82f6].@theme; do not create a tailwind.config.js unless the project already has one.h1, a unique title and meta description, and images with alt, width and height.Want different commands or rules? Load this preset into the generator, change anything, and download your own set.
AGENTS.md is read directly by Codex, Cursor, Windsurf, Cline, Zed and Jules, and by GitHub Copilot's cloud agent, code review and CLI. Claude Code reads it through the generated CLAUDE.md, and Gemini CLI through GEMINI.md. See the compatibility table for details, last verified 2026-11-13.
All presets are on the stacks page.
The site uses plain JavaScript, so there is nothing to type-check. If you add TypeScript, choose it in the generator and add tsc as the type-check command.
For a content-heavy site with many pages, probably; see the Astro template. For a handful of hand-written pages, plain Vite and Tailwind is simpler.
Mostly. Replace the v4 configuration rule with a note that tokens live in tailwind.config.js, and keep the rest.
Yes. Copy them into any project, commercial or not, without attribution. They are a starting point: adjust the commands and rules to match your repository.
You do not have to take our word for it. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing you type is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only the feedback form can add a line to that log, and it sends only the vote and comment you type into it. 2prompt has no server code at all: no API, no model and no database of your files. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site, the fonts and the anonymous analytics endpoint.