What it does
This repo is a collection of 22 skills
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category Coding
Maker’s original description
Make AI coding agents architecture-aware: baseline-first, evidence-verified, drift-checked, and safe across long tasks.For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/ganyuanran-aegis)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one Aegis | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | GanyuanRan | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 22 | 1 | 1 | 1 | 1 |
| GitHub stars | 1,442 | 468,713 | 234,328 | 150,276 | 144,564 |
| Last code change | Nov 14, 2026 | Nov 18, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
22 skills (instruction sets) by GanyuanRan that an AI reads and follows · not an MCP server
Pick the skill to install
Install only the ones you use. Open a skill to see how to install it
Install the whole set (22)
If you want every one, let the AI install them in one go. Know 2 things first
- Every installed skill’s description is loaded into every chat. The more you install, the easier it is for the AI to pick the wrong one
- Some skills duplicate tools the AI already has built in. Installing only the ones you use works better
Uploading to Claude on the web and apps: you need 22 uploads, one ZIP per skill. Open each skill in the list below to download it
Checked against official docs Nov 12, 2026 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com
- anti-entropy-governance
Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.
- brainstorming
Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.
- communicating-concisely
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
- dispatching-parallel-agents
Use when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.
- establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
- executing-plans
Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.
- finishing-a-development-branch
Use when verified work needs integration or cleanup of an existing task-created branch/worktree, or the user explicitly requests merge, PR, or branch lifecycle handling.
- first-principles-review
Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.
- goal-framing
Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work.
- long-task-continuation
Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
- receiving-code-review
Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.
- recording-architecture-decisions
Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
- requesting-code-review
Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.
- subagent-driven-development
Use when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise inline. Ad-hoc 2+ tasks without a plan use dispatching-parallel-agents.
- systematic-debugging
Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes
- test-driven-development
Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.
- update-aegis
Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.
- using-aegis
Use when starting a turn or checking Aegis skill routing.
- using-git-worktrees
Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.
- verification-before-completion
Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.
- writing-plans
Use when you have an approved spec or written requirements for a multi-step task that needs a durable plan document before touching code. Small, single-owner, or fast-path tasks do not need this skill.
- writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodexGemini CLIGitHub CopilotOpenCode
From the maker’s README and the folders in the repo
Install
Pick a skill first
This repo has 22 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 1,442
Stars are for the whole repo, not each skill - Maker
- GanyuanRan
- License
- MIT
- Last code change
- Nov 14, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 22
- Topics
- agent-skills, ai-agents, ai-coding, architecture-driven-development, awsome-coding-plugin, baseline-first, claude-code, codex, coding-agents, dive, dsh-plugin, evidence-driven
- Repo
- ganyuanran/aegis