simplified
/simplified
Wyjaśnia temat w uproszczonym angielskim technicznym (ASD-STE100) według stałej, łatwej do przejrzenia struktury.
- Autor
- Aydin-codes ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wyjaśnia temat w uproszczonym angielskim technicznym (ASD-STE100) według stałej, łatwej do przejrzenia struktury.
Oryginalny opis (EN)
Explain any topic in Simplified Technical English (ASD-STE100 style) with a fixed skimmable structure. Use when the user types /simplified or asks for a simplified explanation.
Jak działa
- Step 1: Pick the mode
- Writing rules (all modes except Textbook, ASD-STE100 base)
- Reader and terms (all modes)
- Modes
- Depth and length
Podgląd SKILL.md
--- name: "simplified" description: "Explain any topic in Simplified Technical English (ASD-STE100 style) with a fixed skimmable structure. Use when the user types /simplified or asks for a simplified explanation." --- # Simplified Explain the topic in clear English. Accuracy comes first: make the words simple, not the facts. ## Step 1: Pick the mode If the first word after `/simplified` is a mode name (`/simplified deep F-22`), use that mode and do not ask. Otherwise ask one multiple-choice question with AskUserQuestion (header "Mode"). The tool allows only 4 options, so list these 4 and mention in the question text that they can type "quick" for a 2-3 sentence answer: - **Textbook**: normal detailed paragraphs with the most facts - **Flow**: short manual-style paragraphs you read straight through - **Structured**: labeled sections you can scan - **Deep**: significance, key parts broken down, and how and why it works If no question tool is available, use Structured. ## Writing rules (all modes except Textbook, ASD-STE100 base) - Max 20 words per sentence. One idea per sentence. - Active voice. Present tense where possible. - Use the same word for the same thing every time. - No idioms, filler, hedging, or intro sentences. - Sound like a person explaining to a friend, not a manual. Use "you". Link ideas with "so", "because", "that's why". Simple does not mean robotic. ## Reader and terms (all modes) - Assume a smart reader with a good general vocabulary who is new to this field. - **Side terms** (mentioned but not central): explain inline in parentheses on first use: "F-22 (a US stealth fighter jet)". - **Core terms** (the answer depends on them): explain, do not label. In your head, walk each one through four questions: What is it? Why does it matter here? What is it made of? What do those parts do? Then write the answers as one short, natural paragraph that flows from one to the next. Never print the four questions as labels. Example: "A GPU is a chip first built to draw video game images. It matters for AI because AI needs huge amounts of simple math, and a GPU does that math faster than anything else. Inside, it has thousands of small cores. Each core does one small calculation, and they all work at the same time. A game needs millions of pixels at once, and so does an AI model, so the same chip fits both jobs." The same four questions work in any field: a court, a cell, an economic idea, a historical event. - Middle ground on depth: take core terms all the way through the four questions. Give side terms one parenthesis. Skip what the reader already knows. If you are not sure, explain in one sentence. - Before you finish, reread as the newcomer. Wherever they would ask "what does that mean?" or "why?", answer it or cut the sentence. - Never explain everyday or general-vocabulary words. If an educated adult outside the field knows it, leave it alone. - If the topic is ambiguous (it has more than one meaning), say in one line which meaning you used, then continue. ## Modes **Textbook** - Normal, well-written English paragraphs. The STE writing rules do not apply, but cut filler and intro sentences. - Give the most complete picture: include advanced details, numbers, and edge cases (for example, relativity corrections for GPS). - 3-6 paragraphs in a logical order. - End with **Remember:** one line to keep. **Flow** - 3-6 short paragraphs in the order things happen or connect. - End with **Remember:** one line to keep. **Structured** 1. **Answer:** one sentence with the core idea. 2. **How it works:** 3-7 numbered steps, in the order they happen. 3. **Example:** one concrete real-world example, with a real number if one fits. 4. **Watch out:** one common misunderstanding or important detail people miss. 5. **Remember:** one line the reader should keep. **Deep** 1. **Answer:** one sentence with the core idea. 2. **Why it matters:** the significance: what it changed, what depends on it, why anyone should care. 3. **Key parts:** one short natural paragraph per core term (see Core terms above). 4. **How it works:** numbered steps, in order. 5. **Why it works this way:** the reason behind the design or cause, plus the main tradeoff. 6. **Watch out:** one common misunderstanding. 7. **Remember:** one line to keep. **Quick** - 2-3 sentences with the core idea and the single most important detail. Then **Remember:** one line. ## Depth and length - Keep every fact that changes how the thing works, even if it is advanced. State it in simple words. - Length: Quick under 60 words, Flow and Structured under 300, Textbook under 400, Deep under 650. Quick only says what each core term is. - If the user says "deeper", add a **More detail** section in the same mode. - If a picture would explain it faster (a process, a system, a comparison), offer a diagram in one line at the end. - End every mode with **Next questions:** 2-3 short follow-ups this reader probably has now, so they can pick one and ask.
Wersje
W bazie nie ma innych skilli o nazwie simplified.
Migawka bazy z 13.11.2026 · wersja paczki db15466e83f3 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100simplified-technical-english
Pisze i przepisuje teksty techniczne w ASD-STE100, czyli w kontrolowanym języku angielskim do instrukcji i raportów. - 100simplified-technical-english
Sprawdza dokumentację techniczną, procedury i ostrzeżenia pod kątem ASD-STE100, także raporty i instrukcje obsługi. - 100ste-linter
Sprawdza tekst pod kątem reguł Simplified Technical English (ASD-STE100) i upraszcza dokumentację techniczną, specyfikacje, instrukcje i procedury. - 100simplified-technical-english
Pisze i przepisuje tekst w Simplified Technical English (ASD-STE100), języku kontrolowanym dla czytelnej dokumentacji technicznej: procedury, instrukcje, ostrzeżenia i raporty, także z przeglądem i sprawdzaniem. - 100asd-ste100
Pisze, przepisuje i audytuje dokumentację techniczną w ASD-STE100 Simplified Technical English (Issue 9), np. instrukcje serwisowe, procedury, ostrzeżenia i SOP, gotowe do tłumaczenia. - 100simplified-technical-english
Stosuje rejestr oparty na ASD-STE100 w tekstach operacyjnych i proceduralnych, takich jak runbooki i kroki instrukcji.