J3W1 / DESIGN SYSTEM
Build with an agent
Give your agent a pinned contract and a complete implementation. The primary workflow is discovering, consuming and verifying exact j3w1 artifacts inside another application.
Prepare an agent kit
Select the components your task needs. The installed CLI includes their complete dependency closure, canonical contracts, eligibility disclosures and shared rules.
j3w1-ui kit --components text-field,button,dialog --out ./vendor/j3w1/taskA bounded consumption workflow
- Pin one release, currently
1.1.0, and record the artifact digest. - Read the canonical consumption contract and compact implementation index.
- Select component IDs. Read only their canonical JSON, implementation contract and maintained examples, plus shared accessibility and eligibility rules.
- Prefer package mode in compatible web apps. Use complete copy bundles when source ownership is needed. Use the existing mapping workflow for incompatible/native hosts.
- Integrate the native markup, CSS and registration closure; bind your application data and actions.
- Verify your real form, keyboard, focus and lifecycle behavior. Record actual results separately from implementation availability.
Prepare a copy task
j3w1-ui kit --components text-field,button,dialog --out ./vendor/j3w1/taskUse the installed binary from the exact package or release tarball. The output contains all selected component closures and refuses to overwrite application files. Full installation and framework guide →
Machine entry points
| Need | Artifact |
|---|---|
| Small discovery request | ui/index.json |
| One implementation/API | ui/contracts/<id>.json |
| Maintained native markup | ui/examples/<id>.json |
| Complete copy files and digests | ui/copy/<id>/manifest.json |
| Canonical meaning and eligibility | exports/components/<id>.json |
| All implementation metadata | ui/manifest.json |
Site URLs help humans explore the current release. For reproducible agent fetches, use the matching immutable release tag and its published digests. Never combine current-site examples with a different installed version.
Mapping compatibility
The existing canonical task kit, lock format and portability disclosures remain available. An official package dependency is recorded alongside that integration evidence; it does not pretend to be a newly verified native port.