| name | logos-scaffold-bootstrap |
| description | Use when the user wants to bootstrap a standalone Logos Scaffold project, choose between the default and LEZ framework templates, understand the required first-success path, or reason about Scaffold's localnet, wallet, deploy, doctor, and report flows without guessing from the CLI surface. |
Logos Scaffold Bootstrap
Use this skill for standalone Scaffold work, especially when the user is new to the CLI and needs a clear path to first success.
Quick start
- Read
references/template-selection.md to choose the right template.
- Read
references/first-success-path.md before proposing commands.
Prefer the logos-scaffold/README.md and template READMEs for exact command wording over bundled references.
Template selection
default -- baseline standalone program_deployment project. Use when the user wants the simplest supported path.
lez-framework -- LEZ framework macros, generated IDL, and more opinionated ergonomics. Use when the user explicitly wants the LEZ framework experience.
If the user is unsure, pick default.
Workflow
- Confirm whether the user is bootstrapping a new project or operating an existing Scaffold project.
- Use the README-backed first-success path:
logos-scaffold setup
logos-scaffold localnet start
logos-scaffold build
logos-scaffold deploy
logos-scaffold wallet topup
- Health checks:
logos-scaffold doctor or logos-scaffold wallet -- check-health
- Keep Scaffold-specific caveats explicit:
- Unix-only scope
- Standalone mode only (not Basecamp, not logoscore)
- Docker or Podman required for guest builds
- Wallet and localnet are part of the normal workflow, not optional extras
Key commands
logos-scaffold setup
logos-scaffold localnet start
logos-scaffold localnet status
logos-scaffold build
logos-scaffold deploy
logos-scaffold wallet topup
logos-scaffold wallet -- check-health
logos-scaffold doctor
logos-scaffold report
Reference map
references/template-selection.md -> choose default versus lez-framework
references/first-success-path.md -> setup, localnet, build, deploy, wallet, and diagnostics flow
Quality rules
- Prefer the Scaffold README and template READMEs over guesswork from subcommand names.
- Keep standalone-only scope explicit.
- Mention wallet, localnet, and diagnostics commands as part of the normal path.
- Do not imply that Scaffold is the same surface as Basecamp or logoscore.
- Scaffold sits on the Logos blockchain / LSSA side, separate from the Qt/liblogos/Basecamp application stack.