| name | Code Scaffold Harness |
| description | Agent harness for headlessly deploying Code Scaffold assets. |
Code Scaffold Agent Harness
This skill equips you with the instructions to interact with the Code Scaffold binary strictly from the CLI/headless interface. Code Scaffold is an advanced code-generation engine that outputs architecture assets for projects.
Reference Website
https://code-scaffold.web.app/
Installation & Availability
The Code Scaffold binary is typically provided natively via code-scaffold.exe on Windows or code-scaffold on Unix. If it is not immediately present in your PATH or working directory, you must acquire the precompiled binary from the project's official distributions or compile it from source via cargo build --release.
Agent Skill Upgrade Notice: If you are upgrading or reinstalling this skill into an existing environment (e.g. ~/.skills/code-scaffold), you MUST completely remove the existing directory (e.g., rm -rf ~/.skills/code-scaffold) before attempting to copy or clone the new version to prevent ENOTEMPTY leftover state errors.
Headless CLI Syntax
Code Scaffold supports a fully headless deployment mode that allows agents to bypass the TUI entirely.
To view the raw machine-readable JSON structure of available artifacts, personas, skills, and licenses, use the /help flag:
code-scaffold.exe /help
To execute a headless deployment, you must provide the --headless flag along with the absolute target directory. You can optionally comma-separate artifacts, skills, and personas:
code-scaffold.exe --headless --target "/absolute/path/to/target" --personas "Web Dev,AI Systems Engineer" --artifacts "readme.md,.gitignore" --skills "github,typescript" --license "MIT" --json-output
Argument Details
--target (Required): The absolute path to the directory where you want to scaffold the project.
--personas (Optional): A comma-separated list of persona labels (e.g. Web Dev, DBA).
--artifacts (Optional): A comma-separated list of core artifacts (e.g. readme.md, apps/, packages/, .gitignore).
--skills (Optional): A comma-separated list of agent skills (e.g. github, firebase).
--license (Optional): An open source license label (e.g. MIT).
--json-output (Optional): Outputs execution results in a strictly machine-readable JSON payload, suppressing all standard TUI logs. Perfect for programmatic integration.
--dry-run (Optional): Constructs the deployment manifest and outputs it as JSON (when combined with --json-output) without executing any file modifications.
--version-json (Optional): Outputs the current Code Scaffold version as a JSON object (e.g. {"version": "5.9.0"}).
Best Practices for Agents
- Before deploying, always query
code-scaffold.exe /help to ingest the absolute list of currently available labels. The labels are matched in a case-insensitive manner.
- Ensure your
--target path is fully resolved and absolute.
- Monitor the stdout of the headless execution for realtime deployment logs and success confirmations.
Scaffold Connect (OTA Bridging)
Code Scaffold features a zero-trust, ephemeral WebSocket bridge ("Scaffold Connect") that allows you (the agent) to securely tap into a user's local terminal and execute commands remotely.
CRITICAL WARNING: There is NO scaffold-connect CLI binary installed on your system. Do not attempt to run scaffold-connect scaffold://....
If a user prompts you with a connection URI like scaffold://063238@6rkkIbQqN8In5UjNZ0ugnU4Hs86C3GKCX7zAomXY/H8=, do NOT attempt to write your own custom bridge connection scripts from scratch. Instead, strictly follow these steps:
-
Ensure your environment has the required dependencies by running:
pip install websockets cryptography
-
Execute remote commands on the user's machine by invoking the embedded Python client script with the exact URI and your desired command:
python ~/.skills/code-scaffold/scripts/scaffold_client.py "scaffold://063238@6rkk..." "cargo build"
The script will securely connect, execute the command, print the stdout/stderr from the user's machine, and cleanly exit.