원클릭으로
langchain
Apply when building LangChain pipelines, LCEL chains, agents, or retrieval-augmented generation systems.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Apply when building LangChain pipelines, LCEL chains, agents, or retrieval-augmented generation systems.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | langchain |
| description | Apply when building LangChain pipelines, LCEL chains, agents, or retrieval-augmented generation systems. |
| license | MIT |
| version | 1.0.0 |
| tokens_target | 2200 |
| triggers | ["langchain","lcel chain","agent framework"] |
| loads_after | ["python"] |
| supersedes | [] |
Purpose: Prevent common LangChain mistakes — deprecated chain classes, missing retry/timeout guards, unsafe prompt handling, and unobservable pipelines.
|) to compose runnables instead of deprecated constructor-based chain classes (LLMChain, SequentialChain, TransformChain). Reference: ERR-2026-026langchain.chains.llm or langchain.chains.sequential; use langchain_core.runnables and langchain_core.prompts instead.RunnablePassthrough to thread context through a chain without mutation rather than writing a lambda that returns its input unchanged.RunnableParallel over manually calling multiple chains and merging dicts; it expresses intent and enables parallel execution.PydanticOutputParser, JsonOutputParser, StrOutputParser) to chains that produce structured data; never parse raw LLM strings manually downstream.prompt.partial(format_instructions=parser.get_format_instructions()) to bind parser instructions into the prompt template rather than hard-coding them in the template string.ChatPromptTemplate.from_messages([("system", ...), ("human", ...)]) instead of a single PromptTemplate for chat models; mixing roles in one string breaks structured output.ChatOpenAI, ChatAnthropic, or equivalent chat-model classes for new code; the base OpenAI LLM class is deprecated for most use cases and lacks tool-calling support.model="gpt-4o" (or equivalent) so upgrades are intentional.RunnableWithMessageHistory over manual history management or deprecated ConversationChain; it integrates cleanly with LCEL and supports async.session_id key when constructing RunnableWithMessageHistory to prevent cross-user memory leakage in multi-tenant services.@tool decorator (or StructuredTool.from_function) with a typed signature and docstring; never pass raw callables to an agent without a schema.create_tool_calling_agent + AgentExecutor over deprecated initialize_agent; it uses native tool-calling APIs and avoids ReAct string parsing.max_iterations and max_execution_time on AgentExecutor to prevent runaway loops; default is unbounded.retriever | format_docs | prompt | llm | parser rather than RetrievalQA.from_chain_type; the latter is deprecated and hides the retrieval step..lazy_load() over .load() for large corpora to avoid loading all documents into memory at once..with_retry(stop_after_attempt=3, wait_exponential_jitter=True) on any runnable that calls an external API; never let transient rate-limit errors propagate uncaught.request_timeout (or timeout) to chat model constructors; omitting it allows indefinitely hanging requests.callbacks=[LangSmithTracer()] or equivalent on chains in production; never ship a pipeline with no tracing so failures are diagnosable.llm.get_num_tokens(text) or a tiktoken counter to verify the payload fits within the model's context window.set_llm_cache(InMemoryCache()) during development and SQLiteCache in staging to avoid redundant API calls and reduce cost during iteration.skills/python/SKILL.mdskills/error-log/SKILL.mdGit-versioned agent memory — agents that never make the same mistake twice.
Apply when generating ideas, exploring solution space, or facilitating divergent thinking before committing to an approach.
Apply when closing out a feature branch — pre-merge checklist, rebase, CI verification, cleanup, and post-merge steps.
Apply when writing or refactoring code. Generic rules to prevent the most common review comments — function length, naming, error handling, security, and tooling.
Apply when designing database schemas, writing migrations, or reviewing table structure. Covers naming, keys, indexes, constraints, nullability, and migration safety.
Apply when diagnosing a bug, reproducing a failure, or performing root cause analysis. Covers systematic isolation, binary search, logging strategy, and hypothesis-driven investigation.