cli-designDesign command-line applications in any language — the interface layer (flags, help, human vs machine output, exit codes, prompting, config precedence) and the program layer (command trees, application context, error and exit policy, config and output boundaries). Use whenever you write, extend, rev
code-craftsmanshipStructure code and its files — repo layout, file naming, module shape, symbol naming — for TypeScript/React, Python, Go, PHP and Rust. Use whenever you write, scaffold or refactor source code, and when the user asks for clean or idiomatic code or wants a codebase restructured.
device-rootingGain root on embedded devices the user owns — IP cameras, IoT appliances, routers — by modifying vendor firmware and flashing it through the safest path. Identify the platform, parse the firmware container, patch the rootfs, verify offline under emulation, flash patiently, then harden with a recover
fork-stewardshipManage forks of third-party projects — choose Embrace vs. Decomposition, set up upstream/origin topology, sync or backport upstream changes, keep a divergence ledger, decide what to contribute back. Use when the user plans, creates or maintains a fork, or asks whether to fork at all.
health-critical-auditAudit an application whose content can affect health outcomes — first-aid guides, triage or symptom-checker flows, emergency features: trace every instruction to a named clinical source, gate-check the AI safety rails, verify the emergency-call UX, and flag MDR/ISO-14971/GDPR gaps in a severity-rank
layout-forensicsFind the cause behind a rendered-UI defect: which rule in which stylesheet sets a value, which cascade layer should own the fix, whether the rule exists at all, and which non-spacing culprits produce spacing symptoms. Use when a visual bug survives the obvious fix, or when a design system and the si
product-ui-designUse whenever building or restyling a web UI that people operate rather than are sold to (admin consoles, dashboards, settings, internal tools), when a header, status bar or detail view needs deciding, when a screen feels empty, or when IDs, states or long values need rendering. Tells product UIs fro
project-conceptionShape an idea into a plannable concept – a new project (landscape, scope, MVP, architecture, stack) or a feature inside an existing codebase (surface inventory, wiring vs. building). Use when the user asks whether to build something, what the MVP is, how to scope it or fit X into Y, or names a produ
reverse-engineeringRecover layouts, addresses and behaviour from native and .NET binaries for interoperability (a plugin, a compatible server, a data reader) with radare2, Ghidra headless and ilspycmd, reading decompiled C instead of disassembly and verifying every claim live; routes Electron, Android and web targets
service-application-designWhat a long-running service owes its operator — schema migrations and startup behaviour, health checks, graceful shutdown, environment configuration, and an install path that works on a fresh system. Use when building or reviewing a service application: adding a database schema, wiring the startup s
spec-writingWrite, review, and improve protocol specifications, technical standards, and RFC-style documents — structure, normative prose (MUST/SHOULD/MAY), scope, terminology, examples, versioning. Use from the first draft on and when reviewing or restructuring an existing spec; feature specs bound for an issu
style-passSweep a rendered UI for style defects and fix them: spatial audit, token drift, cause-and-layer diagnosis for whatever survives, then the pre-ship gate. Use when the request is broad — "check the styling", "polish this", "does the look hold together" — rather than aimed at one known defect.
web-complianceMake a website legally compliant for the German-speaking market and the EU: Impressum per legal form and country (DE/AT/CH), consent with orestbida/cookieconsent v3 that blocks scripts until opt-in, and a Datenschutzerklärung derived from the third-party services the code really loads. Use when buil