LLM Utility: Generate minimal project context map before starting any workflow. ALWAYS run this first at session start, before /prd, before /implement, or after context loss. Triggers on 'context prep', 'orient me', 'start', 'new session'.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Prepare LLM context before starting work. This is a utility that runs before any workflow phase.
When working on Arbitrum projects, use @arbitrum-best-practices for domain-specific patterns.
Generate a minimal, navigable context map using progressive revelation principles.
Launch 4 parallel agents using the Task tool, then synthesize findings.
subagent_type: Explore (thoroughness: "quick")
PROGRESSIVE REVELATION: Build a documentation map with links, not content.
1. List the root documents (README.md, INTERNALS.md, CONTRIBUTE.md, STYLE-GUIDE.md) - document topics, don't read yet
2. Scan README.md first 50 lines - extract project purpose (1-2 sentences)
3. Check for todo.md, CHANGELOG.md, AGENTS.md - current status
4. List package.json locations - map monorepo structure
Deliver navigable map:
- Project purpose (1-2 sentences) → Link: README.md
- Current status → Link: todo.md or AGENTS.md
- Package structure → Links: packages/*/package.json
- Reference materials → Links: the root *.md files (filenames only)
subagent_type: researcher
PROGRESSIVE REVELATION: Scout technology stack, link to deep dives.
Research via docs and MCP:
- What frameworks/libraries are used?
- What target platforms?
- Key integrations?
Deliver scout report:
- 1-sentence description of tech stack
- Top 3 constraints from architecture
- Critical dependencies (list, don't explain)
- Links to docs for deep dives
subagent_type: Explore (thoroughness: "quick")
PROGRESSIVE REVELATION: Surface recent activity, link to history.
1. Run: git log --oneline -10
2. Group commits by theme (1-2 words per group)
3. Check git status for uncommitted changes
4. Identify current branch
Deliver minimal summary:
- Last 5 commits (grouped by theme)
- Current branch and status (clean/dirty)
- Active work (from uncommitted files)
- Link: run `git log --oneline -50` if needed
subagent_type: Explore (thoroughness: "quick")
PROGRESSIVE REVELATION: Map architecture with pointers, not full code.
Scan structure (file listings only):
- src/*.ts or src/**/*.ts - list main files
- contracts/*.sol - list contract files
- packages/*/src/ - list entry points
Deliver navigable map:
- Key packages (name + one-liner purpose)
- Data flow (5-step maximum)
- Entry points → Links to main files
- Critical contracts → Links to .sol files
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📋 PROJECT CONTEXT (Progressive Revelation)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## What We're Building
[1-2 sentences]
→ Deep dive: README.md
## Current Status
- Branch: [branch]
- Progress: [summary]
- Active: [current work]
→ Full plan: todo.md
## Tech Stack
- Frameworks: [list]
- Targets: [list]
- Key integrations: [list]
→ Use MCP for details
## Architecture
**Key Packages:**
- [package]: [purpose] → path/to/main.ts
**Data Flow:**
[5-step flow]
## Reference Materials (Read IF Needed)
**Docs:**
- [list doc files]
**Code:**
- [list key source files]
## Recent Activity
[Last 5 commits grouped]
→ Full history: `git log --oneline -50`
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
💡 Context loaded. Traverse links for deeper detail.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Progressive revelation saves 95%+ of context for actual work.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Arbitrum L2 development best practices. Use when implementing bridges, Orbit chains, SDK integrations, or debugging cross-chain transactions. Triggers on Arbitrum, L2, rollup, bridge, retryable, Orbit, Nitro, or cross-chain contexts.
The English summary is being prepared. Showing the original description.
Create or improve lightweight, brand-consistent SVG concept diagrams for the Arbitrum docs, using the official Google Drive infographic asset kit as the palette/style source. Use when asked to "make a diagram more efficient", replace a bloated haw-*.svg (draw.io PNG-in-SVG exports), replace an ASCII / box-drawing diagram in an MDX page with a real image, author a new concept diagram for content/docs/how-arbitrum-works or similar, or build a diagram from the Arbitrum brand assets. Hand-authored lean vector SVG — not Mermaid, not a full Excalidraw/draw.io pipeline.
The English summary is being prepared. Showing the original description.
Use when asked to rebrand, restyle, re-pace, resize, or re-render an existing explainer video, when a video's labels are baked-in raster pixels that cannot be edited, or when building a new animated explainer for the Arbitrum docs from a prompt or a doc section.
The English summary is being prepared. Showing the original description.
Foundry's cast CLI for Ethereum interactions. Use when querying blockchain data, calling contracts, sending transactions, encoding/decoding data, or debugging on-chain issues. Triggers on "cast", "get balance", "call contract", "decode calldata", "check tx", "get block".
The English summary is being prepared. Showing the original description.
Run full documentation quality audit, covering sidebar orphans, unused-file review, MDX structure, internal links, glossary references, contract addresses, variables, formatting, frontmatter, tests, and types. Triggers on "audit docs", "check docs quality", "find problems", "content audit".
The English summary is being prepared. Showing the original description.
Create new Arbitrum development rules following best practices format. Use when capturing a reusable pattern, common mistake, or architectural decision. Triggers on "create rule", "add rule", "new rule", "document this pattern".
The English summary is being prepared. Showing the original description.