Scroll Enter the Portal

Welcome to

Claude Universe

Claude Universe

Claude Universe

Teach Claude Code to think systematically.

Install

Run these two commands in any Claude Code session

/plugin marketplace add mbwsims/claude-universe
/plugin install universe@claude-universe
View on GitHub

System Map

One slash-command surface, five layers of systematic intelligence.

System Focus Role
Navigate Instruction quality Extract the standards
Diagnose Test depth Pressure the behavior
Shield Security Model the attacks
Survey Codebase structure See the blast radius
Timewarp Code evolution Trace the history
01 Instruction intelligence

Navigate

Discover your project's unwritten conventions, lint instruction quality, and check whether the codebase actually follows the rules.

  • Reverse-engineers conventions from real code with evidence
  • Flags vague rules, conflicts, and coverage gaps inside your instructions
  • Checks conformance between written guidance and actual implementation
/discover /lint-rules /check-rules
02 Testing intelligence

Diagnose

Write tests that catch real bugs instead of just proving the happy path still works.

  • Plans the input space before it writes a single test
  • Generates deeper assertions and stronger error-path coverage
  • Reviews existing tests with graded feedback and concrete fixes
/test /test-review /test-plan
03 Security intelligence

Shield

Find vulnerabilities before attackers do, with reviews centered on exploit paths and mitigations.

  • Scans for issues like IDOR, SSRF, injection, and mass assignment
  • Builds STRIDE threat models around features and attack surfaces
  • Traces untrusted input through code to ask whether it can actually be exploited
/scan /threat-model /security-review
04 Codebase intelligence

Survey

Understand the codebase before you change it so every edit lands with context instead of guesswork.

  • Follows features through routes, services, storage, and side effects
  • Finds hotspots, blast radius, and architectural boundaries before risky edits
  • Explains both what a module does and why it evolved that way
/trace /hotspots /impact /explain /map
05 Temporal intelligence

Timewarp

Understand how your codebase evolved so you can refactor with history, not guesswork.

  • Recaps recent changes and surfaces neglected areas of the codebase
  • Detects architectural drift when code quietly evolves away from its purpose
  • Forecasts which files are about to become problems based on growth trends
/recap /drift /dissect /forecast /rewind

Command Catalog

A catalog for the Claude Universe command surface.

Navigate Instruction IQ
Diagnose Testing IQ
Shield Security IQ
Survey Codebase IQ
Timewarp Temporal IQ
A1

/discover

Reverse-engineer conventions from real code.

Best for surfacing unwritten rules.

A2

/lint-rules

Analyze instruction quality, conflicts, and gaps.

Best for tightening the rulebook before relying on it.

A3

/check-rules

Compare written rules against current code with evidence.

Best for seeing where adherence holds or drifts.

T1

/test-plan

Map the input space before writing tests.

Best for planning coverage with intention.

T2

/test

Generate stronger tests with deeper assertions and edge cases.

Best for turning a plan into real coverage.

T3

/test-review

Grade an existing suite and surface what it still misses.

Best for auditing test quality quickly.

S1

/scan

Sweep code for exploitable vulnerabilities and attack paths.

Best for finding concrete security issues fast.

S2

/threat-model

Build a STRIDE view of assets, surfaces, and threats.

Best for feature-level risk reasoning.

S3

/security-review

Trace untrusted input and ask whether it can be exploited.

Best for inspecting sensitive code like an attacker.

V1

/trace

Follow a feature through routes, services, and storage.

Best for making a system legible end-to-end.

V2

/hotspots

Rank risky files by churn, complexity, and coupling.

Best for finding where change is most dangerous.

V3

/impact

Estimate blast radius before touching a file or interface.

Best for knowing what a change will hit.

V4

/explain

Combine code reading and history into a deeper explanation.

Best for understanding both what and why.

V5

/map

Generate a fast overview of layers, boundaries, and dependencies.

Best for the two-minute system view.

W1

/recap

Summarize recent changes, focus areas, and neglected zones.

Best for catching up after time away.

W2

/drift

Detect when code has quietly evolved away from its original purpose.

Best for finding scope creep and architectural rot.

W3

/dissect

Trace when and why a file became complex.

Best for understanding complexity before simplifying it.

W4

/forecast

Predict which files are about to become problems.

Best for intervening before code hits critical mass.

W5

/rewind

View a historical version with annotated explanations of what changed.

Best for understanding the why behind the diff.

Navigate Instruction IQ 3 cmds
  • /discoverReverse-engineer conventions from real code.
  • /lint-rulesAnalyze instruction quality, conflicts, and gaps.
  • /check-rulesCompare written rules against current code with evidence.
Diagnose Testing IQ 3 cmds
  • /test-planMap the input space before writing tests.
  • /testGenerate stronger tests with deeper assertions and edge cases.
  • /test-reviewGrade an existing suite and surface what it still misses.
Shield Security IQ 3 cmds
  • /scanSweep code for exploitable vulnerabilities and attack paths.
  • /threat-modelBuild a STRIDE view of assets, surfaces, and threats.
  • /security-reviewTrace untrusted input and ask whether it can be exploited.
Survey Codebase IQ 5 cmds
  • /traceFollow a feature through routes, services, and storage.
  • /hotspotsRank risky files by churn, complexity, and coupling.
  • /impactEstimate blast radius before touching a file or interface.
  • /explainCombine code reading and history into a deeper explanation.
  • /mapGenerate a fast overview of layers, boundaries, and dependencies.
Timewarp Temporal IQ 5 cmds
  • /recapSummarize recent changes, focus areas, and neglected zones.
  • /driftDetect when code has quietly evolved away from its original purpose.
  • /dissectTrace when and why a file became complex.
  • /forecastPredict which files are about to become problems.
  • /rewindView a historical version with annotated explanations of what changed.