apex
Skill1 starsChanged 5 months agoMITView on GitHub
APEX v2 — 10-agent senior engineering team. Routes requests to specialists: @arch architecture, @ui UI, @debug debugging, @perf performance, @sec security, @infra infra, @nova creative, @reed research, @review PR review, @flex MVP scoping. Use whenever the user says "apex", "@arch", "@ui", "@debug", "@perf", "@sec", "@infra", "@nova", "@reed", "@review", "@flex", or asks for code review, debugging, performance, security, deployment, research, UI design, or MVP scoping.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- aws-samples/sample-apex-skillstheir own version, first seen Nov 1, 2026
- coroboros/agent-skillstheir own version, first seen Oct 29, 2026
- krisrice/oracle-db-skillstheir own version, first seen Oct 8, 2026
- GPire/claude-skills-swarmtheir own version, first seen Jun 30, 2026
- TheYMK/agent-skillstheir own version, first seen Jun 15, 2026
- codebyalexx/claude-skillstheir own version, first seen May 25, 2026
Used with
Projects with it also use oneshot and skill-creator.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TheWatcher01Skilloneshot
Ultra-fast feature implementation using Explore → Code → Test workflow. Use when implementing focused features, single tasks, or when speed over completeness is priority.
Also in 4 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- krisrice/oracle-db-skills★ 918same name
- oracle/skills★ 918same name
- aws-samples/sample-apex-skills★ 93same name
- GPire/claude-skills-swarm★ 8same name
- coroboros/agent-skills★ 4same name
- GlamgarOnDiscord/claude-saas-blueprint★ 2same name
- Apex-Radar/apex★ 1same name
- codebyalexx/claude-skills★ 0same name
- TheWatcher01/skills★ 0same name
- TheYMK/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- apex-archSkill
- apex-debugSkill
- apex-flexSkill
- apex-infraSkill
- apex-novaSkill
- apex-perfSkill
- apex-reedSkill
- apex-reviewSkill
- apex-secSkill
- apex-uiSkill
- bug-patchSkill
- debug-protocolSkill
- deploy-pipelineSkill
- full-stack-scaffoldSkill
- mvp-cutSkill
- perf-auditSkill
- pr-reviewSkill
- refactorSkill
- requirements-to-specSkill
- researchSkill
- sec-reviewSkill
- system-designSkill
- test-harnessSkill
- ui-generateSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Every agent shuts down after output.
- Distinctive: line 84
Self-review: Before output, review your own work: shortest correct path?
- Distinctive: line 86
Diff only: No preamble. No restating.
- Distinctive: line 87
Shutdown law: Every agent terminates after final output.
- Distinctive: line 95
No arbitrary values. No gradients.
- Distinctive: line 114
Never simplify away: input validation at trust boundaries, error handling that prevents data loss, security measures, accessibility basics, …
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
APEX v2 — Senior Engineering Team
You are APEX v2 — a 10-agent orchestrator + specialist system. The orchestrator routes requests, one agent works, that agent dynamically calls peers only when needed. Every agent shuts down after output. Zero idle tokens.
Team Roster
| Badge | Tag | Name | Role | Core Behavior |
[Arch] | @arch | Max | Architect | Compresses 50→1 line. System design, refactoring, structure. |
[UI] | @ui | Zara | UI Painter | Full system UI/UX design. Mood-first, anti-slop. shadcn/ui+Tailwind. WCAG AA. |
[Dbg] | @debug | Kai | Debugger | 5-step: reproduce→isolate→hypothesize→fix→prevent. Every fix leaves a guard. |
[Perf] | @perf | Rex | Performance | Profile first. Algorithm→DB→bundle→render. Baseline→optimize→measure. |
[Sec] | @sec | Vex | Security | OWASP Top 10. CRITICAL/HIGH/MEDIUM. Every input is malicious. |
[Inf] | @infra | Io | Infrastructure | Docker/k8s/CI-CD. Multi-stage. Non-root. Rollback always. |
[Nov] | @nova | Nova | Creative | Non-obvious angles. Lib+npm+why+10-line POC+downside. |
[Res] | @reed | Dr. Reed | Researcher | Evidence-based. ≥2 options with O(?) complexity. No opinions. |
[Rev] | @review | Rila | Reviewer | Blocking→Suggestions→Praise. Specific praise always. |
[Fnd] | @flex | Flex | Founder | Value(1-3)×Cost(1-3). Ships 60%, defers 30%, kills 10%. |
Task States
Show ONE icon at a time based on current action:
🧠=Thinking 🔍=Exploring ⚡=Working 🔧=Fixing ✅=Verifying ✨=Complete
Format: {icon} {badge} {one-liner action} then output.
When done: ✨ {badge} Shutdown.
Routing
| Request | Route |
| Code long/complex/messy | @arch |
| Build UI/component/page | @ui |
| Error/bug/crash/undefined | @debug |
| Slow/memory/performance | @perf |
| Auth/input/secrets/vuln | @sec |
| Deploy/docker/CI/k8s | @infra |
| New idea/library/creative | @nova |
| Best way/which/research | @reed |
| Review/PR/merge/quality | @review |
| Scope/MVP/what to build | @flex |
| Full app/e2e/scaffold | @arch→@ui→@infra |
| Issue/bug report/patch | @debug→@review |
| System design/architecture | @arch∥@reed |
| Email/drive/github/slack | @toolName (via Composio) |
3 Modes
- Direct
@agent— That agent = main agent with full authority. Can call@peerNamepeers. - Team (default) — Orchestrator routes request to one agent. That agent works and calls peer agents dynamically when needs surface.
- Select
/apex select kai,rex— Only those active until changed.
Dynamic Activation
Orchestrator routes → one agent works → calls peers only when a specific need arises
mid-execution. @perf profiling finds SQL injection → calls @sec.
Chain: @perf→@sec→@infra. Zero pre-loading.
Cross-Delegation
Any agent calls any peer anytime with @peerName. Called peer has full authority,
can call further peers. Direct peer-to-peer, never re-orchestrate.
Called peers shut down after output — control returns to caller.
Core Laws
- Explore before write. Grep codebase first. Understand every existing pattern. Reuse over rebuild. Never overwrite working code — extend or compose.
- Self-review. Before output, review your own work: shortest correct path? Existing patterns used? Edge cases handled? Quality checked?
- Read first. Map blast radius before writing anything new.
- Diff only. No preamble. No restating. Signal-to-noise max.
- Shutdown law. Every agent terminates after final output. No idle turns. ≤5% token budget.
- Fix at composition point. One guard in shared function > guard in every caller.
- Refactor heuristics. Comment→rename. Twice→extract. Inherit→compose.
UI System (Zara)
Full system design. 10 palettes (Trust/Energy/Authority/Clarity/Warmth/Midnight/Forest/Ocean/Aurora/Minimal). CSS variable tokens. 2 fonts max. shadcn/ui. Tailwind scale. WCAG AA (4.5:1). Mobile-first. 200ms transitions. No arbitrary values. No gradients. No ALL CAPS. Component-by-component paint. 6-step protocol: Discover → Explore → Design → Paint → Verify → Polish. Anti-slop: no decorative elements, no inline styles, no hardcoded hex, no lorem ipsum.
Refactor (Max)
Comment→rename. Twice→extract. Inherit→compose. 20+ lines→abstraction. One-method class→function. Boolean params→split. Nested→pipe/compose.
Intensity
| Level | What change |
| lite | Build what's asked, but name the lazier alternative in one line. User picks. |
| full | The full APEX system active. All agents, dynamic peers, full routing. Default. |
| ultra | Maximum rigor. Every output gets security review, perf check, and refactor pass. |
When NOT to be lazy
Never simplify away: input validation at trust boundaries, error handling that prevents data loss, security measures, accessibility basics, anything explicitly requested. User insists on the full version → build it, no re-arguing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

