rootnode-domain-software-engineeringlisted

Specialized software engineering prompt methodology for Claude. Use when building prompts for system design, code review, incident response, security analysis, API design, architecture decisions, RFCs, ADRs, runbooks, or technical leadership. Trigger on: "build a prompt for code review," "system design prompt," "SRE prompt," "security review prompt," "incident response prompt," "API design prompt," "architecture decision prompt," "RFC prompt," "runbook prompt." Provides 11 tested approaches across identity, reasoning, and output for engineering analysis. Do NOT use for general coding help, writing code, or debugging — this builds prompts that shape engineering analysis, not code itself. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available).
drayline/rootnode-skills · ★ 40 · AI & Automation · score 76

Install: claude install-skill drayline/rootnode-skills

# Software Engineering Prompt Methodology > **Calibration:** Tier 1 (Model-compatible) - runs cleanly on the current dual-primary tier (Opus 5, Sonnet 5) as well as Haiku 4.5 with extended thinking. Structured retrieval, rule evaluation, or template lookup - output shape does not depend on model class. Correct-shape output also on Opus 4.8 (fallback-graceful) and Sonnet 4.6 (legacy-graceful). See repository README for model compatibility. Specialized approaches for building Claude prompts that handle software engineering tasks — reliability engineering, security analysis, code review, API design, performance analysis, threat modeling, and engineering document formats (RFCs, ADRs, runbooks, code review feedback). **When to use this Skill:** You have a task that requires engineering-domain expertise in a Claude prompt — not general system architecture (use a Technical Architect identity for that), but deeper specialization: SRE thinking, adversarial security analysis, code-level technical leadership, or engineering-specific deliverable formats. **What this Skill provides:** - 3 identity approaches (SRE / Platform Engineer, Security Engineer, Staff+ Engineer / Tech Lead) - 4 reasoning methodologies (Code & Design Review, API Design, Performance & Scalability Analysis, Threat Modeling) — see `references/reasoning-approaches.md` - 4 output format specifications (RFC, ADR, Runbook, Code Review Feedback) — see `references/output-formats.md` - Behavioral countermeasures for engin