← ClaudeAtlas

ai-agent-designlisted

Design and implement production-grade AI agents using LangGraph (TypeScript) and Convex as the backend. Use this skill whenever the user wants to build an AI agent, agentic workflow, multi-agent system, LLM pipeline, or anything involving autonomous task execution, tool-calling, ReAct loops, orchestrator-worker patterns, or stateful AI systems — especially when TypeScript, LangGraph, or Convex are mentioned or implied. Also trigger when the user asks about state management for agents, agent memory, human-in-the-loop checkpoints, or connecting LLMs to tools and external APIs in a TypeScript codebase.
samintisar/SolomindLM · ★ 2 · AI & Automation · score 58
Install: claude install-skill samintisar/SolomindLM
# LangGraph + Convex AI Agent Design Skill This skill encodes production-grade design principles for building AI agents in **TypeScript** using **LangGraph** for orchestration and **Convex** as the backend (database, real-time state, serverless functions, and caching). Before writing any code, diagnose the right architecture using the decision framework below. The single most common mistake is over-engineering — reaching for multi-agent complexity before validating a single-agent approach. --- ## Part 1: Design Principles (Read First) These aren't rules to follow blindly — they're the distilled lessons of what separates working production agents from prototypes that collapse under real usage. ### 1. Start with the simplest possible thing Always begin with a single LangGraph node and one clear system prompt. Verify the agent reliably understands and executes a tightly-scoped task before expanding. If you find yourself adding complexity early, that's usually a sign the task definition is fuzzy, not that you need more agents. ### 2. LLM intelligence belongs at bounded decision points only Deterministic code should handle routing, data transformation, retries, and error handling. Reserve LLM calls for the things only LLMs can do: natural language understanding, unstructured data extraction, and fuzzy reasoning. The temptation to make everything "smart" is what kills reliability. ### 3. State is the architecture In LangGraph, your `StateAnnotation` is the con