bootstrap

Bootstrap a TypeScript client-server monorepo with tseng metadata and architecture files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kagenti/humr --skill bootstrap-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap
Source: https://github.com/kagenti/humr/tree/main/.agents/skills/bootstrap
Command: npx skills add https://github.com/kagenti/humr --skill bootstrap-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap a new greenfield TypeScript client-server project with an opinionated monorepo architecture. It helps users bootstrap, scaffold, or initialize a fresh project from scratch.

Core Features & Use Cases

  • Greenfield bootstrap for a TypeScript client-server monorepo.
  • Architecture-guided scaffolding, including initial metadata for TSEng.
  • Automated generation of tseng project artifacts (index, reviews, and CLAUDE integration).

Quick Start

Create a new greenfield TypeScript client-server monorepo scaffold with architecture docs and initial tseng metadata.

Frequently Asked Questions about bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new TypeScript monorepo from scratch?

To scaffold a TypeScript monorepo from scratch, this Skill bootstraps a greenfield client-server project by reading architecture/index.md to generate initial project artifacts and tseng metadata.

What files are generated when bootstrapping a greenfield TypeScript project?

Bootstrapping a greenfield TypeScript project generates tseng/index.md, tseng/reviews/001.md, tseng/reviews/index.md, and updates CLAUDE.md using architecture and version metadata.

Can I initialize a TypeScript client-server monorepo without existing architecture documentation?

No, initializing the TypeScript client-server monorepo requires an existing architecture/index.md file and a VERSION file to populate the generated scaffolding metadata accurately.

What is the best way to set up initial TSEng metadata for a new TypeScript project?

The best way to set up TSEng metadata is using an opinionated bootstrap workflow that automatically creates tseng/index.md and review files directly from your architecture documentation.

Does the bootstrap workflow support injecting project version numbers into the scaffolding?

Yes, the bootstrap workflow supports version injection by reading the VERSION file during the greenfield TypeScript monorepo initialization to populate the generated project metadata.

When should I use an opinionated monorepo scaffold instead of manual setup?

Use an opinionated monorepo scaffold when starting a greenfield TypeScript client-server project to ensure consistent architecture loading and automated tseng metadata generation from day one.