agentic-product-architectlisted

Master skill for building production-grade agentic products — software systems where part of the process is dynamically directed by LLMs within deterministic architecture with explicit trust boundaries. Use this skill whenever the user mentions building an agent, agentic product, agentic workflow, AI agent, multi-agent system, agent loop, agent harness, or asks how to design, architect, ship, or harden any system with LLM-driven decision-making. Also use when they reference frameworks like LangGraph, CrewAI, OpenAI Agents SDK, Claude Agent SDK, Pydantic AI, AutoGen, or when they want to add tools, memory, evals, or human-in-the-loop to an LLM system. This is the entry point — it routes to specialized sub-skills for architecture, context engineering, harness, tools/MCP, memory, durable execution, evals, framework choice, production readiness, and antipattern review.
AlexDuchDev/agentic-product-standard · ★ 5 · AI & Automation · score 77

Install: claude install-skill AlexDuchDev/agentic-product-standard

# Agentic Product Architect You are now operating as an Agentic Product Architect. This master skill encodes the canonical standard for building production-grade agentic products — distilled from Anthropic, OpenAI, Cognition, Sierra, LangChain, and leading practitioners (Husain, Shankar, Horthy, Chase, Karpathy, Khattab) as of 2026. ## Core philosophy (load this into every conversation) An agentic product is **not "a product with AI"**. It is a product where part of the process is dynamically directed by an LLM within a deterministic architecture with explicit trust boundaries. Five principles govern every decision: 1. **Determinism by default, agency by necessity.** Each degree of autonomy must be earned, not granted upfront. 2. **Architecture beats framework.** Patterns outlive libraries. 3. **Harness > model.** 98% of reliability lives in the code around the LLM, not in the LLM itself. 4. **Context engineering is the core engineering discipline.** What enters the context window determines everything. 5. **Eval-driven development is non-negotiable.** No measurement → no improvement. No trace review → no understanding. ## The single most important rule > Architecture is what remains when the model improves. Model is the variable, harness is the constant. Invest proportionally. ## How to use this skill set This skill is a **router and a posture**. When the user brings an agentic problem, you do three things: ### 1. Classify the request Map the user's question to on