@atlashub/smartstack-cli 3.37.0 → 3.39.0

package/templates/skills/documentation/SKILL.md

@@ -40,7 +40,7 @@ Claude automatically invokes this skill when it detects:
 
 | Type | Description | Output |
 |------|-------------|--------|
-| `user` | User module (data-driven) | `docs/business/{app}/{module}/doc-data.ts` + `index.tsx` |
+| `user` | User module (Mock UI) | `docs/business/{application}/{module}/index.tsx` (standalone TSX with Mock UI) |
 | `developer` | Development tool guide | `docs/developer/tools/{Tool}Page.tsx` |
 | `database` | Schema with ERD diagram | `docs/developer/database/{Schema}SchemaPage.tsx` |
 | `testing` | Testing tool | `docs/developer/testing/{Tool}TestingPage.tsx` |
@@ -58,371 +58,75 @@ Claude automatically invokes this skill when it detects:
 </parameters>
 
 <workflow>
-## AUTOMATIC WORKFLOW
+## WORKFLOW EXECUTION SEQUENCE
 
-### STEP 1: TYPE DETECTION
+The documentation skill executes in 4 progressive steps, each loaded on-demand:
 
-Analyze the request to identify:
+1. **[Step 00: Init](steps/step-00-init.md)** — Detect documentation type and gather context
+2. **[Step 01: Scan](steps/step-01-scan.md)** — Scan source code and extract data
+3. **[Step 02: Generate](steps/step-02-generate.md)** — Generate documentation content
+4. **[Step 03: Validate](steps/step-03-validate.md)** — Validate and integrate into SmartStack
 
-| Clue | → Type |
-|------|--------|
-| Functional module (SLA, Tickets, Users) | `user` |
-| Dev tool (Docker, Postman, VS Code) | `developer` |
-| Tables, schema, database | `database` |
-| Tests (security, load, E2E) | `testing` |
+### Quick Reference
 
-### STEP 2: TARGET EXTRACTION
+| Type | Key Actions |
+|------|-----------|
+| `user` | Read real page TSX → Extract API/BR → Generate standalone annotated Mock UI TSX → Generate i18n (4 lang, FLAT) → Register routes/DocPanel |
+| `developer\|database\|testing` | Extract tool data → Generate doc-data.ts → Generate DocRenderer wrapper → Generate i18n (4 lang, nested) → Register routes |
+| `update` | Re-read real page TSX → Refresh API endpoints and business rules → Update i18n files (4 lang) → Update docs-manifest.json timestamps |
 
-Identify the specific name:
-- Module: `sla`, `tickets`, `users`, `permissions`
-- Tool: `docker`, `postman`, `playwright`, `maildev`
-- Schema: `support`, `auth`, `nav`, `usr`
-- Test: `security`, `load`, `e2e`
-
-### STEP 3: EXECUTION
-
-**For NEW documentation (type = user) - AUTOMATIC MOCK UI GENERATION:**
-
-Use the automated generator script that creates complete documentation with Mock UI components:
-
-```bash
-npx tsx scripts/generate-doc-with-mock-ui.ts \
-  --module {module} \
-  --context {context} \
-  --application {application} \
-  --app-path "D:/01 - projets/SmartStack.app/02-Develop"
-```
-
-**What it does automatically:**
-
-1. **Find & Extract Entity** (e.g., users → User.cs)
-   - Locates Domain entity file
-   - Extracts all properties with types
-
-2. **Extract API Endpoints** (via `extract-api-endpoints.ts`)
-   - Scans controller for all endpoints
-   - Parses `[HttpGet]`, `[HttpPost]`, `[NavRoute]`, `[RequirePermission]`
-   - Resolves permission constants
-   - Output: JSON array of endpoints with method, path, handler, permission
-
-3. **Extract Business Rules** (via `extract-business-rules.ts`)
-   - Scans Domain entity for guard clauses and DomainExceptions
-   - Scans unit tests for edge case scenarios
-   - Auto-assigns BR-XXX IDs and categorizes rules
-   - Output: JSON array of business rules with id, name, category, statement
-
-4. **Generate Mock UI Components**
-   - **KPIs**: Automatic stats based on entity properties
-     - Total count
-     - Active/Inactive (if IsActive property)
-     - Status breakdown (if Status property)
-     - Time-based stats (if DateTime property)
-   - **Table**: Smart column selection (6 most relevant properties)
-     - Filters out: Hash, Token, *Id (FK), normalized, internal fields
-     - Prioritizes: name/title → email → status → date
-   - **Form**: Create form with intelligent field types
-     - Email → type="email" with placeholder
-     - Bool → checkbox
-     - DateTime → type="date"
-     - Description/Notes → textarea
-     - Default → type="text"
-
-5. **Generate Complete TSX File**
-   - Full React component with breadcrumb, sections, mock data
-   - Section 1: Introduction
-   - Section 2: Access (navigation path + URL)
-   - Section 3: Interface Overview (KPIs + Table Mock UI)
-   - Section 4: Create Form (generated form fields)
-   - Section 5: API Reference (endpoints table)
-
-6. **Manual Steps (Post-Generation)**
-   - Save generated TSX to `docs/business/{context}/{application}/{module}/index.tsx`
-   - Update docs-manifest.json
-   - Update App.tsx routing
-   - Update DocPanelContext.tsx mapping
-   - Generate i18n FR file (if needed)
-
-**For NEW documentation (type = developer|database|testing):**
-
-Follow the data-driven workflow from [templates.md](templates.md):
-
-```
-1. Read source data (feature.json, code patterns)
-2. Generate doc-data.ts (data file, ~50 lines)
-3. Generate index.tsx (page wrapper, ~10 lines) with i18nNamespace prop
-4. Generate i18n FR file (source language only)
-5. Update docs-manifest.json
-6. Update App.tsx routing and parent indexes
-```
-
-**For UPDATE documentation (type = update):**
-
-Re-run the generator script to refresh automatically extracted data:
-
-```
-1. Run generate-doc-with-mock-ui.ts → regenerates with latest API/rules
-2. Update i18n FR file if labels changed
-3. Update docs-manifest.json timestamps
-```
-
-> **i18n simplifié:** Seul FR (source) est généré. EN/IT/DE sont déférés à un pipeline de traduction séparé.
-
----
-
-## EXTRACTION SCRIPTS REFERENCE
-
-### extract-api-endpoints.ts
-
-**Purpose:** Extract all API endpoints from SmartStack controllers
-
-**Input:**
-- `--module {module}` - Module name (e.g., users, tenants)
-- `--app-path {path}` - Path to SmartStack.app
-
-**What it extracts:**
-- Controller file path (e.g., `UsersController.cs`)
-- HTTP method (`[HttpGet]`, `[HttpPost]`, `[HttpPut]`, `[HttpDelete]`, `[HttpPatch]`)
-- Route suffix (e.g., `{id:guid}`, `activate`)
-- Base path from `[NavRoute("platform.administration.users")]`
-- Permission from `[RequirePermission(Permissions.Admin.Users.View)]`
-- Handler method name
-
-**Output:** JSON array
-```json
-[
-  {
-    "method": "GET",
-    "path": "/api/platform/administration/users",
-    "handler": "GetUsers",
-    "permission": "platform.administration.users.read"
-  }
-]
-```
-
-**Permission resolution:**
-- Loads `Permissions.cs` constants
-- Maps `Permissions.Admin.Users.View` → `"platform.administration.users.read"`
-
----
-
-### extract-business-rules.ts
-
-**Purpose:** Extract business rules from Domain entities and unit tests
-
-**Input:**
-- `--module {module}` - Module name (e.g., users, tenants)
-- `--app-path {path}` - Path to SmartStack.app
-
-**Phase 1: Domain Entity Extraction**
-- Scans Domain entity (e.g., `User.cs`)
-- Looks for guard clauses: `if (...) throw new DomainException("...")`
-- Looks for validation in Create/Update methods
-- Extracts exception messages and context
-
-**Phase 2: Unit Tests Extraction**
-- Scans unit test file (e.g., `UserTests.cs`)
-- Looks for test methods with `[Fact]` attribute
-- Extracts test names and scenarios (edge cases)
-- Maps to business rule statements
-
-**Output:** JSON array
-```json
-[
-  {
-    "id": "BR-001",
-    "name": "Email requis",
-    "category": "Validation",
-    "statement": "Un utilisateur doit avoir une adresse email valide et non vide"
-  }
-]
-```
-
-**Auto-categorization:**
-- Validation: Required fields, format checks
-- Security: Password rules, access control
-- Business Logic: State transitions, calculations
-
----
-
-### generate-doc-with-mock-ui.ts
-
-**Purpose:** Main generator - creates complete documentation TSX with Mock UI
-
-**Input:**
-- `--module {module}` - Module name (e.g., users)
-- `--context {context}` - Context (e.g., platform)
-- `--application {application}` - Application (e.g., administration)
-- `--app-path {path}` - Path to SmartStack.app
+</workflow>
 
-**Workflow:**
-1. Find Domain entity file (users → User.cs via singularize)
-2. Extract entity properties (name, type, nullable, required)
-3. Call `extract-api-endpoints.ts`
-4. Call `extract-business-rules.ts`
-5. Generate mock data (5 sample records with realistic values)
-6. Generate KPI stats (Total, Active/Inactive, Status breakdown)
-7. Generate table UI (smart column selection - 6 most relevant)
-8. Generate form UI (intelligent field types based on property)
-9. Output complete TSX file to stdout
+<entry_point>
+## SKILL ENTRY POINT
 
-**Smart Features:**
-- **Singularize**: users → User.cs, tenants → Tenant.cs
-- **Property filtering**: Excludes hash, token, *Id, normalized, internal
-- **Priority selection**: name/title > email > status > date
-- **Field type detection**: email → email input, bool → checkbox
-- **Mock value generation**: Realistic emails, names, dates, GUIDs
+**Start with:** [steps/step-00-init.md](steps/step-00-init.md)
 
-**Output:** Complete React TSX component (400-500 lines)
-
-</workflow>
+All execution flows through this progressive loading architecture. Each step file contains:
+- Clear execution sequence
+- Success metrics
+- Next step reference
+</entry_point>
 
 <execution_rules>
 ## ABSOLUTE RULES
 
-1. **NEVER** hardcoded text → `useTranslation('docs')`
+1. **NEVER** hardcoded text → `useTranslation('namespace')`
 2. **NEVER** ASCII art → React/HTML components for ERD
-3. **ALWAYS** read sources before generating
-4. **ALWAYS** confirm before creating
-5. **ALWAYS** update App.tsx and parent indexes
-6. **ALWAYS** add module in `UserIndexPage.tsx` (IF type == `user`)
-7. **ALWAYS** update `DocPanelContext.tsx` mapping (IF type == `user`)
-8. **ALWAYS** pass `i18nNamespace` prop to DocRenderer in index.tsx
+3. **ALWAYS** read the REAL page TSX before generating Mock UI
+4. **ALWAYS** read the controller to extract real API endpoints
+5. **ALWAYS** annotate every Mock UI section with `Annotation` components
+6. **ALWAYS** generate i18n in ALL 4 languages (FR, EN, DE, IT)
+7. **ALWAYS** use FLAT JSON (no root key) for standalone `user` type pages
+8. **ALWAYS** update App.tsx, docs-manifest.json, i18n/config.ts
+9. **ALWAYS** add module in `UserIndexPage.tsx` (IF type == `user`)
+10. **ALWAYS** update `DocPanelContext.tsx` mapping (IF type == `user`)
+11. **For `user` type:** Generate a standalone annotated Mock UI TSX page. **DO NOT use DocRenderer.**
+12. **For `developer|database|testing` types:** Use DocRenderer with `doc-data.ts` + `index.tsx` wrapper, pass `i18nNamespace` prop.
+13. **NEVER** include "Benefices" or "Avant/Apres" sections — this is documentation, not sales.
 </execution_rules>
 
----
+<step_files>
+## Step Files
+
+| Step | File | Purpose |
+|------|------|---------|
+| 00 | [steps/step-00-init.md](steps/step-00-init.md) | Detect documentation type and gather context |
+| 01 | [steps/step-01-scan.md](steps/step-01-scan.md) | Scan source code and extract data |
+| 02 | [steps/step-02-generate.md](steps/step-02-generate.md) | Generate documentation content |
+| 03 | [steps/step-03-validate.md](steps/step-03-validate.md) | Validate and integrate into SmartStack |
+</step_files>
 
 <success_criteria>
 - Documentation page renders correctly in React app
-- i18n FR file created (EN/IT/DE deferred to translation pipeline)
+- Mock UI faithfully reproduces the real page interface (not generic KPI/table)
+- Every Mock UI section has `Annotation` components explaining each visual element
+- i18n files created in ALL 4 languages (FR, EN, DE, IT) with correct JSON format
 - Route registered in App.tsx
 - docs-manifest.json updated
+- i18n/config.ts updated with new namespace
 - Module appears in UserIndexPage (if type = user)
 - DocPanelContext.tsx mapping updated (if type = user)
 - BookOpen edge button opens correct doc for the module's routes
+- NO "Benefices" or "Avant/Apres" sections present
 </success_criteria>
-
----
-
-## UserIndexPage Integration (TYPE: user)
-
-**MANDATORY** for `user` modules: Add the module to the navigation hierarchy.
-
-| File | Modification |
-|------|--------------|
-| `UserIndexPage.tsx` | Add icon + entry in `modules[]` of parent application |
-| `fr/docs.json` | Add `user.modules.{module}.name` and `.description` |
-| `en/docs.json` | Add `user.modules.{module}.name` and `.description` |
-
-**Parent applications:**
-- `Platform > Administration`: admin modules (users, roles, ai, entra...)
-- `Platform > Support`: support modules (tickets, sla, templates...)
-- `Personal > MySpace`: personal modules (profile, preferences...)
-
-**Verification:** The module should appear on `/docs/user` under its application.
-
----
-
-## DocPanelContext Integration (TYPE: user)
-
-**MANDATORY** for `user` modules: Update the contextual documentation panel mapping.
-
-### How it works
-
-When a user clicks the BookOpen icon (edge button) on any application page, the `DocPanelContext` resolves the current route to the matching documentation URL and opens it in an iframe panel.
-
-### File to update
-
-`web/smartstack-web/src/contexts/DocPanelContext.tsx`
-
-### What to add
-
-For each module, add entries in the `docMapping` object for ALL the module's routes:
-
-```typescript
-const docMapping: Record<string, string> = {
-  // Platform > Administration > {Module}
-  '{module}': '/docs/business/platform/administration/{module}',
-  '{module}/list': '/docs/business/platform/administration/{module}',
-  '{module}/create': '/docs/business/platform/administration/{module}',
-  '{module}/dashboard': '/docs/business/platform/administration/{module}',
-  // ... add ALL sub-routes that exist for the module
-};
-```
-
-### Key resolution logic
-
-The `getDocUrlForPath()` function extracts segments from the pathname:
-- `/platform/administration/users/list` → tries `users/list`, then `users`
-- `/platform/support/tickets/123` → tries `tickets/123`, then `tickets`
-
-**Also update `appDocMapping`** if the module is the "default" for its application:
-
-```typescript
-const appDocMapping: Record<string, string> = {
-  'administration': '/docs/business/platform/administration/users',  // default for admin
-};
-```
-
-### index.tsx must pass i18nNamespace
-
-Each doc page wrapper MUST pass the correct i18n namespace to DocRenderer:
-
-```tsx
-import { DocRenderer } from '@/components/docs';
-import { docData } from './doc-data';
-
-export default function {Module}DocPage() {
-  return (
-    <DocRenderer
-      data={docData}
-      backPath="/docs/business/platform"
-      backLabel="nav.backToAdministration"
-      i18nNamespace="docsAdministration{Module}"
-    />
-  );
-}
-```
-
-### i18n namespace naming convention
-
-| Module | Namespace | File |
-|--------|-----------|------|
-| users | `docsAdministrationUsers` | `docs-administration-users.json` |
-| permissions | `docsAdministrationPermissions` | `docs-administration-permissions.json` |
-| tenants | `docsAdministrationTenants` | `docs-administration-tenants.json` |
-
-The JSON file root key MUST match the namespace: `{ "docsAdministration{Module}": { ... } }`
-
-### i18n config update
-
-Add the new namespace to `web/smartstack-web/src/i18n/config.ts`:
-1. Add to the destructured imports in `loadLanguageResources`
-2. Add the dynamic import with `.catch(() => ({ default: {} }))`
-3. Add to the return object
-4. Add to the `ns` array in `i18n.init()`
-
----
-
-## DATA SOURCES
-
-| Data | Source |
-|------|--------|
-| DB schemas | `src/SmartStack.Infrastructure/Persistence/Configurations/` |
-| Tables | `ApplicationDbContextModelSnapshot.cs` |
-| Existing documentation | `web/smartstack-web/src/pages/docs/` |
-| Testing tools | WebSearch (current versions) |
-
----
-
-## ASSOCIATED FILES
-
-- **React Templates:** [templates.md](templates.md)
-- **Data Schema:** [data-schema.md](data-schema.md)
-- **DocRenderer:** `web/smartstack-web/src/components/docs/DocRenderer.tsx`
-- **Types:** `web/smartstack-web/src/components/docs/types.ts`
-- **DocPanelContext:** `web/smartstack-web/src/contexts/DocPanelContext.tsx`
-- **DocEdgeButton:** `web/smartstack-web/src/components/ui/DocEdgeButton.tsx`
-- **DocPanel:** `web/smartstack-web/src/components/ui/DocPanel.tsx`
-- **i18n Config:** `web/smartstack-web/src/i18n/config.ts`
-- **Manifest Schema:** `_resources/docs-manifest-schema.md`
-- **Complete Command:** `.claude/commands/documentation-module.md`

package/templates/skills/documentation/data-schema.md

@@ -1,9 +1,12 @@
 # Documentation Data Schema
 
+> **SCOPE:** This schema applies to `developer`, `database`, and `testing` doc types ONLY.
+> For `user` type modules, generate standalone Mock UI TSX pages — see [templates.md](templates.md).
+
 ## Purpose
 
 This file describes how to generate `doc-data.ts` files for the `DocRenderer` shared component.
-Instead of generating full TSX components (~250 lines) per module, generate only the data (~50 lines).
+Used for non-user doc types (`developer`, `database`, `testing`).
 
 ## DocData Interface Reference
 
@@ -103,7 +106,7 @@ export const docData: DocData = {
   },
 
   useCases: [
-    { id: 'UC-001', name: 'Create SLA', actor: 'Admin', description: '...', permission: 'business.support.sla.create', priority: 'Must' },
+    { id: 'UC-001', name: 'Create SLA', actor: 'Admin', description: '...', permission: 'support.sla.create', priority: 'Must' },
     // ...
   ],
 
@@ -140,14 +143,14 @@ export const docData: DocData = {
   ],
 
   permissions: [
-    { path: 'business.support.sla.read', description: 'View SLA policies', roles: ['Admin', 'Manager', 'User', 'ReadOnly'] },
-    { path: 'business.support.sla.create', description: 'Create SLA policies', roles: ['Admin', 'Manager'] },
+    { path: 'support.sla.read', description: 'View SLA policies', roles: ['Admin', 'Manager', 'User', 'ReadOnly'] },
+    { path: 'support.sla.create', description: 'Create SLA policies', roles: ['Admin', 'Manager'] },
     // ...
   ],
 
   apiEndpoints: [
-    { method: 'GET', path: '/api/business/sla', handler: 'GetAllSlaQuery', permission: '.read' },
-    { method: 'POST', path: '/api/business/sla', handler: 'CreateSlaCommand', permission: '.create' },
+    { method: 'GET', path: '/api/support/sla', handler: 'GetAllSlaQuery', permission: '.read' },
+    { method: 'POST', path: '/api/support/sla', handler: 'CreateSlaCommand', permission: '.create' },
     // ...
   ],
 
@@ -157,8 +160,8 @@ export const docData: DocData = {
   },
 
   technicalRef: {
-    permissionBase: 'business.support.sla',
-    controllerRoute: 'business.support.sla',
+    permissionBase: 'support.sla',
+    controllerRoute: 'support.sla',
     entityNames: ['Sla', 'SlaPolicy', 'SlaEscalation'],
   },
 };

package/templates/skills/documentation/steps/step-00-init.md

@@ -0,0 +1,70 @@
+---
+name: Init - Detect and Gather Context
+description: Detect documentation type and gather context from request
+next_step: step-01-scan.md
+---
+
+## STEP 00: Init — Detect Documentation Type and Gather Context
+
+### Purpose
+
+Analyze the user request to identify documentation type, target name, and gather execution context before proceeding to scanning.
+
+### Execution Sequence
+
+#### 1. Type Detection
+
+Analyze the request to identify:
+
+| Clue | → Type |
+|------|--------|
+| Functional module (SLA, Tickets, Users) | `user` |
+| Dev tool (Docker, Postman, VS Code) | `developer` |
+| Tables, schema, database | `database` |
+| Tests (security, load, E2E) | `testing` |
+
+#### 2. Target Extraction
+
+Identify the specific name:
+- **Module:** `sla`, `tickets`, `users`, `permissions`
+- **Tool:** `docker`, `postman`, `playwright`, `maildev`
+- **Schema:** `support`, `auth`, `nav`, `usr`
+- **Test:** `security`, `load`, `e2e`
+
+#### 3. Documentation Mode Detection
+
+Determine if this is:
+- **NEW documentation** (type = user|developer|database|testing) → Generate from scratch
+- **UPDATE documentation** (explicit "update" flag or drift detected) → Refresh existing content
+
+#### 4. Available Developer Tools Reference
+
+| Category | Tools |
+|----------|-------|
+| Local Environment | Docker Compose, MailDev, VS Code, Environment variables |
+| API Testing | Postman, REST Client, Swagger/OpenAPI |
+| E2E Testing | Microsoft Playwright, Inspector, Trace Viewer |
+| Load Testing | NBomber (.NET), k6, Azure Load Testing |
+| Security Testing | OWASP ZAP, Security Code Scan, Snyk, OWASP ASVS |
+
+### Output
+
+At end of this step, you should have:
+
+| Variable | Value | Example |
+|----------|-------|---------|
+| `type` | user \| developer \| database \| testing \| update | `user` |
+| `target` | Module/Tool/Schema name | `users` |
+| `application` | Parent app (for user type) | `administration` |
+| `mode` | new \| update | `new` |
+
+### Success Metrics
+
+- [x] Type correctly identified from request
+- [x] Target name extracted and validated
+- [x] Application assigned (if type = user)
+- [x] Mode determined (new vs update)
+
+### Next Step
+
+→ **step-01-scan.md** — Scan source code and existing documentation based on detected type.

package/templates/skills/documentation/steps/step-01-scan.md

@@ -0,0 +1,113 @@
+---
+name: Scan - Source Code and Extract Data
+description: Scan source code and existing documentation, extract API endpoints and business rules
+next_step: step-02-generate.md
+---
+
+## STEP 01: Scan — Source Code and Existing Documentation
+
+### Purpose
+
+Based on the type detected in step-00, scan the appropriate source and extract data needed for documentation generation.
+
+### Execution By Type
+
+#### For `user` Type (Functional Module)
+
+**MANDATORY FIRST STEP: Read the REAL page TSX before extracting.**
+The Mock UI must match the actual interface, NOT a generic KPI/table layout.
+
+**Workflow:**
+
+1. **Read the REAL page TSX**
+   - Find: `web/smartstack-web/src/pages/{Application}/{Module}Page.tsx` (e.g., `TenantsTemplatePage.tsx`, `UsersPage.tsx`)
+   - Understand the actual layout (cards, table, kanban, etc.)
+   - Note the exact components, icons, badges, stats shown
+
+2. **Extract API Endpoints** from the controller
+   - Locate: `src/SmartStack.Api/Controllers/{Module}Controller.cs` (singularized)
+   - Scan for `[HttpGet]`, `[HttpPost]`, `[HttpPut]`, `[HttpDelete]`, `[HttpPatch]`
+   - Parse `[NavRoute]`, `[RequirePermission]` attributes
+   - Resolve permission constants from `Permissions.cs`
+
+3. **Extract Business Rules** from Domain entity and tests
+   - Locate: `src/SmartStack.Domain/Entities/{Module}/{Entity}.cs`
+   - Scan for guard clauses: `if (...) throw new DomainException("...")`
+   - Scan validation in Create/Update methods
+   - Find unit tests: `src/SmartStack.Domain.Tests/{Module}/{Entity}Tests.cs`
+   - Look for `[Fact]` test methods and edge case scenarios
+   - Auto-assign BR-XXX IDs and categorize:
+     - **Validation:** Required fields, format checks
+     - **Security:** Password rules, access control
+     - **Business Logic:** State transitions, calculations
+
+#### For `developer` Type (Development Tool)
+
+1. **Locate source reference**
+   - `_resources/developer-tools/` or web search for current versions
+   - Extract: purpose, installation, setup, common commands, screenshots
+
+2. **Reference available developer tools catalog**
+   - Local Environment: Docker Compose, MailDev, VS Code, Environment variables
+   - API Testing: Postman, REST Client, Swagger/OpenAPI
+   - E2E Testing: Microsoft Playwright, Inspector, Trace Viewer
+   - Load Testing: NBomber (.NET), k6, Azure Load Testing
+   - Security Testing: OWASP ZAP, Security Code Scan, Snyk, OWASP ASVS
+
+#### For `database` Type (Schema)
+
+1. **Locate schema configuration**
+   - Find: `src/SmartStack.Infrastructure/Persistence/Configurations/{Schema}Configuration.cs`
+   - Find: `ApplicationDbContextModelSnapshot.cs` for complete schema
+
+2. **Extract:**
+   - Table structure (columns, types, constraints)
+   - Relationships (foreign keys, one-to-many, many-to-many)
+   - Indexes and unique constraints
+
+#### For `testing` Type (Testing Tool)
+
+1. **Locate testing reference**
+   - Current test patterns in project
+   - External tool documentation (Playwright, NBomber, Snyk, etc.)
+
+2. **Extract:**
+   - Tool purpose and integration points
+   - Test execution patterns
+   - Result interpretation
+
+#### For `update` Type
+
+Re-read the real page TSX and controller to refresh extracted data:
+
+```
+1. Read real page TSX → check if interface changed
+2. Read controller → check for new/modified API endpoints
+3. Read Domain entity → check for new business rules
+4. Gather timestamps for doc-manifest.json update
+```
+
+### Output
+
+At end of this step, collected data:
+
+| Type | Data Collected |
+|------|-----------------|
+| `user` | Real page interface, API endpoints array, Business rules array |
+| `developer` | Tool metadata, setup steps, commands, examples |
+| `database` | Schema structure, relationships, constraints |
+| `testing` | Tool integration, test patterns, execution flow |
+| `update` | Changed UI elements, new endpoints, new rules, new timestamps |
+
+### Success Metrics
+
+- [x] Real page TSX read and interface documented (user type)
+- [x] API endpoints extracted with correct HTTP methods and routes
+- [x] Business rules categorized with BR-IDs and statements
+- [x] Permission constants resolved from Permissions.cs
+- [x] Mock data template identified (5+ realistic records)
+- [x] KPI stats template documented (Total, Active, Status breakdown)
+
+### Next Step
+
+→ **step-02-generate.md** — Generate documentation content based on scanned data.