Imported from zubair480/bring-your-own-intelligence-yc-26 (
skills/ignition/project-scan-deploy/SKILL.md). Install upstream withnpx skills add zubair480/bring-your-own-intelligence-yc-26 --skill project-scan-deploy. Copyright stays with the author.
Faceplate skill · Ignition 8.3 · used by agents in the QM room Station 01 HMI
How to deploy project changes (project scan and the 8.3 REST API)
Purpose
Make the gateway load changed project resources from disk with system.project.requestScan(), and find the right Ignition 8.3 REST API endpoints from the gateway's own OpenAPI spec.
When to use
- After any view.json write or upsert
- "My change isn't showing up."
- "Deploy the screen."
Inputs
- Gateway address, e.g.
http://localhost:8088 - For REST calls: a gateway API key
Steps
- Write the resources, using
perspective_upsert_viewor file writes underdata/projects/<project>/. - Request a scan so the gateway picks up the changes.
- For anything beyond a scan, open
http://<gateway>:8088/openapi. Read the spec for project and resource endpoints rather than guessing paths. - Confirm the change is live, then log the deploy to [[decisions/log]].
Gateway script (Jython 2.7)
system.project.requestScan()
system.util.getLogger("Faceplate").info("project scan requested by Faceplate agent")
REST (8.3)
# discover the endpoints this gateway exposes
curl -s http://localhost:8088/openapi -o openapi.json
Authenticate REST calls with a gateway API key. Never paste the key into chat or GBrain.
ignition-mcp
project_scan. perspective_list_views then confirms the view is registered.
Verify
perspective_get_viewreturns the new JSON.- An open Perspective session shows the change after it refreshes.
gateway_logs_queryshows no resource-load errors.
Team rules
- Scan after every upsert. An upsert without a scan isn't deployed.
- Deploys happen from the Faceplate loop, so they're traceable in [[decisions/log]].
Part of [[projects/faceplate]].
