archrip 0.2.5 → 0.2.7

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.
Files changed (4) hide show
  1. package/dist/templates/slash-commands/claude/archrip-scan.md +9 -9
  2. package/dist/templates/slash-commands/codex/archrip-scan.md +9 -9
  3. package/dist/templates/slash-commands/gemini/archrip-scan.md +9 -9
  4. package/package.json +1 -1
package/dist/templates/slash-commands/claude/archrip-scan.md CHANGED
@@ -39,18 +39,18 @@ Both layouts use this value — dagre places higher layers lower on screen, conc
39
39
  **Reference mappings** (layer numbers in parentheses — adapt to actual project structure):
40
40
 
41
41
  MVC / Layered:
42
- - Laravel: External(0) → Controllers(1) → Services(2) → Models(3)
43
- - Rails: External(0) → Controllers(1) → Services(2) → Models(3)
44
- - Django: External(0) → Views(1) → Serializers(2) → Services(3) → Models(4)
45
- - Spring Boot: External(0) → Controllers(1) → Services(2) → Repositories(3) → Entities(4)
46
- - NestJS: External(0) → Controllers(1) → Services(2) → Repositories(3) → Entities(4)
42
+ - Laravel: External(0) → Controllers(1) → Services(2) → Domain(3)
43
+ - Rails: External(0) → Controllers(1) → Services(2) → Domain(3)
44
+ - Django: External(0) → Views(1) → Serializers(2) → Services(3) → Domain(4)
45
+ - Spring Boot: External(0) → Controllers(1) → Services(2) → Repositories(3) → Domain(4)
46
+ - NestJS: External(0) → Controllers(1) → Services(2) → Repositories(3) → Domain(4)
47
47
  - Next.js App Router: External(0) → Route Handlers/Pages(1) → Components(2) → Hooks/Services(3) → Data Access(4)
48
- - FastAPI: External(0) → Routers(1) → Services(2) → Repositories(3) → Models(4)
48
+ - FastAPI: External(0) → Routers(1) → Services(2) → Repositories(3) → Domain(4)
49
49
 
50
50
  DDD / Clean Architecture / Hexagonal (use `"layout": "concentric"`):
51
- - Generic: External(0) → Adapters(1) [Controllers, DB impl, API clients] → Application Services(2) → Ports(3) [domain-defined interfaces] → Domain Entities(4)
51
+ - Generic: External(0) → Adapters(1) [Controllers, DB impl, API clients] → Application Services(2) → Ports(3) [domain-defined interfaces] → Domain(4)
52
52
  - Go (Hex): External(0) → Adapters(1) [Handlers, Repositories] → Use Cases(2) → Ports(3) → Domain(4)
53
- - Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Entities(4)
53
+ - Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Domain(4)
54
54
  - Note: Ports are interfaces **defined by the domain** — they belong near domain core, not at the adapter layer. Adapters implement/use Ports from the outside.
55
55
 
56
56
  Serverless / Microservices:
@@ -153,7 +153,7 @@ After writing the file:
153
153
 
154
154
  ### Node Rules
155
155
  - `id`: kebab-case, prefixed by category abbreviation (ctrl-, svc-, port-, adpt-, model-, db-, ext-, job-, dto-)
156
- - `layer`: non-negative integer. **Higher = closer to domain core / more stable. Lower = closer to external world / more volatile.** Dagre (TB) places higher layers lower on screen; concentric places them at center. Use as many layers as the architecture requires (typically 3-6). Example for DDD: 0=external, 1=adapters (controllers + infra), 2=app services, 3=ports, 4=domain entities. Example for MVC: 0=external, 1=controllers, 2=services, 3=models.
156
+ - `layer`: non-negative integer. **Higher = closer to domain core / more stable. Lower = closer to external world / more volatile.** Dagre (TB) places higher layers lower on screen; concentric places them at center. Use as many layers as the architecture requires (typically 3-6). Example for DDD: 0=external, 1=adapters (controllers + infra), 2=app services, 3=ports, 4=domain. Example for MVC: 0=external, 1=controllers, 2=services, 3=domain.
157
157
  - `category`: one of controller, service, port, adapter, model, database, external, job, dto (or custom). Use `model` for domain entities/value objects (core business logic). Use `database` for DB tables, migrations, ORMs, and infrastructure persistence.
158
158
  - `label`: display name for the node
159
159
  - `description`: 1-3 sentences explaining responsibility + business context. Do NOT just echo the label. Cross-reference documentation for richer context (see Description Guidelines below)
package/dist/templates/slash-commands/codex/archrip-scan.md CHANGED
@@ -39,18 +39,18 @@ Both layouts use this value — dagre places higher layers lower on screen, conc
39
39
  **Reference mappings** (layer numbers in parentheses — adapt to actual project structure):
40
40
 
41
41
  MVC / Layered:
42
- - Laravel: External(0) → Controllers(1) → Services(2) → Models(3)
43
- - Rails: External(0) → Controllers(1) → Services(2) → Models(3)
44
- - Django: External(0) → Views(1) → Serializers(2) → Services(3) → Models(4)
45
- - Spring Boot: External(0) → Controllers(1) → Services(2) → Repositories(3) → Entities(4)
46
- - NestJS: External(0) → Controllers(1) → Services(2) → Repositories(3) → Entities(4)
42
+ - Laravel: External(0) → Controllers(1) → Services(2) → Domain(3)
43
+ - Rails: External(0) → Controllers(1) → Services(2) → Domain(3)
44
+ - Django: External(0) → Views(1) → Serializers(2) → Services(3) → Domain(4)
45
+ - Spring Boot: External(0) → Controllers(1) → Services(2) → Repositories(3) → Domain(4)
46
+ - NestJS: External(0) → Controllers(1) → Services(2) → Repositories(3) → Domain(4)
47
47
  - Next.js App Router: External(0) → Route Handlers/Pages(1) → Components(2) → Hooks/Services(3) → Data Access(4)
48
- - FastAPI: External(0) → Routers(1) → Services(2) → Repositories(3) → Models(4)
48
+ - FastAPI: External(0) → Routers(1) → Services(2) → Repositories(3) → Domain(4)
49
49
 
50
50
  DDD / Clean Architecture / Hexagonal (use `"layout": "concentric"`):
51
- - Generic: External(0) → Adapters(1) [Controllers, DB impl, API clients] → Application Services(2) → Ports(3) [domain-defined interfaces] → Domain Entities(4)
51
+ - Generic: External(0) → Adapters(1) [Controllers, DB impl, API clients] → Application Services(2) → Ports(3) [domain-defined interfaces] → Domain(4)
52
52
  - Go (Hex): External(0) → Adapters(1) [Handlers, Repositories] → Use Cases(2) → Ports(3) → Domain(4)
53
- - Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Entities(4)
53
+ - Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Domain(4)
54
54
  - Note: Ports are interfaces **defined by the domain** — they belong near domain core, not at the adapter layer. Adapters implement/use Ports from the outside.
55
55
 
56
56
  Serverless / Microservices:
@@ -153,7 +153,7 @@ After writing the file:
153
153
 
154
154
  ### Node Rules
155
155
  - `id`: kebab-case, prefixed by category abbreviation (ctrl-, svc-, port-, adpt-, model-, db-, ext-, job-, dto-)
156
- - `layer`: non-negative integer. **Higher = closer to domain core / more stable. Lower = closer to external world / more volatile.** Dagre (TB) places higher layers lower on screen; concentric places them at center. Use as many layers as the architecture requires (typically 3-6). Example for DDD: 0=external, 1=adapters (controllers + infra), 2=app services, 3=ports, 4=domain entities. Example for MVC: 0=external, 1=controllers, 2=services, 3=models.
156
+ - `layer`: non-negative integer. **Higher = closer to domain core / more stable. Lower = closer to external world / more volatile.** Dagre (TB) places higher layers lower on screen; concentric places them at center. Use as many layers as the architecture requires (typically 3-6). Example for DDD: 0=external, 1=adapters (controllers + infra), 2=app services, 3=ports, 4=domain. Example for MVC: 0=external, 1=controllers, 2=services, 3=domain.
157
157
  - `category`: one of controller, service, port, adapter, model, database, external, job, dto (or custom). Use `model` for domain entities/value objects (core business logic). Use `database` for DB tables, migrations, ORMs, and infrastructure persistence.
158
158
  - `label`: display name for the node
159
159
  - `description`: 1-3 sentences explaining responsibility + business context. Do NOT just echo the label. Cross-reference documentation for richer context (see Description Guidelines below)
package/dist/templates/slash-commands/gemini/archrip-scan.md CHANGED
@@ -39,18 +39,18 @@ Both layouts use this value — dagre places higher layers lower on screen, conc
39
39
  **Reference mappings** (layer numbers in parentheses — adapt to actual project structure):
40
40
 
41
41
  MVC / Layered:
42
- - Laravel: External(0) → Controllers(1) → Services(2) → Models(3)
43
- - Rails: External(0) → Controllers(1) → Services(2) → Models(3)
44
- - Django: External(0) → Views(1) → Serializers(2) → Services(3) → Models(4)
45
- - Spring Boot: External(0) → Controllers(1) → Services(2) → Repositories(3) → Entities(4)
46
- - NestJS: External(0) → Controllers(1) → Services(2) → Repositories(3) → Entities(4)
42
+ - Laravel: External(0) → Controllers(1) → Services(2) → Domain(3)
43
+ - Rails: External(0) → Controllers(1) → Services(2) → Domain(3)
44
+ - Django: External(0) → Views(1) → Serializers(2) → Services(3) → Domain(4)
45
+ - Spring Boot: External(0) → Controllers(1) → Services(2) → Repositories(3) → Domain(4)
46
+ - NestJS: External(0) → Controllers(1) → Services(2) → Repositories(3) → Domain(4)
47
47
  - Next.js App Router: External(0) → Route Handlers/Pages(1) → Components(2) → Hooks/Services(3) → Data Access(4)
48
- - FastAPI: External(0) → Routers(1) → Services(2) → Repositories(3) → Models(4)
48
+ - FastAPI: External(0) → Routers(1) → Services(2) → Repositories(3) → Domain(4)
49
49
 
50
50
  DDD / Clean Architecture / Hexagonal (use `"layout": "concentric"`):
51
- - Generic: External(0) → Adapters(1) [Controllers, DB impl, API clients] → Application Services(2) → Ports(3) [domain-defined interfaces] → Domain Entities(4)
51
+ - Generic: External(0) → Adapters(1) [Controllers, DB impl, API clients] → Application Services(2) → Ports(3) [domain-defined interfaces] → Domain(4)
52
52
  - Go (Hex): External(0) → Adapters(1) [Handlers, Repositories] → Use Cases(2) → Ports(3) → Domain(4)
53
- - Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Entities(4)
53
+ - Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Domain(4)
54
54
  - Note: Ports are interfaces **defined by the domain** — they belong near domain core, not at the adapter layer. Adapters implement/use Ports from the outside.
55
55
 
56
56
  Serverless / Microservices:
@@ -153,7 +153,7 @@ After writing the file:
153
153
 
154
154
  ### Node Rules
155
155
  - `id`: kebab-case, prefixed by category abbreviation (ctrl-, svc-, port-, adpt-, model-, db-, ext-, job-, dto-)
156
- - `layer`: non-negative integer. **Higher = closer to domain core / more stable. Lower = closer to external world / more volatile.** Dagre (TB) places higher layers lower on screen; concentric places them at center. Use as many layers as the architecture requires (typically 3-6). Example for DDD: 0=external, 1=adapters (controllers + infra), 2=app services, 3=ports, 4=domain entities. Example for MVC: 0=external, 1=controllers, 2=services, 3=models.
156
+ - `layer`: non-negative integer. **Higher = closer to domain core / more stable. Lower = closer to external world / more volatile.** Dagre (TB) places higher layers lower on screen; concentric places them at center. Use as many layers as the architecture requires (typically 3-6). Example for DDD: 0=external, 1=adapters (controllers + infra), 2=app services, 3=ports, 4=domain. Example for MVC: 0=external, 1=controllers, 2=services, 3=domain.
157
157
  - `category`: one of controller, service, port, adapter, model, database, external, job, dto (or custom). Use `model` for domain entities/value objects (core business logic). Use `database` for DB tables, migrations, ORMs, and infrastructure persistence.
158
158
  - `label`: display name for the node
159
159
  - `description`: 1-3 sentences explaining responsibility + business context. Do NOT just echo the label. Cross-reference documentation for richer context (see Description Guidelines below)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "archrip",
3
- "version": "0.2.5",
3
+ "version": "0.2.7",
4
4
  "description": "Generate interactive architecture diagrams from your codebase using AI agents",
5
5
  "type": "module",
6
6
  "bin": {