ANGULAR AGENTS.MD

Angular has changed a lot: standalone components, signals and the built-in control flow replaced NgModules, much of RxJS state and structural directives. These files keep an agent on the modern APIs.

Zero retention: everything you type stays in this browser. Verify it yourself in DevTools.
AGENTS.mdFor Codex, Cursor, Copilot, Jules, Windsurf and more
# AGENTS.md

Project: angular-app. An Angular application using standalone components and signals.

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: TypeScript, HTML and CSS
- Framework: Angular
- Hosting: Azure
- Tests: Vitest
- Package manager: npm

## Commands

Run these from the repository root.

- Install dependencies: `npm ci`
- Run locally: `npx ng serve`
- Build: `npx ng build`
- Run all tests: `npx ng test`
- Run one test file: `npx ng test --include src/app/path/file.spec.ts`
- Lint: `npx ng lint`
- Type-check: `npx tsc -p tsconfig.app.json --noEmit`
- Format: `npx prettier --write src`

## Project layout

- `src/app/`: Application code grouped by feature
- `src/app/core/`: Singleton services, interceptors and guards
- `src/app/shared/`: Reusable standalone components, pipes and directives
- `src/environments/`: Build-time configuration (no secrets)

## Code style

- Indent with 2 spaces. Never tabs.
- TypeScript runs in strict mode. Do not use `any`; use `unknown` and narrow it, or write the real type.
- Match the style and patterns of the surrounding code, even where you would personally choose differently.
- Never swallow an error. Handle it where you can act on it, or rethrow it with context about what failed.
- Commit messages follow Conventional Commits: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, with an imperative summary under 72 characters.
- 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 delete, skip or loosen a test to make it pass. If a test is wrong, say why and ask before changing it.
- 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.

## Project-specific notes

- All new components, directives and pipes are standalone. Do not create NgModules.
- Use signals (`signal`, `computed`, `input()`, `output()`) for component state and inputs; reserve RxJS for streams such as HTTP and events.
- Use the built-in control flow (`@if`, `@for` with `track`, `@switch`) instead of `*ngIf` and `*ngFor`.
- Inject dependencies with `inject()` rather than constructor parameters in new code.
- Set `changeDetection: ChangeDetectionStrategy.OnPush` on new components.
- Generate new pieces with `ng generate` so file names, selectors and specs follow the project schematics.
- Unsubscribe automatically with `takeUntilDestroyed` or the `async` pipe; never leave manual subscriptions open.

## Project phase

This project is in active development. Follow the patterns that already exist; consistency beats novelty.
CLAUDE.mdFor Claude Code
# 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.mdFor Gemini CLI
# 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.
.github/copilot-instructions.mdFor GitHub Copilot
# Copilot instructions

Project: angular-app. An Angular application using standalone components and signals.

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: TypeScript, HTML and CSS
- Framework: Angular
- Hosting: Azure
- Tests: Vitest
- Package manager: npm

## Commands

- Install dependencies: `npm ci`
- Run locally: `npx ng serve`
- Build: `npx ng build`
- Run all tests: `npx ng test`
- Run one test file: `npx ng test --include src/app/path/file.spec.ts`
- Lint: `npx ng lint`
- Type-check: `npx tsc -p tsconfig.app.json --noEmit`
- Format: `npx prettier --write src`

## 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 delete, skip or loosen a test to make it pass. If a test is wrong, say why and ask before changing it.
- 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.
.cursor/rules/project.mdcFor Cursor
---
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.

About the Angular preset

What Is in the Angular AGENTS.md?

The preset describes a an Angular application using standalone components and signals. Its AGENTS.md is 47 non-empty lines with 8 exact commands, 4 key directories, and 7 stack-specific rules on top of the shared working rules.

  • Commands: npm ci, npx ng serve, npx ng build, npx ng test, npx ng test --include src/app/path/file.spec.ts, npx ng lint, npx tsc -p tsconfig.app.json --noEmit, npx prettier --write src.
  • Layout: src/app/, src/app/core/, src/app/shared/, src/environments/.
  • Wrappers: CLAUDE.md and GEMINI.md import AGENTS.md; the Copilot file repeats the essentials; the Cursor rule points to AGENTS.md.

Why These Rules for Angular?

Three generations of Angular in the data

Agents happily write NgModule-based code, structural directives and constructor injection because most Angular examples predate the modern APIs. Each rule names the old pattern and its replacement so the agent can recognize both.

Signals versus RxJS

Signals are simpler for synchronous component state, while RxJS still shines for async streams. Without a rule, agents wrap everything in BehaviorSubjects or convert everything to signals; the split here matches the Angular team guidance.

@for needs track

The new loop syntax requires a track expression. Agents that omit it get a compile error; agents that track by index get poor performance on reordering.

Leaked subscriptions

Manual subscriptions that outlive their component are the classic Angular memory leak. takeUntilDestroyed makes the cleanup automatic.

Which Stack Rules Does the File Add?

  • All new components, directives and pipes are standalone. Do not create NgModules.
  • Use signals (signal, computed, input(), output()) for component state and inputs; reserve RxJS for streams such as HTTP and events.
  • Use the built-in control flow (@if, @for with track, @switch) instead of *ngIf and *ngFor.
  • Inject dependencies with inject() rather than constructor parameters in new code.
  • Set changeDetection: ChangeDetectionStrategy.OnPush on new components.
  • Generate new pieces with ng generate so file names, selectors and specs follow the project schematics.
  • Unsubscribe automatically with takeUntilDestroyed or the async pipe; never leave manual subscriptions open.

How Do You Add These Files to a Angular Repository?

  1. Download the zip above. It is laid out exactly as the files go into the repository.
  2. Unzip it at the repository root. AGENTS.md, CLAUDE.md and GEMINI.md go next to your README; the Copilot file goes in .github/ and the Cursor rule in .cursor/rules/.
  3. Open AGENTS.md and check every command against your package scripts or Makefile.
  4. Delete wrappers for tools your team does not use, and any old .cursorrules or .windsurfrules file.
  5. Commit, then run the linter on AGENTS.md whenever you change it.

Want different commands or rules? Load this preset into the generator, change anything, and download your own set.

Which Agents Will Read These Files?

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.

Which Similar Stacks Are in the Library?

All presets are on the stacks page.

Frequently Asked Questions

Which Angular version does this target?

Any recent version with standalone components, signals and the built-in control flow as defaults. If your project is older, remove those rules until you migrate.

Is the test runner Karma or Vitest?

Newer Angular CLI projects can use Vitest; older ones use Karma with Jasmine. The ng test command works for both, so only the single-file command may need adjusting.

Should environments files hold API keys?

No. Environment files are compiled into the browser bundle, so anything in them is public. Keep secrets on your backend.

Are these Angular files free to use?

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.

How Can You Verify That Nothing Leaves This Browser?

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.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your input.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Switch between the file tabs, copy a file and download the zip.
  5. Look at the Network tab again. It is still empty. Downloads are built in the page as Blob URLs, so even the zip never touches a server. For extra proof, turn on offline mode after the page loads: everything keeps working.

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.

Was this helpful?