the-frame-ai 0.7.2 → 0.9.0

package/README.de.md

@@ -223,6 +223,7 @@ Diese 7 Befehle decken 90% der Solo-Dev-Arbeit ab:
 | `/frame:research <Thema>` | Vor der Planung eines neuen Features |
 | `/frame:explain <Datei>` | Warum sieht dieser Code so aus? |
 | `/frame:why <Thema>` | Entscheidungshistorie durchsuchen |
+| `/frame:arch <Modul>` | Modularchitektur in `docs/arch/{Modul}.md` dokumentieren |
 </details>
 
 <details>

package/README.es.md

@@ -223,6 +223,7 @@ Estos 7 comandos cubren el 90% del trabajo de desarrollo en solitario:
 | `/frame:research <tema>` | Antes de planificar una nueva funcionalidad |
 | `/frame:explain <archivo>` | ¿Por qué este código tiene este aspecto? |
 | `/frame:why <tema>` | Buscar historial de decisiones |
+| `/frame:arch <módulo>` | Documentar la arquitectura de un módulo en `docs/arch/{módulo}.md` |
 </details>
 
 <details>

package/README.hi.md

@@ -223,6 +223,7 @@ npx the-frame-ai init
 | `/frame:research <विषय>` | नई सुविधा की योजना बनाने से पहले |
 | `/frame:explain <फ़ाइल>` | यह कोड ऐसा क्यों दिखता है? |
 | `/frame:why <विषय>` | निर्णय इतिहास खोजें |
+| `/frame:arch <मॉड्यूल>` | मॉड्यूल की आर्किटेक्चर `docs/arch/{मॉड्यूल}.md` में दस्तावेज़ करें |
 </details>
 
 <details>

package/README.ja.md

@@ -223,6 +223,7 @@ npx the-frame-ai init
 | `/frame:research <トピック>` | 新機能の計画前 |
 | `/frame:explain <ファイル>` | このコードがこうなっている理由は？ |
 | `/frame:why <トピック>` | 意思決定の履歴を検索 |
+| `/frame:arch <モジュール>` | モジュールのアーキテクチャを `docs/arch/{モジュール}.md` に記録 |
 </details>
 
 <details>

package/README.md

@@ -225,6 +225,7 @@ These 7 commands cover 90% of solo dev work:
 | `/frame:research <topic>` | Before planning a new feature |
 | `/frame:explain <file>` | Why does this code look like this? |
 | `/frame:why <topic>` | Search decision history |
+| `/frame:arch <module>` | Document a module's architecture to `docs/arch/{module}.md` |
 </details>
 
 <details>

package/README.ru.md

@@ -221,6 +221,7 @@ npx the-frame init
 | `/frame:research <тема>` | Перед планированием новой фичи |
 | `/frame:explain <файл>` | Почему этот код выглядит именно так? |
 | `/frame:why <тема>` | Поиск по истории решений |
+| `/frame:arch <модуль>` | Задокументировать архитектуру модуля в `docs/arch/{модуль}.md` |
 </details>
 
 <details>

package/README.zh.md

@@ -223,6 +223,7 @@ npx the-frame-ai init
 | `/frame:research <主题>` | 在规划新功能之前 |
 | `/frame:explain <文件>` | 为什么这段代码看起来是这样的？ |
 | `/frame:why <主题>` | 搜索决策历史 |
+| `/frame:arch <模块>` | 将模块架构记录到 `docs/arch/{模块}.md` |
 </details>
 
 <details>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "the-frame-ai",
-  "version": "0.7.2",
+  "version": "0.9.0",
   "description": "FRAME — Framework for AI-Assisted Solo Development",
   "type": "module",
   "bin": {

package/templates/commands/frame:arch.md

@@ -0,0 +1,113 @@
+# /frame:arch — Module Architecture
+
+Analyse a module and generate `docs/arch/{module}.md` with its architecture description.
+
+## Instructions
+
+### Step 0: Fail-fast
+
+Require a module name or path. If missing, STOP: "Which module? Provide a module name or path (e.g. `/frame:arch chat` or `/frame:arch src/payments`)."
+
+### Step 1: Locate the module
+
+Find relevant files:
+```bash
+find . -type f \( -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" \) \
+  | grep -i "{module}" | grep -v node_modules | grep -v dist | head -30
+```
+
+If nothing found, try broader search:
+```bash
+grep -rn "{module}" . --include="*.ts" --include="*.js" --include="*.py" --include="*.go" \
+  -l | grep -v node_modules | grep -v dist | head -20
+```
+
+If still nothing: STOP — "Module '{module}' not found. Check the name and try again."
+
+### Step 2: Read the files
+
+Read all located files fully. For large files (>200 lines), focus on:
+- Exports / public API
+- Main classes, functions, types
+- Imports (what this module depends on)
+
+### Step 3: Find entry points and dependencies
+
+```bash
+grep -rn "import.*{module}\|require.*{module}\|from.*{module}" . \
+  --include="*.ts" --include="*.js" --include="*.py" --include="*.go" \
+  | grep -v node_modules | grep -v dist | head -20
+```
+
+This shows who depends on this module.
+
+### Step 4: Check existing doc
+
+```bash
+cat docs/arch/{module}.md 2>/dev/null
+```
+
+If it exists, note what has changed since it was written.
+
+### Step 5: Generate the document
+
+Create or overwrite `docs/arch/{module}.md`:
+
+```markdown
+# {Module} — Architecture
+
+> Generated: {date}
+
+## Overview
+
+{2-3 sentences: what this module does and why it exists}
+
+## Responsibilities
+
+- {responsibility 1}
+- {responsibility 2}
+- ...
+
+## File Structure
+
+| File | Role |
+|------|------|
+| {file} | {what it does} |
+
+## Public API
+
+{Key exports, functions, classes with one-line descriptions}
+
+## Dependencies
+
+**Depends on:**
+- {internal module or external package} — {why}
+
+**Used by:**
+- {module or file} — {how}
+
+## Data Flow
+
+{Describe how data enters, transforms, and exits this module. Use plain text or a simple ASCII diagram.}
+
+## Key Decisions
+
+{Non-obvious design choices, constraints, or trade-offs. If none — omit this section.}
+```
+
+Write the file:
+```bash
+mkdir -p docs/arch
+```
+Then write `docs/arch/{module}.md` with the generated content.
+
+### Step 6: Confirm
+
+Report: "Architecture documented → `docs/arch/{module}.md`" and list the files analysed.
+
+## Rules
+
+- Overwrite if file already exists — always reflect current state
+- No code changes, only the doc file
+- Keep the doc factual — describe what exists, not what should exist
+- If the module spans many files, summarise patterns rather than listing every detail