Skip to content

Agent Knowledge Base ​

An AI Agent knowledge system built for web frontend developers: from your first LLM API call to complete, interview-defensible practical skills. Everything is aligned with what 2026 job postings actually demand — "AI Application Engineer / Agent Engineer" roles don't ask you to train models; they ask you to engineer LLM capability into real business: call APIs well, understand RAG, orchestrate agents, build streaming UIs, and reason about evaluation and cost.

First, the mindset: what this market is actually hiring for ​

Translating JD buzzwords into plain requirements:

JD wordingWhat they really meanCovered in
"Familiar with LLM internals"Understand the engineering meaning of tokens / context windows / sampling params — no backprop by handLLM Basics & APIs
"Strong prompt writing & tuning"Structured prompts, few-shot, structured output, bad-case iterationPrompt Engineering
"Task planning, tool use, memory, autonomous decisions"The agent-loop quartet; implement a minimal agent from scratchAgent Core Principles
"Deep understanding of RAG (reranking, multi-way recall, KG integration)"Every pipeline stage: why, what to pick, how to tuneRAG
"Understand MCP; able to build custom MCP servers"Know the protocol + have shipped a TS SDK serverTool Ecosystem & MCP
"Familiar with LangChain / LangGraph / Dify"Know each framework's niche and trade-offs, not just doc-copyingFrameworks & Selection
"Streaming output, multi-platform delivery"SSE parsing, streaming Markdown rendering, typewriter & abortFrontend Agent Engineering
"Agent evaluation & production deployment"Eval datasets, LLM-as-judge, observability, cost controlProduction & Career Guide

Know your edge as a frontend dev: TypeScript is now a first-class citizen of the agent ecosystem — Vercel AI SDK, LangGraph.js, the official MCP TypeScript SDK, and the Claude Agent SDK all ship full TS support. The interaction layer of AI products (streaming UIs, workflow visualizers, low-code orchestration) is literally the frontend's home turf. Don't fight algorithm engineers on model internals — build your advantage in product delivery and agent engineering.

Knowledge map & page navigation ​

Read in table order — the first four pages are foundations, the last four are practice:

#PageWhat you gain
1LLM Basics & API CallingTokens/context/sampling mental model, OpenAI-compatible API, SSE streaming, model & pricing landscape
2Prompt Engineering & Structured OutputPrompt templates, few-shot/CoT, JSON mode, the full Function Calling mechanism
3Agent Core PrinciplesA 50-line hand-built agent loop, ReAct, planning/tools/memory/reflection, workflow vs agent
4RAGEnd-to-end engineering judgment: chunking → embeddings → vector DB → hybrid recall → rerank → eval
5Tool Ecosystem & MCPMCP architecture and primitives; write your own MCP server with the TS SDK
6Frameworks & SelectionWhere LangGraph.js / Vercel AI SDK / OpenAI Agents SDK / Mastra / Dify·Coze each fit
7Frontend Agent EngineeringFull streaming chat stack: SSE parsing, useChat, Markdown rendering, tool-progress UI, XSS defense
8Production & Career GuideEval, observability, cost & latency optimization, safety, plus resume projects and top interview questions

Interviewers distinguish "followed a tutorial" from "built a project" brutally — can you explain exception handling and selection rationale? Build in this order:

  1. Streaming AI chat app (1 week): Vercel AI SDK or raw SSE + your own UI. Must-haves: typewriter rendering, stop generation (AbortController), multi-turn context, streaming Markdown parsing. → Covers pages 1, 2, 7.
  2. Document-QA RAG assistant (2 weeks): upload PDF → chunk → embed (pgvector/sqlite-vec) → hybrid recall + rerank → citation source view. Must-haves: chunking strategy A/B experiments, retrieval quality metrics. → Covers page 4; the project you'll be grilled on most.
  3. Tool-calling agent (2–3 weeks): a multi-step agent that checks weather / searches the web / reads files, or write an MCP server plugged into Claude/Cursor. Must-haves: tool-failure retry, max-iteration guardrails, trace logs. → Covers pages 3, 5, 6.

Learning resources ​


Ready? Start with lesson one: LLM Basics & API Calling →