@kiroku-solutions/kiroku-ai 0.2.1 → 0.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -48,6 +48,8 @@ pnpm --dir CLI start init
|
|
|
48
48
|
| `init` | Pick a setup mode, then download skills into the engine's folders. |
|
|
49
49
|
| `update` | Re-resolves the recorded stack, re-downloads, and prunes removed skills. |
|
|
50
50
|
| `env [tool]` | Switches the AI tool: **migrates the folders** and regenerates its pointer. |
|
|
51
|
+
| `scaffold` | Generates a runnable starter project for the recorded stack (Phase 2). |
|
|
52
|
+
| `analyze` | Scans the current project to detect its stack and missing technologies. |
|
|
51
53
|
|
|
52
54
|
### Setup modes
|
|
53
55
|
|
|
@@ -56,6 +58,7 @@ pnpm --dir CLI start init
|
|
|
56
58
|
| Mode | What it asks |
|
|
57
59
|
| ------------- | --------------------------------------------------------------------------------- |
|
|
58
60
|
| **Quickstart**| Pick one predefined stack (see presets below), then just the AI tool. |
|
|
61
|
+
| **Auto-Detect**| Analyzes your codebase to infer the stack, warns about missing tech, then installs. |
|
|
59
62
|
| **Guided** | The classic stack questionnaire (scope → frontend → backend → db → deploy → devops).|
|
|
60
63
|
| **Modular** | Guided **plus** Architecture, Methodology and Development practices, and per-agent selection. |
|
|
61
64
|
|
|
@@ -84,6 +87,33 @@ pointer file an **Engineering approach** the AI must follow:
|
|
|
84
87
|
The matching docs come from `skills/architecture/`, `skills/methodology/` and
|
|
85
88
|
`skills/practices/` in the SSOT and install under your tool's skills folder.
|
|
86
89
|
|
|
90
|
+
### Scaffolding a starter project (Phase 2)
|
|
91
|
+
|
|
92
|
+
After `init` you can optionally generate a **runnable starter repo** for your
|
|
93
|
+
stack (it also asks at the end of `init`, defaulting to no):
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
kiroku-ai scaffold # reads .kiroku-ai/lockfile.json
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
Generators used (official where they exist; our own templates otherwise):
|
|
100
|
+
|
|
101
|
+
| Stack piece | How it's generated | Needs |
|
|
102
|
+
| ----------- | -------------------------------------------------------------- | ------- |
|
|
103
|
+
| Next.js | `npx create-next-app@latest <dir> --yes --skip-install --disable-git` | `npx` |
|
|
104
|
+
| Astro | `npm create astro@latest <dir> -- --template minimal -y --no-install --no-git` | `npm` |
|
|
105
|
+
| SvelteKit | `npx sv create <dir> --template minimal --types ts --no-install` | `npx` |
|
|
106
|
+
| .NET | `dotnet new webapi -o <dir>` | `dotnet`|
|
|
107
|
+
| FastAPI | template `CLI/templates/scaffold/fastapi/` | — |
|
|
108
|
+
| Java | template `CLI/templates/scaffold/java/` | — |
|
|
109
|
+
|
|
110
|
+
For **fullstack** projects you pick the layout (`apps/web`+`apps/api`,
|
|
111
|
+
`frontend`+`backend`, or custom names); single-scope projects scaffold at the
|
|
112
|
+
root. Dependencies are **not** installed automatically — a next-steps note tells
|
|
113
|
+
you how. If a required toolchain (e.g. `dotnet`) is missing, that piece is
|
|
114
|
+
skipped with a clear message and the rest still runs. Existing non-empty target
|
|
115
|
+
folders are never overwritten.
|
|
116
|
+
|
|
87
117
|
### AI environments
|
|
88
118
|
|
|
89
119
|
During `init` you pick the AI tool the project targets. The CLI installs into
|