Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
This meta-skill routes you to the right security architecture skills based on your situation. Load this skill when you need security expertise but aren't sure which specific security skill to use.
Core Principle: Different security tasks require different skills. Match your situation to the appropriate skill, load only what you need.
When to Use
Load this skill when:
Starting any security-related task
User mentions: "security", "threat", "authentication", "authorization", "compliance", "classified", "review this design"
You recognize security implications but unsure which skill applies
You need to document security decisions
Don't use for: Simple features with no security implications (e.g., UI styling, basic CRUD with existing auth)
How to Access Reference Sheets
IMPORTANT: All reference sheets are located in the SAME DIRECTORY as this SKILL.md file.
When this skill is loaded from:
skills/using-security-architect/SKILL.md
Reference sheets like threat-modeling.md are at:
skills/using-security-architect/threat-modeling.md
NOT at:
skills/threat-modeling.md ← WRONG PATH
When you see a link like [threat-modeling.md](threat-modeling.md), read the file from the same directory as this SKILL.md.
Routing by Situation
New System Design
Symptoms: "Design a new...", "We're building...", "Greenfield project"
Wrong: Load all 8 security-architect skills for every security task
Right: Load only the skills your situation needs (use decision tree)
❌ Skipping Threat Modeling
Wrong: Jump straight to implementation for new security features
Right: Always threat model first for new systems/features
❌ Using Core Skills for Specialized Contexts
Wrong: Use generic threat modeling for classified systems
Right: Load classified-systems-security for MLS contexts
❌ Not Cross-Referencing Muna
Wrong: Write security docs without documentation structure skills
Right: Load both ordis/documenting-threats + muna/documentation-structure
Examples
Example 1: Payment Processing System
User: "Design a payment processing microservice"
Your routing:
1. Recognize: New system + financial domain → security critical
2. Load: threat-modeling (identify payment-specific threats)
3. Load: secure-by-design-patterns (encryption, secrets management)
4. Load: security-controls-design (PCI-DSS controls)
5. Consider: compliance-awareness-and-mapping (PCI-DSS is compliance requirement)
Example 2: Simple Feature (No Security Needed)
User: "Add a favorites button to the UI"
Your routing:
1. Recognize: UI feature, uses existing auth, no new security surface
2. Decision: No security skills needed
3. Proceed with standard implementation
Example 3: Classified System Architecture
User: "Review architecture for system handling SECRET and UNCLASSIFIED data"
Your routing:
1. Recognize: Classified context (SECRET mentioned) + review task
2. Load: classified-systems-security (MLS patterns required)
3. Load: architecture-security-review (review process)
4. Load: threat-modeling (if threats not already modeled)
Phase 1 Note
Currently Available (Phase 1):
✅ using-security-architect (this skill)
✅ threat-modeling (in progress)
Coming Soon (Phases 2-3):
security-controls-design
architecture-security-review
secure-by-design-patterns
classified-systems-security
compliance-awareness-and-mapping
security-authorization-and-accreditation
documenting-threats-and-controls
For Phase 1: Focus on threat-modeling as primary skill. Reference other skills by name even though they're not implemented yet - this tests the routing logic.
Summary
This skill maps your situation → specific security skills to load.
Identify your situation (new system, review, specialized context)
Use decision tree to find applicable skills
Load core skills for universal needs
Add extension skills for specialized contexts
Cross-reference Muna for documentation needs
Don't load security skills when not needed
Meta-rule: When in doubt, start with threat-modeling.md. Threats drive everything else.
Security Architect Specialist Skills Catalog
After routing, load the appropriate specialist skill for detailed guidance:
