From site-flow
Bootstrap Astro + Tailwind website foundations in a dedicated execution agent
How this agent operates — its isolation, permissions, and tool access model
Agent reference
site-flow:agents/bootstrap-astroThe summary Claude sees when deciding whether to delegate to this agent
This agent is dispatched by `/site-flow:site-build` for Astro bootstrap work. It should be attempted first for Stage 3 bootstrap. If agent launch is unavailable, the same bootstrap scope may run as documented `main-session-fallback`. Create and normalize the Astro + Tailwind project foundation directly in the final target directory, then stop once shared foundations and residue cleanup are comp...
This agent is dispatched by /site-flow:site-build for Astro bootstrap work. It should be attempted first for Stage 3 bootstrap. If agent launch is unavailable, the same bootstrap scope may run as documented main-session-fallback.
Create and normalize the Astro + Tailwind project foundation directly in the final target directory, then stop once shared foundations and residue cleanup are complete.
This agent must not handle:
The orchestrator must provide:
astro-tailwinddesign-tokens.mdsite-blueprint.mdsrc/layouts/BaseLayout.astro.site/bootstrap-report.md.HEAD, branch metadata, base-branch metadata, or worktree support.HEAD, lacks branch/history metadata, or cannot resolve worktree/base-branch information — including failures such as Failed to resolve base branch "HEAD": git rev-parse failed — the orchestrator must treat bootstrap as launch-unavailable and continue as main-session-fallback.Write .site/bootstrap-report.md with:
Executor: sub-agent | main-session-fallbackAgent: bootstrap-astro | noneDelegation outcome: agent-used | fallback-usedFallback reason: none | agent-launch-failed | agent-unavailable | otherExpert Go code reviewer that analyzes diffs, runs go vet and staticcheck, and checks for idiomatic Go, concurrency bugs, error handling, and security issues.
npx claudepluginhub scopes-lab/site-flow --plugin site-flow