architext 0.0.5 → 0.0.6

package/dist/templates/en/docs/prompts/inherit.md

@@ -101,13 +101,13 @@
 
     ### Information Routing Rules
 
-    > Rule files (`02_tech_stack`, `90_custom_rules`, etc.) are already injected into context by IDE; AI knows their paths, write directly.
+    > Rule files (`tech_stack`, `90_custom_rules`, etc.) are already injected into context by IDE; AI knows their paths, write directly.
 
     **With Brief** (Brief → target file):
     | Brief content | Target file |
     |:---|:---|
     | Project identity, target users, success metrics, references | `[[__DOCS_DIR__]]/global/vision.md` |
-    | Tech stack, deploy target, 3rd-party libs/services | rule file `02_tech_stack` |
+    | Tech stack, deploy target, 3rd-party libs/services | rule file `tech_stack` |
     | Core task list | `[[__DOCS_DIR__]]/global/roadmap.json` (phase-1/2, call archi-decompose-roadmap) |
     | Rules/conventions/preferences from supplementary notes | rule file `90_custom_rules` |
     | Style/tone (UI only) | `design_tokens.json` aestheticDirection etc. |
@@ -116,7 +116,7 @@
     | Source | Target file |
     |:---|:---|
     | README description/features | vision.md |
-    | Dependencies/config/code patterns | 02_tech_stack |
+    | Dependencies/config/code patterns | tech_stack |
     | Directory structure/module deps/user journeys | map.json |
     | Domain terminology/naming conventions | dictionary.json |
     | eslint/prettier etc. | 90_custom_rules |
@@ -129,7 +129,7 @@
     - **Without Brief**: Derive from README + project config; mark un-inferrable items `(AI completion — user review suggested)`
     - Do not retain template placeholders
 
-    ### 3.2 Tech Stack (rule file `02_tech_stack`)
+    ### 3.2 Tech Stack (rule file `tech_stack`)
     - **With Brief**: Brief confirmed → write directly; blank/recommend → AI recommends; code deps as supplement
     - **Without Brief**: Existing deps/config → write directly; visible conventions → write to Coding Standards
     - Fill complete Section 1-8
@@ -210,14 +210,13 @@
     - `dictionary.json`: Extract domain terminology from code
     - (UI projects only) `design_tokens.json`: Extract from CSS variables/theme
     - (Data projects only) `data_snapshot.json`: Extract from schema/migration
+    - (API projects only) `api_snapshot.json`: Extract endpoints from existing API routes/controller code
+    - `env_registry.json`: Extract env vars from `process.env` references in code
+    - (CLI projects only) `command_api.json`: Extract commands from existing CLI entry code
+    - (Lib projects only) `public_api.json`: Extract exports from package.json exports or entry files
     - `error_codes.json`: Extract from error definitions in code
 
-    UI projects only: **UI concept design (Adopt mode)**: [[SKILL: archi-ui-wireframe|Invoke skill (adopt mode) to reverse-generate UI concept design from code.]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md` and follow its Adopt protocol)]]
-    - Read route definitions, page components, layout files from code
-    - Read design_tokens.json written in step_3 (containing CSS variables/theme extracted from code)
-    - When tokens incomplete, triggers skill's built-in guidance flow
-    - Write `ui_concept.html` + `ui_context.md`
-    - Output UI concept design summary; await user confirmation or feedback for adjustments
+    UI projects only: **UI concept design (Adopt mode)**: Skip — completed independently by `/archi.ui`.
 
     **Output**: Write all files, run `npx archi render`. Enter step_4_verify.
 </step_3_constitution>
@@ -234,12 +233,16 @@
 
     **Pre-signoff Checklist** (confirm each item after Gate passes, before Output):
     □ vision.md — filled (without Brief: inferred content annotated `(AI completion — review recommended)`)
-    □ 02_tech_stack.md — Sections 1-8 fully filled
+    □ tech_stack.md — Sections 1-8 fully filled
     □ roadmap.json — each functional module has a corresponding LEG-xx (status: done, tag: Legacy)
     □ tasks/LEG-xx_<Slug>/spec.md — each LEG has a corresponding Stub spec (with related file list)
     □ map.json — directoryMapping + logicalTopology + criticalUserJourneys + featureRelations all filled
-    □ dictionary.json + error_codes.json — extracted from codebase
-    □ (UI projects only) design_tokens.json + ui_concept.html + ui_context.md — Adopt mode executed
+    □ dictionary.json + error_codes.json + env_registry.json — extracted from codebase
+    □ (UI projects only) design_tokens.json — Adopt mode executed
+    □ (Data projects only) data_snapshot.json — initial entity skeleton written
+    □ (API projects only) api_snapshot.json — initial API endpoints registered
+    □ (CLI projects only) command_api.json — initial CLI commands registered
+    □ (Lib projects only) public_api.json — initial lib exports registered
     □ Step 4 Silent Audit — executed, all CRITICAL issues resolved
 
     **Action** (after Checklist confirmed):
@@ -256,6 +259,8 @@
     | Priority | Action | Notes |
     |:---|:---|:---|
     | 1 | Review vision.md | Confirm AI-completed vision description |
+    | (UI projects only) Recommended | `/archi.ui` | Generate UI concept design (`screens/` multi-file structure, Adopt mode) |
+    | (Post-INF) | `/archi.script` | Generate AI automation scripts (validate/dev-up/dev-reset) |
     | 2 | `/archi.edit LEG-xx` | Enrich core module stubs into full spec (auto-triggers Enrich flow) |
     | 3 | `/archi.scope [file_path]` | Plan new features/major modules |
     | 4 | `/archi.plan <task ID>` | Deep-plan individual task |

package/dist/templates/en/docs/prompts/map.md

@@ -8,7 +8,7 @@
     <principles>
       1.  **Scan vs Map**: Actual filesystem is Ground Truth; map.json is old snapshot.
       2.  **Smart Granularity**: Directory-level by default; when single file has multiple responsibilities, refine to file-level.
-      3.  **Architecture Inference**: New entry layer/location must reference existing map pattern + `02_tech_stack.md`.
+      3.  **Architecture Inference**: New entry layer/location must reference existing map pattern + `tech_stack.md`.
       4.  **Batch Confirm**: Show all changes at once; user confirms in batch.
       5.  **IDE-Native First**: Leverage IDE native capabilities to drive execution rhythm; this protocol defines quality standards and checkpoints, not fight IDE planning/execution mechanisms.
     </principles>
@@ -17,7 +17,7 @@
 <step_1_scan>
     **Action**:
     1.  **Read Map**: Read `[[__DOCS_DIR__]]/global/map.json` — current architecture map.
-    2.  **Read Tech Stack**: Read `02_tech_stack.md` — directory structure conventions, architecture pattern.
+    2.  **Read Tech Stack**: Read `tech_stack.md` — directory structure conventions, architecture pattern.
     3.  **Scan Directory Tree**: Scan project directory structure.
         - **Exclude**: `.git/`, `node_modules/`, `dist/`, `build/`, `[[__DOCS_DIR__]]/`, and paths in `.gitignore`.
         - **Depth**: Follow granularity pattern of existing map.json entries.
@@ -48,7 +48,7 @@
     ### Classification strategy
 
     1.  **Pattern match**: Reference same-level existing entries in map.json.
-    2.  **Tech Stack conventions**: Directory structure rules in `02_tech_stack.md`.
+    2.  **Tech Stack conventions**: Directory structure rules in `tech_stack.md`.
     3.  **Content inference**: Read file content (imports, exported types).
     4.  **Cannot determine**: Mark `[?]` for user to specify.
 
@@ -100,6 +100,7 @@
     □ Stale entries removed from directoryMapping
     □ New entries correctly classified (path + layer + description all filled)
     □ Renamed entries explicitly handled (not silently ignored)
+    □ featureRelations — updated if directory changes affect linkage relations
     □ lastUpdated updated
     □ Terminal Gate — task --check + render passed
 

package/dist/templates/en/docs/prompts/plan.md

@@ -24,7 +24,7 @@
 <step_1_load>
     **Action**:
     1.  **Pre-flight**: Read roadmap.json; read only `<ID>` entry and direct deps' `id/title/status`; reject if deps incomplete (unless user forces).
-    2.  **Load**: vision.md (North Star + design philosophy only), 02_tech_stack.md (red lines + §9 project conventions; extract Error Handling/Data Flow/Auth inheritance), (UI projects only) design_tokens.json + ui_context.md (locate screen IDs, lock scope for step_4; do not invent new IDs; skip if absent), (Data projects only) data_snapshot.json.
+    2.  **Load**: vision.md (North Star + design philosophy only), tech_stack.md (red lines + §9 project conventions; extract Error Handling/Data Flow/Auth inheritance), (UI projects only) design_tokens.json + ui_context.md (locate screen IDs, lock scope for step_4; do not invent new IDs; skip if absent), (Data projects only) data_snapshot.json.
     3.  **Dependency Context** (when deps exist): Read only dep task spec.md Interface/Type section; skip if no ref. Stub dep → extract public interfaces from associated files.
     4.  **Refs** (if any): Read refs/index.json; match by tag semantics; load only matched ref files; skip if absent.
 
@@ -126,7 +126,7 @@
 
     **Action Checklist**:
     1.  **`map.json`**: Register `[[__DOCS_DIR__]]/tasks/<ID>_<Slug>` in `directoryMapping`; define module responsibility and dependencies in `logicalTopology`.
-    2.  **Data governance sync** (`dictionary.json` / `error_codes.json` / `data_snapshot.json` etc.): Per `03_data_governance.md`, incrementally sync new business terms, error codes, Schema to corresponding global files.
+    2.  **Data governance sync**: [[SUBAGENT: archi-data-sync|context: Scan Task proposal for new business entities/error codes/Schema/endpoints/commands/exports, incrementally sync per 00_system.md]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-data-sync/SKILL.md`, follow its execution protocol)]]
     3.  **`map.json` featureRelations**: [[SUBAGENT: archi-feature-relations|mode: register, context: Determine if this Task is aggregator; if yes register featureRelations entry]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-feature-relations/SKILL.md`, follow mode: register logic)]]
 
     **Output**: Diff summary of above files. Enter step_5_generate.
@@ -151,7 +151,7 @@
     > Mixed tasks use sub-headings in § 2 to distinguish dimensions.
 
     **spec § 4 Interface Exports**: INF **required**; FEAT required when has downstream deps.
-    **spec § 5 Constraints**: **Required** — extract relevant red lines from vision.md + 02_tech_stack.md.
+    **spec § 5 Constraints**: **Required** — extract relevant red lines from vision.md + tech_stack.md.
 
     **General rules**:
     - Do not invent AC items; each must map to concrete content in task design.
@@ -165,7 +165,7 @@
          | Divergence Type | Criteria | Handling |
          |:---|:---|:---|
          | No divergence | Screen index matches design | Write `ui.md` directly; reference screen ID |
-         | Minor addition | New state/popup/local area; overall layout unchanged | Call skill to update `ui_concept.html` + `ui_context.md`; note `MODIFIED: S-XX` |
+         | Minor addition | New state/popup/local area; overall layout unchanged | Run `/archi.ui` to update `screens/S-XX.html` + `ui_context.md`; note `MODIFIED: screens/S-XX.html` |
          | Structural divergence | Layout refactor, new standalone screen, flow path change | **Pause** — output divergence summary to user; wait for **OK**; then call skill to update; then write `ui.md` |
 
       2. After resolving divergence, fill screen scope and delta components per `ui.template.md`.
@@ -224,7 +224,13 @@
     □ plan.json — every AC in spec § 2 → ≥1 task covering it (100% coverage rule)
     □ plan.json — every task notes includes verification field (not empty, not title paraphrase)
     □ map.json — tasks/<ID>_<Slug> registered in directoryMapping
-    □ Global files — new terms/error codes/schemas synced (dictionary/error_codes/data_snapshot)
+    □ Global files — new terms/error codes/schemas/Tokens/env vars synced:
+      - dictionary.json + error_codes.json + env_registry.json — required
+      - (UI projects only) design_tokens.json + ui_context.md
+      - (Data projects only) data_snapshot.json
+      - (API projects only) api_snapshot.json
+      - (CLI projects only) command_api.json
+      - (Lib projects only) public_api.json
     □ Step 6 Silent Audit — executed, all CRITICAL issues resolved
 
     **Action** (after Checklist confirmed):

package/dist/templates/en/docs/prompts/remove.md

@@ -17,7 +17,7 @@
     **Action**:
     1.  **Resolve ID**: Parse `<id>` from roadmap.json → Task Name, Slug, status.
     2.  **ID Not Found** → Error and list available task IDs.
-    3.  **Load**: task docs directory, roadmap.json (deps), map.json (architecture reg), 99_context_glue.md (associations).
+    3.  **Load**: task docs directory, roadmap.json (deps), map.json (architecture reg).
 
     **Output**: Target Task info (ID, name, status, associated file count).
 </step_1_resolve>
@@ -37,7 +37,7 @@
 
     ### 2.2 Code file identification
 
-    Locate code files via: context_glue paths, map.json registered modules, plan.json mentioned files, Slug-named or clearly owned files.
+    Locate code files via: map.json registered modules, plan.json mentioned files, Slug-named or clearly owned files.
 
     ### 2.3 Global ref scan
 
@@ -45,7 +45,6 @@
     |:---|:---|
     | `roadmap.json` | Task entry + deps refs |
     | `map.json` | Module entry + featureRelations where deleted Task is aggregator |
-    | `99_context_glue.md` | Association entries |
     | `dictionary.json` | Exclusive terms (mark only) |
     | `error_codes.json` | Exclusive error codes (mark only) |
 
@@ -57,7 +56,7 @@
 
     Scan other Tasks' `spec.md`; check refs to deleted Task's interface/components/data. Mark refs as `[Breaking]`.
 
-    **Output**: Output decommission impact report to user — include Task status, docs and code to delete (file/source table), global ref cleanup items (roadmap/map/context_glue), (if any) term/error code residue (manual confirm needed), (if any) aggregator linkage table, (if any) cross-Task ref [Breaking] table. End: OK to execute / Abort to cancel.
+    **Output**: Output decommission impact report to user — include Task status, docs and code to delete (file/source table), global ref cleanup items (roadmap/map), (if any) term/error code residue (manual confirm needed), (if any) aggregator linkage table, (if any) cross-Task ref [Breaking] table. End: OK to execute / Abort to cancel.
 
     **Gate**: Proceed to step_3 only after user replies OK. Re-warn when `[Breaking]` refs exist.
 </step_2_impact>
@@ -72,8 +71,7 @@
     | 2 | Delete Task docs dir | `[[__DOCS_DIR__]]/tasks/<id>_<slug>/` |
     | 3 | Update `roadmap.json` | Remove task entry; clean deps refs |
     | 4 | Update `map.json` | Remove module entry + featureRelations entry |
-    | 5 | Update `99_context_glue.md` | Remove association entries |
-    | 6 | [?exclusive terms] Update `dictionary.json` | Remove or mark deprecated |
+    | 5 | [?exclusive terms] Update `dictionary.json` | Remove or mark deprecated |
     | 7 | [?exclusive error codes] Update `error_codes.json` | Remove or mark deprecated |
     | 8 | [?aggregator linkage] Check aggregator code | Confirm refs cleaned |
 
@@ -95,13 +93,20 @@
     □ tasks/<id>_<slug>/ doc directory — deleted (step_3 action #2)
     □ roadmap.json — task entry + deps refs — cleaned (step_3 action #3)
     □ map.json — module entry + featureRelations — cleaned (step_3 action #4)
-    □ 99_context_glue.md — association entries — cleaned (step_3 action #5)
     □ (if exclusive terms/codes) dictionary.json + error_codes.json — handled
+    □ Global files cleanup check:
+      - vision.md + tech_stack.md — required
+      - dictionary.json + error_codes.json + env_registry.json — required
+      - (UI projects only) design_tokens.json + ui_context.md
+      - (Data projects only) data_snapshot.json
+      - (API projects only) api_snapshot.json
+      - (CLI projects only) command_api.json
+      - (Lib projects only) public_api.json
     □ Terminal Gate — project build passes, no residual import refs (step_4)
 
     **Output**: Decommission completion summary:
     - **Deleted**: N doc files, N code files
-    - **Cleaned**: refs in roadmap / map / context_glue
+    - **Cleaned**: refs in roadmap / map
     - **Build status**: Pass/Fail
     - **[?if any] Manual follow-up**: Term/error code/cross-Task ref residue
     - **Git Commit Suggestion**: `feat(remove): decommission <ID> <Name>`

package/dist/templates/en/docs/prompts/revise.md

@@ -19,7 +19,7 @@
 
 <step_1_load>
     **Action**:
-    1.  **Load**: All global assets (vision/roadmap/map/dictionary/error_codes/02_tech_stack + conditional: design_tokens/data_snapshot).
+    1.  **Load**: All global assets (vision/roadmap/map/dictionary/error_codes/tech_stack + conditional: design_tokens/data_snapshot).
     2.  **Scan Task Index**: Scan tasks/ directory; build Task index (ID, name, status).
     3.  **Intent Analysis**: From `[context]`, identify affected global asset categories.
 
@@ -101,7 +101,15 @@
     **Pre-signoff Checklist** (confirm each item after Gate passes, before Output):
     □ step_4 Safety Checkpoint — Git workspace confirmed (no uncommitted changes or user informed)
     □ Phase 1 — all confirmed global assets modified, change summary output per file
-    □ (UI projects only, design system changed) User notified to re-run archi-ui-wireframe
+    □ Phase 1 — Global files check:
+      - roadmap.json + vision.md + tech_stack.md + map.json — required
+      - dictionary.json + error_codes.json + env_registry.json — required
+      - (UI projects only) design_tokens.json + ui_context.md
+      - (Data projects only) data_snapshot.json
+      - (API projects only) api_snapshot.json
+      - (CLI projects only) command_api.json
+      - (Lib projects only) public_api.json
+    □ (UI projects only, design system changed) User notified to re-run `/archi.ui`
     □ Phase 2 — each affected Task: spec.md updated + plan.json appended Revision Phase
     □ Step 5 Silent Audit — executed, all CRITICAL issues resolved
     □ Consistency confirmed: vision ↔ tech_stack ↔ roadmap ↔ map, no orphan refs (stale terms/paths cleaned)

package/dist/templates/en/docs/prompts/scope.md

@@ -34,7 +34,7 @@
 
 <step_1_load>
     **Action**:
-    1.  **Load**: vision.md (North Star + Boundaries only), roadmap.json (id/title/status/deps/tag + max ID watermark only), 02_tech_stack.md, map.json (directoryMapping + featureRelations only).
+    1.  **Load**: vision.md (North Star + Boundaries only), roadmap.json (id/title/status/deps/tag + max ID watermark only), tech_stack.md, map.json (directoryMapping + featureRelations only).
     2.  **Scan Tasks**: Scan tasks/ — understand existing task summaries (title + key flows; full read not needed).
 
     **Output**: Internal context summary, proceed to `<step_2_analysis>`.
@@ -117,7 +117,8 @@
     **Pre-signoff Checklist** (confirm each item before Output):
     □ Decomposition proposal confirmed by user (replied OK before writing to roadmap — step_4 Gate)
     □ roadmap.json — tasks appended (not overwritten), lastUpdated updated
-    □ (new modules) map.json directoryMapping — new task module paths pre-registered
+    □ (new modules) map.json directoryMapping + logicalTopology — new task module paths pre-registered
+    □ featureRelations — synced if new tasks involve impact on existing file linkages
     □ step_5 Terminal Gate — task --check + render passed
 
     **Action** (Gate must complete in step_5):
@@ -132,7 +133,7 @@
 
     | Priority | Action | Notes |
     |:---|:---|:---|
-    | (UI projects only) Recommended | [[SKILL: archi-ui-wireframe|Run skill (append mode)]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md` and follow its protocol)]] | Append screens for new tasks to `ui_concept.html` |
+    | (UI projects only) Recommended | `/archi.ui` | Generate/update UI concept design (`screens/` multi-file structure) |
     | 1 | `/archi.plan <first pending task ID>` | Deep-plan the first executable task |
     | 2 | Review roadmap | Confirm dependency relationships and priorities |
 </step_5_signoff>

package/dist/templates/en/docs/prompts/script.md

@@ -0,0 +1,102 @@
+<protocol_script>
+  **Trigger**: `/archi.script`
+  **Goal**: Generate/update `.architext/scripts/` based on frozen `tech_stack.md`.
+  **When**: After infrastructure tasks (INF-01, etc.) complete, when `tech_stack` commands are actual values (not placeholders) and runnable.
+
+<meta>
+    <style>Deterministic, Auto-Detect, Post-Infra</style>
+    <language>English</language>
+    <principles>
+      1. **Post-Infra Only**: Only run after infrastructure is ready, `tech_stack` commands must be actual values.
+      2. **Auto-Detect**: Auto-detect OS, generate `.sh` (Unix) and `.ps1` (Windows).
+      3. **Tech-Stack Driven**: Strictly extract actual commands from `tech_stack.md`, no hardcoding.
+      4. **Idempotent**: Multiple runs produce same result, only write on change.
+    </principles>
+</meta>
+
+<step_1_ingest>
+    **Action**:
+    1. Read `[[__DOCS_DIR__]]/global/tech_stack.md`
+    2. Read actual project code, extract real commands:
+       - `package.json` → `scripts` field (if exists)
+       - Config files → `vite.config.*` / `webpack.config.*` / `tsconfig.json`, etc.
+       - CI configs → `.github/workflows/` / `.gitlab-ci.yml`, etc. (if exists)
+    3. Cross-validate: tech_stack commands vs actual config
+       - Consistent → use tech_stack commands
+       - Inconsistent → use actual code (tech_stack may be outdated)
+    4. Extract commands (skip `[e.g.: ...]` placeholders):
+       - **Lint**: Section 3 Static Analysis
+       - **Format**: Section 3 Formatter
+       - **Build**: Section 3 Build Command
+       - **Test**: Section 5 Test Command
+       - **Dev**: Section 3 Dev Command
+       - **Install**: Section 3 Package Manager + install
+    5. Detect current OS (Windows / Unix-like)
+
+    **Output**: Internal command map (tech_stack + actual code cross-validated), enter step_2_generate.
+</step_1_ingest>
+
+<step_2_generate>
+    **Action**: Generate three scripts based on extracted commands:
+
+    ### validate
+    Aggregated checks: Lint → Format Check → Type Check → Build → Test
+    - Exit on first failure (exit 1)
+    - Colored output (green=pass, red=fail, yellow=skip)
+
+    ### dev-up
+    Start environment: Install → Build → Health Check
+    - Health Check: Run build artifact (e.g., `--version` for CLI)
+
+    ### dev-reset
+    Reset environment: Kill Process → Clean Cache → Reinstall → Rebuild → Health Check
+    - Kill: Terminate node/tsx processes
+    - Clean: Remove node_modules/.cache, dist, coverage
+
+    **Script Structure**:
+    - Unix (`.sh`): `#!/bin/bash`, `set -e`, ANSI colors
+    - Windows (`.ps1`): PowerShell, `$ErrorActionPreference`, Write-Host colors
+
+    **Output**: Script content in memory, enter step_3_write.
+</step_2_generate>
+
+<step_3_write>
+    **Action**:
+    1. Ensure `[[__DOCS_DIR__]]/scripts/` directory exists
+    2. Compare with existing scripts (if any):
+       - Same content → skip
+       - Changed → overwrite, mark `MODIFIED`
+       - Not exists → write, mark `ADDED`
+    3. Write files:
+       - Unix: `validate`, `dev-up`, `dev-reset` (no ext, +x)
+       - Windows: `validate.ps1`, `dev-up.ps1`, `dev-reset.ps1`
+
+    **Output**: File change list.
+</step_3_write>
+
+<step_4_signoff>
+    **Terminal Gate** (do not skip): Standard check (task --check + render).
+
+    **Pre-signoff Checklist**:
+    □ tech_stack.md — Successfully extracted non-placeholder commands
+    □ scripts/ — validate/dev-up/dev-reset generated (Unix + Windows)
+    □ Change labels — ADDED / MODIFIED / SKIPPED correctly output
+
+    **Output**:
+    ```
+    ✅ Scripts Generated
+
+    | Script | OS | Status |
+    |:---|:---|:---|
+    | validate | Unix | ADDED/MODIFIED/SKIPPED |
+    | validate | Windows | ADDED/MODIFIED/SKIPPED |
+    | dev-up | Unix | ... |
+    | dev-up | Windows | ... |
+    | dev-reset | Unix | ... |
+    | dev-reset | Windows | ... |
+
+    **Next**: AI will auto-use `scripts/validate` when running `/archi.code`
+    ```
+</step_4_signoff>
+
+</protocol_script>

package/dist/templates/en/docs/prompts/start.md

@@ -90,13 +90,13 @@
 
     ### Information Routing Rules
 
-    > Rule files (`02_tech_stack`, `90_custom_rules`, etc.) are already injected into context by IDE; AI knows their paths, write directly.
+    > Rule files (`tech_stack`, `90_custom_rules`, etc.) are already injected into context by IDE; AI knows their paths, write directly.
 
     | Brief content | Target file |
     |:---|:---|
     | Project identity, target users, success metrics, references | `[[__DOCS_DIR__]]/global/vision.md` |
-    | Tech stack, deploy target, 3rd-party libs/services | rule file `02_tech_stack` |
-    | Style/tone — aesthetic direction / density / motion preference | `02_tech_stack` (UI Protocol) + `design_tokens.json` |
+    | Tech stack, deploy target, 3rd-party libs/services | rule file `tech_stack` |
+    | Style/tone — aesthetic direction / density / motion preference | `tech_stack` (UI Protocol) + `design_tokens.json` |
     | (UI projects only) Aesthetic preset + visual reference (brand palette / font / icon / competitor screenshots) | `design_tokens.json` corresponding fields + `vision.md` Visual Reference |
     | (UI projects only) Images in brief-assets/ tagged `[competitor reference]` | `design_tokens.json` aestheticDirection reference + `vision.md` Visual Reference |
     | Core task list | `[[__DOCS_DIR__]]/global/roadmap.json` |
@@ -107,7 +107,7 @@
     | Files in brief-assets/ tagged `[database Schema]` | Parse and write to `data_snapshot.json` |
     | Files in brief-assets/ tagged `[API docs]` | Parse and route to `vision.md` Context + related Roadmap tasks |
     | Boundaries and anti-goals | `vision.md` Boundaries |
-    | Existing resources | `vision.md` + `02_tech_stack` by content |
+    | Existing resources | `vision.md` + `tech_stack` by content |
     | Rules/conventions/preferences from supplementary notes | rule file `90_custom_rules` |
     | Domain terminology from supplementary notes | `dictionary.json` |
     | Other background from supplementary notes | `vision.md` Context |
@@ -118,7 +118,7 @@
     - Fill from Brief: Core Vision / Target Audience / Boundaries / Design & Experience / Product Principles / background context
     - Fill all placeholders; do not retain template example text
 
-    ### 3.2 Tech Stack (rule file `02_tech_stack`)
+    ### 3.2 Tech Stack (rule file `tech_stack`)
     - Brief confirmed → write directly | Blank/"recommend" → AI recommends and mark `(AI Recommended)` + rationale
     - **AX Optimization**: Prefer AI-friendly tech when recommending
     - Fill complete Section 1-9
@@ -139,16 +139,18 @@
     - (Data projects only) `data_snapshot.json`: Initialize core entity skeleton; write empty template if no data description
     - (UI projects only) `design_tokens.json`: Fill aestheticDirection / primitivePalette / mode / motion / illustration / semanticTokens from "Style & Tone" and "Visual Reference"
     - `error_codes.json`: Predefine core error codes from task list
+    - (API projects only) `api_snapshot.json`: Initial endpoint registration; extract from Brief if API description exists, otherwise write empty template
+    - `env_registry.json`: Initial env var registration
+    - (CLI projects only) `command_api.json`: Initial command registration; extract from Brief if command description exists, otherwise write empty template
+    - (Lib projects only) `public_api.json`: Initial export registration; extract from Brief if export description exists, otherwise write empty template
+
+    UI projects only: **UI concept design**: Skip — completed independently by `/archi.ui`. Only ensure `design_tokens.json` is populated.
 
     ### 3.6 Map (`[[__DOCS_DIR__]]/global/map.json`)
     - `directoryMapping`: Pre-register core directory skeleton from tech_stack architecture pattern
     - `logicalTopology` / `criticalUserJourneys` / `featureRelations`: Empty array for now
 
-    UI projects only: **UI concept design**: [[SKILL: archi-ui-wireframe|Follow the skill protocol to auto-generate UI concept design.]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md` and follow its protocol)]]
-    - Start generation without user confirmation
-    - Read the just-written vision.md + roadmap.json + design_tokens.json + 02_tech_stack
-    - Write `ui_concept.html` + `ui_context.md`
-    - Output UI concept design summary; await user confirmation or feedback for adjustments
+    UI projects only: **UI concept design**: Skip — completed independently by `/archi.ui`.
 
     **Output**: Write all files, then run `npx archi render`. Enter step_4_verify.
 </step_3_constitution>
@@ -165,12 +167,15 @@
 
     **Pre-signoff Checklist** (confirm each item after Gate passes, before Output):
     □ vision.md — all placeholders replaced, no template example text remaining
-    □ 02_tech_stack.md — Sections 1-9 fully filled, Section 9 Project Conventions includes Strategy + Rationale
+    □ tech_stack.md — Sections 1-9 fully filled, Section 9 Project Conventions includes Strategy + Rationale
     □ roadmap.json — archi-decompose-roadmap Skill executed, task chain generated
     □ map.json — core directory skeleton pre-registered (directoryMapping)
-    □ dictionary.json + error_codes.json — domain terms and core error codes extracted
-    □ (UI projects only) design_tokens.json + ui_concept.html + ui_context.md — generated
+    □ dictionary.json + error_codes.json + env_registry.json — domain terms, core error codes, env vars extracted
+    □ (UI projects only) design_tokens.json — generated
     □ (Data projects only) data_snapshot.json — initial entity skeleton written
+    □ (API projects only) api_snapshot.json — initial API endpoints registered
+    □ (CLI projects only) command_api.json — initial CLI commands registered
+    □ (Lib projects only) public_api.json — initial lib exports registered
     □ Step 4 Silent Audit — executed, all CRITICAL issues resolved
 
     **Action** (after Checklist confirmed):
@@ -185,8 +190,9 @@
 
     | Priority | Action | Notes |
     |:---|:---|:---|
-    | (UI projects only) Recommended | Review ui_concept.html | UI concept design auto-generated; confirm layout and visuals in browser |
+    | (UI projects only) Recommended | `/archi.ui` | Generate UI concept design (`screens/` multi-file structure) |
     | Recommended | `/archi.plan INF-01` | Plan the first infrastructure task |
+    | (Post-INF) | `/archi.script` | Generate AI automation scripts (validate/dev-up/dev-reset) |
     | Optional | `/archi.scope <scope-brief.md>` | If more requirements to decompose, append to Roadmap |
 </step_5_signoff>
 

package/dist/templates/en/docs/prompts/ui.md

@@ -0,0 +1,113 @@
+<protocol_ui>
+  **Trigger**: `/archi.ui` | Auto-loaded by Workflow Dispatch on natural language trigger
+  **Goal**: Generate or incrementally update multi-file UI concept designs (`screens/` directory).
+
+<meta>
+    <style>Visual, Systematic, Incremental</style>
+    <language>English</language>
+    <principles>
+      1.  **Auto-Detect**: No subcommands; automatically detects `screens/` directory state to decide full generation or incremental update.
+      2.  **Multi-File**: Each screen as independent `S-XX.html`, shared styles in `_shared.css`, `index.html` as navigation hub.
+      3.  **Token-Driven**: Visual styles strictly from `design_tokens.json`; no hardcoding.
+      4.  **IDE-Native First**: Leverage IDE native capabilities to drive execution rhythm; this protocol defines quality standards and checkpoints without fighting IDE planning/execution mechanisms.
+    </principles>
+</meta>
+
+<step_1_load>
+    **Action**:
+    1.  **Pre-flight**: Check `architext.json` → `features` contains `ui`. If not → reject ("UI feature not enabled for this project").
+    2.  **Load**: vision.md (platform/users/north star), roadmap.json (UI-related tasks), design_tokens.json, tech_stack.md (platform/navigation framework), ui_context.md (if exists).
+    3.  **Mode Detection**:
+
+        | Condition | Mode | Behavior |
+        |:---|:---|:---|
+        | `screens/` directory does not exist | **Full Generation** | Extract all UI screens from roadmap → step_2 |
+        | `screens/` exists | **Incremental Update** | Compare roadmap + ui_context.md, identify new/changed screens → step_2 |
+
+    **Output**: Mode determination + context summary. Proceed to step_2_plan.
+</step_1_load>
+
+<step_2_plan>
+    **Action**:
+
+    **Full mode**: Extract all UI-related screens from roadmap tasks, assign screen IDs (S-01, S-02...).
+    **Incremental mode**: Compare existing `screens/` with roadmap, identify differences:
+
+    | Diff Type | Action |
+    |:---|:---|
+    | New screen (roadmap has task but no corresponding S-XX) | Assign new ID, add to generation list |
+    | Screen change (existing screen's task has requirement changes) | Add to update list |
+    | No change | Skip |
+
+    **Tokens Check**: Check `design_tokens.json`:
+    - `aestheticDirection.preset` empty → guide selection
+    - `primitivePalette.brand` empty → guide Hex input
+    - Other empty values → AI infers, non-blocking
+
+    **Output**: Screen plan list (ID / Name / Task / States / Action: add/update/skip).
+
+    **Gate**: User replies **OK** to proceed to step_3_generate; no file generation without confirmation.
+</step_2_plan>
+
+<step_2_5_refinement>
+    **Trigger**: User replies non-OK, with corrections, screen additions/removals, or mapping adjustments.
+    **Action**: Incorporate feedback, refresh screen plan list and re-output, await confirmation.
+
+    User replies OK → proceed to step_3_generate.
+</step_2_5_refinement>
+
+<step_3_generate>
+    **Action**: Call Skill for actual generation.
+
+    [[SKILL: archi-ui-wireframe|Follow skill protocol to generate multi-file UI concept designs based on confirmed screen plan. Full mode generates all screens; incremental mode generates only new/changed screens.]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md` and follow its protocol)]]
+
+    **Artifacts**:
+    - `[[__DOCS_DIR__]]/global/screens/_shared.css` — CSS variables (from design_tokens) + base layout + control bar styles
+    - `[[__DOCS_DIR__]]/global/screens/S-XX.html` — Each screen as independent file
+    - `[[__DOCS_DIR__]]/global/screens/index.html` — Navigation hub listing all screens
+    - `[[__DOCS_DIR__]]/global/ui_context.md` — AI screen index (routes reference `screens/S-XX.html`)
+
+    **Output**: Generated file list + change summary. Proceed to step_4_verify.
+</step_3_generate>
+
+<step_4_verify>
+    **Role**: Independent Reviewer
+
+    **Verification checklist**:
+
+    | Check | Pass Criteria |
+    |:---|:---|
+    | File completeness | `screens/` contains `index.html` + `_shared.css` + all `S-XX.html` |
+    | Cross-file links | All `S-XX.html` links in `index.html` are valid; each `S-XX.html` has back-to-index link |
+    | CSS references | Each `S-XX.html` references `_shared.css`; CSS variables from design_tokens |
+    | State coverage | Each screen contains default + applicable states (loading/empty/error) |
+    | ui_context.md | Screen index routes reference `screens/S-XX.html` paths |
+    | (Incremental) Existing screens | Unmodified screen files were not overwritten |
+
+    Failed items → fix and recheck. All pass → proceed to step_5_signoff.
+</step_4_verify>
+
+<step_5_signoff>
+    **Pre-signoff Checklist** (confirm before output):
+    □ `screens/` directory structure complete (index.html + _shared.css + S-XX.html)
+    □ `ui_context.md` generated/updated with correct path references
+    □ Step 4 verification all passed
+    □ (Incremental) Only target screens modified, other files unchanged
+
+    **Output**: UI concept design summary:
+    - **Mode**: Full generation / Incremental update
+    - **Screen coverage**: N screens total (X new / Y updated / Z retained)
+    - **Aesthetic direction**: preset + brand color
+    - **File list**: Generated/modified files
+
+    **User confirmation**: Reply **OK** to finish; non-OK enters Refinement (calls Skill for partial update).
+
+    **Next Steps**:
+
+    | Priority | Action | Description |
+    |:---|:---|:---|
+    | Recommended | Open `screens/index.html` in browser | Verify layout and visual design |
+    | 1 | `/archi.plan <first pending task ID>` | Start planning tasks |
+</step_5_signoff>
+
+</protocol_ui>

package/dist/templates/en/docs/shared/ui-redlines.md

@@ -0,0 +1,7 @@
+**UI Design Red Lines (Anti-patterns)**:
+- **No purple-gradient-on-white** — AI default aesthetic signature
+- **No emoji as icons** (🔔📁⚙️) → use self-drawn SVG or declared icon library
+- **No identical centered-card layout for all screens** → list/detail/form must differ
+- **No pure-black + pure-white** → use layered grays
+- **No generic feel** → opening must instantly identify aesthetic (Linear vs Notion vs Grafana)
+- **No hardcoding** — use Tokens for colors, variables for spacing, no magic numbers

package/dist/templates/en/docs/templates/spec.template.md

@@ -79,7 +79,7 @@ description: Task Specification for {FEATURE_NAME}.
 
 ## 5. Constraints
 
-<!-- [AI]: Extract red-line constraints relevant to this task from vision.md + 02_tech_stack.md.
+<!-- [AI]: Extract red-line constraints relevant to this task from vision.md + tech_stack.md.
 
   Format:
   - [constraint content] (ref: [source])