Coordinate Components

by dotnet

Coordinate Components is a Frontend skill for Claude Code, published by dotnet in skills.

5.2K stars384 forkson dotnet/skillsAdded 2026/08/16Repository updated 2026/08/15

View source on GitHub Download repo ZIP

agent-skills

Install in seconds

Install Coordinate Components

Copy Coordinate Components into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/dotnet/skills/tree/main/plugins/dotnet-blazor/skills/coordinate-components ~/.claude/skills/coordinate-components

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/dotnet/skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: plugins/dotnet-blazor/skills/coordinate-components/SKILL.md in dotnet/skills
Installs to: ~/.claude/skills/coordinate-components
Collection: One of 25 skills cataloged from this repository
Category: Frontend — 567 skills

What Coordinate Components does

Coordinate Components shares state between Blazor components without a direct parent-child relationship, using cascading values, scoped services, or CascadingValueSource. Use it for cascading values across render mode boundaries or app-wide shared data.

Coordinate Components is cataloged under Frontend on DirSkills. Coordinate Components comes from a repository tagged agent-skills.

Documentation

README

Excerpt

Coordinate Components

Step 1 — Read AGENTS.md

Read AGENTS.md at the workspace root to learn the project's conventions before making changes.

Step 2 — Decide the scope

Need	Mechanism	When to use
Subtree (same render mode)	`CascadingValue` component	Theme, layout config within a layout
App-wide (all render modes)	`CascadingValueSource<T>` via DI	Current user, feature flags, theme shared globally
Mutable shared state within a circuit	Scoped service + `Action` event	Shopping cart, notification count, selected filters

For parent→child one level: use [Parameter] / EventCallback (see author-component skill). For persisting state across prerender→interactive: see support-prerendering skill.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Coordinate Components

What else does dotnet publish alongside Coordinate Components?
Coordinate Components is one of 25 skills that DirSkills catalogs from dotnet/skills, the repository it ships in. Its siblings there include .NET P/Invoke, ASP.NET Core Web API and Agentic Workflows. Each one is a separate skill with its own page in this directory, installs the same way Coordinate Components does, and is maintained by dotnet in that same repository. The rest of the collection is listed on the dotnet/skills page.
How does Coordinate Components compare to other Frontend skills?
Coordinate Components ranks #152 by stars among the 567 Frontend skills in this catalog. The most-starred ones next to it are Angular Developer, Android Clean Architecture and Accessibility. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Coordinate Components against them. Open each page to compare what they document and how they install.