Choose by the behavior you need
Begin with a concrete job: define a first operation, inspect an approval boundary, render a data grid, retrieve knowledge safely or compose a feature. The minimal package exposes a user contract, feature, example entry and handler-oriented source. DataGridShowcase is the registry’s canonical table showcase. Other examples cover agent, integration, workflow and domain scenarios. Read the declared surfaces and prerequisites before choosing; a broad registry helps discovery, while a focused walkthrough should explain the important decisions and failure cases.
Use the catalog without loading every runtime
The examples module provides metadata-only catalog discovery and a separate runtime surface for rich template previews. Apps render specific examples through named host ports rather than directly importing example packages across the layer boundary. Rich UI is loaded only where the package exposes the appropriate surface. This separation makes a catalog card, source link, runtime fixture and interactive preview distinct deliverables. The 91 example-directory workspaces in the package inventory also include registry/shared/test support, so they are not 91 independently qualified product demos.
Adapt an evidence-bearing pattern
For each selected example, identify the exact contract, handler, adapter, data source and host behavior. List what remains supplied by the surrounding product: identity, persistence, provider credentials, authority, UI shell or background execution. Preserve useful negative cases such as invalid input, denied scope or missing provider. Source presence establishes an inspectable pattern; it does not establish public package installation, an executed fixture, a successful provider call or production readiness. Keep those evidence states visible when publishing an example page.
Follow a practical path.
Read the smallest complete slice
Open the example’s declared entry and feature, follow one operation into its handler, and identify the selected transport or UI. Compare its manifest to the actual available files before copying a capability claim.
Reproduce within the declared scope
Use the example package’s actual scripts and prerequisites from its package reference. Record the source/package versions and which checks ran. Keep external-provider and deployment qualification separate from local deterministic behavior.
Adapt one boundary at a time
Replace the fixture’s store, authority, provider or host with your intended implementation while retaining the contract behavior and relevant negative cases. Link the resulting product guide to the source pattern and state the additional dependencies you introduced.