'continuity' 검색 결과

Update PROJECT_CONTINUITY.md and notes.toml with current session state. Use proactively before context compaction or when switching tasks.

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

This skill should be used when the user asks to "implement a DiD regression", "run a staggered difference-in-differences", "set up an event study", "implement IV / 2SLS", "run a regression discontinuity design", "build synthetic control", "do propensity score matching", "test parallel trends", "run Honest DiD", "wild cluster bootstrap", "Callaway-Sant'Anna", "Sun-Abraham", "Bacon decomposition", "double machine learning", "debiased machine learning", "DML / DoubleML", "cross-fitting", "causal forest", "heterogeneous treatment effects", "ATE with ML controls", "which causal design fits my data", or needs causal-inference code, diagnostics, or identification writing in Python (StatsPAI), R, or Stata. Based on Scott Cunningham's Causal Inference: The Mixtape, with runnable validated templates, ML-based causal inference patterns, and Journal of Finance applications.

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

Agente de contexto para continuidade entre sessoes. Salva resumos, decisoes, tarefas pendentes e carrega briefing automatico na sessao seguinte.

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

Applies Gestalt psychology principles to web layout, spacing, grouping, and visual hierarchy. Proximity, similarity, closure, continuity, figure-ground, common fate, Pragnanz — translated into CSS, component structure, and information architecture. Activate on 'gestalt', 'visual grouping', 'proximity spacing', 'visual hierarchy', 'perceptual organization', 'layout psychology', 'whitespace strategy'. NOT for color theory (use color-theory-palette-harmony-expert), not for accessibility auditing (use design-accessibility-auditor).

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

Persistent vector memory for Claude Code via LanceDB. Use when: remembering across sessions, storing lessons, recalling past decisions, maintaining context continuity. Tools: memory_store, memory_recall, memory_update, memory_forget, memory_merge.

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

Read-only audit of `.claude/` structural overhead. Reports prioritized "remove X save Y tokens" recommendations against the model context window. NOT for monetary cost tracking — that's /mk:budget. NOT for transcript size monitoring — long-session continuity defers to Claude Code native compaction. NOT for runtime context decisions (what to read, when to compact) — see mk:context-engineering. Use when planning to add context capacity, diagnosing perceived slowdowns, or auditing health.

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

Load relevant memories at session start for context continuity. IMPORTANT: Use this AUTOMATICALLY at the START of every session. Search for memories related to: - Current working directory/project - Recent activity (last 7 days) - Topics the user mentions in their first message Execute silently - do not announce what you're loading.

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

After a weekly report is built, diff it against the PRIOR report to find items that appear in BOTH weeks, then print the Owner (and prospect "Passed to") value recorded last week so it can be carried forward. Print-only — never edits the owner fields; Nathan verifies and re-tags in Notion. Invoked by weekly-report near the end, and standalone on "carry forward owners", "who owned this last week", "owner continuity".

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

Expert-level fluid mechanics covering fluid statics, continuity, Bernoulli, Navier-Stokes, boundary layers, turbulence, pipe flow, and external aerodynamics.

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

Expert-level fluid physics knowledge. Use when working with fluid statics, fluid dynamics, Bernoulli equation, viscosity, turbulence, Navier-Stokes equations, boundary layers, vorticity, compressible flow, or surface tension. Also use when the user mentions 'Bernoulli', 'Navier-Stokes', 'Reynolds number', 'turbulence', 'viscosity', 'boundary layer', 'vorticity', 'continuity equation', 'laminar flow', 'pressure', 'buoyancy', or 'surface tension'.

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

Expert-level topology knowledge. Use when working with topological spaces, continuity, compactness, connectedness, metric spaces, homeomorphisms, fundamental groups, homology, manifolds, or algebraic topology. Also use when the user mentions 'open set', 'closed set', 'compactness', 'connectedness', 'homeomorphism', 'homotopy', 'fundamental group', 'covering space', 'manifold', 'homology', 'Euler characteristic', or 'topological invariant'.

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

Real-time work context tracking for session continuity. Maintains task/step state across sessions, tracks progress, manages logs, integrates with phase enforcement.

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

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).

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

Select a current video model and endpoint against duration, references, motion, audio, ratio, quality, cost, and continuity requirements using live schemas.

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

Proposes the piping content a P&ID adds to an accepted PFD process model: line inventory with off-page continuity and required ancillary lines, line identification elements per the project line numbering procedure, connection items at nozzles matched to a quoted schedule, per quoted standards, specification break questions and observations. Every proposal cites its source and revision; no source, no proposal; never sizes a line or selects a class. Use when the user asks to "run the piping enrichment", "start the discipline enrichment", "list the lines the P&ID adds to this PFD" or "fill the line identifiers from the numbering procedure" after gate G2. Do not use for instruments, loops or instrument tags, use instrumentation-and-control-enrichment instead; do not use before gate G2, use process-model-check. Drafts for human review; never approves, authorises or signs off.

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

Use when the user asks to "pre-launch check the landing page", "run a Quality-Score preflight", or "verify ad-to-page message match before launch"; produces an ad↔page continuity report — message-match gaps, above-the-fold check, page-speed read, form-friction count, mobile-render flags — as a pass/fix punch list. Not for redesigning or rewriting the page — use landing-optimizer; not for scoring the account or the RQS — use ad-account-auditor. 落地页体验预检/广告落地页一致性检查

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

Cross-session progress tracking, pattern extraction, and session resumption. Gives agents memory across sessions using markdown files in `.memory/pipeline/progress/`. Subsumes self-improving-agent — handles both implementation tracking AND experiential learning in one skill. Workflows invoke specific protocols by name.

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

Serena MCP for project memory and code navigation. Use when managing Serena memories, navigating symbols, performing intelligent refactoring, or maintaining context/continuity across AI agent sessions.

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

Easing mathematics: production-level cubic bezier, damped spring, velocity continuity. Use when implementing, reviewing or testing easing mathematics for React, Vite, Next.js or Perfect_AI projects.

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

Three-file state management for session continuity. Maintains STATE.md, DECISIONS.md, and PROGRESS.md as human-readable session context alongside the SQLite ticket database. Use this skill when updating workflow state, logging decisions, tracking session progress, or resuming work after a context break.

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

Architectures and techniques for neural operators on discontinuous PDE solutions (shocks, contact discontinuities, steep gradients). Covers local-global spectral design (ShockFNO), reflection padding for non-periodic BCs, resolution scaling for shock width, and frequency-band error diagnostics. Use for low-viscosity Burgers, compressible Euler, Riemann problems, or any PDE where standard FNO produces Gibbs oscillations.

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

OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex". (gstack) Voice triggers (speech-to-text aliases): "code x", "code ex", "get another opinion".

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

Build the smallest, highest-signal context package for an AI coding task — goal, constraints, repo facts, boundaries, and a verification plan. Load when prompts are underspecified, the agent is missing key files or decisions, the user says "use the right context", "here's the repo", or when work is drifting due to missing constraints. Also triggers on "context engineering", "gather context", "what do you need from me", "before you start". Not for cross-session continuity (use memory-startup/memory-recall).

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

Audit or design server-side indexes, directories, reputations, or aggregates that are DERIVED from traffic a platform witnesses (chain heads, run verdicts, heartbeats, publish activity) so that consent gates the derivation, not merely the read: no shadow index over non-consenting principals, post-consent-only evidence windows, retention bounds and delete-propagation into derived rows, activity-oracle threat modeling, and audit-logged ranking discretion. Use when building a capability directory / whois from witnessed activity, a reputation ledger from settled outcomes, vitals aggregation across tenants, or any "the yellow pages can't lie because they index signatures" feature. Keywords: shadow index, derived index, consent gates derivation, activity oracle, phone book not a log, delist propagation, ranking weight audit, k-anonymous aggregate, subpoena surface. NOT for the consent-screen UX and scope-ladder mechanics themselves (use local-first-tenancy-boundary), reputation scoring math and Sybil economics (use agent-identity-continuity-reputation), or discovery-layer architecture L1/L2/L3 (use agent-discovery-directories-guilds).

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