mcpbeat

Using Aegis

ganyuanran/using-aegis

Use when starting a turn or checking Aegis skill routing.

7k tokens
context cost
the whole folder, loaded on every use
7
files
instructions only
0
copies elsewhere
how many repositories repackaged it
894
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/GanyuanRan/Aegis --skill using-aegis

The instruction itself

1 sections, as written by the author

<SUBAGENT-STOP>Skip for subagents.</SUBAGENT-STOP>

<EXTREMELY-IMPORTANT>

You have Aegis. Load explicit/relevant Aegis skill before response/action;

otherwise proceed normally.

</EXTREMELY-IMPORTANT>

Hot Path

  • User/project instructions outrank Aegis.
  • Active codebase question/"what next": check README/ADR/rules/baseline, else

bounded index-first scan. Non-trivial owners passively use relevant

CONTEXT-MAP.md/CONTEXT.md; compose establishing-project-context only

for semantic delta/conflict. Create baselines only with evidence.

  • Direct grilling or plan/design pressure-tests (grill me, grill this plan, 审问我, 盘问我, 拷问我) route to brainstorming; literal/explanatory uses do not.
  • /aegis-goal or Aegis goal: loads goal-framing before routing.
  • Bug, failure, regression, or unexpected behavior routes to systematic-debugging; quick bug lane owns Change Necessity before source edits.
  • Classify before implementation/start/resume/compaction. Low: intent, baseline, verification. Medium/high: baseline read-set + plan. TDD: off=no auto route/load; auto=strict/light/skipped; explicit request applies. Spec Brief or Design Spec only for ambiguous/contract/cross-module medium/high work. Shared/core/contract/cross-module never low without evidence. Source edits/new paths: owner workflow surfaces Change Necessity.
  • Before the first repo write, the coordinator records TaskStartSnapshot.

Complexity, TDD, planning, or subagents alone do not

justify branch/worktree creation.

  • Non-tiny loaded skill: at first substantive user-visible stage say why Aegis is shaping work/risk; do not wait for the user to ask. structured trace only for audit/debug/release/long-task review/asked; Trace Digest does not route. Tiny stays implicit.
  • ArchitectureReviewRequired: yes for medium/high architecture/contract/

cross-module/owner/source-of-truth/fallback/adapter/baseline; carry to

verification.

10. Workspace support is lazy; use configured Aegis workspace support only when records needed. Fast Q&A/status/tiny edits write no files.

11. Load smallest needed skill/reference.

12. Tool/log/memory/search outputs are evidence candidates, not prompt payloads;

summary first, large input index->window->excerpt.

13. No history/sessions/transcripts/large logs by default; bound requested

evidence by scope/time/lines.

14. Unclear host tool-name mapping: read smallest relevant reference.

Contract: Route: fast-path; Aegis Reason Note.

How to use it

Copy the folder

Take ganyuanran/using-aegis from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.