catalyst-develop
Installation
SKILL.md
The local development loop
Goal: end this skill with the user's own process running on their machine, talking to a real Catalyst sidecar, and able to see what it did. A loop that requires a redeploy per edit is not this loop; if you find yourself recreating resources to test a code change, something above is wrong.
Everything here goes through the Catalyst MCP server, the catalyst_* tools. If they are
missing or refuse with NOT_AUTHENTICATED, the catalyst-setup skill covers it.
1. The shape of the loop
| Frequency | Step | How |
|---|---|---|
| Once per app | Make sure the App ID exists, with its components | catalyst_get_app, else catalyst_apply (section 2) |
| Every run of the process | Get the connection values and start the process with them | catalyst_get_connection (section 3) |
| Every iteration | Trigger a run and read what happened | catalyst_start_workflow, catalyst_get_workflow_run (section 4) |