Automated summary

Generates NgRx Signal Stores that follow a specific Angular workspace's conventions (entities, loading flags, rxMethod/tapResponse, notifications).

Strengths

Enforces a precise, repeatable store structure instead of ad-hoc state code
Keeps collections in withEntities and scalar values or flags in withState
Wraps async calls with rxMethod plus tapResponse and a consistent loading flag
Ships a complete, directly reusable TypeScript example

Limitations

Assumes NgRx Signals, NotificationService and API services already exist in the workspace
Defers the root vs component scope decision to a separate state-management skill
Does not cover store testing, optimistic updates or retry strategies

When to use it

Use it when you ask the agent to create or extend a state management store for a feature in this Angular workspace.

When not to use it

Skip it if the project doesn't use NgRx Signal Store, or if you only need to decide where the store should live rather than author it.

Security analysis

Safe

Quality score85/100

This is a pure documentation/instruction skill for Angular state management. It contains no executable commands, no shell invocations, no network calls, no file deletion, and no secret handling. The only actions described are writing TypeScript code and using framework APIs (NgRx Signal Store, RxJS, an injected NotificationService). There is no meaningful execution risk in listing it.

No concerns found

How this analysis is made

Examples

Create a feature store

Create a store for the products feature that loads the product list on init, tracks loading, and shows success and error notifications.

Add an action to an existing store

Add an addToCart action to the CartStore using rxMethod and keep the loading flag in sync.

Entities collection store

Create a component-scoped signal store for orders using withEntities<Order>() with a method to refresh orders from the API.

name: create-signal-store description: Use when the user asks to add state management or create a store for a feature in this Angular workspace.

Creating a Signal Store

Name: Create a Signal Store
Author: Skills Guide Bot

In this workspace we manage state exclusively with the NgRx Signal Store. When asked to create a store, follow these rules:

Create the store with signalStore from @ngrx/signals.
Decide providedIn: 'root' vs. component-provided scope using the placement test in the state-management skill — don't default to root.
Keep collections with withEntities<T>(); keep flags and scalar values with withState({ ... }).
Implement every asynchronous action as an rxMethod and wrap the HTTP call in tapResponse. Track loading with a loading flag kept in withState({ loading: false }): set it to true before the call in a leading tap, and back to false when the data arrives.
On success, patch the state AND show a success notification through the injected NotificationService. On error, show an error notification.
Inject services through default parameters of the withMethods factory.
If the store should load its data immediately, call the load method from a withHooks({ onInit }) hook.

Example

export const DogsStore = signalStore(
  { providedIn: 'root' },
  withEntities<Dog>(),
  withState({ loading: false }),
  withMethods(
    (
      store,
      notificationService = inject(NotificationService),
      dogsApiService = inject(DogsApiService),
    ) => ({
      loadDogs: rxMethod<void>(
        pipe(
          tap(() => patchState(store, { loading: true })),
          exhaustMap(() =>
            dogsApiService.getDogs().pipe(
              tapResponse({
                next: (dogs) => {
                  patchState(store, setAllEntities(dogs), { loading: false });
                  notificationService.showSuccess('Dogs Loaded');
                },
                error: () => notificationService.showError(),
              }),
            ),
          ),
        ),
      ),
    }),
  ),
  withHooks({
    onInit(store) {
      store.loadDogs();
    },
  }),
);

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-a-signal-store-mrx3y03x' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-a-signal-store-mrx3y03x/download' --output '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md.part' && mv '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md.part' '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md' && test -s '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/create-signal-store' && cp -R '.skill-downloads/create-a-signal-store-mrx3y03x' '.claude/skills/create-signal-store'

Cursor

test -f '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md' && test -s '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/create-signal-store' && cp -R '.skill-downloads/create-a-signal-store-mrx3y03x' '.cursor/skills/create-signal-store'

Codex

test -f '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md' && test -s '.skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/create-signal-store' && cp -R '.skill-downloads/create-a-signal-store-mrx3y03x' '.agents/skills/create-signal-store'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/create-a-signal-store-mrx3y03x'

openskills read 'create-a-signal-store-mrx3y03x'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-a-signal-store-mrx3y03x/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623

Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981

Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015

Skills Guide Bot

Create a Signal Store

Recommended for

Automated summary

Strengths

Limitations

Security analysis

Examples

name: create-signal-store description: Use when the user asks to add state management or create a store for a feature in this Angular workspace.

Creating a Signal Store

Example

From the file to a first result

1. Download the file

2. Check prerequisites

3. Load the skill

4. Try a first task

React Hook Form Best Practices

Emotion to Mantine Migration

Scope Creep Detector