{"id":"1bc2ab65-a9d2-4dd6-92cf-3379a7319fe7","entityType":"agent","slug":"clawhub-samonysh-plantuml-skill","name":"Plantuml","canonicalUrl":"https://www.xpersona.co/agent/clawhub-samonysh-plantuml-skill","canonicalPath":"/agent/clawhub-samonysh-plantuml-skill","generatedAt":"2026-10-10T07:42:14.412Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T04:01:34.738Z","emptyReason":null},"description":"Turn natural language into uml-diagrams.org style PlantUML diagrams (sequence, class, activity, use case, component, state…) and render to SVG/PNG/PDF. Use w... Skill: Plantuml Owner: samonysh Summary: Turn natural language into uml-diagrams.org style PlantUML diagrams (sequence, class, activity, use case, component, state…) and render to SVG/PNG/PDF. Use w... Tags: latest:1.7.2 Version history: v1.7.2 | 2026-07-12T08:55:11.880Z | user Release v1.7.2 v1.7.1 | 2026-07-09T03:37:10.011Z | user Release v1.7.1 v1.7.0 | 2026-07-07T19:01:02.791Z | user Release v1.7.0 v1.6.1 | 2026-","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.7K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s179t2y0de4pmccw2jxzpwwkr18802cc:plantuml-skill","sourceUrl":"https://clawhub.ai/samonysh/plantuml-skill","homepage":"https://clawhub.ai/samonysh/skills/plantuml-skill","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/samonysh/plantuml-skill","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/samonysh/skills/plantuml-skill","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":65,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Turn natural language into uml-diagrams.org style PlantUML diagrams (sequence, class, activity, use case, component, state…) and render to SVG/PNG/PDF. Use w..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T04:01:34.738Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T04:01:34.738Z","emptyReason":null},"stars":null,"forks":null,"downloads":1706,"packageName":null,"latestVersion":"1.7.2","tractionLabel":"1.7K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T04:01:34.738Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T04:01:34.738Z","lastCrawledAt":"2026-10-10T04:01:34.738Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T04:01:34.738Z","lastVerifiedAt":null,"highlights":[{"version":"1.7.2","createdAt":"2026-07-12T08:55:11.880Z","changelog":"Release v1.7.2","fileCount":4,"zipByteSize":28763},{"version":"1.7.1","createdAt":"2026-07-09T03:37:10.011Z","changelog":"Release v1.7.1","fileCount":5,"zipByteSize":42206},{"version":"1.7.0","createdAt":"2026-07-07T19:01:02.791Z","changelog":"Release v1.7.0","fileCount":6,"zipByteSize":49864},{"version":"1.6.1","createdAt":"2026-07-05T07:25:45.819Z","changelog":"v1.6.1 — SVG style compliance, dark mode fixes, documentation cleanup","fileCount":5,"zipByteSize":39193},{"version":"1.6.0","createdAt":"2026-07-05T02:01:04.102Z","changelog":"Release v1.6.0","fileCount":5,"zipByteSize":37095},{"version":"1.5.0","createdAt":"2026-07-04T12:52:16.564Z","changelog":"## v1.5.0 ### New Features - Aspect ratio band 0.7–1.4 with --min-aspect / --max-aspect overrides - Spacing guards during auto-fix to preserve text legibility - Dark mode (--dark-mode) emits light + dark companion with recolored palette - Direction-injection safety for activity/sequence/state diagrams ### Improvements - Both Bash and PowerShell render scripts updated (full parity) - All 7 example SVGs regenerated (light + dark variants) - SKILL.md and both READMEs updated","fileCount":5,"zipByteSize":37791},{"version":"1.4.1","createdAt":"2026-06-25T01:53:11.585Z","changelog":"v1.4.1 — migrate opt-in public backend from plantuml.com to kroki.io; add PLANTUML_PUBLIC_SERVER for self-hosted Kroki","fileCount":5,"zipByteSize":33011},{"version":"1.4.0","createdAt":"2026-06-25T01:31:18.100Z","changelog":"v1.4.0 — A4 paper fit validation, render script bug fixes, README refresh, regenerated examples","fileCount":5,"zipByteSize":31412}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s179t2y0de4pmccw2jxzpwwkr18802cc:plantuml-skill","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T07:42:14.408Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-samonysh-plantuml-skill/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T04:01:34.738Z","emptyReason":null},"readme":"Skill: Plantuml\n\nOwner: samonysh\n\nSummary: Turn natural language into uml-diagrams.org style PlantUML diagrams (sequence, class, activity, use case, component, state…) and render to SVG/PNG/PDF. Use w...\n\nTags: latest:1.7.2\n\nVersion history:\n\nv1.7.2 | 2026-07-12T08:55:11.880Z | user\n\nRelease v1.7.2\n\nv1.7.1 | 2026-07-09T03:37:10.011Z | user\n\nRelease v1.7.1\n\nv1.7.0 | 2026-07-07T19:01:02.791Z | user\n\nRelease v1.7.0\n\nv1.6.1 | 2026-07-05T07:25:45.819Z | user\n\nv1.6.1 — SVG style compliance, dark mode fixes, documentation cleanup\n\nv1.6.0 | 2026-07-05T02:01:04.102Z | user\n\nRelease v1.6.0\n\nv1.5.0 | 2026-07-04T12:52:16.564Z | user\n\n## v1.5.0\n\n### New Features\n- Aspect ratio band 0.7–1.4 with --min-aspect / --max-aspect overrides\n- Spacing guards during auto-fix to preserve text legibility\n- Dark mode (--dark-mode) emits light + dark companion with recolored palette\n- Direction-injection safety for activity/sequence/state diagrams\n\n### Improvements\n- Both Bash and PowerShell render scripts updated (full parity)\n- All 7 example SVGs regenerated (light + dark variants)\n- SKILL.md and both READMEs updated\n\nv1.4.1 | 2026-06-25T01:53:11.585Z | user\n\nv1.4.1 — migrate opt-in public backend from plantuml.com to kroki.io; add PLANTUML_PUBLIC_SERVER for self-hosted Kroki\n\nv1.4.0 | 2026-06-25T01:31:18.100Z | user\n\nv1.4.0 — A4 paper fit validation, render script bug fixes, README refresh, regenerated examples\n\nv1.3.0 | 2026-06-16T11:33:04.222Z | user\n\nv1.3.0 — Privacy-first defaults: public PlantUML server is now opt-in only (--use-public-server / -UsePublicServer). Local rendering (Docker → JAR) is the default. Addresses ClawHub security audit (SDI-1, SDI-2, SQP-2). Full changelog: https://github.com/samonysh/plantuml-skill/releases/tag/v1.3.0\n\nv1.2.0 | 2026-06-13T02:20:23.747Z | auto\n\nplantuml-skill 1.2.0\n\n- Added: New SKILL.md file consolidating documentation.\n- Removed: Deprecated skill-card.md and skill.md documentation files.\n- Updated: Improved Unix shell and PowerShell rendering scripts for PlantUML (generate-plantuml.sh, generate-plantuml.ps1).\n- Documentation and scripting workflow are now clearer and more maintainable.\n\nv1.1.1 | 2026-06-04T11:26:12.536Z | user\n\nplantuml-skill 1.1.1\n\n- Added a skill manifest section with version, emoji, homepage, and backend requirements.\n- Clarified rendering backend requirements: only one of curl, docker, or java is needed.\n- Shortened and streamlined the skill description for clarity and conciseness.\n- No changes to workflow or diagram style requirements.\n- Documentation improvements only; no functional changes.\n\nv1.1.0 | 2026-06-04T11:09:43.315Z | auto\n\nPlantUML Skill v1.1.0\n\n- Added comprehensive SKILL.md documentation describing the PlantUML diagram generation workflow from requirements parsing to output rendering.\n- Strictly enforces uml-diagrams.org reference style (black-and-white, Visio UML 2.x stencil look) for all generated diagrams unless the user requests otherwise.\n- Details mandatory PlantUML code preamble, syntax requirements, and styling do’s and don’ts.\n- Lists supported diagram types and relevant trigger phrases for use.\n- Provides step-by-step workflow and usage instructions for rendering with included conversion scripts across different OS environments.\n\nArchive index:\n\nArchive v1.7.2: 4 files, 28763 bytes\n\nFiles: scripts/generate_plantuml.py (41933b), skill-card.md (2225b), SKILL.md (46401b), _meta.json (133b)\n\nFile v1.7.2:SKILL.md\n\n---\r\nname: plantuml\r\ndescription: Turn natural language into uml-diagrams.org style PlantUML diagrams (sequence, class, activity, use case, component, state…) and render to SVG/PNG/PDF. Use when the user asks to draw a UML diagram.\r\nversion: 1.7.2\r\nemoji: \"📐\"\r\nhomepage: https://github.com/samonysh/plantuml-skill\r\nmetadata:\r\n openclaw:\r\n # The render script is local-first: it tries Docker, then a local plantuml.jar.\r\n # The Kroki public server is OPT-IN ONLY (--use-public-server)\r\n # because it uploads diagram source to a third-party service (kroki.io by default,\r\n # overridable to a self-hosted Kroki via PLANTUML_PUBLIC_SERVER).\r\n requires:\r\n anyBins:\r\n - docker\r\n - java\r\n - curl\r\n # This skill reads no environment variables and writes no secrets; nothing to\r\n # declare under primaryEnv / envVars / requires.env.\r\n---\r\n\r\n# PlantUML Diagram Generator\r\n\r\nGenerate professional PlantUML diagrams from natural language descriptions. This skill handles\r\nthe full pipeline: requirement analysis → PlantUML code generation → image rendering.\r\n\r\n## Trigger Phrases\r\n\r\nUse this skill when the user asks to:\r\n- \"Generate/draw/create a PlantUML diagram for...\"\r\n- \"Create a sequence/class/activity/... diagram showing...\"\r\n- \"Visualize this flow/architecture/process as...\"\r\n- \"Turn this description into a UML diagram\"\r\n- \"Make a flowchart / ERD / Gantt chart from...\"\r\n- Any request involving diagram generation from text descriptions\r\n\r\n## Mandatory Style Requirements\r\n\r\nALL diagrams generated by this skill MUST adhere to the **uml-diagrams.org reference style** —\r\nstrict OMG UML 2.x rendered with Visio UML 2.x stencils (black-and-white, no decoration).\r\nThis is the canonical style used throughout https://www.uml-diagrams.org and serves as the\r\nauthoritative visual reference for every diagram this skill produces.\r\nNo exceptions unless the user explicitly requests otherwise.\r\n\r\n- **Black and white only**: Pure black lines (`#000000`) on a pure white background (`#FFFFFF`). No colors, no grayscale fills, no gradients, no themed accents.\r\n- **Thin uniform line weight**: All borders, arrows and connectors use the default hair-line stroke (≈0.75pt). Never thicken or stylize lines.\r\n- **No circle visibility icons**: Class attributes MUST NOT show colored circle icons (● public / ◐ protected / ○ private). Enforced via `skinparam classAttributeIconSize 0`. Use `+ - # ~` text markers only.\r\n- **No circle stereotype icons**: Class and interface headers MUST NOT show circle-with-letter icons (Ⓒ / Ⓘ / Ⓐ / Ⓔ). Instead of relying on `skinparam style strictuml` (which degrades actors into plain text and use cases into rectangles — see [Common Failure Patterns](#common-failure-patterns)), we suppress the circle adornments purely at the **syntax level**: always declare interfaces / abstract classes / enumerations via a `class <>` / `class <>` / `class <>` text stereotype — never use the `interface` / `abstract class` / `enum` keywords, which are what trigger the circle icons in the first place.\r\n- **Abstract classifiers in italics**: Per UML 2.5 §9 and uml-diagrams.org \"Name of an abstract classifier is shown in italics\" — the `<>` text stereotype combined with `{abstract}` method markers renders correctly without needing `strictuml`.\r\n- **No 3D effects**: Drop shadows MUST be disabled (`skinparam shadowing false`).\r\n- **Clean typography**: Sans-serif font (Helvetica, equivalent to the Arial used by Visio stencils on uml-diagrams.org), 12pt default. No colored or bold text except diagram titles. When CJK characters are present, use `--cjk` flag to switch to a CJK-compatible font (see [CJK Font Support](#cjk-chinesejapanesekorean-font-support)).\r\n- **Aspect ratio**: Generated diagrams are automatically validated for an aspect-ratio band. By default the renderer tries to keep width/height between **0.7 and 1.4** (a comfortable page-like shape), re-rendering with layout corrections when the output falls outside that band. Diagrams that cannot be fixed safely after a few attempts are kept with a warning, so unusual diagrams are not destroyed. Use `--no-fix` to disable this behavior (see Step 3).\r\n- **A4 paper fit**: After aspect-ratio validation passes, the diagram is checked against A4 paper (210×297 mm). At the **96 DPI CSS standard**, this works out to **794×1123 px portrait** and **1123×794 px landscape**. The renderer accepts the diagram if it fits in EITHER orientation; otherwise it injects a computed PlantUML `scale N` directive and re-renders up to once. The default body font of 12 px (from the mandatory preamble) shrinks proportionally; if the estimated on-paper font drops below `--min-font-pt` (default **8 pt**), the script prints a legibility warning — at that point no further down-scaling helps and the user must split the diagram or abbreviate labels. A4 fit is **ON by default**; disable with `--no-a4-check`.\r\n- **Standard UML shapes**:\r\n - Actors are **stick figures** (never Visio icons or images).\r\n - Classes / components / nodes are plain rectangles; activities are round-cornered rectangles with the activity name in the upper-left.\r\n - Dependencies and realizations use **dashed** lines; lifelines use **dashed** vertical lines (uml-diagrams.org explicitly: *\"a rectangle forming its head followed by a vertical line (which may be dashed) that represents the lifetime of the participant\"*).\r\n - Notes are white folded-corner rectangles; no shading.\r\n- **Sequence diagram specifics** (matching uml-diagrams.org figures exactly):\r\n - **Lifeline** head is a **white rectangle**; the vertical lifeline is a **dashed** black line.\r\n - **Execution specification / activation bar** is a *\"thin grey or white rectangle on the lifeline\"* — this skill renders it as a thin **white** rectangle with a black border (no yellow PlantUML default).\r\n - **Destruction occurrence** is shown as an `X` at the bottom of the lifeline (PlantUML ` !` syntax).\r\n - Synchronous messages use a **filled solid triangle arrowhead** on a solid line.\r\n - Asynchronous messages use an **open stick arrowhead** on a solid line.\r\n - Reply / return messages use an **open stick arrowhead** on a **dashed** line.\r\n- **Activity diagram specifics**: round-cornered action rectangles, solid arrows with **open arrowheads** for control flow, diamond decisions/merges, thick horizontal/vertical bar for forks/joins, filled black dot for initial node, bull's-eye for activity final.\r\n- **Use case diagram specifics**: stick-figure actor on the left, ellipses for use cases inside a rectangle **subject boundary**, `«include»` / `«extend»` as dashed open arrows.\r\n- **Class diagram specifics**: associations are plain solid lines, aggregation = hollow diamond, composition = filled diamond, generalization = hollow triangle arrowhead on solid line, realization = hollow triangle arrowhead on dashed line, dependency = open arrow on dashed line.\r\n\r\nEvery `.puml` file MUST include the mandatory uml-diagrams.org-style preamble as its first lines after `@startuml` (see [Style Configuration](#omg-uml-style-configuration-mandatory)).\r\n\r\n---\r\n\r\n## Workflow\r\n\r\n### Step 1: Parse and Confirm Requirements\r\n\r\nExtract from the user's description:\r\n- **Diagram type** — which PlantUML diagram fits best\r\n- **Actors/participants** — who/what is involved\r\n- **Relationships/flows** — how they interact\r\n- **Constraints/rules** — conditions, ordering, cardinality\r\n- **Output format** — svg (default), png, pdf, or txt (ASCII art)\r\n\r\nIf the diagram type is not explicitly stated, infer it from the description:\r\n\r\n| Description signals | Recommended diagram |\r\n|---|---|\r\n| \"A sends X to B\", \"request/response\", \"handshake\" | Sequence |\r\n| \"inherits from\", \"has many\", \"belongs to\", entities & fields | Class |\r\n| \"if/then\", \"approve/reject\", workflow, pipeline | Activity |\r\n| \"user can\", \"admin manages\", roles & permissions | Use Case |\r\n| \"depends on\", \"connects to\", services & interfaces | Component |\r\n| \"deployed on\", \"hosted on\", nodes & servers | Deployment |\r\n| \"transitions from\", \"changes state\", lifecycle | State |\r\n| timeline, milestones, phases, schedule | Gantt |\r\n| hierarchy, brainstorming, tree structure | Mind Map |\r\n\r\n**If ambiguous, ask the user to clarify the diagram type before proceeding.**\r\n\r\n### Step 2: Generate PlantUML Code\r\n\r\nWrite the PlantUML source following these rules:\r\n\r\n1. Start EVERY file with one of the two mandatory uml-diagrams.org-style preambles\r\n immediately after `@startuml`:\r\n - **Default**: the `skinparam` preamble — see [OMG-UML / uml-diagrams.org Style Configuration](#omg-uml--uml-diagramsorg-style-configuration-mandatory).\r\n Maximum backward compatibility, used by every example except #07.\r\n (Example #07 is a legacy alias of #01_css — same OAuth2 sequence diagram, same CSS preamble.)\r\n - **Backup option**: the CSS-style `\r\nskinparam classAttributeIconSize 0\r\n\r\ntitle Payment System\r\n\r\nclass User {\r\n +id: UUID\r\n +email: String\r\n +name: String\r\n +register()\r\n}\r\n\r\nclass Order {\r\n +id: UUID\r\n +total: Decimal\r\n +status: OrderStatus\r\n +calculateTotal()\r\n}\r\n\r\nclass PaymentProcessor <> {\r\n +processPayment(amount: Decimal): Boolean\r\n +refund(transactionId: UUID): Boolean\r\n}\r\n\r\nclass NotificationService <> {\r\n #enabled: Boolean\r\n +{abstract} send(to: String, body: String)\r\n}\r\n\r\nenum OrderStatus {\r\n PENDING\r\n CONFIRMED\r\n SHIPPED\r\n DELIVERED\r\n}\r\n\r\nUser \"1\" -- \"*\" Order : places\r\nOrder ..|> PaymentProcessor\r\nNotificationService <|-- EmailNotifier\r\n@enduml\r\n```\r\n\r\nKey syntax: `+` public, `-` private, `#` protected, `{abstract}` abstract method,\r\n`class Foo <>` (interface via text stereotype — NOT `interface Foo`),\r\n`class Bar <>` (abstract class — NOT `abstract class Bar`),\r\n`enum`, relationships: `--` association, `*--` composition, `o--` aggregation,\r\n`<|--` inheritance, `..|>` realization\r\n\r\n### Activity Diagram\r\n\r\n```\r\n@startuml\r\ntitle Order Processing\r\n\r\nstart\r\n:Receive Order;\r\nif (Payment Valid?) then (yes)\r\n :Reserve Inventory;\r\n if (Inventory Available?) then (yes)\r\n :Confirm Order;\r\n :Ship Order;\r\n stop\r\n else (no)\r\n :Notify Customer;\r\n :Cancel Order;\r\n stop\r\n endif\r\nelse (no)\r\n :Reject Order;\r\n stop\r\nendif\r\n@enduml\r\n```\r\n\r\nKey syntax: `start/stop/end`, `if/then/else/endif`, `repeat/repeat while`,\r\n`fork/fork again/end fork` (parallel), `split/split again/end split`,\r\n`partition \"name\" { ... }` (swimlane), `:Text;` action\r\n\r\n### Use Case Diagram\r\n\r\n```\r\n@startuml\r\ntitle E-Commerce System\r\n\r\nleft to right direction\r\n\r\nactor Customer\r\nactor Admin\r\n\r\nrectangle \"E-Commerce\" {\r\n usecase \"Browse Products\" as UC1\r\n usecase \"Place Order\" as UC2\r\n usecase \"Manage Inventory\" as UC3\r\n usecase \"Process Returns\" as UC4\r\n}\r\n\r\nCustomer --> UC1\r\nCustomer --> UC2\r\nAdmin --> UC3\r\nAdmin --> UC4\r\nUC2 ..> UC1 : <>\r\n@enduml\r\n```\r\n\r\nKey syntax: `actor`, `usecase`, `rectangle/package` for system boundary,\r\n`-->` association, `..>` dependency, `<>` / `<>` stereotypes\r\n\r\n### Component Diagram\r\n\r\n```\r\n@startuml\r\ntitle Microservice Architecture\r\n\r\npackage \"Frontend\" {\r\n [Web App]\r\n [Mobile App]\r\n}\r\n\r\npackage \"API Gateway\" {\r\n [Gateway]\r\n}\r\n\r\npackage \"Services\" {\r\n [User Service]\r\n [Order Service]\r\n [Payment Service]\r\n}\r\n\r\ndatabase \"PostgreSQL\" as DB\r\ncloud \"Message Queue\" as MQ\r\n\r\n[Web App] --> [Gateway]\r\n[Mobile App] --> [Gateway]\r\n[Gateway] --> [User Service]\r\n[Gateway] --> [Order Service]\r\n[Order Service] --> [Payment Service]\r\n[User Service] --> DB\r\n[Order Service] --> DB\r\n[Order Service] --> MQ\r\n@enduml\r\n```\r\n\r\nKey syntax: `[Component]`, `package \"name\" { }`, `database`, `cloud`, `node`,\r\n`frame`, `interface`, `()--` required interface, `--()` provided interface\r\n\r\n### Deployment Diagram\r\n\r\n```\r\n@startuml\r\ntitle Production Deployment\r\n\r\nnode \"AWS us-east-1\" {\r\n node \"VPC\" {\r\n node \"Public Subnet\" {\r\n [Load Balancer]\r\n [Bastion Host]\r\n }\r\n node \"Private Subnet\" {\r\n node \"App Server 1\" {\r\n [Application]\r\n }\r\n node \"App Server 2\" {\r\n [Application]\r\n }\r\n database \"RDS Primary\"\r\n }\r\n }\r\n cloud \"CDN\"\r\n}\r\n@enduml\r\n```\r\n\r\nKey syntax: `node \"name\" { }`, nested `node`, `database`, `cloud`, `actor`\r\n\r\n### State Diagram\r\n\r\n```\r\n@startuml\r\ntitle Order Lifecycle\r\n\r\n[*] --> Draft\r\nDraft --> Submitted : submit()\r\nSubmitted --> Paid : processPayment()\r\nSubmitted --> Cancelled : cancel()\r\nPaid --> Shipped : ship()\r\nShipped --> Delivered : confirmDelivery()\r\nDelivered --> [*]\r\nCancelled --> [*]\r\n\r\nstate Paid {\r\n [*] --> Authorizing\r\n Authorizing --> Captured : success\r\n Authorizing --> Failed : decline\r\n Captured --> [*]\r\n}\r\n@enduml\r\n```\r\n\r\nKey syntax: `[*]` start/end, `-->` transition with optional `: label`,\r\n`state Name { }` composite state, `state \"Name\" as Alias`\r\n\r\n### Gantt Chart\r\n\r\n```\r\n@startuml\r\ntitle Project Roadmap\r\n\r\nproject starts 2025-01-06\r\n\r\n[Design] lasts 10 days\r\n[Development] lasts 20 days\r\n[Development] starts at [Design]'s end\r\n[Testing] lasts 10 days\r\n[Testing] starts at [Development]'s end\r\n[Deployment] lasts 3 days\r\n[Deployment] starts at [Testing]'s end\r\n\r\n[Frontend] lasts 12 days\r\n[Frontend] starts at [Design]'s end\r\n[Backend] lasts 15 days\r\n[Backend] starts at [Design]'s end\r\n@enduml\r\n```\r\n\r\nKey syntax: `project starts YYYY-MM-DD`, `[Task] lasts N days`,\r\n`[Task] starts at [Other]'s end`, `--` separator for dependency,\r\n`printscale weekly/monthly`, `@dailymail`, `@weeklymail`\r\n\r\n### Mind Map\r\n\r\n```\r\n@startmindmap\r\ntitle System Architecture\r\n\r\n* Root Node\r\n** Level 1 A\r\n*** Level 2 A1\r\n*** Level 2 A2\r\n** Level 1 B\r\n*** Level 2 B1\r\n**** Level 3 B1a\r\n**** Level 3 B1b\r\n** Level 1 C\r\n@endmindmap\r\n```\r\n\r\nKey syntax: `*` root, `**` level 1, `***` level 2, etc.\r\nUse `@startmindmap` / `@endmindmap` (not `@startuml`).\r\nAffix `_` to markdown-style side notation, e.g., `***_ Right side node`.\r\nColors: ``\r\n\r\n---\r\n\r\n## OMG-UML / uml-diagrams.org Style Configuration (MANDATORY)\r\n\r\nEvery generated `.puml` file MUST include this CSS-style preamble immediately after `@startuml`.\r\nIt locks PlantUML's rendering to the **uml-diagrams.org reference style** (strict OMG UML 2.x,\r\nblack-and-white Visio stencils).\r\n\r\nSince PlantUML `1.2019.9` the project officially recommends the **CSS-like `\r\n\r\n' ── Per-element skinparam fallback (mandatory) ─────────────────────────────\r\n' The CSS ` is therefore\r\nmandatory — treat CSS and skinparam as **complementary layers**, not\r\nalternatives. Together they guarantee black borders + white fills for actor /\r\nusecase / rectangle / class / component / interface / package / node / database\r\n/ cloud / state / activity / sequence / note across every diagram type and both\r\nlight and dark backgrounds.\r\n\r\nThe **only** allowed `skinparam ... style` value is the default — do NOT add\r\n`skinparam style strictuml`. Even though `strictuml` sounds like a \"make it\r\nmore UML-compliant\" flag, in practice it:\r\n\r\n- collapses `actor Foo` from a stick figure into a plain text label\r\n- collapses `usecase \"X\" as UC` from an ellipse into a plain rectangle\r\n- removes the class-header separator line so name/attribute/method sections merge\r\n\r\nThe render script also **defensively strips** any leftover\r\n`skinparam style strictuml` line before dispatching to the backend, so\r\naccidental re-introductions from user edits or LLM output are neutralized at\r\nthe pipeline level.\r\n\r\n`skinparam classAttributeIconSize 0` is retained separately because it only\r\nremoves the colored visibility dots (●/◐/○) and has no side effects on shapes.\r\n\r\n### Common Failure Patterns\r\n\r\nSymptoms and their root cause — check this list first if a rendered diagram\r\nlooks visually wrong:\r\n\r\n| Symptom | Root cause | Fix |\r\n|---|---|---|\r\n| Actor rendered as bare text, no stick figure | `skinparam style strictuml` in the source | Remove the line; rely on the per-element skinparam fallback (the render script also auto-strips it). |\r\n| Use case rendered as a plain rectangle instead of an ellipse | Same as above (`strictuml`) | Same as above. |\r\n| Class header separator line missing / name+attributes merged | Same as above (`strictuml`) | Same as above. |\r\n| Ellipses / actor paths lose their black border on light background | CSS `\r\nskinparam classAttributeIconSize 0\r\n\r\ntitle Payment System\r\n\r\nclass User {\r\n +id: UUID\r\n +email: String\r\n +name: String\r\n +register()\r\n}\r\n\r\nclass Order {\r\n +id: UUID\r\n +total: Decimal\r\n +status: OrderStatus\r\n +calculateTotal()\r\n}\r\n\r\nclass PaymentProcessor <> {\r\n +processPayment(amount: Decimal): Boolean\r\n +refund(transactionId: UUID): Boolean\r\n}\r\n\r\nclass NotificationService <> {\r\n #enabled: Boolean\r\n +{abstract} send(to: String, body: String)\r\n}\r\n\r\nenum OrderStatus {\r\n PENDING\r\n CONFIRMED\r\n SHIPPED\r\n DELIVERED\r\n}\r\n\r\nUser \"1\" -- \"*\" Order : places\r\nOrder ..|> PaymentProcessor\r\nNotificationService <|-- EmailNotifier\r\n@enduml\r\n```\r\n\r\nKey syntax: `+` public, `-` private, `#` protected, `{abstract}` abstract method,\r\n`class Foo <>` (interface via text stereotype — NOT `interface Foo`),\r\n`class Bar <>` (abstract class — NOT `abstract class Bar`),\r\n`enum`, relationships: `--` association, `*--` composition, `o--` aggregation,\r\n`<|--` inheritance, `..|>` realization\r\n\r\n### Activity Diagram\r\n\r\n```\r\n@startuml\r\ntitle Order Processing\r\n\r\nstart\r\n:Receive Order;\r\nif (Payment Valid?) then (yes)\r\n :Reserve Inventory;\r\n if (Inventory Available?) then (yes)\r\n :Confirm Order;\r\n :Ship Order;\r\n stop\r\n else (no)\r\n :Notify Customer;\r\n :Cancel Order;\r\n stop\r\n endif\r\nelse (no)\r\n :Reject Order;\r\n stop\r\nendif\r\n@enduml\r\n```\r\n\r\nKey syntax: `start/stop/end`, `if/then/else/endif`, `repeat/repeat while`,\r\n`fork/fork again/end fork` (parallel), `split/split again/end split`,\r\n`partition \"name\" { ... }` (swimlane), `:Text;` action\r\n\r\n### Use Case Diagram\r\n\r\n```\r\n@startuml\r\ntitle E-Commerce System\r\n\r\nleft to right direction\r\n\r\nactor Customer\r\nactor Admin\r\n\r\nrectangle \"E-Commerce\" {\r\n usecase \"Browse Products\" as UC1\r\n usecase \"Place Order\" as UC2\r\n usecase \"Manage Inventory\" as UC3\r\n usecase \"Process Returns\" as UC4\r\n}\r\n\r\nCustomer --> UC1\r\nCustomer --> UC2\r\nAdmin --> UC3\r\nAdmin --> UC4\r\nUC2 ..> UC1 : <>\r\n@enduml\r\n```\r\n\r\nKey syntax: `actor`, `usecase`, `rectangle/package` for system boundary,\r\n`-->` association, `..>` dependency, `<>` / `<>` stereotypes\r\n\r\n### Component Diagram\r\n\r\n```\r\n@startuml\r\ntitle Microservice Architecture\r\n\r\npackage \"Frontend\" {\r\n [Web App]\r\n [Mobile App]\r\n}\r\n\r\npackage \"API Gateway\" {\r\n [Gateway]\r\n}\r\n\r\npackage \"Services\" {\r\n [User Service]\r\n [Order Service]\r\n [Payment Service]\r\n}\r\n\r\ndatabase \"PostgreSQL\" as DB\r\ncloud \"Message Queue\" as MQ\r\n\r\n[Web App] --> [Gateway]\r\n[Mobile App] --> [Gateway]\r\n[Gateway] --> [User Service]\r\n[Gateway] --> [Order Service]\r\n[Order Service] --> [Payment Service]\r\n[User Service] --> DB\r\n[Order Service] --> DB\r\n[Order Service] --> MQ\r\n@enduml\r\n```\r\n\r\nKey syntax: `[Component]`, `package \"name\" { }`, `database`, `cloud`, `node`,\r\n`frame`, `interface`, `()--` required interface, `--()` provided interface\r\n\r\n### Deployment Diagram\r\n\r\n```\r\n@startuml\r\ntitle Production Deployment\r\n\r\nnode \"AWS us-east-1\" {\r\n node \"VPC\" {\r\n node \"Public Subnet\" {\r\n [Load Balancer]\r\n [Bastion Host]\r\n }\r\n node \"Private Subnet\" {\r\n node \"App Server 1\" {\r\n [Application]\r\n }\r\n node \"App Server 2\" {\r\n [Application]\r\n }\r\n database \"RDS Primary\"\r\n }\r\n }\r\n cloud \"CDN\"\r\n}\r\n@enduml\r\n```\r\n\r\nKey syntax: `node \"name\" { }`, nested `node`, `database`, `cloud`, `actor`\r\n\r\n### State Diagram\r\n\r\n```\r\n@startuml\r\ntitle Order Lifecycle\r\n\r\n[*] --> Draft\r\nDraft --> Submitted : submit()\r\nSubmitted --> Paid : processPayment()\r\nSubmitted --> Cancelled : cancel()\r\nPaid --> Shipped : ship()\r\nShipped --> Delivered : confirmDelivery()\r\nDelivered --> [*]\r\nCancelled --> [*]\r\n\r\nstate Paid {\r\n [*] --> Authorizing\r\n Authorizing --> Captured : success\r\n Authorizing --> Failed : decline\r\n Captured --> [*]\r\n}\r\n@enduml\r\n```\r\n\r\nKey syntax: `[*]` start/end, `-->` transition with optional `: label`,\r\n`state Name { }` composite state, `state \"Name\" as Alias`\r\n\r\n### Gantt Chart\r\n\r\n```\r\n@startuml\r\ntitle Project Roadmap\r\n\r\nproject starts 2025-01-06\r\n\r\n[Design] lasts 10 days\r\n[Development] lasts 20 days\r\n[Development] starts at [Design]'s end\r\n[Testing] lasts 10 days\r\n[Testing] starts at [Development]'s end\r\n[Deployment] lasts 3 days\r\n[Deployment] starts at [Testing]'s end\r\n\r\n[Frontend] lasts 12 days\r\n[Frontend] starts at [Design]'s end\r\n[Backend] lasts 15 days\r\n[Backend] starts at [Design]'s end\r\n@enduml\r\n```\r\n\r\nKey syntax: `project starts YYYY-MM-DD`, `[Task] lasts N days`,\r\n`[Task] starts at [Other]'s end`, `--` separator for dependency,\r\n`printscale weekly/monthly`, `@dailymail`, `@weeklymail`\r\n\r\n### Mind Map\r\n\r\n```\r\n@startmindmap\r\ntitle System Architecture\r\n\r\n* Root Node\r\n** Level 1 A\r\n*** Level 2 A1\r\n*** Level 2 A2\r\n** Level 1 B\r\n*** Level 2 B1\r\n**** Level 3 B1a\r\n**** Level 3 B1b\r\n** Level 1 C\r\n@endmindmap\r\n```\r\n\r\nKey syntax: `*` root, `**` level 1, `***` level 2, etc.\r\nUse `@startmindmap` / `@endmindmap` (not `@startuml`).\r\nAffix `_` to markdown-style side notation, e.g., `***_ Right side node`.\r\nColors: ``\r\n\r\n---\r\n\r\n## OMG-UML / uml-diagrams.org Style Configuration (MANDATORY)\r\n\r\nEvery generated `.puml` file MUST include this CSS-style preamble immediately after `@startuml`.\r\nIt locks PlantUML's rendering to the **uml-diagrams.org reference style** (strict OMG UML 2.x,\r\nblack-and-white Visio stencils).\r\n\r\nSince PlantUML `1.2019.9` the project officially recommends the **CSS-like `\r\n\r\n' ── Per-element skinparam fallback (mandatory) ─────────────────────────────\r\n' The CSS ` is therefore\r\nmandatory — treat CSS and skinparam as **complementary layers**, not\r\nalternatives. Together they guarantee black borders + white fills for actor /\r\nusecase / rectangle / class / component / interface / package / node / database\r\n/ cloud / state / activity / sequence / note across every diagram type and both\r\nlight and dark backgrounds.\r\n\r\nThe **only** allowed `skinparam ... style` value is the default — do NOT add\r\n`skinparam style strictuml`. Even though `strictuml` sounds like a \"make it\r\nmore UML-compliant\" flag, in practice it:\r\n\r\n- collapses `actor Foo` from a stick figure into a plain text label\r\n- collapses `usecase \"X\" as UC` from an ellipse into a plain rectangle\r\n- removes the class-header separator line so name/attribute/method sections merge\r\n\r\nThe render script also **defensively strips** any leftover\r\n`skinparam style strictuml` line before dispatching to the backend, so\r\naccidental re-introductions from user edits or LLM output are neutralized at\r\nthe pipeline level.\r\n\r\n`skinparam classAttributeIconSize 0` is retained separately because it only\r\nremoves the colored visibility dots (●/◐/○) and has no side effects on shapes.\r\n\r\n### Common Failure Patterns\r\n\r\nSymptoms and their root cause — check this list first if a rendered diagram\r\nlooks visually wrong:\r\n\r\n| Symptom | Root cause | Fix |\r\n|---|---|---|\r\n| Actor rendered as bare text, no stick figure | `skinparam style strictuml` in the source | Remove the line; rely on the per-element skinparam fallback (the render script also auto-strips it). |\r\n| Use case rendered as a plain rectangle instead of an ellipse | Same as above (`strictuml`) | Same as above. |\r\n| Class header separator line missing / name+attributes merged | Same as above (`strictuml`) | Same as above. |\r\n| Ellipses / actor paths lose their black border on light background | CSS `\nskinparam style strictuml\nskinparam classAttributeIconSize 0\n\ntitle Payment System\n\nclass User {\n +id: UUID\n +email: String\n +name: String\n +register()\n}\n\nclass Order {\n +id: UUID\n +total: Decimal\n +status: OrderStatus\n +calculateTotal()\n}\n\nclass PaymentProcessor <> {\n +processPayment(amount: Decimal): Boolean\n +refund(transactionId: UUID): Boolean\n}\n\nclass NotificationService <> {\n #enabled: Boolean\n +{abstract} send(to: String, body: String)\n}\n\nenum OrderStatus {\n PENDING\n CONFIRMED\n SHIPPED\n DELIVERED\n}\n\nUser \"1\" -- \"*\" Order : places\nOrder ..|> PaymentProcessor\nNotificationService <|-- EmailNotifier\n@enduml\n```\n\nKey syntax: `+` public, `-` private, `#` protected, `{abstract}` abstract method,\n`class Foo <>` (interface via text stereotype — NOT `interface Foo`),\n`class Bar <>` (abstract class — NOT `abstract class Bar`),\n`enum`, relationships: `--` association, `*--` composition, `o--` aggregation,\n`<|--` inheritance, `..|>` realization\n\n### Activity Diagram\n\n```\n@startuml\ntitle Order Processing\n\nstart\n:Receive Order;\nif (Payment Valid?) then (yes)\n :Reserve Inventory;\n if (Inventory Available?) then (yes)\n :Confirm Order;\n :Ship Order;\n stop\n else (no)\n :Notify Customer;\n :Cancel Order;\n stop\n endif\nelse (no)\n :Reject Order;\n stop\nendif\n@enduml\n```\n\nKey syntax: `start/stop/end`, `if/then/else/endif`, `repeat/repeat while`,\n`fork/fork again/end fork` (parallel), `split/split again/end split`,\n`partition \"name\" { ... }` (swimlane), `:Text;` action\n\n### Use Case Diagram\n\n```\n@startuml\ntitle E-Commerce System\n\nleft to right direction\n\nactor Customer\nactor Admin\n\nrectangle \"E-Commerce\" {\n usecase \"Browse Products\" as UC1\n usecase \"Place Order\" as UC2\n usecase \"Manage Inventory\" as UC3\n usecase \"Process Returns\" as UC4\n}\n\nCustomer --> UC1\nCustomer --> UC2\nAdmin --> UC3\nAdmin --> UC4\nUC2 ..> UC1 : <>\n@enduml\n```\n\nKey syntax: `actor`, `usecase`, `rectangle/package` for system boundary,\n`-->` association, `..>` dependency, `<>` / `<>` stereotypes\n\n### Component Diagram\n\n```\n@startuml\ntitle Microservice Architecture\n\npackage \"Frontend\" {\n [Web App]\n [Mobile App]\n}\n\npackage \"API Gateway\" {\n [Gateway]\n}\n\npackage \"Services\" {\n [User Service]\n [Order Service]\n [Payment Service]\n}\n\ndatabase \"PostgreSQL\" as DB\ncloud \"Message Queue\" as MQ\n\n[Web App] --> [Gateway]\n[Mobile App] --> [Gateway]\n[Gateway] --> [User Service]\n[Gateway] --> [Order Service]\n[Order Service] --> [Payment Service]\n[User Service] --> DB\n[Order Service] --> DB\n[Order Service] --> MQ\n@enduml\n```\n\nKey syntax: `[Component]`, `package \"name\" { }`, `database`, `cloud`, `node`,\n`frame`, `interface`, `()--` required interface, `--()` provided interface\n\n### Deployment Diagram\n\n```\n@startuml\ntitle Production Deployment\n\nnode \"AWS us-east-1\" {\n node \"VPC\" {\n node \"Public Subnet\" {\n [Load Balancer]\n [Bastion Host]\n }\n node \"Private Subnet\" {\n node \"App Server 1\" {\n [Application]\n }\n node \"App Server 2\" {\n [Application]\n }\n database \"RDS Primary\"\n }\n }\n cloud \"CDN\"\n}\n@enduml\n```\n\nKey syntax: `node \"name\" { }`, nested `node`, `database`, `cloud`, `actor`\n\n### State Diagram\n\n```\n@startuml\ntitle Order Lifecycle\n\n[*] --> Draft\nDraft --> Submitted : submit()\nSubmitted --> Paid : processPayment()\nSubmitted --> Cancelled : cancel()\nPaid --> Shipped : ship()\nShipped --> Delivered : confirmDelivery()\nDelivered --> [*]\nCancelled --> [*]\n\nstate Paid {\n [*] --> Authorizing\n Authorizing --> Captured : success\n Authorizing --> Failed : decline\n Captured --> [*]\n}\n@enduml\n```\n\nKey syntax: `[*]` start/end, `-->` transition with optional `: label`,\n`state Name { }` composite state, `state \"Name\" as Alias`\n\n### Gantt Chart\n\n```\n@startuml\ntitle Project Roadmap\n\nproject starts 2025-01-06\n\n[Design] lasts 10 days\n[Development] lasts 20 days\n[Development] starts at [Design]'s end\n[Testing] lasts 10 days\n[Testing] starts at [Development]'s end\n[Deployment] lasts 3 days\n[Deployment] starts at [Testing]'s end\n\n[Frontend] lasts 12 days\n[Frontend] starts at [Design]'s end\n[Backend] lasts 15 days\n[Backend] starts at [Design]'s end\n@enduml\n```\n\nKey syntax: `project starts YYYY-MM-DD`, `[Task] lasts N days`,\n`[Task] starts at [Other]'s end`, `--` separator for dependency,\n`printscale weekly/monthly`, `@dailymail`, `@weeklymail`\n\n### Mind Map\n\n```\n@startmindmap\ntitle System Architecture\n\n* Root Node\n** Level 1 A\n*** Level 2 A1\n*** Level 2 A2\n** Level 1 B\n*** Level 2 B1\n**** Level 3 B1a\n**** Level 3 B1b\n** Level 1 C\n@endmindmap\n```\n\nKey syntax: `*` root, `**` level 1, `***` level 2, etc.\nUse `@startmindmap` / `@endmindmap` (not `@startuml`).\nAffix `_` to markdown-style side notation, e.g., `***_ Right side node`.\nColors: ``\n\n---\n\n## OMG-UML / uml-diagrams.org Style Configuration (MANDATORY)\n\nEvery generated `.puml` file MUST include this CSS-style preamble immediately after `@startuml`.\nIt locks PlantUML's rendering to the **uml-diagrams.org reference style** (strict OMG UML 2.x,\nblack-and-white Visio stencils).\n\nSince PlantUML `1.2019.9` the project officially recommends the **CSS-like `\n\n' Two settings still have NO CSS equivalent yet — keep them as skinparams:\nskinparam style strictuml\nskinparam classAttributeIconSize 0\n```\n\n**What each CSS block does (mapped to uml-diagrams.org figures):**\n\n| CSS Block | Effect / uml-diagrams.org reference |\n|---|---|\n| `root` | Global defaults: Helvetica 12px black-on-white, 0.75pt lines, no shadows, square corners. Matches Visio UML 2.x stencil look. |\n| `root > Shadowing 0` | Disables drop shadows — uml-diagrams.org figures never have shadows. |\n| `root > RoundCorner 0` | Square corners on rectangles (matches Visio stencils). `activityDiagram.activity` overrides to `10` for round-cornered actions. |\n| `title` | Bold 14px black text, transparent background/border. |\n| `note` | White fill, black border, black text — matches uml-diagrams.org note style. |\n| `sequenceDiagram.lifeLine` | **Dashed black lines** (`LineStyle 5-5`) — exactly the lifeline notation on uml-diagrams.org/sequence-diagrams.html. |\n| `sequenceDiagram.arrow` | Thin black arrows (0.75pt) — matches Visio stencil hair-line strokes. |\n| `classDiagram.class` | White fill, black border — no grey fills. |\n| `activityDiagram.activity` | White fill with **round corners** (`RoundCorner 10`) — matches uml-diagrams.org activity shape. |\n| `activityDiagram.diamond` | White fill, black border for decision/merge diamonds. |\n| `useCaseDiagram` | White actors, use cases, and rectangles — no colored fills. |\n| `componentDiagram` | White components and packages — no colored fills. |\n| `stateDiagram.state` | White fill, black border — no grey fills. |\n\n**Two skinparam settings have NO CSS equivalent yet** (as of PlantUML 1.2026.x):\n- `skinparam style strictuml` — enforces text stereotypes (`«interface»`, `«abstract»`, `«enumeration»`) and removes circle adornments\n- `skinparam classAttributeIconSize 0` — removes coloured visibility dots (●/◐/○)\n\nThese must remain as `skinparam` lines beside the `