angular-doctor
AGENTS.md1 starsChanged 6 days agoMITView on GitHub
You are an expert in TypeScript, Angular, and scalable web application development. You write functional, maintainable, performant, and accessible code following Angular and TypeScript best practices. Use the skills in this repo when the user asks or the task clearly fits.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- angular-developerSkill
- cavemanSkill
- find-animation-opportunitiesSkill
- frontend-designSkill
- grillingSkill
- grill-meSkill
- impeccableSkill
- improve-animationsSkill
- ui-tasteSkill
- web-design-guidelinesSkill
- angular-doctorSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
37 rules. About 0 are common, 16 are distinctive, and 21 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
21
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Do NOT verify visual or interactive work with headless Chrome, browser screenshots, --screenshot, CDP/Remote Debugging, or browser …
- Very specific: line 6
Do NOT start any server (docs:dev, docs:preview, node …/index.mjs, ng serve, or similar) unless the user explicitly asks.
- Distinctive: line 7
Verify with builds, typechecks, unit/integration tests, and non-browser CLI output only.
- Distinctive: line 12
Use the skills in this repo when the user asks or the task clearly fits.
- Distinctive: line 18
Out of scope: Do not apply caveman voice to persisted text (commits, PR bodies, generated docs) unless the user wants that.
- Distinctive: line 23
What: Run a relentless interview: challenge assumptions, edge cases, failure modes, and missing requirements.
- Very specific: line 28
angular-doctor: After Angular edits, follow skills/angular-doctor/SKILL.md (or run the CLI skill install). - Distinctive: line 32
Use strict type checking
- Distinctive: line 33
Prefer type inference when the type is obvious
- Very specific: line 34
Avoid the any type; use unknown when type is uncertain
- Distinctive: line 38
Always use standalone components over NgModules
- Very specific: line 39
Must NOT set standalone: true inside Angular decorators.
- Very specific: line 40
Do NOT set changeDetection: ChangeDetectionStrategy.OnPush explicitly.
- Distinctive: line 41
Use signals for state management
- Very specific: line 43
Do NOT use the @HostBinding and @HostListener decorators.
- Very specific: line 44
Use NgOptimizedImage for all static images.
- Distinctive: line 54
Keep components small and focused on a single responsibility
- Very specific: line 55
Use input() and output() functions instead of decorators
- Very specific: line 56
Use model() for two-way bound properties with [(prop)] syntax instead of pairing input() with output()
- Very specific: line 57
Use computed() for derived state
- Very specific: line 58
Use linkedSignal() for state derived from multiple reactive sources that must stay synchronized
- Distinctive: line 59
Prefer inline templates for small components
- Very specific: line 60
Prefer Signal Forms (@angular/forms/signals) for new forms.
- Distinctive: line 61
When not using Signal Forms, prefer Reactive forms instead of Template-driven ones
- Very specific: line 62
Do NOT use ngClass, use class bindings instead
- Very specific: line 64
Do NOT import CommonModule, import only the directives and pipes the template uses, such as AsyncPipe or DatePipe
- Distinctive: line 65
When using external templates/styles, use paths relative to the component TS file.
- Distinctive: line 69
Use signals for local component state
- Distinctive: line 71
Keep state transformations pure and predictable
- Very specific: line 72
Do NOT use mutate on signals, use update or set instead
- Distinctive: line 76
Keep templates simple and avoid complex logic
- Very specific: line 77
Use native control flow (@if, @for, @switch) instead of *ngIf, *ngFor, *ngSwitch
- Distinctive: line 78
Use the async pipe to handle observables
- Very specific: line 79
Do not assume globals like (new Date()) are available.
- Very specific: line 84
Use the providedIn: 'root' option for singleton services
- Very specific: line 85
Prefer the @Service decorator over @Injectable({providedIn: 'root'}) for new singleton services (Angular v22+)
- Very specific: line 86
Use the inject() function instead of constructor injection
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are an expert in TypeScript, Angular, and scalable web application development. You write functional, maintainable, performant, and accessible code following Angular and TypeScript best practices.
Verification Boundaries
- Do NOT verify visual or interactive work with headless Chrome, browser screenshots,
--screenshot, CDP/Remote Debugging, or browser automation unless the user explicitly asks for browser verification in that turn. - Do NOT start any server (
docs:dev,docs:preview,node …/index.mjs,ng serve, or similar) unless the user explicitly asks. The user already runs the docs server for this repo and verifies manually. - Verify with builds, typechecks, unit/integration tests, and non-browser CLI output only. If a visual check the user asked for cannot run without a server, say so in one line instead of starting one.
- These boundaries apply to all agent sessions in this repo (Muse, Claude Code, Codex, Cursor, and any other tool that reads this file). They stay until the user lifts them in-session.
Project agent skills
Use the skills in this repo when the user asks or the task clearly fits.
caveman (.agents/skills/caveman/SKILL.md)
- When: The user says
/caveman, "caveman mode", "be brief", "less tokens", or similar. - What: Terse, answer-first replies. Keep every technical fact, path, command, and code change exact. Stay in caveman voice until the user says "stop caveman" or "normal mode".
- Out of scope: Do not apply caveman voice to persisted text (commits, PR bodies, generated docs) unless the user wants that.
grill-me (.agents/skills/grill-me/SKILL.md)
- When: The user says
/grill-me, "grill me", "interview this plan", or wants a design or plan stress-tested before implementation. - What: Run a relentless interview: challenge assumptions, edge cases, failure modes, and missing requirements. Do not start large implementation until the user confirms the sharpened plan (unless they say to proceed anyway).
Other skills
angular-developer:.agents/skills/angular-developer/SKILL.mdis the source of truth for Angular conventions in this repo.angular-doctor: After Angular edits, followskills/angular-doctor/SKILL.md(or run the CLI skill install).
TypeScript Best Practices
- Use strict type checking
- Prefer type inference when the type is obvious
- Avoid the
anytype; useunknownwhen type is uncertain
Angular Best Practices
- Always use standalone components over NgModules
- Must NOT set
standalone: trueinside Angular decorators. It's the default in Angular v20+. - Do NOT set
changeDetection: ChangeDetectionStrategy.OnPushexplicitly.OnPushis the default in Angular v22+. - Use signals for state management
- Implement lazy loading for feature routes
- Do NOT use the
@HostBindingand@HostListenerdecorators. Put host bindings inside thehostobject of the@Componentor@Directivedecorator instead - Use
NgOptimizedImagefor all static images.NgOptimizedImagedoes not work for inline base64 images.
Accessibility Requirements
- It MUST pass all AXE checks.
- It MUST follow all WCAG AA minimums, including focus management, color contrast, and ARIA attributes.
Components
- Keep components small and focused on a single responsibility
- Use
input()andoutput()functions instead of decorators - Use
model()for two-way bound properties with[(prop)]syntax instead of pairinginput()withoutput() - Use
computed()for derived state - Use
linkedSignal()for state derived from multiple reactive sources that must stay synchronized - Prefer inline templates for small components
- Prefer Signal Forms (
@angular/forms/signals) for new forms. They are stable in Angular v22+ and provide signal-based state, type-safe field access, and schema-based validation - When not using Signal Forms, prefer Reactive forms instead of Template-driven ones
- Do NOT use
ngClass, useclassbindings instead - Do NOT use
ngStyle, usestylebindings instead - Do NOT import
CommonModule, import only the directives and pipes the template uses, such asAsyncPipeorDatePipe - When using external templates/styles, use paths relative to the component TS file.
State Management
- Use signals for local component state
- Use
computed()for derived state - Keep state transformations pure and predictable
- Do NOT use
mutateon signals, useupdateorsetinstead
Templates
- Keep templates simple and avoid complex logic
- Use native control flow (
@if,@for,@switch) instead of*ngIf,*ngFor,*ngSwitch - Use the async pipe to handle observables
- Do not assume globals like (
new Date()) are available.
Services
- Design services around a single responsibility
- Use the
providedIn: 'root'option for singleton services - Prefer the
@Servicedecorator over@Injectable({providedIn: 'root'})for new singleton services (Angular v22+) - Use the
inject()function instead of constructor injection
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

