balsm-health

Decide whether full DDD is worth it, then plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture (CQRS, event sourcing, sagas, projections). Use for the up-front viability check and staged planning; for the in-depth DDD manual (bounded contexts, aggregates, ubiquitous language, repositories) use domain-driven-design.

Use this skill to generate well-branded interfaces and assets for Balsm.health (بَلسَم) — the community-owned healthcare OS for the Arab world. Includes the official five-petal flower mark, the five-color petal palette, warm olive-gray neutrals, type system (Montserrat / IBM Plex Sans / IBM Plex Sans Arabic / Cairo / IBM Plex Mono), Lucide iconography, a Pharmacy POS UI kit (Slice 1), and a Patient App prototype (Slice 2). Brand promise: "Your care. Your data. Your system." Three words: Open. Arab. Owned.

Produce a comprehensive STRIDE-based threat model for a healthcare or other regulated software system, covering cybersecurity, application security, and AI/ML security in one unified document. Use this whenever the user asks for a threat model, security analysis, STRIDE catalog, security review of an architecture, "what could go wrong" analysis, or risk assessment of a healthcare/clinical/pharmacy/EHR/EMR/medical/fintech/government system — even if they don't say "STRIDE" or "threat model" explicitly. Also trigger when a user shares system requirements, an architecture doc, a phased roadmap, or a compliance review and asks about security or threats. The output is a single markdown document the team can drop into their docs folder.