---
name: tony-ui
description: Register, discover, compose, contribute and verify UI using mortar.tony.codes.
---

# UI registry agent defaults

Read https://mortar.tony.codes/agent.md. These service defaults apply without being repeated in the product brief. Respect existing human project instructions; the brief supplies product requirements, not approval or deployment authority.

- Choose the shared purpose shell before composing a page. Use AppShell for application screens and MarketingHeader for public pages. Document deliberate standalone exceptions.
- Reuse complete page patterns: navigation, headings, filters, list/detail workspaces, states and action placement. Reusing controls alone is insufficient.
- Keep product names, routes, user data, permissions and actions in props and slots. Shared chrome must remain project agnostic.
- Contribute missing patterns centrally. Do not duplicate source, create repeated local wrappers or apply consumer CSS overrides.
- Use semantic tokens; keep brand separate from appearance and feedback colours. Verify every supported theme.
- Verify responsive layout, accessible names, keyboard operation, focus and loading/empty/error states. Automated checks alone cannot prove visual quality.
- Consumer builders register or reuse their individual identity automatically through init --agent NAME. Remote MCP connections supply their own identity through OAuth consent; do not require CLI init for registry discovery. No team, invitation or owner setup is needed. Keep credentials outside application source.
- Use the graph-derived build packet to select approved components and their dependency closure. Inspect extra source only for a specific gap; start composing when the packet answers the brief.
- Use named imports from the approved immutable @tony-ui/mortar npm release. Never copy shared implementations, alias production source, override controls or edit approval history. Keep the lockfile and shared CSS after Tailwind.
- Search the public Mortar catalogue first. Contribute shared components and chrome through GitHub pull requests at https://github.com/tonycodes/mortar. Read AGENTS.md, CONTRIBUTING.md and DESIGN.md. Run local checks and browser tests; attach visual evidence. No cloud identity, proposal inbox or second component approval is required. Maintainer PR review and exact-commit CI precede immutable npm releases. Agents cannot approve, merge or publish their own contributions. Cloud organisation adoption policies are separate.
- Build responsive interfaces with light and dark modes, semantic structure, accessible names, keyboard navigation and visible focus. Supply application data and behaviour through props and callbacks. Verify mobile/desktop, both themes and meaningful interactions in a browser.
- Run the application build, typecheck and live registry audit. Fix failures and review findings, then rerun affected checks. Report actual results and remaining blockers; do not declare completion with unresolved required checks.
- Provide a local preview by default. Deploy only with user authorisation; existing explicit authorisation counts. A passing audit is not deployment permission. Protected CI independently verifies the actual deployment checkout.

Required completion evidence: build, typecheck, registry-audit, browser-responsive, browser-light-dark, browser-keyboard-and-accessibility.
Build/typecheck execution, visual fidelity, responsiveness, complete accessibility or deployment authorisation. Supply separate evidence for these checks.

Workflow version: 2.0.0. Current policy: https://mortar.tony.codes/agent-policy.json