What This Skill Does

Prerequisites

• Name which part of this move is real tool use versus battle-chip framing before you act.
• These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

Operator Inputs

• Name the critical surface Hermes needs to protect from constant touches: focus block, approval lane, endpoint, queue, review path, or live decision channel.
• Describe the low-commitment contact pattern you want to reject or surface: pings, retries, speculative asks, spammy requests, opportunistic edits, or constant probes.
• State what should happen on contact: bounce, alert, log, throttle, queue for later, or force escalation to a narrower channel.
• Say what level of interruption is still acceptable while the charged perimeter is active.

Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Collect the operator inputs below so the chip lands on the right panel.
3. Name the exact work surface or focus window that keeps getting touched by low-commitment interference.
4. Define what kinds of contact should be bounced, rate-limited, escalated, logged, or forced to declare themselves.
5. Raise the charged perimeter, then use the protected interval to advance the real work while triaging only the contacts that prove they are worth a turn.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A charged defensive layer that rejects or surfaces low-grade interruptions around the named target surface.
• A short note on what kinds of contact now bounce off, what kinds still break through, and what signals Hermes will treat as meaningful.

Output Contract

• A clear perimeter rule set for what kinds of contact are ignored, bounced, surfaced, or allowed through.
• An explanation of how Elec Aura preserves operator focus or workflow integrity by making casual touches costly.
• A concrete distinction between incidental noise, meaningful escalation, and truly authorized access.
• A handoff condition for when the charged posture should relax or convert into a different form of defense.

Do Not Use For

• General calming or de-escalation problems better handled by Aqua Aura.
• Defenses whose main value comes from automatic counterattack after absorbing hits, which are closer to Leaf Shield.
• Cases where the real requirement is a safe repair zone or recovery patch rather than a charged perimeter.

Pair With

• Elec Aura + North Wind: shock away casual interference at the perimeter, then strip the one remaining obstructive shield blocking clean contact.
• Elec Aura + Barrier: use Elec Aura to reject probes and interruptions, then add Barrier if one heavy committed hit is still expected.
• Elec Aura + Full Custom: stabilize the focus window against interruption, then redraw and spend the hand while the perimeter is still charged.

Pitfalls / Guardrails

• Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
• Elec Aura is for preserving a defended edge against probing contact, not for retaliatory overreach.
• Do not use a charged perimeter if legitimate collaborators need frictionless access and you cannot distinguish friend from foe.
• If the response path for contact is not explicit, the aura becomes noise instead of protection.
• Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

Verification

• Check that the response includes every promised deliverable and leaves an inspectable audit trail.
• Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
• Confirm the response names a real interruption or probe pattern rather than a generic threat.
• Confirm the proposed aura makes contact legible by rejection, escalation, or surfacing, not merely by vague hardening language.
• Confirm the operator can tell what gets bounced, what gets through, and when the charged posture should end.
• Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Elec Aura on this approval path: reject casual interruptions, force meaningful requests to declare themselves, and preserve a clean focus window for the actual decision.
Use Elec Aura here so every low-grade probe either bounces or becomes visible immediately, instead of stealing attention a dozen times.