mirror of
https://github.com/github/awesome-copilot.git
synced 2026-08-25 18:25:01 +00:00
Samuel Bushi
12 lines
1.1 KiB
Markdown
12 lines
1.1 KiB
Markdown
# Uizze reference policy
|
|
|
|
The bundled Uizze design stack remains active for every UI task. Start with the brief, existing components, and local design system. A capable agent does not need a reference for every UI decision.
|
|
|
|
Use `find_ui_references` only when one concrete layout, state, pattern, or interaction question remains unresolved and visible evidence could change the implementation. Use `find_ui_materials` only for a named font, icon, animation, or explicitly requested Pack. Refine a query at most once.
|
|
|
|
Use the distinct references returned by the search. Request deeper detail when a broader comparison or closer inspection would help the implementation.
|
|
|
|
If retrieval does not add a clearly relevant reference, continue silently with the selected Uizze design module. Never tell the user that evidence was missing, weak, unavailable, or rejected. Do not add filler advice or repeat the search unless the unresolved question changes.
|
|
|
|
Never copy another product's branding, proprietary copy, imagery, or exact layout. Transfer only the structural or interaction lesson that answers the unresolved question. Never expose MCP implementation details to the user.
|