Agent prompts

Copyable prompts for agents

Replace bracketed task descriptions with the actual scope. These prompts point agents at v1.1.0 while preserving the consuming project's authority. Update the entire pin deliberately when upgrading.

Build a Vue screen with package components

Implement [the project settings screen] using j3w1/theme v1.1.0, approved
default profile. Inspect and follow this repository's own instructions and
existing Vue 3 JavaScript architecture first.

Read:
https://raw.githubusercontent.com/j3w1/theme/v1.1.0/agents/consume.md
Discover implementations through:
https://raw.githubusercontent.com/j3w1/theme/v1.1.0/packages/ui/dist/index.json

Install @j3w1/ui from:
https://github.com/j3w1/theme/releases/download/v1.1.0/j3w1-ui-1.1.0.tgz
Use the installed CLI to prepare a package kit for the selected components.
Start by evaluating text-field, select, button and dialog; adjust the IDs
to the actual screen requirements.

Use maintained markup, matching token/style/registration imports, and Vue's
j3w1-* Custom Elements compiler configuration. Keep Vue bindings on native
inputs when Vue owns their values. Use documented properties and events for
custom behavior, and themed choices instead of native popup menus.

Preserve this app's backend, authentication, authorization and domain rules.
Do not infer a backend from the demo. Read only relevant pinned contracts,
examples and dependencies; do not scrape the site or infer colors from images.

Record canonical revision, package identity, pending decisions and deviations.
Verify required validation, FormData, reset, disabled state, keyboard selection,
dialog Escape/focus return and narrow layout in this app. Report actual checks
and anything unavailable. Complete the integration, not just a plan or snippet.

Incorporate complete copies

Build [the requested interface] using complete j3w1/theme v1.1.0 copy bundles.
Follow this repository's instructions first. Read the pinned consumer protocol
and implementation index. Install the published archive, then run:

npx --no-install j3w1-ui kit --components text-field,button,dialog --mode copy --framework vue --out ./j3w1-copy-task

Adapt selected IDs/framework to the authorized task. Choose a new output
directory if it already exists. Preserve each bundle's complete runtime,
CSS, token sheet, manifest and notices. Do not flatten colliding filenames.
Incorporate maintained markup with unique IDs and matching ARIA/label references.
Keep copied-source changes reviewable and record upstream identity.
Use approved semantic roles, keep the app's behavior, and verify real forms,
keyboard, focus, responsive layout and lifecycle after integration.

The CLI's framework flag supplies guidance, not automatic conversion into Vue SFCs. The agent still incorporates the code. See Package and copy.

Theme an existing framework or native host

Apply j3w1/theme v1.1.0 to [the named surfaces] in this application.
Follow this project's instructions and supported theming API. Read the pinned
agents/consume.md, compact rules and relevant component contracts.
Use mapping mode if the host cannot consume the official web components.

Map semantic roles to supported host keys. Preserve existing behavior,
keybindings, unrelated settings and accessibility features. Document unsupported,
inherited and out-of-scope surfaces. Do not create colors or silently approximate
a blocked role. Record the canonical lock, pending decisions, deviations,
install/rollback instructions and actual checks. A parsed file alone is not
evidence of a successful import into the host application.

Upgrade a consumer

Upgrade this app's pinned j3w1 integration to v1.1.0. Identify its current
package/copy/mapping mode, revision, lockfiles and deviations first. Read the
target release notes, True Black / Rose migration and changed contracts.
Review the new artifact in a clean fixture before changing the integration.

Preserve app-owned customizations and behavior. Update the package or complete
copy closure, canonical lock and integration record together. Check labels,
form values, reset, disabled/read-only states, themed choices, focus, contrast
on actual surfaces and responsive layout. Report deviations and actual checks;
do not infer compatibility solely from the version number.

Short everyday prompt

Once the repository records its pin and protocol:

Implement this interface with the repository's pinned j3w1/theme integration. Reuse its official components, preserve application behavior, and verify the resulting screen.

Next: Agent integration · Versioning.