component-architecture skillA
component-architecture is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Decide where a component's boundaries go, where state lives, what its props should be, and whether to split it — using composition instead of configuration flags. Fires when adding a component to an existing tree, when a component has grown props or responsibilities, or when a review asks whether a structure will hold. Not for visual design decisions, not for styling systems, and not a licence to restructure code the task did not ask you to touch..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Component architecture Structure is decided by where change arrives, not by file length. A 300-line component with one reason to change is fine; a 40-line one that both fetches and renders is not. ## When this fires Adding a component to an existing tree, changing one whose props or responsibilities have grown, or reviewing whether a proposed structure will survive the next feature. It does not fire for styling-only edits or for copy changes. ## Procedure 1. **Read the neighbours before designing.** Open two or three components in the same directory. The project has already answered most of these questions — prop naming, where data is fetched, whether state lives in a store or in the tree. Matching an existing pattern beats importing a better one into one file. 2. **State the component's one responsibility in a sentence.** If the sentence needs "and", you have either two components or one component with a helper. Write the sentence down; it is the boundary. 3. **Place each piece of state at the lowest node that reads it.** Then move it up only when a second reader actually appears — not when you predict one. State owned above where it is read …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/component-architecture@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/component-architecture@sha256:cb88a47e8f2379d3Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_hi7sgqtzze2ieqlc)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5652 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hi7sgqtzze2ieqlc GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/component-architecture GET https://markdownregistry.com/api/v1/blob/cb88a47e8f2379d3b316c1b8df5258fb335a1adbb497e09fad1ade44ba72c23a
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher