janpereira-dev/ngautopilot/angular-signals-signals-rxjs-interop

Claude Code and agent skill by janpereira-dev/ngautopilot

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Reviews the boundary between Angular Signals and RxJS, focusing on toSignal, toObservable, cancellation, async orchestration, and version-safe interop patterns.

Install

npx vskill@latest install janpereira-dev/ngautopilot/angular-signals-signals-rxjs-interop

SKILL.md

The same SKILL.md was published earlier as janpereira-dev/ngautopilot/angular-signals-signals-rxjs-interop.

Angular Signals RxJS Interop

Purpose

Use this skill to define the boundary between Angular Signals and RxJS.

Interop should be deliberate. RxJS remains the right tool for async orchestration, cancellation, and stream composition, while Signals are best for synchronous local state and derived UI values.

The core rule is simple:

txt
Convert at the boundary, not everywhere.

When to Use

Use this skill when:

  • an Observable needs to feed a signal-driven component
  • a signal must be exposed to Observable consumers
  • HTTP or router streams meet local UI state
  • async orchestration and local derivation need a clean boundary

Do

Convert streams at clear boundaries:

ts
readonly user = toSignal(this.user$, { initialValue: null });
readonly filter$ = toObservable(this.filter);

Keep async work in RxJS:

ts
readonly results$ = this.search$.pipe(
debounceTime(300),
switchMap((query) => this.api.search(query)),
);

Use Signals for local consumption after the conversion boundary.

Do Not

Avoid converting every Observable into a Signal.

Avoid using Signals to replace cancellation-heavy async flows.

Avoid creating interop loops without a clear ownership model.

Avoid using experimental APIs as a default unless the project has explicitly accepted them.

Review Checklist

  • [ ] The interop boundary is explicit.
  • [ ] RxJS still owns async orchestration.
  • [ ] Signals still own local derived state.
  • [ ] Conversion is not overused.
  • [ ] The Angular version supports the APIs being used.

Expected Output

  1. Identify where interop is actually needed.
  2. Define the conversion boundary.
  3. Preserve RxJS for async workflows.
  4. Preserve Signals for local synchronous state.
  5. Explain why the conversion belongs where it does.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
4
Repository forks
1
7-day trend score
13

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/janpereira-dev/ngautopilot/angular-signals-signals-rxjs-interop/badge)](https://verified-skill.com/skills/janpereira-dev/ngautopilot/angular-signals-signals-rxjs-interop)

Something wrong with this skill or its page? Tell us.