Claude Skill

explain

Explain the architecture and logic of a specified module or design in plain, approachable language.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download tykisgod-quick-question-skills_explain-7ea04b8.zip · 1 KB

Install

skills CLI npx skills add https://github.com/tykisgod/quick-question/tree/main/skills/explain
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tykisgod-quick-question@llmmart
Git git clone https://github.com/tykisgod/quick-question.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole tykisgod/quick-question collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).

In a Unity project, for "how does X work right now", also query the live Editor (read-only) so you explain what the code actually does, not just what it says. Channel per shared/unity-live-state.md: official Unity CLI (Library/Pipeline/.unity-pipeline-port exists; never open or print it — it holds an eval token) → unity command --project-path "$PWD" --json --no-banner <find_gameobjects|get_component_properties|get_serialized_fields|get_scene_hierarchy> -- <params> (parameters: unity command --project-path "$PWD" --query <keyword> --detail full --json); tykit (Temp/tykit.json) → get-properties / get-field / get-array / inspect; neither → explain from source and say the runtime values are unverified.

Arguments: $ARGUMENTS

  • Module or design name (e.g., "PlayerController", "inventory system", "save system")

Behavior

  1. Read design docs: Start by checking for project documentation (e.g., Docs/, Documentation/, or AGENTS.md) to understand the design intent
  2. Read core code: Find the key interfaces and implementation classes to understand the actual structure
  3. Explain in plain language, following these principles:
    • Start with a real-world analogy to build intuition
    • Then break down the concrete code structure (use a tree diagram or simple illustration)
    • Explain "why it was designed this way" not just "what it is"
    • If there is a history of evolution (changed from A to B), explain the motivation
    • Point out common pitfalls or misconceptions
  4. Do not:
    • Do not paste large blocks of source code; use pseudocode or key lines instead
    • Do not pile on design pattern terminology (say "each ship has its own service container", not "per-instance service locator pattern with dependency injection")
    • Do not assume the reader knows the project history
Files (quick-question)
  • SKILL.md 2.1 KB
    ---
    description: "Explain the architecture and logic of a specified module or design in plain, approachable language."
    ---
    
    Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
    
    > **In a Unity project**, for "how does X work right now", also query the live Editor (read-only) so you explain what the code *actually* does, not just what it *says*. Channel per [`shared/unity-live-state.md`](../../shared/unity-live-state.md): official Unity CLI (`Library/Pipeline/.unity-pipeline-port` exists; never open or print it — it holds an eval token) → `unity command --project-path "$PWD" --json --no-banner <find_gameobjects|get_component_properties|get_serialized_fields|get_scene_hierarchy> -- <params>` (parameters: `unity command --project-path "$PWD" --query <keyword> --detail full --json`); tykit (`Temp/tykit.json`) → `get-properties` / `get-field` / `get-array` / `inspect`; neither → explain from source and say the runtime values are unverified.
    
    Arguments: $ARGUMENTS
    - Module or design name (e.g., "PlayerController", "inventory system", "save system")
    
    ## Behavior
    
    1. **Read design docs**: Start by checking for project documentation (e.g., `Docs/`, `Documentation/`, or `AGENTS.md`) to understand the design intent
    2. **Read core code**: Find the key interfaces and implementation classes to understand the actual structure
    3. **Explain in plain language**, following these principles:
       - Start with a real-world analogy to build intuition
       - Then break down the concrete code structure (use a tree diagram or simple illustration)
       - Explain "why it was designed this way" not just "what it is"
       - If there is a history of evolution (changed from A to B), explain the motivation
       - Point out common pitfalls or misconceptions
    4. **Do not**:
       - Do not paste large blocks of source code; use pseudocode or key lines instead
       - Do not pile on design pattern terminology (say "each ship has its own service container", not "per-instance service locator pattern with dependency injection")
       - Do not assume the reader knows the project history
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.