React Rsc

About development MCP servers and Claude skills

development MCP servers extend what AI agents can do inside Claude Code, Cursor, Copilot, Codex, and Windsurf. The Skiln directory indexes 16,000+ such integrations across 22 categories.

React Rsc is one of hundreds of development entries indexed on Skiln. Browse the full development category or the complete directory of Claude skills, MCP servers, agents, commands, and hooks.

Related development MCPs and skills

• Status Update Generator by borghei

  Generate weekly executive status updates from Jira/Linear data exports. Produces a structured "highlights / blockers / risks / asks / what's next" briefing in markdown, Confluence, Notion, Linear, JSON, or Mermaid.

• Story Mapping by borghei

  Jeff Patton-style user story mapping for visualizing user journeys and translating product strategy into prioritized, deliverable work. Use for release planning, MVP definition, backlog sequencing, and cross-team alignment on what to build and in what order.

• Service Mesh Expert by aiskillstore

  Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con

• 1692 Code Guide 23e43f0c by tools-only

  Universal principles for writing maintainable code. Stack-specific details should live in project CLAUDE.md files.

• 1699 Agent Operating Manual Daa8c0c5 by tools-only

  **When to plan**: New features touching multiple files, refactoring with unclear scope, architecture changes, bug fixes with unclear root cause. **Interview first**: Before non-trivial tasks, use `AskUserQuestion` iteratively. For complex tasks, up to 40 questions across multiple rounds. **Workflow**: 1. Interview the user thoroughly 2. Check existing ADRs in `.meridian/adrs/` for relevant architectural decisions 3. Research the codebase (direct tools or Explore agents) 4. Follow the `/planni...

• 1704 Story A73684d4 by tools-only

  I was building AI agents for automated testing - Helena for frontend QA, Victor for backend verification. They worked great... until they didn't. **The same mistakes kept happening:** - Helena would use `sleep(5000)` for waits, causing flaky tests - Victor would forget that the API uses JWT with 24-hour expiry - Both agents would repeat failed strategies session after session Every conversation started fresh. No memory. No learning. Just an expensive LLM making the same mistakes I'd a

• 1712 Weboptimizer 9de1c683 by tools-only

  Establish performance benchmarks and optimize Next.js + FastAPI apps

• 1722 Doc Quality 9caf90ff by tools-only

  A well-documented module tells the reader four things: what it does, when to use it, how to use it, and how to configure it.

Frequently asked questions