rxjs-like-a-pro
RxJS Like a Pro
This skill helps you write RxJS code that is idiomatic, composable, and free of common pitfalls. The core
philosophy: keep logic in the observable chain. Every time you reach for .subscribe(), ask whether the
work could instead be expressed as a transformation inside .pipe().
Reference files
For detailed examples and patterns, read the relevant reference file:
references/loading-state-patterns.md— Deriving loading/error state in the chain, thewithLoadingStatecustom operator, and usingscanto preserve previous results across loading states. Read when working with async data fetching that needs loading indicators.references/massive-observable.md— How to refactor bloatednew Observable()constructors into small focused pieces. Read when you see anew Observablecallback longer than ~10 lines.references/inner-observable-chains.md— Building rich inner observable sequences with timing, delays, and animation phases. Read when composing multi-step async sequences or replacingsetTimeoutpatterns.references/custom-operators.md— How to write inline and extracted custom operators withOperatorFunction. Read when extracting reusable stream logic.
More from sanity-io/sanity
playwright-best-practices
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
10grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
8find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
8playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
7write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
7improve-codebase-architecture
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
7