Angular App taste — ChatGPT prompt: what it does, how to install
Angular App taste — a prompt for ChatGPT and Claude Code that enforces modern enterprise Angular architectural standards. Sets rules for standalone components, signals, and native control flow.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Angular App taste does
The prompt instructs the model to generate enterprise-grade Angular code using contemporary framework conventions. It mandates standalone components over NgModule, ChangeDetectionStrategy.OnPush or zoneless operation, and signal-based state management. RxJS remains reserved for asynchronous event streams and HTTP cancellation, while derived state relies on computed().
File structure is organized around feature folders rather than artifact types. Dependencies are resolved through the inject() function, templates use native control flow blocks (@if, @for with track, and @defer), and validation logic runs through typed reactive forms. Common network concerns like authentication headers and retries are delegated to functional HTTP interceptors.
Testing guidelines favor Angular Testing Library for components and Playwright for critical end-to-end flows, accompanied by strict bundle budgets in angular.json.
What it helps with
- enforce modern enterprise Angular architecture in generated code
- eliminate legacy NgModules from new application features
- transition component state management to signals and
computed() - standardize component and end-to-end tests with Playwright
Example prompts for the agent
- Design a user profile feature following the Angular App taste rules
- Create a checkout form using typed reactive forms and signals
How to install Angular App taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Angular App taste
How to install Angular App taste in Claude Code?
For Claude Code, save the prompt file to .claude/commands/prompts.csv.md. In ChatGPT, paste the text into custom instructions or directly into the chat session.
What does the Angular App taste prompt do?
It directs the model to write modern enterprise Angular code: dropping NgModule, utilizing signals, enforcing OnPush change detection, applying native control flow syntax, and moving logic to injectable services.
Which testing frameworks does the prompt recommend?
The prompt specifies Angular Testing Library for component-level tests and Playwright for critical end-to-end user flows.
Source text
prompts.csv · CC0-1.0
# Angular App taste of a frontend lead on large enterprise apps - Use standalone components everywhere and skip NgModules on new code. Confidence: 0.90 - Use signals for local and shared state, and keep RxJS for event streams, HTTP composition and cancellation. Confidence: 0.85 - Prefer `computed()` over manual subscriptions for derived state, and keep `effect()` for side effects only. Confidence: 0.80 - Set `ChangeDetectionStrategy.OnPush` on every component, or go zoneless on new apps. Confidence: 0.85 - Use the built-in control flow (`@if`, `@for` with `track`, `@switch`) instead of the old structural directives. Confidence: 0.90 - Lazy load every feature route with `loadComponent` or `loadChildren`, and use `@defer` blocks for heavy widgets below the fold. Confidence: 0.85 - Inject dependencies with the `inject()` function rather than long constructor parameter lists. Confidence: 0.75 - Use typed reactive forms; avoid template-driven forms for anything with validation logic. Confidence: 0.85 - Keep components thin: put data access and business logic in injectable services, and keep templates free of complex expressions. Confidence: 0.85 - Split components into smart containers and presentational components that talk through `input()` and `output()`. Confidence: 0.75 - Organize the code by feature folders, not by file type (all components, all services). Confidence: 0.80 - Reach for NgRx (Store or SignalStore) only when several features share complex state; services with signals cover most apps. Confidence: 0.70 - Handle auth headers, errors and retries in functional HTTP interceptors, not in each service call. Confidence: 0.85 - Never subscribe manually without cleanup; use the `async` pipe, `toSignal()` or `takeUntilDestroyed()`. Confidence: 0.90 - Turn on `strict` mode and strict template checking in `tsconfig.json`. Confidence: 0.90 - Use the Angular CLI and its esbuild-based builder, and keep `angular.json` customizations to a minimum. Confidence: 0.80 - Write component tests with Angular Testing Library, and cover critical user flows with Playwright end-to-end tests. Confidence: 0.75 - Enforce an initial bundle size budget in `angular.json` so the build fails when it is exceeded. Confidence: 0.80 - Use server-side rendering with hydration for public, SEO-relevant pages and keep internal dashboards client-only. Confidence: 0.70 - Upgrade with `ng update` one major version at a time, staying no more than one major behind. Confidence: 0.85 - Run ESLint with `angular-eslint` and format with Prettier in a pre-commit hook. Confidence: 0.80
© f · CC0-1.0 · f/prompts.chat