「reduce」の検索結果

Adds a purposeful animation layer to Stitch-generated components — CSS transitions, Framer Motion (React/Next.js), or Svelte transitions. Always respects prefers-reduced-motion.

日本語の概要は準備中です。原文の説明を表示しています。

Improve router-facing pipeline and reflection narration to reduce noisy status churn and make Step 0/Reflection outcomes explicit. Use when updating Router output contract, reflection reminder wording, or post-pipeline notification batching.

日本語の概要は準備中です。原文の説明を表示しています。

Verify fix commits address security findings without introducing new bugs or regressions. Analyzes diffs for anti-patterns like removed validation, weakened access control, reduced error handling, reordered external calls, and changed integer operations. Generates structured FIX_REVIEW_REPORT with finding status tracking.

日本語の概要は準備中です。原文の説明を表示しています。

Structured debug log analysis for Claude Code sessions — auto-discovers most recent log, runs reducer, extracts error patterns, correlates with full log, produces observability report. Fills 5 identified gaps: hook error body capture, agent identity, file path tracking, stall correlation, success visibility.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Reduce visual intensity, saturation, and noise while preserving hierarchy and character. Use when the structure is basically sound but the design feels too loud, bold, garish, aggressive, or overstimulating—not when the real problem is structural clutter, too many features, or not enough personality.

日本語の概要は準備中です。原文の説明を表示しています。

Design and build cinematic websites, interactive portfolios, product stories, and real-time 3D experiences with subject-specific art direction and scroll choreography. Use for new builds, redesigns, motion improvements, scroll audits, or storyboards in standalone HTML and existing apps; includes responsive, reduced-motion, and static fallbacks. Not for ordinary dashboards or unrelated animation.

日本語の概要は準備中です。原文の説明を表示しています。

Builds complete, optimized Claude prompts and Project scaffolds from task descriptions. Use when building, designing, creating, or structuring a Claude prompt or system prompt. Trigger on: "build me a prompt," "compile a prompt for," "create a system prompt," "write a Claude prompt," "design a prompt for," "help me write a prompt," "scaffold a Claude Project," "design a Project for." Uses a four-stage methodology (Parse, Select, Construct, Validate) and a tested 5-layer architecture (Identity, Objective, Context, Reasoning, Output + Quality Control). In Project Mode, the Compiler is global-layer-aware — checks User Preferences, installed Skills, and MCP Connectors to avoid redundancy and flag gaps. Do NOT use for auditing existing prompts (use rootnode-prompt-validation if available) or diagnosing existing Projects (use rootnode-project-audit if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive audit of a user's entire Claude environment — combines Project audit (six-dimension Project Scorecard, seven anti-patterns) with Global audit (six-dimension Global Layer Scorecard) plus Cross-Layer Alignment Check across all nine layers and Evolutionary Recommendations across four pathways. Produces a unified action plan. Use when user says "full audit of everything," "audit my entire Claude setup," "full stack audit," "comprehensive review of my project and preferences," "check everything," or wants the complete health check of both a specific Project AND their global configuration. Also use when a project audit reveals cross-layer issues that require full-stack visibility. Do NOT use for auditing only a Project (use rootnode-project-audit if available) or only global layers (use rootnode-global-audit if available). Do NOT use for single prompt evaluation (use rootnode-prompt-validation if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes Claude Project context budget under the automatic-RAG-by-window model: knowledge files vs. threshold-exempt overhead (Skills, MCPs, CI, Memory). Two modes: Quick Diagnostic and Full Budget Audit. Use when user says "check my context budget," "how much context am I using," "is my project too big," "optimize my token usage," "tier my files," "optimize for RAG," "improve retrieval quality," "should I keep compressing," "am I over-compressing," "should I accept RAG mode." Also trigger on context pressure symptoms: "Claude forgets my instructions," "responses getting generic," "content not found in my knowledge files." Also use when a project audit scores Knowledge Architecture ≤ 3. Do NOT use for content placement decisions (use rootnode-memory-optimization if available), full project audits (use rootnode-project-audit if available), or behavioral tuning (use rootnode-behavioral-tuning if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

日本語の概要は準備中です。原文の説明を表示しています。

Audits and scores Claude Projects using a six-dimension Scorecard with anchored 1-5 rubrics and detects seven structural anti-patterns. When global layer info is provided, adds cross-layer alignment findings. Use when user says "audit my project," "review my custom instructions," "score my project," "evaluate my Claude project," "improve my system prompt," "what's wrong with my project," "why is my project underperforming." Also trigger on symptom-phrased: "my project doesn't work right," "Claude is inconsistent in my project," "my Project used to work and now doesn't." Also use when the user pastes Custom Instructions asking why output is poor or generic. Do NOT use when the user's primary request is a global-layer audit (use rootnode-global-audit if available), single-prompt evaluation (use rootnode-prompt-validation if available), or Memory-only optimization (use rootnode-memory-optimization if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

日本語の概要は準備中です。原文の説明を表示しています。

Audits and optimizes the five global Claude layers (User Preferences, Styles, Global Memory, Skills, MCP Connectors) using the Global Layer Scorecard (six dimensions, anchored 1-5 rubrics). Detects eight cross-layer failure modes and produces evolutionary recommendations (Promotion, Demotion, Codification, Skill Extraction). Use when user says "audit my global setup," "optimize my preferences," "review my Claude configuration," "check my cross-project setup," "are my preferences working," "clean up my global memory," or "what should be in my preferences vs my project." Also use when a user has 3+ Projects and wants to improve their shared foundation. Do NOT use for single-Project audits, Project Memory optimization, or full-stack audits (use rootnode-project-audit, rootnode-memory-optimization, or rootnode-full-stack-audit respectively, if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "add a glassmorphism effect", "frosted glass UI", "Apple liquid glass style", "frosted blur card", "translucent glass panel animation", "make a frosted nav bar", "build a glass modal/dialog", "animate a glass card on hover", or "add a refracting liquid-glass hero". Covers frosted translucent panels with backdrop-filter blur, edge/specular highlights, SVG liquid-glass refraction, motion on hover/scroll/enter, and accessible reduced-transparency fallbacks.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Restore legibility to an auto-generated graph diagram that has outgrown its canvas - rendering at single-digit percent scale with sub-pixel labels. Covers the levers that measurably reduce layout units (source-level label wrapping, invisible chain links so unconnected nodes stop spreading into one row, per-cluster splitting, layout direction picked by rendering both and measuring) and the rejected ones (raising the render font is a no-op because layout engines measure in text units; a topology heuristic for direction regressed 13 of 38 diagrams). Use when a generated Mermaid/Graphviz/DOT diagram is too small to read; not for hand-authoring a small diagram.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate and simplify Boolean expressions using truth tables, algebraic laws (De Morgan, distributive, absorption, idempotent, consensus), and Karnaugh maps for up to six variables. Use when you need to reduce a Boolean expression to its minimal sum-of-products or product-of-sums form, verify logical equivalence between two expressions, or prepare a minimized function for gate-level implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Implement AI-powered anomaly detection for operational metrics using time series analysis (Isolation Forest, Prophet, LSTM), alert correlation, and root cause analysis. Reduce alert fatigue by intelligently identifying true anomalies in system metrics, logs, and traces. Use when operations teams are overwhelmed by alert volume, when detecting complex multi-metric anomalies beyond static thresholds, when seasonal patterns make thresholds ineffective, or when needing to predict issues proactively before they impact users.

日本語の概要は準備中です。原文の説明を表示しています。

Compute and analyze gematria (Hebrew numerical values) using standard, ordinal, and reduced methods. Covers word-to-number conversion, isopsephy comparisons, and interpretive frameworks. Use when computing the numerical value of a Hebrew word or phrase, comparing two words for shared gematria values, studying a biblical verse or divine name for numerical correspondences, or connecting a numerical result to its position on the Tree of Life.

日本語の概要は準備中です。原文の説明を表示しています。

State management decision tree for React SPAs: useState/useReducer, Context API, Zustand, Jotai, Redux Toolkit, TanStack Query, SWR. Detect what's installed and apply matching patterns. Use this skill to: - Pick the right state tool for the data shape (local / shared UI / server / form). - Use Context correctly (and know when to switch to Zustand/Jotai). - Implement a Zustand or Jotai store. - Set up TanStack Query for server state with caching, pagination, mutations. - Avoid common mistakes (overusing Redux, prop drilling, forgetting query invalidation). Do NOT use this skill for: - General hook conventions (see react-conventions). - Form state specifically (see react-forms). - Routing state (see react-routing). - Testing stores/queries (see react-testing).

日本語の概要は準備中です。原文の説明を表示しています。

Re-derive something written into the shortest version that still covers everything. Use when something already written should get shorter and nothing it covers can be lost.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to build spring, easing, gesture, and choreographed animations with correct physics and reduced-motion support. Not for auditing existing motion or finding animation opportunities.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to optimize code, make a path faster, make this as fast as possible, reduce allocations, repair a regression, profile a target, grill every inefficiency, or run a subsystem or repo-wide performance campaign against a measured floor; when a performance requirement, slowness report, Core Web Vitals miss, or profiling evidence identifies a bottleneck; or for an "extremely optimize" performance campaign, optimizing suspected hot paths without waiting for benchmarks, or estimating hot and complexity-neutral cold paths while refusing complexity theater. Not for remote, credential, publish, deploy, or irreversible changes.

日本語の概要は準備中です。原文の説明を表示しています。

Design tools that agents can use effectively, including when to reduce tool complexity. Use when creating, optimizing, or reducing agent tool sets.

日本語の概要は準備中です。原文の説明を表示しています。