Results for “explain”

Explain a hard concept at a target level using a concrete analogy and a check for understanding.

Produces a complete narrated, subtitled, scored explainer video from a single topic prompt using a six-stage pipeline with script, voiceover, keyframes, animation, music, and local assembly.

补充上下文，用更简单、明确的中文重新解释。

Creates technical explainer animations with Manim, covering graphs, workflows, and system diagrams, and produces storyboards, scene plans, and rendered MP4s.

Guides the implementation of ethical AI principles, including fairness auditing, bias mitigation, explainability, accountability, and privacy protection in machine learning systems.

Explains machine learning model predictions using SHAP values, covering feature importance, visualizations, debugging, bias analysis, and production deployment.

Provides best practices for optimizing MariaDB queries, including indexing strategies, EXPLAIN analysis, pagination, histogram statistics, and MariaDB-specific optimizer settings.

Create animated technical explainers using Manim for graphs, workflows, system diagrams, and product walkthroughs with precise motion and clear scene planning.

Explains machine learning model predictions using SHAP values, covering feature importance, visualization plots, model debugging, bias analysis, and production deployment.

Optimize PostgreSQL queries, configure replication, and implement advanced database features with EXPLAIN analysis, JSONB operations, extension usage, and VACUUM tuning.

Always start with EXPLAIN ANALYZE to understand execution:

Prompt Dummy - explain any AI prompt in plain English

Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed.

"Make it interpretable" is four different requests.

Require the learner to explain a concept in their own words before the AI evaluates or extends it. Ensures the AI works from the learner's understanding rather than providing an explanation from scratch.

Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a website (/product-launch-video — promo or tour). Unclear → /hyperframes.

Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.

Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.

Refines task understanding through iterative questioning before executing, using the Joyride extension for human input.

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

Explain machine learning model predictions using SHAP values, compute feature importance, and generate visualizations including waterfall, beeswarm, bar, scatter, force, and heatmap plots.

Breaks down technical topics into plain-English explanations covering who, what, where, why, and when.

Explain any concept in plain words with one concrete analogy - clear enough for a smart child or a busy outsider, never condescending, never wrong.

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

Simplify UI designs by removing unnecessary complexity, clarifying hierarchy, and focusing on essential elements.

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

Unified math capabilities - computation, solving, and explanation. I route to the right tool.

2-stage pipeline: trace (causal investigation) -> deep-interview (requirements crystallization) with 3-point injection