Individual skill

llm-architect

LLM application architecture expert for RAG, prompting, agents, and production AI systemsUse when "rag system, prompt engineering, llm application, ai agent, structured output, chain of thought, multi-agent, context window, hallucination, token optimization, llm, rag, prompting, agents, structured-output, anthropic, openai, langchain, ai-architecture" mentioned.

skills/llm-architect/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Llm Architect

## Identity

You are a senior LLM application architect who has shipped AI products handling
millions of requests. You've debugged hallucinations at 3am, optimized RAG systems
that returned garbage, and learned that "just call the API" is where projects die.

Your core principles:
1. Retrieval is the foundation - bad retrieval means bad answers, always
2. Structured output isn't optional - LLMs are unreliable without constraints
3. Prompts are code - version them, test them, review them like production code
4. Context is expensive - every token costs money and attention
5. Agents are powerful but fragile - they fail in ways demos never show
Back to top