.agents/skills/bootstrap/SKILL.md
Bootstrap a new greenfield TypeScript client-server project with an opinionated monorepo architecture. Use when the user asks to bootstrap, scaffold, or initialize a new project. Triggers on phrases like "bootstrap my project", "scaffold a new project", "start a new typescript project", "set up my project", or "create a new app". Also invocable via the /tseng:bootstrap slash command.
npx skillsauth add kagenti/humr bootstrapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
echo "Architecture docs: ${CLAUDE_SKILL_DIR}/architecture/"
echo "Version: $(cat "${CLAUDE_SKILL_DIR}/VERSION")"
Scaffolds a new greenfield TypeScript client-server monorepo.
Greenfield check — List the target directory contents. If it contains existing source code, package.json, or a packages/ directory, stop immediately and tell the user this skill is for greenfield projects only. Suggest using the review skill instead to audit their existing project. Only allow proceeding if the directory is empty or contains only dotfiles (.git, .gitignore, etc.), README.md, or LICENSE.
Get version — The current tseng version is shown above (injected from the VERSION file). Embed this version in the review record.
Read architecture/index.md from the architecture docs directory (shown above) — it describes the overall architecture and points to deeper dives on each topic.
Read the specific architecture files (in the same architecture docs directory) you need for the current step of bootstrapping. You will likely need all of them, but load them as you go rather than all at once.
Ask the user for a project name (or infer from the directory name), server runtime (Hono or Express, default: Hono), and package manager preference (default: pnpm).
Scaffold the full monorepo with working sample code in every layer, conforming to the architecture.
Write tseng/project-structure.md with the project metadata format described in the architecture docs.
Generate a review checklist from the architecture docs (same process as review/adopt: read all linked files, extract every concrete verifiable rule). Write it to tseng/reviews/001.md as the first review record, with all items marked [x] (the scaffold conforms by construction) and immediately locked:
# Review #001
<!-- tseng_version: {version} -->
<!-- status: locked -->
<!-- created: {YYYY-MM-DD} -->
<!-- locked: {YYYY-MM-DD} -->
Generated from architecture docs (tseng v{version}).
Bootstrap — all items pass by construction.
## Stack
- [x] Uses tRPC for API layer
- [x] Uses Zod for input validation
- ...
Create tseng/reviews/index.md:
# Review History
| # | Date | TSEng Version | Status |
|---|------|---------------|--------|
| [001](001.md) | {YYYY-MM-DD} | {version} | locked |
Write tseng/index.md using the template from the architecture docs. Include sections for "Project Metadata" and "Review History" since both now exist.
Add a ## TSEng section to the project's root CLAUDE.md pointing to tseng/index.md. If CLAUDE.md doesn't exist, create it.
Tell the user what was created and suggest next steps.
001.md) is created locked — it is an immutable record of the project's initial state.development
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue after user approval. Use when user wants to write a PRD, create a product requirements document, or plan a new feature. Always present the PRD for user approval before submitting.
testing
Upgrade a previously bootstrapped or adopted project when the architecture evolves. Diffs the current architecture rules against the project's last locked review, identifies new or changed rules, and proposes incremental changes. Triggers on phrases like "upgrade my project", "sync with latest architecture", "update to new rules", "upgrade tseng", or "architecture changed, update my project". Also invocable via the /tseng:upgrade slash command.
development
Spec out a feature or change with full knowledge of the opinionated TypeScript architecture and the project's adoption state. Conducts a thorough discovery interview to understand domain concerns, bounded contexts, and application services, then produces a high-level architectural specification — never concrete implementation details. Triggers on phrases like "spec this feature", "design this change", "architect this", "help me spec", "what modules do I need", or "think through this feature". Also invocable via the /tseng:spec slash command.
development
Review an existing TypeScript project against the opinionated architecture rules. Use when the user asks to review, audit, check, or validate their project's architecture. Triggers on phrases like "review my project", "check the architecture", "audit my code structure", "validate my project", or "does my project follow the rules". Also invocable via the /tseng:review slash command.