You now have access to Niblet Designer UI and designer-skill. Set up both in one pass; if either is already installed, refresh it rather than adding a second copy.
Use them throughout UI work. References and materials are optional additions and never block the task.

1. Install or refresh both skills into the user skill directory (not this project):
npx skills add PyModel/niblet-skill-mcp --skill niblet -g -y
npx skills add PyModel/designer-skill --skill designer-skill -g -y

2. Connect both MCP servers using this client's native MCP configuration, in the user-level (not project-level) config:

Name: niblet
Transport: Streamable HTTP
URL: https://niblet-api.pymodel.com/mcp
Authorization: Bearer YOUR_NIBLET_KEY

Name: designer-skill
Transport: stdio
Command: npx
Args: -y @pymodel/designer-skill-mcp@latest
(designer-skill is keyless: do not add a key to it.)

Write the Niblet key into that local config literally. Do not reference an environment variable unless you have confirmed it is set in the process this client is running in; an unset variable sends an empty or literal "${VAR}" header, and the server answers 401. Never commit, print, log, or share the key.

3. Verify: list each server's tools and confirm niblet exposes find_ui_references, find_ui_materials, get_design_reference, get_ui_component and designer-skill exposes get_preflight_brief, dispatch_intent, review_and_gate. Do not run a sample search. If niblet answers 401, read the response body — it says whether the header was empty, a placeholder, or an unknown key — and fix the config rather than retrying.

When setup is complete, confirm both skills are installed and both servers expose their tools. On UI work from now on: call get_preflight_brief first, use dispatch_intent to load only the references it recommends, pull screen references and materials from the niblet server, then call review_and_gate on the changed files before saying the work is done. If there is an active UI task, continue it. Otherwise say: "Niblet and designer-skill are ready. Show me the screen you're building and name one UI decision you want references for."