Arcana
Apply deep technical knowledge to understand how systems work under the hood.
What This Skill Does
In D&D, Arcana is knowledge of magic, its traditions, symbols, and mechanisms. The real-world version is deep technical literacy: understanding how software architectures work, what protocols do at the wire level, how APIs behave beyond their documentation, and what the actual mechanisms are behind the abstractions everyone else takes on faith.
In this grimoire, Arcana is treated as a metaphorical skill with a shipping-now delivery profile.
Canonical reference input: Arcana (skill).
When To Use
- A technical system needs to be understood at a level deeper than its documentation provides.
- You need to explain how something actually works — not what it claims to do, but what it does.
- A debugging or architecture question requires knowledge of underlying mechanisms, not just surface APIs.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the system, protocol, or technology to analyze.
- Explain the mechanism at the appropriate depth: not the marketing version, but how it actually works.
- Surface non-obvious implications, edge cases, or failure modes that follow from the mechanism.
- Deliver the explanation with a clear note on what is documented fact vs. observed behavior vs. inference.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A mechanistic explanation of how the system actually works under the hood.
- Non-obvious implications or edge cases that follow from the mechanism.
- A confidence note: what is documented, what is observed, and what is inferred.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not confuse documentation with behavior. The docs say what it should do; arcana reveals what it does.
- Clearly separate established knowledge from speculation when reasoning about undocumented behavior.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/arcana explain how this [system/protocol/technology] actually works under the hood, beyond what the documentation says
1---2name: arcana-23description: In D&D, Arcana is knowledge of magic, its traditions, symbols, and mechanisms. The real-world version is deep technical literacy: understanding how software architectures work, what protocols do at the wire level, how APIs behave beyond their documentation, and what the actual mechanisms are behind the abstractions everyone else takes on faith.4license: CC0-1.05---6# Arcana7Apply deep technical knowledge to understand how systems work under the hood.8## What This Skill Does9In D&D, Arcana is knowledge of magic, its traditions, symbols, and mechanisms. The real-world version is deep technical literacy: understanding how software architectures work, what protocols do at the wire level, how APIs behave beyond their documentation, and what the actual mechanisms are behind the abstractions everyone else takes on faith.10In this grimoire, Arcana is treated as a metaphorical skill with a shipping-now delivery profile.11Canonical reference input: Arcana (skill).12## When To Use1314- A technical system needs to be understood at a level deeper than its documentation provides.15- You need to explain how something actually works — not what it claims to do, but what it does.16- A debugging or architecture question requires knowledge of underlying mechanisms, not just surface APIs.1718## Prerequisites1920- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.2122## Procedure23241. Restate the target, the success condition, and any no-touch boundaries before taking action.252. Identify the system, protocol, or technology to analyze.263. Explain the mechanism at the appropriate depth: not the marketing version, but how it actually works.274. Surface non-obvious implications, edge cases, or failure modes that follow from the mechanism.285. Deliver the explanation with a clear note on what is documented fact vs. observed behavior vs. inference.296. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.3031## Deliverables3233- A mechanistic explanation of how the system actually works under the hood.34- Non-obvious implications or edge cases that follow from the mechanism.35- A confidence note: what is documented, what is observed, and what is inferred.3637## Pitfalls / Guardrails3839- Keep the metaphor anchored to a real mechanism instead of drifting into lore.40- Do not confuse documentation with behavior. The docs say what it should do; arcana reveals what it does.41- Clearly separate established knowledge from speculation when reasoning about undocumented behavior.4243## Verification4445- Check that the result includes every deliverable promised above.46- Check that confirmed facts, assumptions, and inferences are visibly separated.47- Check that the metaphor still maps cleanly to a real operational mechanism.4849## Example Invocation50```text51/arcana explain how this [system/protocol/technology] actually works under the hood, beyond what the documentation says52```
Hmbown