Results for “explain”

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

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

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

Build a visual sequence that proves, explains, and supports decisions.

Turns a GitHub pull request into a code-change explainer video with changelog, feature reveal, or refactoring walkthrough built from the diff, commits, and files.

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.

Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.

Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.

Teach and guide GitHub workflows. Explains concepts, recommends approaches, and references specialist GitHub skills for execution.

Run, watch, debug, extend, or explain MarketingClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.

Creates 3Blue1Brown-style animated explainer videos, algorithm visualizations, and math animations using Manim Community Edition.

Front door to the small-business toolkit — routes a vague or specific request to the best skill and explains what's available.

Explains cryptographic primitives and provides Python implementations for encryption, hashing, key exchange, and digital signatures.

Transform code files into learning resources by adding educational comments that explain syntax, idioms, and design choices.

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

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.

Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.

Use when content is verbose, repetitive, or padded and needs tightening while preserving meaning

Analyzes codebases in depth and produces structured markdown analysis documents covering architecture, module design, call flows, data models, and design patterns.

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"

Structured root cause analysis for arriving at a concrete action. Use when something went wrong, a pattern keeps recurring, behavior has drifted, or you catch yourself resolving to "do better" / "remember to X" without a concrete artifact. Five-whys forces behavioral resolutions into file edits, config changes, memory block updates, or scheduled jobs — the action item must produce a diff someone else can verify. Do not use for simple debugging with an obvious cause.

构建可复用的Manim解释器，用于技术概念、图表、系统图和产品演示，并在需要时移交给更广泛的ECC视频栈。当用户希望获得清晰的动画解释而非通用的人物讲解脚本时使用。

Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.

Understand through recursive decomposition and modular reconstruction of simple operations to reproduce emergent complexity. Use this skill whenever reasoning is required. Framework for [[#parse|parsing]], [[#branch|branching]], [[#reduce|reducing]], [[#ground|grounding]] and [[#emit|emitting]]. Employs metacognitive reasoning epistemology, leveraging first principles through recursive decomposition[^1]. Self-referential and scale-invariant.

Identify underspecified areas in the current feature spec by asking targeted clarification questions and encoding answers back into the spec.

Reduce complexity of over-engineered code. Identify unnecessary abstractions, remove dead code, flatten deep nesting, and simplify logic while preserving behavior.