SOLECA794
@SOLECA794
Public Skills
debug-principles
by SOLECA794
Use when debugging kernel, LTP, QEMU, runner, rootfs, or architecture-specific failures, especially large or mixed failure sets. Guides progressive failure indexing, small-batch root-cause iteration, failure-set diffing, and correct write-back.
development-workflow
by SOLECA794
Use when classifying, planning, documenting, reviewing, promoting, or closing development work across patches, small change records, and RFCs. Enforces minimal artifact selection, Implementation Boundary, cutover honesty, and architecture-friction closeout.
evidence-discipline
by SOLECA794
Use when producing performance conclusions, running A/B experiments, interpreting profiling artifacts, or making any claim that must be reproducible. Enforces evidence hierarchy, fixed experiment topology, SHA-256 identity, denominator honesty, and write-back rules.
code-review-principles
by SOLECA794
Use when reviewing kernel changes, running periodic engineering audits of a subsystem, or writing review guidance for agents. Focus on architecture, owner boundaries, local semantic integrity, concurrency, ABI containment, resource lifetime, failure paths, and justified complexity — not syntax.