Agent skill

Angular Style Guide

Naming conventions, file structure, and coding standards for Angular projects.

View SKILL.md on GitHub Repository
Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/style-guide-hoangnguyen0403-agent-skills-standar

Metadata

Additional technical details for this skill

labels
angular style naming structure
triggers 
{
    "files": [
        "**/*.ts"
    ],
    "keywords": [
        "angular style",
        "naming convention",
        "file structure"
    ]
}

SKILL.md

Angular Style Guide

Priority: P0 (CRITICAL)

Principles

  • Single Responsibility: One component/service per file. Small functions (< 75 lines).
  • Size Limits: Keep files under 400 lines. Refactor if larger.
  • Strict Naming: feature.type.ts (e.g., hero-list.component.ts).
  • Barrels: Use index.ts only for public APIs of specific features/libraries. Avoid deep barrel imports within the same feature.
  • LIFT: Locate, Identify, Flat structure, Try DRY.

Naming Standards

  • Files: kebab-case.type.ts
  • Classes: PascalCase + Type suffix (HeroListComponent)
  • Directives: camelCase selector (appHighlight)
  • Pipes: camelCase name (truncate)
  • Services: PascalCase + Service suffix (HeroService)

Anti-Patterns

  • Logic in Templates: Move complex logic to the component class or a computed signal.
  • Deep Nesting: Avoid $>3$ levels of folder nesting.
  • Prefixing interfaces: No IUser. Use User.

References

  • Naming Conventions

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

majiayu000/claude-skill-registry

agent-ops-spec

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-state

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-spec

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-testing

Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-testing

Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-state

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

163 31
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results