UNS Kit Project Bootstrap
Overview
Create new uns-kit projects and bring them to a ready-to-code baseline using the official CLI flow:
- create project, 2) configure project, 3) verify generated structure, 4) hand off to implementation tasks.
Read references/command-matrix.md when selecting commands or feature sets.
Gather Inputs
Collect these inputs before executing commands:
- Stack:
tsorpython - Project name
- Destination directory
- Configure profile:
minimal,standard, orcustom - Optional extras:
api,cron,pythonbridge (TS projects),devops
If stack is not explicit:
- Infer
tswhen user mentions npm/pnpm/Node. - Infer
pythonwhen user mentions poetry/pip/Python-only runtime. - Ask one concise clarifying question only when signals are mixed.
Bootstrap TypeScript Projects
Execute scaffold:
pnpm --package=@uns-kit/cli dlx uns-kit create <project_name>
Configure from project root (or pass path):
- Minimal:
uns-kit configure . vscode
- Standard:
uns-kit configure . vscode codegen uns-reference
- Add API plugin:
uns-kit configure . api
- Add cron plugin:
uns-kit configure . cron
- Add Python gateway template:
uns-kit configure . python
Only run when explicitly requested:
uns-kit configure . devops
Finalize:
pnpm install
Bootstrap Python Projects
Execute scaffold:
uns-kit-py create <project_name>
From project root:
poetry install
Apply configuration commands individually:
poetry run uns-kit-py configure-vscode .
poetry run uns-kit-py configure-workspace .
Only run when explicitly requested (interactive/Azure-specific):
poetry run uns-kit-py configure-devops .
Verify Ready State
Verify generated files after bootstrap.
TypeScript expected:
package.jsonconfig.jsonsrc/index.ts- Optional based on features:
codegen.ts,uns-dictionary.json,uns-measurements.json,python/
Python expected:
pyproject.tomlconfig.jsonmain.py.vscode/and<project>.code-workspacewhen configured
Run a quick sanity check when available:
- TypeScript:
pnpm run build - Python:
poetry run python main.py
Handoff To Implementation
After bootstrap verification:
- Summarize exactly which create/configure commands ran.
- List generated optional features.
- Propose the next implementation prompt for Codex (domain entities, topics, transforms, APIs, schedulers).
Do not run publish/deploy/pull-request workflows unless explicitly requested.
Source: uns-datahub/uns-kit — distributed by TomeVault.