Web accessibility baseline (WCAG 2.0 AA / AODA) for landmarks, keyboard operability, focus states, motion, and contrast. Use when building or reviewing UI components, pages, navigation, overlays, or any self-starting animation/motion in a web frontend.
Claude Code repo hygiene — keeping CLAUDE.md a symlink to AGENTS.md and gitignoring Claude Code's local-only state. Use when setting up a repo for Claude Code, or auditing one that already has a CLAUDE.md and/or AGENTS.md.
House style for authoring, shaping, and styling React/shadcn components (file skeleton, CVA variants, this repo's flat ui/layout organization, layout shell). Use when adding, refactoring, or reviewing a component in this project.
Where content and state live in a typed frontend (constants/ as source of truth, state discipline, date and media handling). Use when adding site copy/content, deciding where data or state should live, or handling dates and media entries.
Git workflow standards — Conventional Commits, branch naming, the no-AI-attribution rule, and how to review a PR. Use when creating branches, writing commit messages, opening PRs, reviewing a PR, or the user asks how a change should be recorded in git.
Next.js App Router conventions — runtime/language foundations, server-vs-client components, static generation, metadata, and folder structure. Use when scaffolding a Next.js app, adding a route/page, or deciding how a piece of code should be organized in a Next.js + TypeScript codebase.
Frontend performance discipline — LCP budget, lazy-loading, vector assets, motion budgets, and font loading. Use when adding images/media, animation, custom fonts, or reviewing a page for load/interactivity regressions.
Project delivery methodology for planning and initial implementation — the PRD pipeline, division of truth between repo/design tool/GitHub, and milestone kinds. Use when planning work, cutting milestones, deciding what belongs in which doc, or setting up a delivery process for a new project.
SEO baseline — root/route metadata, Open Graph and Twitter cards, crawlable server-rendered content. Use when adding metadata to a page/route, sharing links, or reviewing whether content is crawlable.
Testing strategy — the testing pyramid (unit base, integration middle, e2e few), when to reach for each layer, and keeping the runner green. Use when deciding what kind of test to add, setting up a test runner, or reviewing a PR that adds test coverage.
House style for project prose — docs, plans, PR and commit bodies. Declarative voice, load-bearing sentences, rationale inline, structure and mechanics rules. Use when writing or editing documentation, PR descriptions, commit bodies, or standards/process docs (not product/site copy, which is the design's voice).
Instructions for techtankto/techtank-site, covering agents.md, what this repo is, repository layout, how the information architecture works and working conventions.