Agent skill · AI & Agents

langgraph-architecture

Guides architectural decisions for LangGraph applications. Use when deciding between LangGraph vs alternatives, choosing state management strategies, designing multi-agent systems, or selecting persistence and streaming approaches.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill langgraph-architecture --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/agent/langgraph-architecture/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# LangGraph Architecture Decisions ## When to Use LangGraph ### Use LangGraph When You Need: - **Stateful conversations** - Multi-turn interactions with memory - **Human-in-the-loop** - Approval gates, corrections, interventions - **Complex control flow** - Loops, branches, conditional routing - **Multi-agent coordination** - Multiple LLMs working together - **Persistence** - Resume from checkpoints, time travel debugging - **Streaming** - Real-time token streaming, progress updates - **Reliability** - Retries, error recovery, durability guarantees ### Consider Alternatives When: | Scenario | Alternative | Why | |----------|-------------|-----| | Single LLM call | Direct API call | Overhead not justified | | Linear pipeline | LangChain LCEL | Simpler abstraction | | Stateless tool use | Function calling | No persistence needed | | Simple RAG | LangChain retrievers | Built-in patterns | | Batch processing | Async tasks | Different execution model | ## State Schema Decisions ### TypedDict vs Pydantic | TypedDict | Pydantic | |-----------|----------| | Lightweight, faster | Runtime validation | | Dict-like access | Attribute access | | No validation overhead | Type coercion | | Simple

What's inside
Steps it walks through
  1. When to Use LangGraph
  2. Use LangGraph When You Need:
  3. Consider Alternatives When:
  4. State Schema Decisions
  5. TypedDict vs Pydantic
  6. Reducer Selection
  7. State Size Considerations
  8. Graph Structure Decisions
  9. Single Graph vs Subgraphs
  10. Conditional Edges vs Command
  11. Static vs Dynamic Routing
  12. Persistence Strategy
  13. Checkpointer Selection
  14. Checkpointing Scope
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the langgraph-architecture skill do?

Guides architectural decisions for LangGraph applications. Use when deciding between LangGraph vs alternatives, choosing state management strategies, designing multi-agent systems, or selecting persistence and streaming approaches.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill langgraph-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going