'long context' 검색 결과

Turn long Markdown files into a single HTML file for reading, reviewing code, or presenting slides. Routes each input to a specialized converter and applies shared design settings, with navigation and interaction suited to the document type.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Converting long specifications or reports into navigable HTML
• Presenting code reviews with diffs and severity annotations
• Turning Markdown into slides with keyboard navigation

Use Memori Cloud from Claude Code to consult stored preferences, decisions, and project history before substantive work, then save the exchange afterward. Recall can span sessions and use filters for dates and information types.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check previous decisions before coding
• Recall preferences and project requirements
• Review progress after time away

Turn OpenClaw conversations, actions, and tool history into structured long-term memory. Agents can retrieve past facts, decisions, and summaries when needed, helping them continue work across sessions and recover context after it is shortened.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Retrieve decisions made in previous sessions
• Review summaries of earlier work
• Recover context after conversation compaction

Keep context for work that spans multiple sessions without belonging to a specific project phase. The skill manages lightweight persistent threads, letting you create, list, resume, check, and close them as work progresses.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Keeping context for work across sessions
• Recording work outside a specific phase
• Listing open or resolved threads

Develop public equity trade pitches for portfolio managers, covering long, short, or paired positions. Explain the difference from market expectations, potential catalysts, gains and losses, risk considerations, and exit rules, while labeling assumptions and missing evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Develop a long or short equity trade pitch
• Compare a trade thesis with market expectations
• Test catalysts, scenarios, and risk controls

Turn a Figma design into code that fits an existing project. Reuse its components and shared style values, follow designer notes and component mappings, and adapt Figma's reference output to the project's framework and conventions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a screen from a Figma design
• Reusing existing project components in a design implementation
• Applying designer notes and shared style values

Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restoring project context after /clear
• Reviewing recent changes after a long break
• Checking unfinished work before choosing the next task

Clean up stored agent state in `.squad/` by compressing histories, pruning old logs, archiving stale decisions, and removing orphaned inbox files. Use it after long sessions or before starting work with many agents to reclaim context space.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing for work that starts many agents
• Cleaning up after long sessions or sprints
• Managing oversized history files or stored state

Execute proactive auto-loading: automatically detects and loads agents.md files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Keep Claude Code sessions productive across resets with output filtering, session logging, and auto-resume. Use when starting a long or complex coding session, when previous sessions lost context mid-task, or when you need Claude to resume exactly where it left off after a reset. Produces a session.log at the project root, filtered command output that preserves context, and automatic resume of in-progress tasks after any reset.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Measure and shrink the always-loaded context of a Claude Code harness (CLAUDE.md + rules without paths frontmatter) back under budget — migrate narrative to reference files, convert rules to path-scoped or skill-triggered loading, and verify zero governance loss with deterministic preservation checks. Use on "harness diet", "context diet", "rules diet", "CLAUDE.md too long", "always-load budget", "trim my rules", "context bloat", "하네스 다이어트", "룰 다이어트", "컨텍스트 다이어트", "always-load 줄여줘". Not for one-off prose editing or project docs cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage context and prompt-cache costs without losing task state. Use for context management, orchestration cost, token budgets, large tool outputs, cache misses, or long-running conversations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Protect Claude Code sessions from context overflow by running a background daemon that monitors session size and auto-prunes before compaction hits. Use when the user says "guard", "protect session", "context getting long", "prevent compaction", "session management", or is running agent teams that need continuous context protection.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Optimizes context window via MECW principles and memory tiering. Use when context exceeds 30% or before long multi-step tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compress selected context to a target token budget while preserving decisions, evidence, constraints, and unresolved questions. Use when relevant material is already selected but too long; use context-optimization when selection, deduplication, and ordering are also required.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read, study, and answer questions about long books and papers without loading the whole text into one context window, keeping page-anchored notes as a reusable workspace. Use whenever the user asks to read, study, summarize, analyze, review, or answer questions about a long book, textbook, PDF, EPUB, thesis, dissertation, survey paper, or any document of roughly 50+ pages, in any language (Vietnamese "đọc sách", "tóm tắt sách", "phân tích luận án"). Also use when a `{slug}-notes/` workspace from a previous session sits next to a source file and the user asks a follow-up question about that book. Not for short documents (under ~30 pages) that fit in context; read those directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Load, validate, and use DACP bundles as structured execution context. Detects .bundle/ companion directories, validates integrity (manifest schema, fidelity, provenance), loads typed data, and builds ExecutionContext for receiving agents. Scripts are NEVER auto-executed. Use when processing incoming DACP bundles, interpreting .bundle/ directories alongside .msg files, validating bundle integrity, or building execution context from bundle payloads.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered sources. Skip one file, one function, a single needle, or a one-page PDF conversion. Triggers: long context, context rot, large codebase, many files, all files, big document, multi-document, PDF, aggregate, summarize everything, codebase-wide, multi-hop, recursive, sub-agents, map-reduce.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Context-Driven Development methodology - treating project context as managed artifacts alongside code for consistent AI interactions and team alignment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compress large context before reasoning to reduce token usage while preserving evidence. Use this whenever the user mentions huge files, long prompts, RAG payloads, prompt caching, expensive sessions, codebase context, chat history compaction, or wants the same answer quality with fewer tokens.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rebalances context across Memory, Custom Instructions, knowledge files, and User Preferences in Claude Projects. Audits Memory for redundancy, staleness, and misplacement; prescribes optimization including Codification of stable Memory patterns into explicit User Preferences or Project CI rules. Use when user says "optimize my memory," "what should be in my memory," "trim my knowledge files," "reduce my context usage," "rebalance my project," "what should be in my preferences vs memory," or asks whether something belongs in Memory, a knowledge file, or User Preferences. Also trigger on symptom-phrased: "my project feels bloated," "Claude keeps forgetting things," "my context window keeps hitting limits." Activate whenever Memory-layer balance is the primary concern. Do NOT use for full Project audits (use rootnode-project-audit if available), single-prompt evaluation (use rootnode-prompt-validation if available), or global-layer audits that don't touch Project Memory (use rootnode-global-audit if available).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work with the @upstash/workflow TypeScript/JavaScript SDK for durable, long-running workflows in serverless functions, multi-step processes that survive timeouts, retries, and restarts (built on QStash). Use when defining a workflow endpoint with serve(), running steps with context.run, sleeping for minutes to days without holding a function open, calling external APIs with context.call, waiting for an external event or webhook, invoking other workflows, configuring retries, failure callbacks, and a DLQ, controlling concurrency, rate, and parallelism, triggering, cancelling, or inspecting runs with the Workflow client, building AI agents and orchestrators, human-in-the-loop approvals, realtime updates, local development with the QStash dev server, adding middleware, or migrating workflows safely. Also use when the user asks for durable execution, step functions, saga or orchestration patterns, background jobs with checkpoints, or long-running tasks on Vercel, Next.js, Cloudflare Workers, or other serverless platforms.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.