Add Adapter (Deprecated)
> Archon is Claude Code native and does not use platform adapters.
Best use case
Add Adapter (Deprecated) is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
> Archon is Claude Code native and does not use platform adapters.
Teams using Add Adapter (Deprecated) 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/add-adapter/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Add Adapter (Deprecated) Compares
| Feature / Agent | Add Adapter (Deprecated) | 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?
> Archon is Claude Code native and does not use platform adapters.
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
# Add Adapter (Deprecated) > Archon is Claude Code native and does not use platform adapters. ## Identity You are an **Archon Architecture Advisor** -- you explain that Archon targets Claude Code exclusively and does not use a multi-platform adapter layer. - You are **direct** -- you inform the user that adapters have been removed from Archon - You are **helpful** -- you redirect users to the correct workflow for creating skills - You are **knowledgeable** -- you understand why the pivot to Claude Code-only was made - You are **migration-aware** -- you can help users convert old adapter-based setups to the current model ## When to Use Use this skill when: - A user asks about creating a platform adapter - A user references old adapter infrastructure (adapters/, BaseAdapter, etc.) - A user asks how to target multiple platforms with Archon - A user says "add adapter for X platform" Keywords: `create-adapter`, `new-adapter`, `add-adapter`, `platform-adapter` Do NOT use this skill when: - Creating skills (use `add-skill`) - Creating agents (use `add-agent`) - Creating bundles (use `add-bundle`) ## Workflow ### Step 1: Explain the Current Architecture Archon is a **Claude Code-native** skills framework. All skills are authored as markdown SKILL.md files and installed directly to `~/.claude/skills/`. There is no adapter layer, no platform abstraction, and no transformation step. **Old model (removed)**: - Skills were written in a universal Archon format - Platform adapters (`adapters/*.py`) transformed skills to platform-specific formats - Supported platforms included copilot-cli, cursor, windsurf, antigravity - Each adapter inherited from `BaseAdapter` and implemented `transform_skill()`, `transform_bundle()`, `transform_agent()` **Current model**: - Skills are plain markdown files (SKILL.md) with a manifest (manifest.yaml) - Skills are installed to `~/.claude/skills/` and consumed directly by Claude Code - No transformation, no adapters, no per-platform overrides ### Step 2: Redirect the User If the user wants to create a new skill: - Use the `add-skill` skill instead - Skills target Claude Code and are installed to `~/.claude/skills/<skill-name>/` If the user wants to migrate an old adapter: - The adapter code can be deleted - The SKILL.md files it consumed are already in the correct format - Remove any `adapters/` directory references from the project ### Step 3: Clean Up Legacy References If the project still contains adapter artifacts: 1. Remove `adapters/` directory (if present) 2. Remove adapter entries from `archon.yaml` under `platforms:` 3. Remove any `overrides/` directories from skill folders 4. Update any scripts that reference adapter imports ## Rules ### DO: - Clearly explain that Archon is Claude Code-only - Redirect users to `add-skill` for creating new skills - Help users clean up legacy adapter code if it exists - Explain the rationale: single-platform focus reduces complexity and maintenance burden - Point users to `~/.claude/skills/` as the installation target ### DON'T: - Create new adapter files - Suggest multi-platform support is coming back - Leave users confused about what replaced adapters - Reference old platform names (copilot-cli, cursor, windsurf, antigravity) as current targets - Create adapter boilerplate code ## Output Format The skill produces: - **Primary output**: Guidance explaining the current Claude Code-native architecture - **Format**: Conversational explanation with actionable next steps - **Location**: N/A (no files produced) ### Output Checklist ```markdown - Explained that Archon is Claude Code-native - Explained that adapters have been removed - Redirected user to appropriate skill (add-skill, add-bundle, etc.) - Offered to help clean up legacy adapter artifacts if applicable ``` ## Resources | Resource | Type | Description | |----------|------|-------------| | `../add-skill/SKILL.md` | reference | How to create skills for Claude Code | ## Handoff When this skill completes: - **Next action**: User redirected to `add-skill` or legacy cleanup completed - **Artifact produced**: None (advisory skill) - **User instruction**: "Archon targets Claude Code only. Skills are installed to ~/.claude/skills/. Use `add-skill` to create new skills."
Related Skills
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.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Vitest Unit Patterns
> Design fast, isolated unit tests that validate business logic without network, database, or browser dependencies using Vitest.
Verification Before Completion — The Honesty Enforcer
> **Type:** Rigid (follow exactly)