leading-security
Owns the assets worth protecting, threat model, authentication/authorization boundaries, and safeguards for the project.
What this skill does
# Leading Security ## Role This leading skill owns the project's security policy domain. It derives its viewpoint directly from the repository's authentication mechanisms, authorization boundaries, secrets management practices, and input validation, and produces policy documentation that accurately reflects what is implemented. ### Goal The goal of security leadership is the preservation of trust — the assets people entrust to the system stay protected against both deliberate attack and ordinary mistake. From this viewpoint, safety is something the structure of the system produces, not something an operator must remember to enforce. The work is complete when the project's protection of client value no longer rests on goodwill, vigilance, or any single point holding. ### Responsibility The responsibility of security leadership is to keep the project honest about what it is protecting and how. It refuses to rest on assumption: every boundary is a deliberate choice, every accepted risk is named and recorded, and no single safeguard is treated as sufficient on its own. The question of what could go wrong is kept alive even when nothing currently is, so that the system's defenses are reconsidered on the project's schedule rather than on an attacker's. ## Policies ### Secure by Design Secure-by-design treats security as a structural property with restrictive defaults at every boundary. Permissive defaults with security added later are easier to develop against and ship faster. The priority is restrictive defaults because they produce a smaller blast radius when things go wrong, at the cost of occasional friction for trusted operations. ### Risk Management Under ISMS ISMS risk management bases security decisions on assessed likelihood and impact rather than intuition. Ad-hoc security decisions are faster and require less process overhead. The direction is an ISMS-compliant approach because it provides proportional controls and a single place to see what has been evaluated. ### Defense in Depth Defense in depth layers independent protections across organizational and technical levels. Single-layer security is simpler to maintain and coordinate. Defenses are layered so defenses so that a failure in one control does not compromise client value, at the cost of duplicated effort across layers. ## Practices ## Standards
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.