Write Actions, not infrastructure

Run one Action, learn the contract, then publish

• 1. Build your first Assistant Generate a valid starter and run one Action locally without Docker.
• 2. Understand the project structure Use the required actions directory and one async run function per file.
• 3. Read Assistant Spec v1 See what belongs in source and what Shimpz generates during pre-build.
• 4. Test the unpublished Assistant in Local Stage an exact image, authorize it for one Team, and exercise its normal Actions.
• 5. Publish one immutable release Authorize the exact source and wait for an installable artifact.

Load the current Shimpz guide into Codex or Claude Code

Install the coding agent you intend to use, then run one command from the Assistant project. You may also pass another Assistant project directory as the final argument.

Shimpz loads the current versioned Assistant development guide and starts the selected agent in that directory. By default, the agent keeps its own permission protections. Adding --yolo disables those protections and lets the agent run commands with your operating-system user's access.

The SDK describes; the Controller decides

1. The SDK derives a machine contract from the files in actions/.
2. The platform generates locks and runtime/container artifacts during pre-build.
3. The Controller validates the manifest and generated contract without importing source.
4. Every input and output is validated again when an Action runs.