create-yss-spec 2.1.4 → 2.1.6

package/template/.pi/skills/drawio/references/docs/xml-format.md

@@ -1,53 +0,0 @@
-# Draw.io XML Format Notes
-
-This file is the **local supplement** to the official draw.io XML reference. For the complete upstream rules on styles, containers, layers, tags, metadata, dark mode, and XML well-formedness, read:
-
-- [Official XML Reference Mirror](../official/xml-reference.md)
-- [Official Style Reference Mirror](../official/style-reference.md)
-
-This document only covers drawio-skill-specific guidance that does not belong in the upstream mirror.
-
-## What this skill adds on top of the official XML rules
-
-### Offline-first bundle contract
-
-The skill does not treat XML as the canonical authoring format. XML is the render target for:
-
-- YAML spec
-- imported `.drawio`
-- normalized Mermaid / CSV input
-
-When work is expected to continue later, keep the canonical trio together:
-
-- `<name>.drawio`
-- `<name>.spec.yaml`
-- `<name>.arch.json`
-
-### Standalone SVG limitation
-
-Standalone SVG export without draw.io Desktop renders faithfully for most diagrams:
-
-- node geometry is preserved, including container-relative child coordinates resolved to absolute positions
-- edges honor fixed exit/entry connection points and replay `<Array as="points">` waypoints; floating endpoints are clipped to node boundaries
-- orthogonal edges without explicit waypoints are approximated with L/Z-shaped bends; exact jetty spacing and obstacle-avoiding routing still require draw.io Desktop export or manual refinement in draw.io
-
-### Formula rules
-
-When labels include math:
-
-- use `$$...$$` for standalone formulas
-- use `\\(...\\)` for inline formulas
-- use `` `...` `` for AsciiMath only when explicitly preferred or very simple
-- do **not** emit `$...$`, `\\[...\\]`, or bare LaTeX commands
-
-### Runtime order
-
-Prefer this backend order:
-
-1. offline bundle generation
-2. draw.io Desktop export when available
-3. optional live backend only when browser or inline refinement is genuinely needed
-
-### Live edit fallback
-
-If a live backend does not support both `read_diagram_xml` and `patch_diagram_cells`, do not attempt incremental live editing. Import to YAML sidecars first, then regenerate.

package/template/.pi/skills/drawio/references/examples/README.md

@@ -1,33 +0,0 @@
-# Reusable YAML Examples
-
-Indexed catalog of the base skill's example specs. Each renders standalone:
-
-```bash
-node <base-skill-dir>/scripts/cli.js <example>.yaml out.drawio --validate
-```
-
-| File                                | Diagram type           | Theme / layout           | Shows                                                                    | When to load                                                  |
-| ----------------------------------- | ---------------------- | ------------------------ | ------------------------------------------------------------------------ | ------------------------------------------------------------- |
-| `agentic-rag.yaml`                  | AI agent architecture  | arch-dark / horizontal   | Agent + RAG loop: user → agent → vector store → LLM with tool calls      | Agent/RAG requests needing `agent`/`vector_store`/`llm` types |
-| `arch-dark-aws-serverless.yaml`     | Cloud architecture     | arch-dark / manual       | AWS serverless map: cloud entry, services, queue, database in one module | Dark-style AWS/serverless service maps                        |
-| `arch-dark-microservices.yaml`      | Architecture           | arch-dark / manual       | Two-module microservices with queues, databases, role-based coloring     | Dark microservice maps with module grouping                   |
-| `arch-dark-web-app.yaml`            | Architecture           | arch-dark / manual       | Minimal client → service → database web app                              | Smallest arch-dark starter                                    |
-| `auto-layout-workflow.yaml`         | Workflow               | tech-blue / hierarchical | Branching review pipeline laid out automatically (no manual bounds)      | Hierarchical auto-layout reference                            |
-| `aws-vpc-topology.yaml`             | Network topology       | tech-blue / star         | Internet ingress → load balancer → app servers → private subnet          | VPC/star topologies with subnet containers                    |
-| `campus-lan-topology.yaml`          | Network topology       | tech-blue / hierarchical | Core/distribution/access/wireless segments with structured link metadata | Campus LAN maps with labeled links                            |
-| `cloud-reference-architecture.yaml` | Architecture           | tech-blue / hierarchical | Four-node gateway → compute → queue → storage skeleton                   | Tiny cloud-reference starter                                  |
-| `e-commerce.yaml`                   | Architecture           | tech-blue / horizontal   | Four-module business platform: services, queues, per-service databases   | Multi-module business platform maps                           |
-| `login-flow.yaml`                   | Flowchart              | nature / vertical        | Login decision flow with success/error paths                             | Simple vertical decision flowcharts                           |
-| `mem0-memory-layer.yaml`            | AI agent architecture  | arch-dark / horizontal   | Memory layer: agent, vector store, database, and `memory` node type      | Memory-layer / stateful-agent diagrams                        |
-| `microservices.yaml`                | Architecture           | tech-blue / horizontal   | Minimal three-module services + database map                             | Smallest module-grouping starter                              |
-| `multi-agent-orchestration.yaml`    | AI agent architecture  | arch-dark / horizontal   | Orchestrator + worker agents with shared text annotations                | Multi-agent orchestration patterns                            |
-| `neural-network.yaml`               | Academic-style diagram | academic / horizontal    | Encoder-decoder CNN drawn with standard node types only                  | `academic` theme demo in the base (non-publication)           |
-| `onprem-dmz-topology.yaml`          | Network topology       | tech-blue / mesh         | Firewall, DMZ services, and internal app/database tiers in two modules   | DMZ segmentation and `mesh` layout                            |
-| `rag-pipeline.yaml`                 | AI pipeline            | arch-dark / horizontal   | Linear ingest → embed → store → retrieve → LLM answer path               | Linear RAG pipeline requests                                  |
-| `replicated-brand-flow.yaml`        | Replicated flowchart   | tech-blue / vertical     | Redraw that preserves the source brand palette via `meta.replication`    | Replicate-mode output shape reference                         |
-| `swimlane-engineering-review.yaml`  | Swimlane process map   | tech-blue / vertical     | Three-swimlane review/remediation sequence                               | Swimlane / process-map requests                               |
-| `tiered-network-topology.yaml`      | Network topology       | tech-blue / tiered       | Internet edge to server farm in classic North-South three-tier rows      | `tiered` layout from `network.tier` roles                     |
-| `tool-call-loop.yaml`               | AI agent diagram       | arch-dark / horizontal   | LLM tool-call cycle with text annotations                                | Tool-use loop diagrams                                        |
-| `vendor-device-mapping.yaml`        | Network topology       | tech-blue / star         | Vendor/device metadata mapped to documented provider and Cisco stencils  | Provider-icon mapping driven by network metadata              |
-
-Palette swatch catalog and previews: `palettes/README.md`.

package/template/.pi/skills/drawio/references/examples/agentic-rag.yaml

@@ -1,71 +0,0 @@
-# Agentic RAG: a reasoning agent orchestrates retrieval and tool use in a loop
-# before handing the grounded context to an LLM for synthesis.
-# arch-dark renders control (orange), memory_read (green), feedback (violet).
-meta:
-  title: Agentic RAG
-  theme: arch-dark
-  layout: horizontal
-
-nodes:
-  - id: query
-    label: User Query
-    type: user
-    position: { x: 80, y: 200 }
-  - id: agent
-    label: "Agent Core\nPlan / Reason"
-    type: agent
-    position: { x: 320, y: 200 }
-  - id: retriever
-    label: Retriever
-    type: process
-    position: { x: 320, y: 380 }
-  - id: store
-    label: "Vector Store\nEmbeddings"
-    type: vector_store
-    position: { x: 100, y: 380 }
-  - id: tool
-    label: "Tool\nSearch / Code"
-    type: tool
-    position: { x: 560, y: 380 }
-  - id: llm
-    label: "LLM\nSynthesis"
-    type: llm
-    position: { x: 760, y: 200 }
-  - id: response
-    label: Response
-    type: user
-    position: { x: 980, y: 200 }
-
-  - id: legend
-    label: 'Legend:  gray = primary   orange = control   green = memory read   violet = feedback loop'
-    type: text
-    position: { x: 530, y: 620 }
-
-edges:
-  - from: query
-    to: agent
-    type: primary
-  - from: agent
-    to: retriever
-    type: control
-  - from: retriever
-    to: store
-    type: memory_read
-  - from: retriever
-    to: agent
-    type: memory_read
-    label: context
-  - from: agent
-    to: tool
-    type: control
-    label: call
-  - from: tool
-    to: agent
-    type: feedback
-    label: result
-  - from: agent
-    to: llm
-    type: primary
-  - from: llm
-    to: response
-    type: primary

package/template/.pi/skills/drawio/references/examples/arch-dark-aws-serverless.yaml

@@ -1,103 +0,0 @@
-# AWS serverless architecture in the arch-dark design language.
-# Adapted from architecture-diagram-generator examples/aws-serverless.html (MIT, Cocoon AI).
-meta:
-  title: AWS Serverless Architecture
-  theme: arch-dark
-  source: replicated
-
-nodes:
-  - id: clients
-    label: "Clients\nWeb / Mobile"
-    type: user
-    position: { x: 70, y: 120 }
-
-  - id: cloudfront
-    label: "CloudFront\nCDN"
-    type: cloud
-    position: { x: 320, y: 120 }
-    module: region
-
-  - id: apigw
-    label: "API Gateway\nREST + WebSocket"
-    type: cloud
-    position: { x: 560, y: 120 }
-    module: region
-
-  - id: lambda
-    label: "Lambda\nNode.js / Python"
-    type: service
-    position: { x: 800, y: 120 }
-    module: region
-
-  - id: s3
-    label: "S3\nStatic Assets"
-    type: cloud
-    position: { x: 320, y: 280 }
-    module: region
-
-  - id: sqs
-    label: "SQS\nQueue"
-    type: queue
-    position: { x: 560, y: 280 }
-    module: region
-
-  - id: dynamodb
-    label: "DynamoDB\nNoSQL On-demand"
-    type: database
-    position: { x: 800, y: 280 }
-    module: region
-
-  # Legend row: outside the region boundary, below it with clearance
-  - id: legend-cloud
-    label: AWS Service
-    type: cloud
-    position: { x: 320, y: 460 }
-    size: small
-
-  - id: legend-compute
-    label: Compute
-    type: service
-    position: { x: 460, y: 460 }
-    size: small
-
-  - id: legend-db
-    label: Database
-    type: database
-    position: { x: 580, y: 460 }
-    size: small
-
-edges:
-  - from: clients
-    to: cloudfront
-    label: HTTPS
-    type: primary
-
-  - from: cloudfront
-    to: apigw
-    type: primary
-
-  - from: apigw
-    to: lambda
-    type: primary
-
-  - from: cloudfront
-    to: s3
-    label: OAI
-    type: data
-
-  - from: lambda
-    to: sqs
-    type: data
-
-  - from: lambda
-    to: dynamodb
-    type: primary
-
-modules:
-  - id: region
-    label: 'AWS Region: us-east-1'
-    style:
-      fillColor: none
-      strokeColor: '#FBBF24'
-      dashed: true
-      dashPattern: '8 4'

package/template/.pi/skills/drawio/references/examples/arch-dark-microservices.yaml

@@ -1,146 +0,0 @@
-# Microservices architecture in the arch-dark design language.
-# Adapted from architecture-diagram-generator examples/microservices.html (MIT, Cocoon AI).
-meta:
-  title: Microservices Architecture
-  theme: arch-dark
-  source: replicated
-
-nodes:
-  - id: webapp
-    label: "Web App\nReact SPA"
-    type: user
-    position: { x: 80, y: 160 }
-
-  - id: mobile
-    label: "Mobile App\niOS / Android"
-    type: user
-    position: { x: 80, y: 300 }
-
-  - id: gateway
-    label: "API Gateway\nKong :443"
-    type: service
-    position: { x: 320, y: 230 }
-    module: sg-gateway
-
-  - id: auth
-    label: "Auth Service\nOAuth 2.0 / JWT"
-    type: terminal
-    position: { x: 320, y: 380 }
-
-  - id: user-svc
-    label: "User Service\nGo :8081"
-    type: service
-    position: { x: 560, y: 120 }
-    module: cluster
-
-  - id: order-svc
-    label: "Order Service\nJava :8082"
-    type: service
-    position: { x: 560, y: 230 }
-    module: cluster
-
-  - id: product-svc
-    label: "Product Service\nPython :8083"
-    type: service
-    position: { x: 560, y: 340 }
-    module: cluster
-
-  # Event bus sits in the gap between the service column and the data column
-  - id: bus
-    label: "Event Bus\nKafka / RabbitMQ"
-    type: queue
-    position: { x: 780, y: 285 }
-    module: cluster
-
-  - id: users-db
-    label: "Users DB\nPostgreSQL"
-    type: database
-    position: { x: 1000, y: 120 }
-    module: cluster
-
-  - id: orders-db
-    label: "Orders DB\nMongoDB"
-    type: database
-    position: { x: 1000, y: 230 }
-    module: cluster
-
-  - id: products-db
-    label: "Products\nElasticsearch"
-    type: database
-    position: { x: 1000, y: 340 }
-    module: cluster
-
-  # Legend row: outside the cluster boundary, below it with clearance
-  - id: legend-service
-    label: Service
-    type: service
-    position: { x: 320, y: 500 }
-    size: small
-
-  - id: legend-db
-    label: Database
-    type: database
-    position: { x: 440, y: 500 }
-    size: small
-
-  - id: legend-bus
-    label: Message Bus
-    type: queue
-    position: { x: 560, y: 500 }
-    size: small
-
-edges:
-  - from: webapp
-    to: gateway
-    label: HTTPS
-    type: primary
-  - from: mobile
-    to: gateway
-    type: primary
-  - from: gateway
-    to: auth
-    label: JWT
-    type: optional
-  - from: gateway
-    to: user-svc
-    type: primary
-  - from: gateway
-    to: order-svc
-    type: primary
-  - from: gateway
-    to: product-svc
-    type: primary
-  - from: user-svc
-    to: bus
-    type: data
-  - from: order-svc
-    to: bus
-    type: data
-  - from: product-svc
-    to: bus
-    type: data
-  - from: user-svc
-    to: users-db
-    type: primary
-  - from: order-svc
-    to: orders-db
-    type: primary
-  - from: product-svc
-    to: products-db
-    type: primary
-
-modules:
-  - id: cluster
-    label: 'Kubernetes Cluster'
-    style:
-      fillColor: none
-      strokeColor: '#FBBF24'
-      dashed: true
-      dashPattern: '8 4'
-  - id: sg-gateway
-    label: 'sg-gateway :443'
-    style:
-      fillColor: none
-      strokeColor: '#FB7185'
-      dashed: true
-      dashPattern: '4 4'

package/template/.pi/skills/drawio/references/examples/arch-dark-web-app.yaml

@@ -1,62 +0,0 @@
-# Web application architecture in the arch-dark design language.
-# Adapted from architecture-diagram-generator examples/web-app.html (MIT, Cocoon AI).
-meta:
-  title: Web App Architecture
-  theme: arch-dark
-  source: replicated
-
-nodes:
-  - id: users
-    label: "Users\nBrowser"
-    type: terminal
-    position: { x: 80, y: 120 }
-
-  - id: frontend
-    label: "Frontend\nReact + TS :3000"
-    type: user
-    position: { x: 320, y: 120 }
-
-  - id: backend
-    label: "Backend\nNode.js :8080"
-    type: service
-    position: { x: 560, y: 120 }
-
-  - id: db
-    label: "Database\nPostgreSQL :5432"
-    type: database
-    position: { x: 800, y: 120 }
-
-  # Legend row: below the diagram, one entry per role in use
-  - id: legend-frontend
-    label: Frontend
-    type: user
-    position: { x: 320, y: 280 }
-    size: small
-
-  - id: legend-backend
-    label: Backend
-    type: service
-    position: { x: 440, y: 280 }
-    size: small
-
-  - id: legend-db
-    label: Database
-    type: database
-    position: { x: 560, y: 280 }
-    size: small
-
-edges:
-  - from: users
-    to: frontend
-    label: HTTPS
-    type: primary
-
-  - from: frontend
-    to: backend
-    label: REST
-    type: primary
-
-  - from: backend
-    to: db
-    label: SQL
-    type: data

package/template/.pi/skills/drawio/references/examples/auto-layout-workflow.yaml

@@ -1,81 +0,0 @@
-# Auto-Layout Workflow Example
-# No node carries bounds/position: with layout: hierarchical the CLI runs the
-# edge-aware layered auto-layout (vendored elkjs), which fills node bounds and
-# orthogonal edge waypoints automatically. Direct sync conversion falls back to
-# the legacy grid and reports an info notice instead.
-meta:
-  title: Content Publishing Workflow
-  description: Branching and merging review pipeline, laid out automatically.
-  theme: tech-blue
-  layout: hierarchical
-
-modules:
-  - id: prep
-    label: Preparation
-  - id: delivery
-    label: Delivery
-
-nodes:
-  - id: start
-    label: Start
-    type: terminal
-  - id: validate
-    label: Validate
-    module: prep
-  - id: enrich_a
-    label: Enrich A
-    module: prep
-  - id: enrich_b
-    label: Enrich B
-    module: prep
-  - id: merge
-    label: Merge
-    module: prep
-  - id: transform
-    label: Transform
-  - id: review
-    label: Review
-  - id: approve
-    label: Auto Approve
-  - id: publish
-    label: Publish
-    module: delivery
-  - id: notify
-    label: Notify
-    module: delivery
-  - id: archive
-    label: Archive
-    module: delivery
-  - id: end
-    label: End
-    type: terminal
-
-edges:
-  - from: start
-    to: validate
-  - from: validate
-    to: enrich_a
-  - from: validate
-    to: enrich_b
-  - from: enrich_a
-    to: merge
-  - from: enrich_b
-    to: merge
-  - from: merge
-    to: transform
-  - from: transform
-    to: review
-  - from: transform
-    to: approve
-  - from: review
-    to: publish
-  - from: approve
-    to: publish
-  - from: publish
-    to: notify
-  - from: publish
-    to: archive
-  - from: notify
-    to: end
-  - from: archive
-    to: end

package/template/.pi/skills/drawio/references/examples/aws-vpc-topology.yaml

@@ -1,66 +0,0 @@
-meta:
-  profile: engineering-review
-  theme: tech-blue
-  layout: star
-  title: "AWS VPC Topology"
-  description: "Internet ingress, load balancing, application servers, and private data tier."
-
-modules:
-  - id: vpc
-    label: AWS VPC
-    color: $surface
-
-nodes:
-  - id: internet
-    label: Internet Gateway
-    type: internet
-    icon: aws.internet_gateway
-    module: vpc
-  - id: alb
-    label: Public ALB
-    type: load_balancer
-    icon: aws.application_load_balancer
-    module: vpc
-  - id: web1
-    label: App Server A
-    type: server
-    icon: aws.ec2
-    module: vpc
-  - id: web2
-    label: App Server B
-    type: server
-    icon: aws.ec2
-    module: vpc
-  - id: db
-    label: RDS Subnet
-    type: subnet
-    icon: aws.rds_instance
-    module: vpc
-    network:
-      cidr: 10.0.2.0/24
-
-edges:
-  - from: internet
-    to: alb
-    type: primary
-    bandwidth: HTTPS
-  - from: alb
-    to: web1
-    type: primary
-    srcInterface: listener-443
-    dstInterface: eth0
-  - from: alb
-    to: web2
-    type: primary
-    srcInterface: listener-443
-    dstInterface: eth0
-  - from: web1
-    to: db
-    type: data
-    ip: 10.0.2.10
-    linkType: private
-  - from: web2
-    to: db
-    type: data
-    ip: 10.0.2.11
-    linkType: private

package/template/.pi/skills/drawio/references/examples/campus-lan-topology.yaml

@@ -1,89 +0,0 @@
-meta:
-  profile: engineering-review
-  theme: tech-blue
-  layout: hierarchical
-  title: "Campus LAN Topology"
-  description: "Core, distribution, access, and wireless segments with structured link metadata."
-
-modules:
-  - id: campus
-    label: Campus Network
-    color: $primaryLight
-
-nodes:
-  - id: internet
-    label: Internet
-    type: internet
-    module: campus
-  - id: firewall
-    label: Edge Firewall
-    type: firewall
-    module: campus
-  - id: core
-    label: Core Switch
-    type: switch
-    module: campus
-    network:
-      device: switch
-      role: core
-  - id: distA
-    label: Distribution A
-    type: switch
-    module: campus
-  - id: distB
-    label: Distribution B
-    type: switch
-    module: campus
-  - id: access
-    label: Access Switch
-    type: switch
-    module: campus
-  - id: ap1
-    label: Wireless AP
-    type: ap
-    module: campus
-  - id: users
-    label: User Segment
-    type: subnet
-    module: campus
-    network:
-      cidr: 10.10.20.0/24
-
-edges:
-  - from: internet
-    to: firewall
-    type: primary
-    bandwidth: 1G
-    linkType: uplink
-  - from: firewall
-    to: core
-    type: primary
-    srcInterface: ge-0/0/0
-    dstInterface: ge-0/0/1
-    vlan: 10
-  - from: core
-    to: distA
-    type: primary
-    bandwidth: 10G
-    linkType: trunk
-  - from: core
-    to: distB
-    type: primary
-    bandwidth: 10G
-    linkType: trunk
-  - from: distA
-    to: access
-    type: primary
-    vlan: 20
-  - from: distB
-    to: access
-    type: data
-    linkType: control
-  - from: access
-    to: ap1
-    type: primary
-    bandwidth: 1G
-  - from: access
-    to: users
-    type: primary
-    ip: 10.10.20.0/24