agentsclimarketplace
Sign in

Dec rendering architecture

Skill jpoindexter/design-engineering-canon/skills/dec-rendering-architecture

Frontend rendering and state architecture — CSR/SSR/SSG/ISR/streaming SSR/RSC chosen per route, state colocation and derived state, server-state vs client-state, Suspense and Error Boundaries as first-class. Use when choosing a rendering strategy, structuring component state, deciding what's server vs client, or designing loading/failure states.From its SKILL.md

Install
npx -y skills add jpoindexter/design-engineering-canon --skill dec-rendering-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 264 tokens by cl100k_base, as published. Nobody here has run it

Rendering & Architecture

Where work happens (server vs client) and where state lives are the two highest-leverage frontend decisions.

  • Rendering Strategies: CSR, SSR, SSG, ISR, streaming SSR, and React Server Components — chosen per route by data freshness and interactivity needs. Static content → SSG/ISR; personalized/fresh → SSR/streaming; highly interactive → client islands.
  • State Colocation & Derived State: Keep state as close to where it's used as possible; derive rather than duplicate. Server state (cache of remote data) vs client state (UI) are different problems with different tools — don't conflate them.
  • Suspense & Error Boundaries: Declarative loading and failure states as first-class architecture, not afterthoughts bolted on later.

How to apply

  • Decide rendering route-by-route, not app-wide — match the strategy to each route's freshness/interactivity.
  • Lift state only as high as it's actually shared; duplicated state is a bug — derive it.
  • Use a server-cache library for remote data; reserve local state for genuine UI concerns.
  • Wrap async boundaries in Suspense + Error Boundary so loading and failure are designed, not accidental.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.