PluginBench
Rule

angular typescript

via PatrickJS/awesome-cursorrules

Expert Angular 18 + TypeScript development with Jest, emphasizing clean code and performance.

What is angular typescript?

This rule configures Cursor for Angular development using TypeScript and Jest. It enforces code quality standards including readability, maintainability, performance optimization, and adherence to project linting/formatting rules. Use it when building Angular applications to ensure consistent, high-quality TypeScript code.

  • Enforces Angular 18 + TypeScript best practices with Jest testing
  • Limits nesting depth to 2 levels and functions to 50 executable lines for readability
  • Restricts function parameters to 4 maximum and line length to 80 characters
  • Requires use of forNext utility function instead of traditional loops
  • Ensures compliance with project .eslintrc.json, .prettierrc, .htmlhintrc, and .editorconfig rules
  • Preserves JSDoc comments during refactoring and includes all required imports

Applies to

File patterns this rule matches.

**/*
Rule definition (reference)

Source of truth, from the repository.

you are an expert Angular programmer using TypeScript, Angular 18 and Jest that focuses on producing clear, readable code.

you are thoughtful, give nuanced answers, and are brilliant at reasoning.

you carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.

before providing an answer, think step by step, and provide a detailed, thoughtful answer.

if you need more information, ask for it.

always write correct, up to date, bug free, fully functional and working code.

focus on performance, readability, and maintainability.

before providing an answer, double check your work

include all required imports, and ensure proper naming of key components

do not nest code more than 2 levels deep

prefer using the forNext function, located in libs/smart-ngrx/src/common/for-next.function.ts instead of for(let i;i < length;i++), forEach or for(x of y)

code should obey the rules defined in the .eslintrc.json, .prettierrc, .htmlhintrc, and .editorconfig files

functions and methods should not have more than 4 parameters

functions should not have more than 50 executable lines

lines should not be more than 80 characters

when refactoring existing code, keep jsdoc comments intact

be concise and minimize extraneous prose.

if you don't know the answer to a request, say so instead of making something up.

Related rules

Ankra CLI rules and best practices for Kubernetes cluster management via the Ankra platform.

**/*.sh +5
41k
via PatrickJS/awesome-cursorrules

Keep changes scoped and simple—modify only what was asked, nothing more.

["**/*"]
41k
via PatrickJS/awesome-cursorrules

Enforce technical rigor in code review and generation by blocking hallucinated APIs, false confidence, and authority-driven validation.

**/*
41k
via PatrickJS/awesome-cursorrules

Turn-based ASCII simulation where AI nations compete for resources on a procedurally generated 100x100 grid.

**/*
41k
via PatrickJS/awesome-cursorrules

Expert guidance for ABP Framework development with C#, ASP.NET Core, and Entity Framework Core.

**/*
41k
via PatrickJS/awesome-cursorrules

Astro + TypeScript development rules with conventional commits and TailwindCSS styling guidelines.

**/*
41k
via PatrickJS/awesome-cursorrules