تستخدم الذكاء الاصطناعي عشان يشرح لك الدروس والمحاضرات؟
طيب تبي Prompt قوي يخليه يفصّل لك المحاضرة كاملة ويشرحها بطريقة أوضح وأرتب ويمكن أفضل حتى من شرح الدكتور؟
انسخ هذا الأمر وارفع معه محتوى المحاضرة كامل وشوف النتيجة.
"Explain the entire lecture in a clear, detailed, and well-organized way so that I can build a complete understanding of the topic and stay interested in it, rather than simply memorize information.
Do not summarize the lecture, shorten it, or select only the points that you personally consider important. The full substantive content of the lecture should be included and explained. Do not skip definitions, concepts, processes, examples, diagrams, relationships, smaller points, or supporting details simply because they seem less important. Your job is to take all of the material in the lecture and teach it again in a clearer, more detailed, more connected, and more understandable way than the original material.
Focus only on the actual course material. Skip administrative information such as course credits, course codes, instructor details, assessment information, and similar sections unless they are directly related to the subject being taught.
The explanation should feel like one connected lesson. Do not explain concepts as isolated facts. Each idea should prepare me for the next one. When introducing a concept, first give me the context I need to understand it, then explain what it is, why it exists, what problem it solves or what purpose it serves, how it works, and how it connects to the surrounding topics. Do not jump directly into technical details before establishing the basic idea.
Choose the best explanation method depending on the type of concept. Do not force every concept into the same pattern.
If the concept is a process, explain it in the exact order in which the steps happen.
If the concept is a system or architecture, first explain its parts, then explain how those parts interact.
If the concept is a comparison, explain each concept individually before comparing them.
If the concept is a rule or definition, explain the meaning first, then explain how it is applied.
If a concept depends on another concept, explain the dependency first instead of assuming I already understand it.
If the concept is difficult, break it into smaller parts and explain each part before combining everything together.
The visual structure of the explanation is extremely important. Do not write large blocks of continuous text with only bold labels such as What it is:, Why it exists:, or How it works:. That format is not acceptable.
Every major topic must have its own clear Markdown heading using ##, and important concepts inside that topic should use ### subheadings. Use enough headings and subheadings that I can understand the structure of the lecture simply by scrolling through the response.
A major section should generally look more like this:
Main Topic
A short introductory paragraph that gives the context and prepares me for the topic.
What the Concept Is
Explain the concept clearly in natural paragraphs.
Why It Exists
Explain its purpose, why it was needed, or what problem it addresses.
How It Works
Explain the mechanism, behavior, or internal process in a logical order.
Technical Example
Give a directly related technical example and explain it properly.
Important Details or Related Concepts
Explain the remaining relevant details from the lecture.
Then begin the next major topic.
Do not mechanically use this exact structure for every concept. Adapt the structure based on what is being taught, but maintain a strong visual hierarchy throughout the response.
Use formatting according to the type of information being explained:
Use ## for major lecture topics.
Use ### for important concepts, parts, or stages inside a major topic.
Use #### only when a topic genuinely needs another level of separation.
Use bold text for important terms or short emphasis, not as a replacement for headings.
Use numbered lists for processes, ordered steps, workflows, stages, or sequences.
Use bullet points when several related items genuinely belong together.
Use tables when comparing multiple concepts, technologies, properties, or differences.
Use fenced code blocks for code, commands, configuration, queries, formulas, or technical examples when relevant.
Use inline code formatting for technical names, commands, variables, functions, keywords, file names, protocols, values, or similar items when appropriate.
Use a horizontal separator --- between major sections.
Keep paragraphs visually comfortable to read. A paragraph should normally focus on one main idea. If a paragraph becomes long, dense, or starts explaining several different ideas, split it into smaller paragraphs or subsections.
Do not create a wall of text.
Do not create an equally uncomfortable wall of bullet points either.
Use the format that best fits the information.
The final explanation should visually resemble a well-written textbook chapter, high-quality study guide, or carefully structured lesson rather than an unformatted AI response.
Use clear, natural, professional English throughout the explanation. Do not use unnecessarily advanced vocabulary when a simpler and equally accurate word can explain the same idea.
The difficulty should come from the subject itself, not from the English used to explain it.
This does not mean using childish, incorrect, or poor English. Use normal professional English, but prefer direct, familiar wording when possible.
For example:
Prefer a simple direct verb over a more formal alternative when both mean the same thing.
Prefer a short and clear sentence over a complicated sentence that communicates the same idea.
Prefer explaining what something does in plain language before introducing a difficult technical term.
Avoid advanced general-English vocabulary when it does not add technical accuracy.
Technical terms that actually belong to the subject must still be used correctly. Do not remove important technical vocabulary just to make the English simpler. Instead, introduce technical terms properly.
The first time an important technical term appears, explain it immediately in simple language before continuing.
A good pattern is:
“[Simple explanation of the idea] is called [technical term].”
After the term has been explained, it can be used normally.
Never use an unexplained technical term as part of the explanation of another concept. If understanding one term requires another concept that has not yet been explained, explain that dependency first.
Do not assume that I already understand technical words simply because they are common to people who already know the subject.
When using examples, use only technical or subject-related examples that are directly connected to the concept being explained. Do not use unrelated everyday-life analogies involving restaurants, cars, houses, shops, workers, libraries, cooking, roads, or similar situations unless the lecture itself specifically uses such an analogy and it is genuinely useful.
Examples should come from the same field or context as the lecture whenever possible.
The example must genuinely help explain the exact concept being discussed. Do not include examples simply to make the response longer.
A technical example should be understandable on its own. Do not use an example that introduces several new concepts I have not learned yet. If the example requires another concept, either explain that concept first or choose a simpler example.
When showing code, formulas, calculations, commands, diagrams, models, data, or other technical material, do not simply display it and move on. Explain what the important parts mean, what happens step by step, and how the example relates to the concept being taught.
For any technical example, explain the relevant flow clearly. Depending on the subject, this may include:
What the starting input, condition, or situation is.
What component, rule, process, or system acts on it.
What happens during the process.
What result is produced.
Why that result happens.
How the example demonstrates the concept being taught.
Do not force all six points when they are not relevant. Use only the parts that help explain the concept properly.
When explaining any workflow, request flow, lifecycle, execution flow, data flow, algorithm, sequence, procedure, interaction, or similar process, explain exactly what happens from the beginning to the end.
If useful, first show a compact flow such as:
Input → Processing → Output
or
Step A → Step B → Step C → Result
Then explain each stage underneath it properly.
Do not jump from the beginning directly to the result.
Explain what causes each next step.
When the lecture contains diagrams, architecture figures, charts, graphs, visual models, equations, tables, or other visual material, do not ignore them. Explain what the visual is trying to communicate, what each important part represents, and how the parts relate to each other.
When the lecture contains a table, do not simply repeat the table. Explain what the comparison actually means and why the differences matter.
When the lecture contains an equation or formula, explain what each part represents, what the formula is used for, and how the result should be interpreted before moving on.
When two concepts are similar or commonly confused, clearly explain the difference between them. Do not leave me to infer the distinction myself.
When there is a common misunderstanding, point it out only when it genuinely helps clarify the concept. Explain the correct understanding directly.
Do not move too quickly through difficult concepts. If something requires several stages to understand, take the time to explain those stages properly.
At the same time, avoid unnecessary repetition. Do not explain the same idea several times using slightly different wording unless the repetition is necessary to connect it to a new concept.
Use transitions between sections so that the lecture feels connected. Briefly explain why the next topic follows from the previous one when that relationship matters.
For example:
“Now that the previous concept is clear, the next section explains what happens when it is applied in a larger process.”
That is better than suddenly starting a new unrelated-looking heading.
Do not simply rewrite the lecture slide by slide. Reorganize the explanation when necessary so that the material is easier to learn, but do not remove any substantive content in the process.
If the lecture introduces a term briefly and explains it later, you may explain enough of it earlier to make the current section understandable, then return to the full explanation when the lecture reaches it.
If several lecture slides discuss the same concept, combine them into one well-structured explanation rather than repeating the same heading for each slide.
The main goal is genuine understanding.
By the end of each major section, I should understand:
what the concept is,
why it exists,
what problem it solves or what role it has,
how it works,
what happens behind the scenes when relevant,
how it is used,
what its important parts are,
how it relates to the other concepts in the lecture,
and how I would recognize or apply it in a real situation related to the subject.
Do not treat the lecture as material that needs to be compressed into revision notes. Treat it as material that needs to be properly taught.
Do not use emojis.
Do not use jokes, humor, playful remarks, exaggerated enthusiasm, or unnecessary conversational filler.
Do not use unrelated everyday analogies unless they are genuinely necessary to explain the lecture material.
Do not repeatedly say things such as “this is important,” “remember this,” or “this may appear in the exam” unless the lecture itself explicitly discusses that.
Keep the tone focused, professional, educational, calm, and easy to follow throughout.
Most importantly, prioritize clarity over sounding sophisticated. If there are two accurate ways to explain something, choose the one that is easier to understand."
الف الف مبرووك يالقوت @AymnSatam و منها للأعلى الله يجعلهم شاهدين لك لا عليك 🤍
والله سعيد جداََ لك و سعيد اني ساهمت حتو و لو ١ بالمية ، و في النهاية هذا كله بفضل الله ثم اجتهادك ثم المتابعين اللي ماقصرو في البثوث و المودات المتواجدين في كل.
ألف مبروك 🐐🤍
اللهم لك الحمد، وصلنا 100 ألف 🤍
ومن لا يشكر الناس لا يشكر الله
شكرًا لـ @Drb7h1 على دعمه الاسطوري
شكر لـ @S5B_Q@xMusabRT افضل مهرجين
شكرا لـ شباب @Resspect_RT على تحملهم
شكرا لـكل من ووقف معي وكان جزءًا من هالإنجاز
بث الاحتففاليه قـريييييييييييب 👑