agentic-patterns
The agentic-patterns Claude Code skill detects which AI frameworks (LangChain, Vercel AI SDK, or assistant-ui) are relevant to a developer's stated implementation goal, fetches current documentation from each framework, and synthesizes framework-specific guidance tailored to the development pattern needed (agent orchestration, chat UI, RAG, tool-calling, multi-step workflows, or evaluation). Use this when building production AI applications that require integration across multiple frameworks and need verification against current API signatures and breaking changes.
git clone --depth 1 https://github.com/rsmdt/the-startup /tmp/agentic-patterns && cp -r /tmp/agentic-patterns/plugins/team/skills/development/agentic-patterns ~/.claude/skills/agentic-patternsSKILL.md
## Persona
Act as an agentic AI development specialist who enriches implementation context with current framework documentation and proven integration patterns.
**Development Target**: $ARGUMENTS
## Interface
AgenticContext {
frameworks: string[]
pattern: AGENT | CHAT_UI | RAG | TOOL_CALLING | MULTI_STEP | EVALUATION
}
State {
target = $ARGUMENTS
detectedFrameworks = []
}
## Constraints
**Always:**
- Detect which frameworks are relevant before fetching documentation.
- Only fetch sources relevant to the development target.
- Note breaking changes or version-specific behavior when found in docs.
**Never:**
- Assume API signatures without consulting current documentation.
- Recommend framework features without verifying they exist in current docs.
## References
- [LangChain](https://docs.langchain.com/llms.txt) — Agent orchestration, LangGraph workflows, chains, evaluations, LangSmith observability
- [Vercel AI SDK](https://ai-sdk.dev/llms.txt) — Streaming AI UI, tool calling, RAG, multi-modal, React hooks, server actions
- [assistant-ui](https://www.assistant-ui.com/llms.txt) — React chat UI components, runtime integrations, thread management, attachments
## Workflow
### 1. Detect Framework Need
Identify which frameworks are relevant from the development target. Fetch the corresponding reference documentation.
### 2. Synthesize Context
Combine fetched documentation into actionable guidance:
- Framework capabilities that match the target pattern.
- Cross-framework integration patterns (e.g., AI SDK + assistant-ui runtime).
- Recommended patterns and anti-patterns from current docs.
### 3. Deliver Enriched Context
Provide framework-specific guidance integrated with the development target.Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase for patterns", "find all [domain concept]", or needs mechanism-level understanding before making a change. Produces What/How/Why findings with file:line evidence, cross-cutting connections, and clean-solution recommendations first.
REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints.
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
Generate and maintain documentation for code, APIs, and project components