메뉴
Explain a technology, technique, tool, platform, or concept using a structured format (Kind, Background, and more). Triggered when the user wants a structured tech overview. Keywords include "explain", "explainer", "tech overview", "describe tool", "what is".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user provides the wikitext of a MediaWiki/Wikipedia article (a .wikitext/.txt file or pasted markup) and wants to find events its chronology is MISSING. Works on dedicated "Timeline of ..." pages AND on the History section of any ordinary article. Parses the existing dated entries, numbers them, researches notable events for the theme, cross-checks against the latest version/release info, and reports gaps as suggested new entries with the entry number each would take. Triggers on "find missing events", "gaps in this timeline", "check this history", "what's missing from this history/timeline", "research this timeline", "suggest events for this timeline".
Use when the user gives a Wikipedia (or any MediaWiki) page URL and wants its raw source. Fetches the underlying MediaWiki wikitext (the raw markup) for the page via the MediaWiki API. Triggers on "get the wikitext", "fetch the MediaWiki source", "raw wiki source", "wikitext of this page", or pasting a wikipedia.org/wiki/... URL and asking for its source.
Translates input prose steps or bash commands into equivalent PowerShell 7 commands on Windows.
Use as an English-Japanese / Japanese-English dictionary and thesaurus. Triggered when the user wants to look up word meanings, translations, synonyms, antonyms, collocations, or etymology. Keywords include "meaning", "define", "translate", "synonym", "antonym", "collocation", "etymology", "thesaurus", "dictionary".
Use as a Japanese-English / English-Japanese translator. Triggered when the user wants to translate text between Japanese and English. Keywords include "translate", "translation", "put into English", "put into Japanese", "English version", "Japanese version".
| name | tech-explainer |
| description | Explain a technology, technique, tool, platform, or concept using a structured format (Kind, Background, and more). Triggered when the user wants a structured tech overview. Keywords include "explain", "explainer", "tech overview", "describe tool", "what is". |
Explain a given technology, technique, tool, platform, or concept using the structured format below. Use the context7 MCP tools to fetch up-to-date documentation when available. Write clearly and concisely in English.
When the user asks to explain, describe, or break down a specific technology, technique, tool, platform, or concept using this structured format. Keywords include "explain", "explainer", "tech overview", "describe tool", "what is".
Given a topic, produce an explanation with the following sections:
Define what the topic is and categorize it (e.g., programming language, design pattern, protocol, framework, platform, algorithm, etc.).
Describe the background context and the problem(s) this topic solves. Why does it exist? What need does it address?
Explain how it works: the operating principles, architecture, or implementation details. Highlight its strengths and key characteristics.
List what influenced or inspired the topic — predecessor technologies, research papers, other tools, or concepts it draws from.
Provide a brief history and timeline of major milestones (creation, major releases, adoption events, etc.).
List similar or related items — alternatives, competitors, complementary technologies, or concepts in the same domain.
Write a concrete user story that illustrates a practical use case. Describe a realistic scenario where someone would use this technology to solve a problem.
Provide code examples used in the story above. Keep them minimal, runnable, and well-commented.
