dev-create-injectable

Scaffolds Angular injectables with Signals and inject()-based dependency injection.

20|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/HerbertJulio/specialist-agent --skill dev-create-injectable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-create-injectable
Source: https://github.com/HerbertJulio/specialist-agent/tree/main/packs/angular/skills/dev-create-injectable
Command: npx skills add https://github.com/HerbertJulio/specialist-agent --skill dev-create-injectable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolding Angular injectables that embrace Signals and the inject() API to simplify stateful stores and lightweight utilities.

Core Features & Use Cases

  • Angular Injectable with Signals: Generates a ready-to-use Injectable with providedIn root (or component-scoped) and a signal-based internal state when required.
  • Inject-based Dependencies: Replaces constructor DI with inject() calls for dependencies, enabling tree-shakable, test-friendly code.
  • Guided Patterns: Distinguishes between Signal Store, Utility Service, and Data Orchestrator patterns, with examples and quick-start templates.
  • Use Case: Build a small UI state store that exposes a readonly signal and a few mutators in a clean service layer.

Quick Start

Create an Angular injectable following docs/ARCHITECTURE.md section 4.4.

Frequently Asked Questions about dev-create-injectable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why use the inject() API instead of constructor dependency injection in Angular?

The Angular inject() API replaces constructor dependency injection by allowing you to inject dependencies directly inside the property initialization. This enables tree-shakable, test-friendly code by removing the need for verbose constructor parameters.

What is the best way to structure a signal store in Angular?

The best way to structure a signal store in Angular is to use an Injectable pattern that exposes readonly signals for state alongside dedicated mutator methods. This clean service layer distinguishes between Signal Store, Utility Service, and Data Orchestrator patterns.

Can I use Angular Signals for component-scoped services?

Yes, you can use Angular Signals for component-scoped services by configuring the @Injectable decorator with component-level providers instead of providedIn: 'root'. This ties the signal-based internal state directly to the component lifecycle.

Does scaffolding an Angular Injectable require TypeScript?

Yes, scaffolding Angular injectables with Signals requires TypeScript to enforce type safety for WritableSignal definitions and the inject() API. This ensures appropriate public and readonly state exposure across the frontend application architecture.