Learning From Exemplar Repos

The most reliable way to write idiomatic code in a framework is to study a real repo that already does it well, then follow its patterns. Fresh docs (via Context7) tell you the API surface; an exemplar repo shows you how a strong team actually structures, composes, and wires it in practice. Use both.

When to reach for an exemplar

Check for an internal precedent first. If this codebase already does the thing well somewhere, that local code is your exemplar: read those files and match them. Reach for an external repo only when there is no local precedent to follow.

External exemplars are for:

• A fresh project, or a framework the codebase does not use yet, where the "right" structure is not obvious (routing, data loading, server functions, effect composition).
• Going for a specific design or UX style: find an open-source product whose look and interaction you want to approximate.
• Adopting a pattern the codebase does not yet have an internal precedent for.

How to use one