itamarzand88/cli-anything-web/boilerplate

Boilerplate Generator (Template-Driven)

Primary method: run the v2 scaffold script — it renders everything below

deterministically and writes a .manifest.json provenance file:

```bash

python ${CLAUDE_PLUGIN_ROOT}/scripts/scaffold-cli.py <app>/agent-harness \

--app-name <app> \

--protocol <rest|graphql|html-scraping|batchexecute> \

--http-client <httpx|curl_cffi> \

--auth-type <none|cookie|api-key|google-sso> \

--resource <name> [--resource <name> ...] \

[--has-polling] [--has-context] [--has-partial-ids]

```

Requires pip install jinja2 (TEMPLATE_VERSION 2.1.0). Each repeatable

--resource flag scaffolds a commands/<resource>.py module.

If the script is unavailable, do NOT render templates by hand from

memory — follow skills/shared/RECOVERY.md §scaffold-cli.py Unavailable

(adapt from the newest generated CLI, e.g., capitoltrades/agent-harness/).

All templates live in ${CLAUDE_PLUGIN_ROOT}/templates/*.tpl (Jinja2 syntax). Generated code must satisfy skills/shared/CONVENTIONS.md — the templates already encode those rules; never "simplify" them away.

Step 1: Collect Template Variables

Casing is derived inside the templates via Jinja2 filters — you only supply --app-name.

Step 2: Template → Output Map

Also produced by the script (not templates): __init__.py files, the vendored runtime adapters utils/repl_skin.py, utils/doctor.py, and utils/mcp_server.py (canonical source cli-web-core/cli_web_core/, synced by cli-web-devkit resync; the entry point registers doctor + mcp-serve from them), utils/config.py, and `.manifest.json` at the harness root recording template_version, profile (protocol/http_client/auth), resources, and generation timestamp — fleet tooling (cli-web-devkit drift) depends on it.

Step 3: Profile Recipes

Step 4: Post-Scaffold Checklist

• [ ] .manifest.json exists at the harness root with template_version: 2.1.0
• [ ] cli_web/ has NO __init__.py; cli_web/<app>/ HAS one
• [ ] No unresolved Jinja2 markers ({{, {%) remain in any output file
• [ ] FILL_IN_BASE_URL markers noted — replace during implementation
• [ ] auth_type=none → no core/auth.py, no auth command group anywhere
• [ ] protocol=batchexecute → core/rpc/ has types/encoder/decoder; otherwise core/rpc/ does NOT exist
• [ ] One commands/<resource>.py exists per --resource flag, all registered on the CLI group
• [ ] All files pass python -m py_compile

Then continue with methodology/SKILL.md Step B: fill in endpoint methods in client.py from <APP>.md, flesh out the scaffolded command modules, and keep _print_repl_help() in sync (CONVENTIONS.md §REPL Rules).