'just-in-time' 검색 결과

Design file-based storage for agent context, including large tool results, plans, logs, and handoff notes. Keep information available outside the conversation and retrieve relevant sections when needed, instead of loading everything at once.

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

• Saving large tool results for selective reading
• Keeping plans available during long tasks
• Sharing findings between agents through files

[omh] Blocked on a project by a knowledge gap: just-in-time learning workflow: select and confirm an immediate learning target, research credible sources, and prepare an application-first brief without popularity ranking. Use when the user says: jit-learn, learn next, learn now, blocker-specific learning target, highest-leverage learning target, immediate learning payoff, immediately applicable learning brief, source-backed learning brief.

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

Audit, design, and migrate Identity and Access Management — cloud provider IAM (AWS, GCP, Azure), identity providers (Okta, Entra ID / Azure AD, Auth0, Google Workspace), application authorization (RBAC, ABAC, ReBAC), and federated identity. Use when the user mentions 'IAM,' 'identity,' 'access management,' 'least privilege,' 'role design,' 'SSO,' 'SAML,' 'OIDC,' 'OAuth,' 'JIT access,' 'just-in-time access,' 'break-glass,' 'service accounts,' 'RBAC,' 'ABAC,' 'privilege creep,' 'role explosion,' 'identity governance,' 'IAM strategy,' 'identity migration,' 'Okta,' 'Entra ID,' 'Azure AD,' 'Auth0,' 'Cognito,' or needs identity consultant-level guidance.

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

Operations management and lean production techniques for turning inputs into outputs under variability. Covers the Toyota Production System, seven wastes, just-in-time, kanban, jidoka, single-minute die exchange, 5 Whys, value stream mapping, bottleneck theory, and the distinction between mass production and flexible production. Use when diagnosing operational waste, designing production flows, setting up quality systems, or comparing batch-and-queue to one-piece flow.

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

Use this skill when tool outputs exceed 2000 tokens, tasks span multiple conversation turns, sub-agents need to share state, context window is bloating, plans need to persist across summarization, terminal/log output needs selective querying, or when user mentions "offload context", "dynamic context discovery", "filesystem memory", "scratch pad", "reduce context bloat", or "just-in-time context loading".

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

Runtime router for context decisions during a task — decide read-more / stop / ask / assume / delegate, pick a minimal read-set, and time compaction. Front-page mental model is Write / Select / Compress / Isolate; a lazy pattern index routes to 25 context-engineering patterns, one reference per decision. Use when context is near budget, a long session is degrading, you must choose what to read for a task, or you are deciding /compact vs /clear vs a sub-agent. NOT for structural .claude/ overhead audits (see mk:context-audit); NOT for owning persistence (see mk:memory); NOT for USD cost (see mk:budget).

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

This skill should be used when the user asks to "offload context to files", "implement dynamic context discovery", "use filesystem for agent memory", "reduce context window bloat", or mentions file-based context management, tool output persistence, agent scratch pads, or just-in-time context loading.

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