cyber-physical
Cyber-physical / industrial control system (ICS-SCADA) architecture in general: the Purdue model levels, control loops, IT/OT convergence, OT security (IEC 62443, segmentation, zero-trust for OT), safety, determinism, and redundancy. Architect-level, beyond any specific DCS/PLC product. USE WHEN: designing/evaluating industrial control, SCADA, robotics, energy, automotive, or IoT-at-scale systems, "OT security", "Purdue model", "PLC/RTU/ SCADA architecture", "IT/OT convergence", "IEC 62443", "control loop", safety instrumented systems. DO NOT USE FOR: specific DCS platforms / IEC 61131 / ISA formats (use the `industrial/*` skills); pure RTOS scheduling (use `embedded-rtos`); app security (use `security-architecture`).
What this skill does
# Cyber-Physical / ICS-SCADA Architecture (general) Generalizes the product-specific `industrial/*` skills (DCS, IEC 61131, ISA) into engine-agnostic control-system design. A cyber-physical system couples **computation with physical processes** through sensors and actuators in closed control loops, where a software fault can have physical consequences. ## The Purdue reference model (segment by level) ``` L5/4 Enterprise / MES / ERP (IT) ------------------- IT/OT boundary (DMZ) ------------------- L3 Operations / historians / engineering workstations L2 SCADA / HMI / supervisory control L1 Controllers: PLC / RTU / DCS L0 Field devices: sensors, actuators, drives (physical process) ``` Architecture is organized by these levels; the **IT/OT boundary** is the critical trust boundary to design and defend. ## Defining constraints - **Determinism & real-time**: control loops have hard cycle times and deadlines (see `embedded-rtos`); jitter degrades control. - **Safety**: safety-instrumented systems (SIS) are separated from control; fail-safe/fail-operational design, redundancy (TMR), and standards like IEC 61508 / 61511. - **Availability over confidentiality**: unlike IT, OT prioritizes uptime and safety — you cannot just patch/reboot a running plant. ## OT security (IT/OT convergence) - The **air gap is largely a myth** now — connectivity for analytics/remote ops is pervasive. Design for it. - **IEC 62443** is the reference standard. Apply **zone-and-conduit segmentation**, an IT/OT DMZ, least-privilege, and increasingly **zero-trust for OT** (authenticate every cross-zone flow). Pairs with `security-architecture`. - Legacy devices have weak/no auth → compensate with network segmentation, monitoring, and protocol-aware firewalls rather than assuming endpoint security. ## Guidance Treat the IT/OT boundary as the primary trust boundary; segment by Purdue level; keep safety functions independent and redundant; design for determinism and availability first; and assume connectivity — secure it (IEC 62443) rather than relying on isolation.
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.