Loading...
Loading...
Found 4 Skills
Learn mode for explaining code, concepts, and architecture. Use when user asks to explain how things work, understand concepts, or learn about code patterns. Provides explanations from simple to complex with examples and analogies.
Fixed-format explanation discipline for concepts, systems, and code. Use when the user asks "อธิบาย…", "นี่คืออะไร", "อันนี้ทำงานยังไง", "explain X", "what is X", "how does X work", "why does this exist"; when they ask for a simpler, shorter, or plainer version of something; when they say an answer was too long, unformatted, or unreadable; or when they invoke /feynman. Also use before teaching, onboarding, or presenting a concept to someone else.
Use when the user asks to explain what a piece of ADVPL/TLPP code does in plain language, adapting the explanation depth for a junior developer (line-by-line), a senior developer (business logic, design decisions, risks), or a functional consultant (no technical terms) -- e.g. understanding legacy code, filling in missing documentation, or assessing the impact of a customization. Also triggers on Portuguese phrasing like "explicar fonte", "explicar codigo", "o que essa rotina faz", "explicar para o consultor funcional", or requests for a --level junior/senior/funcional explanation.
Explain the last message, or a supplied file, link, or passage, in plain language a person follows on the first read. Use when the user invokes wtf because they did not follow something. Use ce-explain to investigate how or why code works, and ce-noslop to rewrite prose.