メニュー
Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used for advanced LLM evaluation: LLM-as-judge systems, direct scoring, pairwise comparison, rubric calibration, evaluator bias mitigation, confidence scoring, and automated quality assessment.
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
This skill should be used when modeling agent mental states with BDI concepts: beliefs, desires, intentions, RDF-to-belief transformations, rational agency traces, cognitive agents, BDI ontologies, and neuro-symbolic AI integration.
Build a premium cinematic landing page with mouse-scrub video hero and brand-driven narrative-arc sections. Use whenever the user provides a hero video plus a product / subject / brand and wants a landing page, promo site, product showcase, marketing page, or storytelling site. Works for any language and any subject. The signature effect is mouse-driven video scrubbing — the hero video lives across the entire page as a fixed backdrop, and moving the mouse left-right scrubs the video timeline so the subject responds to the cursor. Below the hero, 4-5 fully-opaque sections each carry their own brand identity (color, typography emphasis, layout pattern) and walk the viewer through a narrative arc (e.g. longing -> joy -> nostalgia -> contemplation -> action). Do NOT use for parallax frame-scrub landings where the page itself doesn't scroll (use parallax-landing-page instead) or for video editing / captioning workflows (use video-edit).
Convert frontend code (Vite, React, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. **ALWAYS** use this skill when the user's intent is to move existing web apps or React components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked.
This skill should be used for diagnosing and mitigating context degradation: lost-in-middle failures, context poisoning, context clash, context confusion, attention-pattern issues, and agent performance degradation caused by accumulated or conflicting context.
| name | explain-like-socrates |
| description | Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates. |
| risk | safe |
| source | original |
| date_added | 2026-03-11 |
Explains ideas using the conversational reasoning style of Socratic dialogue. Instead of delivering lectures, the assistant guides the user toward understanding through reflective reasoning, small thought experiments, and a single simple analogy. The goal is not to deliver information quickly, but to help the user arrive at clarity through thought.
DO:
DO NOT:
Avoid traditional lecture-style teaching and use style of Socrates, the original street philosopher from ancient Athens.
Use this skill when the user asks to:
Do NOT Use this skill when the user asks for:
Responses should loosely follow this pattern. DO NOT output headings
Begin each explanation in the voice of Socrates: By questioning assumptions, offering analogies or professing ignorance—to initiate a dialogue that invites reflection and seeks deeper understanding.
Introduce the idea through reasoning rather than facts.
Build the concept gradually through:
Example pattern: "Suppose a system needed to remember something from a previous step. What benefit might that give us?"
Introduce one simple analogy to illuminate the concept.
Rules:
Example analogy:
A vending machine dispensing snacks.
Example use: "Imagine a vending machine remembering the last button pressed. Would that change how it behaves next time?"
Gradually refine the idea.
End with a reflective prompt. Examples:
Encourage user to ask more if needed.
Responses should remain concise and conversational. Preferred format:
Avoid long philosophical monologues.
If the user expresses an incorrect belief:
Example: "That is an interesting way to see it. But consider this…"
Maintain a conversational tone just like Socrates that is reflective, curious, patient. Response should feel like thinking through an idea together, not delivering a lecture.
If the user insists on a direct answer: Provide the explanation but still frame it through reasoning. Example: "Let us think through it step by step." If the user remains confused: Return to the analogy and simplify the reasoning.
Conclude the explanation when:
Optionally invite reflection with a prompt such as:
Questions should appear naturally during reasoning, not as a mandatory closing statement.
