Claude Skill

grandma

Explain technical concepts using everyday analogies that a grandma or 5-year-old could understand.

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

Install

skills CLI npx skills add https://github.com/tykisgod/quick-question/tree/main/skills/grandma
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).

Arguments: $ARGUMENTS — any technical concept, module, or design decision (e.g., "ECS", "why does the task system use a push model", "what is MCP", "A* pathfinding algorithm")

Behavior

  1. Understand the topic: If it's a project module, quickly read design docs and core code to understand what it actually does
  2. Find an everyday life analogy that:
    • Uses a scenario everyone has experienced (cooking, queuing, moving house, school, grocery shopping...)
    • Covers the core mechanism, not just a surface similarity
    • If the concept has multiple layers, use different roles/stages within the SAME scenario — don't switch scenarios
  3. Explain the entire concept through the analogy:
    • Start with the scene: "Imagine you're at..."
    • Map each role and action in the scene to key parts of the technical concept
    • After the analogy, "translate" back in one sentence: "What we just called X is actually Y in the code"
  4. If there are common misconceptions, address them: "Many people think... but actually..."
  5. Don't:
    • Use technical jargon (unless the user is asking what a specific term means)
    • Show code
    • Say "simply put" followed by something not simple
    • Say "it's like in programming..." — the audience doesn't know programming, that's not an analogy
    • Be condescending ("this is basic", "you can think of it as")
Files (quick-question)
  • SKILL.md 1.6 KB
    ---
    description: "Explain technical concepts using everyday analogies that a grandma or 5-year-old could understand."
    ---
    
    Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
    
    Arguments: $ARGUMENTS — any technical concept, module, or design decision (e.g., "ECS", "why does the task system use a push model", "what is MCP", "A* pathfinding algorithm")
    
    ## Behavior
    
    1. **Understand the topic**: If it's a project module, quickly read design docs and core code to understand what it actually does
    2. **Find an everyday life analogy** that:
       - Uses a scenario everyone has experienced (cooking, queuing, moving house, school, grocery shopping...)
       - Covers the core mechanism, not just a surface similarity
       - If the concept has multiple layers, use different roles/stages within the SAME scenario — don't switch scenarios
    3. **Explain the entire concept through the analogy**:
       - Start with the scene: "Imagine you're at..."
       - Map each role and action in the scene to key parts of the technical concept
       - After the analogy, "translate" back in one sentence: "What we just called X is actually Y in the code"
    4. **If there are common misconceptions**, address them: "Many people think... but actually..."
    5. **Don't**:
       - Use technical jargon (unless the user is asking what a specific term means)
       - Show code
       - Say "simply put" followed by something not simple
       - Say "it's like in programming..." — the audience doesn't know programming, that's not an analogy
       - Be condescending ("this is basic", "you can think of it as")
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.