Using Archon — The Gatekeeper
> **Type:** Meta-process (always active)
Best use case
Using Archon — The Gatekeeper is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
> **Type:** Meta-process (always active)
Teams using Using Archon — The Gatekeeper should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/using-superpowers/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Using Archon — The Gatekeeper Compares
| Feature / Agent | Using Archon — The Gatekeeper | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
> **Type:** Meta-process (always active)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Using Archon — The Gatekeeper > **Type:** Meta-process (always active) > **Priority:** CRITICAL — fires before every response > **Category:** Enforcement ## Iron Law ``` CHECK FOR APPLICABLE SKILLS BEFORE EVERY RESPONSE — EVEN A 1% CHANCE MEANS INVOKE ``` ## Purpose This meta-skill ensures that every agent response is informed by the relevant skills in the Archon framework. It prevents the common failure mode where agents "go rogue" and ignore available skills, processes, and guardrails. ## The Protocol Before responding to ANY user message: 1. **SCAN** — Review the user's request against all installed skills 2. **MATCH** — Identify which skills apply (even partially — 1% chance = invoke) 3. **PRIORITIZE** — Process skills before implementation skills: - Design skills (brainstorming) → before planning - Planning skills (writing-plans) → before implementation - Testing skills (TDD) → before writing production code - Verification skills → before claiming completion 4. **INVOKE** — Read and follow the matched skill(s) 5. **RESPOND** — Now respond, guided by the skill content ## Skill Priority Order ``` 1. brainstorming → Design FIRST (any creative/feature work) 2. using-git-worktrees → Isolate workspace (before implementation) 3. writing-plans → Break into TDD tasks (before coding) 4. subagent-driven-dev → Execute with subagents + 2-stage review 5. executing-plans → Fallback if no subagents 6. test-driven-development → RED-GREEN-REFACTOR (any code) 7. verification-before-completion → Before claiming "done" 8. finishing-a-dev-branch → Merge / PR / Cleanup ``` ## Red Flags — Thoughts That Mean STOP | Thought | Reality | |---------|---------| | "This is just a simple question" | Questions are tasks. Check for skills. | | "I need more context first" | Skill check comes BEFORE clarifying questions. | | "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. | | "I can check git/files quickly" | Files lack conversation context. Check for skills. | | "This doesn't need a formal skill" | If a skill exists, use it. Period. | | "I already know how to do this" | Your knowledge may be outdated. Skills are current. | ## Subagent Exception Subagents dispatched for specific tasks (implementer, reviewer, etc.) do NOT run this meta-check — they have focused jobs with pre-assigned skills. Only the main orchestrating agent uses this gatekeeper. ## Integration - **Hooks:** The `session-start` hook injects this skill's content at session beginning - **Synapses:** Works with `anti-rationalization` to prevent skill-skipping excuses - **Pipeline:** Not a pipeline step — it's a pre-step check that runs everywhere
Related Skills
Using Git Worktrees — The Isolator
> **Type:** Rigid
archon-scout
Scout Intelligence Pipeline — deep multi-source research with parallel web fetching, evidence validation, and synthesis into actionable briefs. Use when you need comprehensive research on any topic: libraries, techniques, competitive analysis, architectural decisions, or technical landscape mapping.
Archon Adversarial Review
> Spawn an independent Opus sub-agent to stress-test Archon's architecture, hooks, synapses, and framework evolution decisions against its own design principles.
YAML Prompt Library
> Store reusable AI prompts as YAML files with structured messages, variables, and test data for version-controlled prompt engineering.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Writing Plans — TDD-Sized Task Breakdown
> **Type:** Rigid process (follow structure exactly)
wireframing
Wireframing patterns including layout grids, content blocks, responsive breakpoints, and page layout patterns for landing pages, dashboards, and forms. Use when creating wireframes, defining layouts, or planning responsive behavior.
windows-registry-editor
Expert Windows Registry editor and optimizer via PowerShell. Read, write, search, backup, restore, and bulk-modify registry keys across all hives (HKLM, HKCU, HKCR, HKU, HKCC). Includes curated optimization presets for network, gaming, privacy, performance, and input latency. Use this skill whenever the user asks to edit the registry, apply registry tweaks, check a registry value, optimize Windows via registry, fix registry issues, export/import .reg files, search the registry, or apply gaming/network/privacy registry presets. Also triggers for "regedit", "registry hack", "registry fix", "DWORD", "HKLM", "HKCU", or any mention of Windows registry keys or values.
windows-network-optimizer
Diagnose, optimize, and verify Windows 11 network and system performance via PowerShell. Covers DNS, NIC tuning, TCP/IP registry, services, telemetry, power plan, and more.
windows-error-debugger
Diagnose, debug, and fix Windows crashes, BSODs, driver failures, and system errors via PowerShell. Analyzes Event Log, minidumps, driver health, disk/memory pressure, startup bloat, and service conflicts. Builds a growing knowledge base of resolved issues per machine. Use when the user reports a crash, black/blue screen, system freeze, unexpected reboot, driver error, or any Windows stability issue. Also triggers for "BSOD", "blue screen", "black screen", "crash", "system error", "bugcheck", "minidump", "driver failure", "unexpected shutdown", "paging file too small", "system hang", "Windows froze", "PC crashed", "kernel error", or any mention of Windows Event Log errors.
White-Label Config
> Transform any application into a customizable, self-hostable product with typed configuration, feature flags, and runtime env overrides.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.