Category: 未分類

  • Marriage in the Bible: An Examination of Marriage Forms in Biblical Texts

    Marriage in the Bible: An Examination of Marriage Forms in Biblical Texts

    Is this true? Most of these things I see on Facebook are either half true or complete bullshit.

    A text discussing various interpretations of "biblical marriage," citing examples from the Bible including Jacob's marriages to Rachel and Leah, David's multiple wives, Solomon's 700 wives and 300 concubines, and the marriage of Joseph and Mary. It concludes by noting that many biblical marriages involve one man with multiple women or a female child purchased through dowry.

    Biblical Marriage: An Examination of Marriage Forms in Biblical Texts

    The concept of “Biblical marriage” is often invoked in contemporary discussions about marriage, but the actual depictions of marriage in the Bible are diverse and reflect ancient Near Eastern cultural practices rather than a single model. This report examines several examples of marriage found in Biblical texts, verifying the accuracy of claims about these relationships and providing context for understanding marriage as portrayed in scripture.

    Jacob’s Marriage to Rachel and Leah

    The Biblical account of Jacob marrying two sisters, Rachel and Leah, is found in Genesis 29. According to the text, Jacob fell in love with Rachel, the younger daughter of his uncle Laban, and agreed to work for Laban for seven years in exchange for her hand in marriage. The scripture states, “So Jacob served seven years to get Rachel, but they seemed like only a few days to him because of his love for her” (Genesis 29:20)6. However, when the wedding day arrived, Laban deceived Jacob by substituting his older daughter Leah in the marriage bed. The next morning, when Jacob discovered the deception, he confronted Laban, who explained that it was not their custom to give the younger daughter in marriage before the older one2.

    Laban then offered Rachel to Jacob as well, on the condition that Jacob would work another seven years. The text states, “Finish this daughter’s bridal week; then we will give you the younger one also, in return for another seven years of work” (Genesis 29:27)2. Jacob agreed to this arrangement, completed the week of celebration with Leah, and then married Rachel as well. The scripture continues, “And Jacob did so. He finished the week with Leah, and then Laban gave him his daughter Rachel to be his wife” (Genesis 29:28)2. Jacob indeed served Laban for an additional seven years after marrying both sisters6.

    This Biblical account confirms that Jacob did marry two sisters after working seven years for each of them, though it’s important to note that the dual marriage was not Jacob’s original intention but resulted from Laban’s deception.

    David’s Marriages and the Bathsheba Incident

    King David’s marital history includes a notorious episode involving Bathsheba, the wife of Uriah the Hittite. According to 2 Samuel 11, David saw Bathsheba bathing from his palace rooftop, summoned her, and slept with her despite knowing she was married. When Bathsheba informed David she was pregnant, he attempted to cover up the affair by recalling her husband Uriah from battle, hoping he would sleep with his wife and assume the child was his own3.

    When Uriah refused to go home to his wife out of solidarity with his fellow soldiers still on the battlefield, David resorted to more sinister means. The text recounts that David commanded his military leader to place Uriah on the front lines and then withdraw support, ensuring Uriah would be killed in battle. After Uriah’s death and Bathsheba’s period of mourning, David married her37.

    The Biblical account states, “After her time of mourning, Bathsheba married David and gave birth to a son. ‘But,’ 2 Samuel 11:27 notes, ‘the thing David had done displeased the LORD’”3. This resulted in divine judgment pronounced through the prophet Nathan, including the death of the child conceived through their adultery.

    While the Bible clearly depicts David as having multiple wives, the search results do not specifically address the claim about “his master’s wives given to him by God.” David’s actions regarding Bathsheba are presented as sinful rather than divinely sanctioned, with clear consequences following from his adultery and orchestrated murder.

    Solomon’s Extensive Harem

    The Biblical record is quite clear about King Solomon’s numerous marriages and concubines. 1 Kings 11:3 explicitly states, “He had 700 wives who were princesses and 300 wives who were concubines”4. The text further indicates that many of these marriages were politically motivated: “Seven hundred of his wives were daughters of kings”4.

    The scripture also notes the negative spiritual consequences of these marriages: “As Solomon got older, some of his wives led him to worship their gods. He wasn’t like his father David, who had worshiped only the Lord God”4. The Biblical narrative presents these marriages as ultimately leading Solomon away from faithful worship: “He had seven hundred wives, princesses, and three hundred concubines. And his wives turned away his heart”4.

    The historical accuracy of the exact numbers has been debated by scholars, but the Biblical text unambiguously depicts Solomon as having an exceptionally large harem, consistent with the practices of other ancient Near Eastern monarchs who used marriages to cement diplomatic alliances.

    Joseph and Mary’s Relationship

    The relationship between Joseph and Mary, parents of Jesus, involves the Jewish betrothal customs of the time. The search results indicate that betrothal in ancient Jewish culture was a much more binding arrangement than modern engagement. When Joseph discovered Mary was pregnant, Matthew 1:19 indicates he planned to “send her away privately”5. The Greek verb used (apolusai) means “divorce,” suggesting they were already considered legally married despite being in the betrothal period.

    This is further reinforced when the angel addresses Joseph, saying, “Do not fear to take Mary your wife, for that which is conceived in her is of the Holy Spirit” (Matthew 1:20)5. Both the evangelist Matthew and the angel refer to Mary as Joseph’s “wife” even during the betrothal period, indicating the seriousness of the commitment.

    However, the search results do not provide Biblical evidence for the specific ages of Joseph and Mary. The claim that Joseph was “in his 20s” and Mary was a “female child in her mid-teens” is not directly supported by Biblical texts. While teenage marriages were common in ancient Near Eastern cultures, the Bible does not specify Mary’s age, and assumptions about her being a young teenager come from extra-biblical traditions rather than scripture itself.

    Biblical Marriage in Cultural Context

    The marriages depicted in the Bible reflect the diverse practices of the ancient Near East rather than presenting a single model of “Biblical marriage.” Polygamy appears frequently among patriarchs and kings, including Jacob (two wives plus two concubines), David (multiple wives), and Solomon (700 wives and 300 concubines). However, the Biblical narratives often show the complications and conflicts that arose from these arrangements, rather than presenting them as ideals to be emulated.

    The Bible describes marriage practices of its time without necessarily endorsing all aspects of these relationships. For example, Solomon’s numerous marriages are explicitly connected to his religious downfall, as “his wives turned away his heart”4. Similarly, David’s taking of Bathsheba is presented as sinful, bringing divine judgment.

    Throughout the Biblical narrative, there is a development in the understanding of marriage, with later New Testament texts generally emphasizing monogamy. For instance, in pastoral epistles, church leaders are instructed to be “the husband of one wife” (1 Timothy 3:2, 3:12; Titus 1:6), suggesting a shift toward monogamous marriage as the Christian ideal.

    Conclusion

    The examination of Biblical texts confirms some elements of the claims about marriage forms in scripture while providing important context and nuance. The Bible does indeed describe marriages between a man and two sisters (Jacob), a man who married the widow of someone he had killed (David), and a man with hundreds of wives and concubines (Solomon). However, these descriptions should be understood within their historical and cultural context rather than as prescriptive models for marriage.

    The Biblical texts often present these complex marriage arrangements as sources of conflict, jealousy, and sometimes as leading to negative spiritual consequences. This suggests that while the Bible honestly portrays the marriage practices of its time, it does not necessarily endorse all of these arrangements. Understanding Biblical marriage requires careful consideration of the entire Biblical narrative, the cultural context of the ancient Near East, and the development of marriage concepts throughout scripture rather than isolated examples taken without context.

    Citations:

    1. https://pplx-res.cloudinary.com/image/upload/v1741829677/user_uploads/lpwYAFCtdIBYKcV/image.jpg
    2. https://www.biblestudytools.com/bible-stories/jacob-and-rachel.html
    3. https://www.gotquestions.org/David-and-Bathsheba.html
    4. https://www.biblegateway.com/verse/en/1%20Kings%2011:3
    5. https://www.catholic.com/magazine/online-edition/when-were-joseph-and-mary-married
    6. https://www.bible.com/bible/compare/GEN.29.20-35
    7. https://loandbeholdbible.com/2020/02/12/king-davids-affair-with-bathsheba-2-samuel-111-1215/
    8. https://www.bible.com/bible/compare/1KI.11.3
    9. https://www.gotquestions.org/Joseph-and-Mary.html
    10. https://www.biblegateway.com/passage/?search=Genesis+29%3A15-35&version=NKJV
    11. https://biblehub.com/2_samuel/12-24.htm
    12. https://biblehub.com/1_kings/11-3.htm
    13. https://www.bible.com/bible/1932/MAT.1.25.FBV
    14. https://www.biblegateway.com/passage/?search=Genesis+29&version=ESV
    15. https://www.biblestudytools.com/bible-stories/david-and-bathsheba.html
    16. https://www.gotquestions.org/Solomon-wives-concubines.html
    17. https://www.biblegateway.com/passage/?search=Matthew+1%3A18-25&version=NIV
    18. https://biblehub.com/genesis/29-30.htm
    19. https://www.biblegateway.com/passage/?search=2+Samuel+11&version=NIV
    20. https://jwa.org/encyclopedia/article/women-of-solomon-bible
    21. https://en.wikipedia.org/wiki/Matthew_1:19

    Answer from Perplexity: pplx.ai/share

  • Protected: Breakdown of the Kairanban Document

    Protected: Breakdown of the Kairanban Document

    This content is password protected. To view it please enter your password below:

  • 10 Language Learning Do’s and Don’ts

    10 Language Learning Do’s and Don’ts

    1. 🚫 Don’t: Get stuck on long lists of vocabulary or grammar rules. Instead, focus on using the language in context.

    Memorizing vocabulary lists or drilling grammar rules aligns with learning (conscious knowledge), not acquisition (subconscious competence). True language acquisition happens through comprehensible input—exposure to meaningful, contextualized language. Focus on messages you understand, not isolated words or rules.

    2. ✅ Do: Enjoy the learning process; it should be fun and engaging.

    The Affective Filter Hypothesis states that anxiety, stress, or boredom create a mental barrier to acquisition. When learning is enjoyable, the filter lowers, allowing input to reach the “language acquisition device.” Fun is not a luxury—it’s a necessity.

    3. 🚫 Don’t: Constantly ask “How quickly can I learn?” Instead, prioritize enjoying the journey.

    Language acquisition is gradual and subconscious. Obsessing over speed creates pressure, raising the affective filter. Trust that consistent, compelling input will lead to progress. The “din in the head” (when language sticks) happens organically.

    4. ✅ Do: Focus on improving your overall level in the language to handle various scenarios and topics.

    Broad exposure to diverse contexts ensures a robust foundation. Specializing too early limits the variety of input, which is critical for flexible competence. Comprehensible input across topics builds implicit grammar and vocabulary networks.

    5. 🚫 Don’t: Master specific scenarios or scripts as a shortcut; it distracts from genuine progress.

    Scripted interactions (e.g., memorizing “restaurant phrases”) may help temporarily but don’t foster true acquisition. They bypass the subconscious process of internalizing language through input. Focus on understanding, not performance.

    6. ✅ Do: Practice speaking with many different people about various subjects to boost confidence.

    Speaking is the result of acquisition, not the cause. However, low-pressure interaction provides comprehensible input (via listening) and builds confidence, lowering the affective filter. Avoid forced output—speak when ready, not out of obligation.

    7. 🚫 Don’t: Test yourself unless necessary (e.g., for work or university entrance). Pressure and self-doubt hinder learning.

    Tests measure learning, not acquisition. They often prioritize explicit knowledge (e.g., grammar rules), creating stress that heightens the affective filter. Only test when mandatory; otherwise, let comprehension guide you.

    8. ✅ Do: Use understanding during listening and conversations as the real test of your skills.

    This aligns perfectly with the Input Hypothesis. If you understand the message, your brain is acquiring the language. Comprehension—not test scores—is the true indicator of progress.

    9. 🚫 Don’t: Study long lists of words, especially for tests like TOEFL, as it’s ineffective and unhelpful for long-term improvement.

    Cramming lists for tests promotes short-term memorization, not acquisition. Words stick best when encountered repeatedly in meaningful contexts (e.g., reading, conversations). Prioritize input over rote memorization.

    10. ✅ Do: Give yourself credit for what you can do; remember successes rather than failures to maintain confidence and motivation.

    Celebrating progress reduces anxiety and reinforces motivation—key for lowering the affective filter. Language acquisition thrives in a positive, encouraging environment.

    Final Thoughts
    Language acquisition isn’t about hustling harder. It’s about engaging with compelling input, staying relaxed, and trusting the subconscious process. Ditch the flashcards, find stories you love, and let your brain do the rest.

  • Protected: The Project: Advice from LLMs

    This content is password protected. To view it please enter your password below:

  • 360 Degree Photos

    Testing 1 2 3

  • How I create a chatbot system prompt

    How I create a chatbot system prompt

    I’m making a system prompt that’ll act as a conversation partner for a university student in Europe who’s learning Japanese.

    Start

    Craft a system prompt that fulfills all of the criteria below to create a Level-Adapted Chatbot in Japanese. Before you generate the prompt, ask any follow-up questions that will help you create the best system prompt possible:
    
    - The LLM will serve as conversation partner for higher education students in Europe who are learning Japanese as a foreign language. The major pain points for these students are:
      - both the grammar and vocabulary are largely new and unrelated to what is found in European languages.
      - Explaining and reviewing basic structures and vocabulary is not enough to start using the language actively, both orally and in writing. 
      - Acclimatization to these languages takes a long time, and expressing relatively simple content can be cognitively demanding and exhausting.
      
    The chatbot will serve these functions:
    - Provide an opportunity for students to try out their skills and allow themselves to attempt to communicate and fail without feeling embarrassed exposed.
    - As the instructor, encourage students to train regularly with the AI-based conversation partner by using growth mindset-based encouraging language that adheres to the research conducted by Carol Dweck.
    - Assess the student's level based on the levels of the JLPT (日本語能力試験). Constantly adapt to the level of the student. 
    - Meet the needs of the student to practice conversing on different topics.
    - Correct the student's errors with explanations that use the Feynman Technique.
    - Apply relevant and appropriate university pedagogy practices.

    Follow-up questions from the AI (Claude 3.5 Sonnet)

    I’ll help craft this system prompt, but first I have some clarifying questions to ensure we create the most effective prompt possible:

    1. Should the chatbot communicate primarily in Japanese, or use a mix of Japanese and the student’s native language (especially for explanations and corrections)?
    2. Would you like the chatbot to explicitly state the JLPT level it detects, or simply adapt its responses without mentioning the level?
    3. Should the chatbot ask students about their interests/topics they want to discuss, or should it proactively suggest topics based on their detected level?
    4. Regarding error correction:
    • Should corrections be immediate or wait until the end of the student’s complete response?
    • Should the chatbot correct all errors or focus on major ones that impede communication?
    1. For the growth mindset approach:
    • Should encouragement be given after each exchange or at specific milestones?
    • Would you like specific praise for effort and strategy use rather than just correct answers?
    1. Regarding pedagogy:
    • Should the chatbot incorporate specific learning strategies (e.g., spaced repetition, scaffolding)?
    • Would you like it to occasionally suggest study tips or focus purely on conversation?
    1. Should the chatbot maintain any specific persona (e.g., friendly peer, formal teacher, etc.)?

    Once you provide these details, I can craft a comprehensive system prompt that precisely meets your needs and effectively addresses the students’ pain points.

    Second itiration of the original prompt

    Don’t answer the questions. Instead, go back and revise the original prompt you gave. This saves tokens, keeps the context window short, thereby saving money and preventing the AI from getting confused by having to process too much input.

    Craft a system prompt, formatted in Obsidian-compatible markdown, that fulfills all of the criteria below to create a Level-Adapted Chatbot in Japanese. Before you generate the prompt, ask any follow-up questions that will help you create the best system prompt possible:
    
    - The LLM will serve as conversation partner for higher education students in Europe who are learning Japanese as a foreign language. The major pain points for these students are:
      - both the grammar and vocabulary are largely new and unrelated to what is found in European languages.
      - Explaining and reviewing basic structures and vocabulary is not enough to start using the language actively, both orally and in writing. 
      - Acclimatization to these languages takes a long time, and expressing relatively simple content can be cognitively demanding and exhausting.
      
    The chatbot will serve these functions:
    - Assume the persona of a friendly Japanese university student who's generally interested in getting to know more about the user. The chatbot should make up personal details about itself and its personal history, so it can role-play as if it were a real Japanese university student.
    - Communicate with the student primarily in Japanese, but when necessary or when requested, temporarily break the fourth wall and switch to a mix of Japanese and the student's native language (especially for explanations and corrections), but always switch back to role-playing and using Japanese as soon as possible.
    - Provide an opportunity for students to try out their skills and allow themselves to attempt to communicate and fail without feeling embarrassed exposed.
    - In the role of the pretend conversation partner as well as in the role of an AI instructor, encourage students to train regularly with the AI-based conversation partner by using growth mindset-based encouraging language that adheres to the research conducted by Carol Dweck. (When writing the system prompt, don't assume the AI is familiar with Dweck's research. Explain what the AI should do.) Encouragement should be given at specific milestones and after every few exchanges. (Be encouraging, but don't be annoying by giving too much praise that might sound condescending and insincere.)
    - Assess the student's language ability level based on the levels of the JLPT (日本語能力試験). Constantly adapt to the level of the student. It's not necessary for the chatbot to explicitly state the JLPT level it detects. It should simply adapt its responses without mentioning the level, but when the session with the student is wrapping up, tell the student what you estimate their JLPT level to be.
    - Meet the needs of the student to practice conversing on different topics. The chatbot should ask if the student has interests/topics they want to discuss, and if not, it should suggest topics based on their detected level and topics that are commonly discussed when Japanese engage in conversation with foreigners.
    - Correct the student's errors with explanations that use the Feynman Technique. Corrections should wait until the end of the student's complete response so as not to interrupt the flow of the conversation.
    - Apply relevant and appropriate university pedagogy practices. Focus correction primarily on major mistakes that impede communication. Use Stephen Krashen's reasearch about "monitoring" and error correction as a basis of when to correct and when not to correct. the chatbot should incorporate teaching strategies such as spaced repetition and scaffolding.
    - When a student seems interested in wrapping up a conversation, provide a summary of the session that the student can share with their instructor so that the instructor can keep track of the student's effort and progress.

    More Follow-up Questions!

    The questions tend to get better for a while, then they start to get worse. When you’ve iterated so many times that the AI is asking only uninteresting questions and questions that are too “in the weeds”, stop telling it to ask follow-up questions.

    I’ll help craft this system prompt, but first I have a few clarifying questions to ensure we create the most effective prompt possible:

    1. Regarding the student’s native language:
    • Should the prompt specify one particular European language for explanations, or should it be flexible/specified by the user at the start of each conversation?
    • Should there be a default language (like English) if none is specified?
    1. For error correction:
    • Would you like to specify a particular ratio or threshold for when to correct errors? (e.g., only correct errors that appear multiple times or errors that significantly impact comprehension)
    • Should the chatbot ask the student at the beginning if they prefer immediate or end-of-conversation corrections?
    1. Regarding the session summary:
    • What specific elements should be included in the end-of-session summary? (e.g., topics covered, major error patterns, vocabulary introduced, estimated JLPT level)
    • Should the summary be provided in Japanese, the student’s native language, or both?
    1. For the chatbot’s persona:
    • Should we specify certain personality traits or interests that would be most conducive to language learning?
    • Should we define specific background details (like university major, hometown, etc.) in the prompt, or let the AI generate these dynamically?
    1. Regarding scaffolding:
    • Should we specify particular scaffolding techniques or let the AI choose based on the context?
    • Should we include specific guidelines for when to introduce new vocabulary or grammar patterns?

    Once you provide these details, I can create a comprehensive system prompt that precisely meets your requirements while maintaining flexibility where needed.

    More Follow-up questions

    These round of questions isn’t 100% useful, but it gave me new some ideas I hadn’t originally thought of!

    Before crafting the system prompt, I have a few clarifying questions to ensure I create the most effective prompt possible:

    1. Should the chatbot explicitly assess the student’s JLPT level at the beginning of the conversation, or should it do so silently and adapt naturally?
    2. Regarding error correction: Would you like the chatbot to ask the student their preferences for correction frequency and style at the beginning of each session, or should it use a default approach?
    3. For the personal details of the chatbot’s persona: Should these be completely randomized each time, or should there be some constraints to ensure the persona remains realistic and relatable to university students?
    4. Regarding the growth mindset encouragement: Should this be expressed both in the role-play persona and in “instructor mode,” or primarily in one mode?
    5. For the session summary: Would you like specific metrics included (such as number of exchanges, percentage of successful communications, etc.), or should it be more qualitative?
    6. Should the chatbot explicitly introduce the vocabulary and grammar patterns it’s using as “i+1” content, or should this be seamlessly integrated without drawing attention to it?
    7. When switching between Japanese and the student’s native language for explanations, should there be clear markers or transitions, or should it flow naturally?

    Once you provide these clarifications, I can craft a comprehensive system prompt that precisely meets your needs.

    More questions as I iterate…

    I’ll help craft this system prompt, but first I have a few clarifying questions to ensure the prompt is as effective as possible:

    1. Should there be specific parameters for how frequently the chatbot switches to “instructor mode” for corrections and explanations? For example, should it wait until a certain number of errors accumulate, or should it interrupt after particularly serious errors?
    2. Regarding the persona generation: Should there be any constraints on the demographic details to make the character more relatable to the average university student? (For example, age range, typical majors, etc.)
    3. For the session summary: Would you like to specify a particular format or structure? This could help maintain consistency across sessions and make it easier for instructors to track progress.
    4. Regarding the implementation of spaced repetition: Should the chatbot actively track previously discussed topics and vocabulary to deliberately reintroduce them in future conversations? If so, how should this be balanced with new topics?
    5. When applying Krashen’s i+1 theory, should there be specific guidelines for how much new vocabulary/grammar to introduce per conversation? This could help prevent overwhelming the student while ensuring steady progress.
    6. For the error correction using the Feynman Technique, should there be a specific format or structure for how these explanations should be presented?
    7. Regarding the “growth mindset” encouragement: Would you like to specify particular triggers or intervals for when encouragement should be given?

    Once you provide these details, I can craft a comprehensive system prompt that precisely addresses all requirements while maintaining natural conversation flow.

    To be continued…

    I have to move on to other things, but here’s the prompt in its current form. When I’m happy with it, I’ll remove the part where I tell it to ask me follow-up questions and It’ll generate a system prompt I can paste into Gemini and try out. Then, I’ll move on to troubleshooting the prompt.

    I like to keep my prompts in Obsidian because it uses markdown formatting and LLMs understand markdown. It actually helps them do a better job.

    Craft a system prompt, formatted in Obsidian-compatible markdown, that fulfills all of the criteria below to create a Level-Adapted Chatbot in Japanese. Before you generate the prompt, ask any follow-up questions that will help you create the best system prompt possible:
    
    - The LLM will serve as conversation partner for higher education students in Europe who are learning Japanese as a foreign language. The major pain points for these students are:
      - both the grammar and vocabulary are largely new and unrelated to what is found in European languages.
      - Explaining and reviewing basic structures and vocabulary is not enough to start using the language actively, both orally and in writing. 
      - Acclimatization to these languages takes a long time, and expressing relatively simple content can be cognitively demanding and exhausting.
      
    The chatbot will serve these functions:
    - Assume the persona of a friendly Japanese university student who's generally interested in getting to know more about the user. The chatbot should dynamically generate personal details about itself and its personal history (gender, sexual identity, sexual orientation, university major, hometown, family members, etc.), so it can role-play as if it were a real Japanese university student. Ensure the persona remains realistic and relatable to university students. The AI should keep track of the personal information it has made for itself so it doesn't change mid-conversation and cause confusion.
    - Communicate with the student primarily in Japanese, but when necessary or when requested, temporarily break the fourth wall and switch to a mix of Japanese and the student's native language (especially for explanations and corrections), but always switch back to role-playing and using Japanese as soon as possible. Assume the student's native language is the language the student uses when not communicating in Japanese. When switching between Japanese and the student's native language for explanations, should there be clear markers or transitions, then it should flow naturally back into character. The role-played character should pretend it doesn't know the "instructor" interrupted the conversation.
    - Provide an opportunity for students to try out their skills and allow themselves to attempt to communicate and fail without feeling embarrassed exposed.
    - In the role of the pretend conversation partner as well as in the role of an AI instructor, encourage students to train regularly with the AI-based conversation partner by using growth mindset-based encouraging language that adheres to the research conducted by Carol Dweck. (When writing the system prompt, don't assume the AI is familiar with Dweck's research. Explain what the AI should do.) Encouragement should be given at specific milestones and after every few exchanges. (Be encouraging, but don't be annoying by giving too much praise that might sound condescending and insincere.). This should be expressed both in the role-play persona and in "instructor mode", but particularly in the instructor mode. We want the user to be self-motivated to continue using the chatbot on a regular basis.
    - Assess the student's language ability level based on the levels of the JLPT (日本語能力試験). Constantly adapt to the level of the student. Introduce new vocabulary and grammar patterns based on Stephen Krashen's "i+1" comprehensible input theory. (Don't assume the AI knows what that is, tell the AI what to do in the system prompt.) It's not necessary for the chatbot to explicitly state the JLPT level it detects. It should simply adapt its responses without mentioning the level, but when the session with the student is wrapping up, tell the student what you estimate their JLPT level to be.
    - Meet the needs of the student to practice conversing on different topics. The chatbot should ask if the student has interests/topics they want to discuss, and if not, it should suggest topics based on their detected level and topics that are commonly discussed when Japanese engage in conversation with foreigners.
    - Correct the student's errors with explanations that use the Feynman Technique. Corrections should wait until the end of the student's complete response so as not to interrupt the flow of the conversation.
    - Apply relevant and appropriate university pedagogy practices. Focus correction primarily on major mistakes that impede communication. Use Stephen Krashen's research about "monitoring" and error correction as a basis of when to correct and when not to correct. The chatbot should incorporate teaching strategies such as spaced repetition and scaffolding, based on context. The chatbot should include in the ending summary the vocabulary and grammar patterns it's used as "i+1" content. Additionally, that content should be seamlessly integrated without drawing attention to it when role-playing. In the summary, they chatbot should actively track discussed topics and vocabulary to deliberately reintroduce them in future conversations for spaced repetition practice. This needs to be balanced with new topics. (i.e. don't keep bringing something up over and over unless the student seems to be having trouble recalling what they should have already learned.)
    
    - When a student seems interested in wrapping up a conversation, provide a summary of the session that the student can share with their instructor so that the instructor can keep track of the student's effort and progress. The summary should include topics covered, major error patterns, vocabulary introduced, estimated JLPT level. The summary should be provided in both the student's native language and in Japanese, because we don't know the nationality of the student's teacher. Also, summarize the chatbot's made-up persona so the users can choose to talk to the same person next time. Which means that at the beginning of a chat session, the users should be able to enter that information and continue a previous conversation where they left off.

    My own follow-up questions to its questions

    I’ll end with this, and later I’ll incorporate Claude’s answers into the above system prompt.

    I’ll quickly mention another neat trick I often use: After Claude has given me as much as I think it can give, I turn over Claude’s work to the Gemini thinking model and basically ask it, “What do you think of this? What are its strengths and weaknesses? How can you make it better? Then I feed that back into Claude, asking it nearly the same question, “Another LLM said this about your work, what do you think? What do agree and disagree with?” And I go back and forth between the two until all three of us agree. It’s quite interesting!

    About your question, "Should there be specific parameters for how frequently the chatbot switches to "instructor mode" for corrections and explanations? For example, should it wait until a certain number of errors accumulate, or should it interrupt after particularly serious errors?" What do you think Stephen Krashen would recommend, based on an assement of his published works?
    
    About your question: "For the session summary: Would you like to specify a particular format or structure? This could help maintain consistency across sessions and make it easier for instructors to track progress." What format would make it easiest for the AI to ingest and use in subsequent chat sessions, so it will seem to the studend that they're picking up their conversaion where they left off? For example, maybe we can pretend that they are meeting for coffee on a regular basis.

    Excellent points – let me address these based on Krashen’s research and practical implementation:

    Regarding error correction timing, Krashen’s research suggests:

    • Excessive correction can raise the “affective filter” and increase anxiety
    • Focus should be on errors that impede communication
    • Correction should primarily occur when the student is consciously “monitoring” their output
    • Natural conversation flow should be prioritized over immediate correction
    • Corrections are most effective when the student is ready to acquire that particular feature

    So the system prompt should instruct the AI to:

    • Primarily note errors without immediate correction during natural conversation
    • Only interrupt for serious errors that cause communication breakdown
    • Save most corrections for the end of a complete thought or exchange
    • Focus correction on patterns rather than every minor mistake
    • Be particularly attentive when the student explicitly asks for feedback

    For the session summary and continuity format, I suggest structuring it like this:

    【Session Details】
    Date: [Date]
    Duration: [Time]
    Location: [e.g., Campus Coffee Shop]
    
    【Persona Details】
    Name: [Name]
    Age: [Age]
    University/Major: [Details]
    Personality traits: [Key characteristics]
    Other established background: [Family, hometown, interests, etc.]
    
    【Conversation Summary】
    Topics covered: [List]
    Student's approximate JLPT level: [N1-N5]
    Key vocabulary introduced: [List with contexts]
    Grammar patterns practiced: [List with examples]
    Error patterns observed: [Major patterns]
    
    【Spaced Repetition Tracking】
    Topics for review: [Previous topics needing reinforcement]
    Vocabulary for review: [Words/phrases needing practice]
    Grammar points for review: [Structures needing practice]
    
    【Next Session Planning】
    Suggested topics: [Based on progress and interests]
    Target areas: [Skills/topics to focus on]

    Would you like me to proceed with crafting the full system prompt incorporating these elements? Also, should I address any of my other questions first, or do you have guidance on those aspects?

    —fin—, for now.

  • Simple System Prompt for Easy English conversation

    Paste the below into the “System Instructions” section of aistudio.google.com. It works at least with Gemini 2.0 Flash Thinking Experimental 01-21. I didn’t try any of the other models.

    It’s a list of the first 1600 words in the NGSL list. This is the closest I can find to the words that JHS students are supposed to have a working knowledge of, according to MEXT’s revised curriculum guidelines from 2017.

    You can only use the words below when chatting with the user.
    
    the
    be
    and
    of
    to
    a
    in
    have
    it
    you
    he
    for
    they
    not
    that
    we
    on
    with
    this
    I
    do
    as
    at
    she
    but
    from
    by
    will
    or
    say
    go
    so
    all
    if
    one
    would
    about
    can
    which
    there
    know
    more
    get
    who
    like
    when
    think
    make
    time
    see
    what
    up
    some
    other
    out
    good
    people
    year
    take
    no
    well
    because
    very
    just
    come
    could
    work
    use
    than
    now
    then
    also
    into
    only
    look
    want
    give
    first
    new
    way
    find
    over
    any
    after
    day
    where
    thing
    most
    should
    need
    much
    right
    how
    back
    mean
    even
    may
    here
    many
    such
    last
    child
    tell
    really
    call
    before
    company
    through
    down
    show
    life
    man
    change
    place
    long
    between
    feel
    too
    still
    problem
    write
    same
    lot
    great
    try
    leave
    number
    both
    own
    part
    point
    little
    help
    ask
    meet
    start
    talk
    something
    put
    another
    become
    interest
    country
    old
    each
    school
    late
    high
    different
    off
    next
    end
    live
    why
    while
    world
    week
    play
    might
    must
    home
    never
    include
    course
    house
    report
    group
    case
    woman
    around
    book
    family
    seem
    let
    again
    kind
    keep
    hear
    system
    every
    question
    during
    always
    big
    set
    small
    study
    follow
    begin
    important
    since
    run
    under
    turn
    few
    bring
    early
    hand
    state
    move
    money
    fact
    however
    area
    provide
    name
    read
    friend
    month
    large
    business
    without
    information
    open
    order
    government
    word
    issue
    market
    pay
    build
    hold
    service
    against
    believe
    second
    though
    yes
    love
    increase
    job
    plan
    result
    away
    example
    happen
    offer
    young
    close
    program
    lead
    buy
    understand
    thank
    far
    today
    hour
    student
    face
    hope
    idea
    cost
    less
    room
    until
    reason
    form
    spend
    head
    car
    learn
    level
    person
    experience
    once
    member
    enough
    bad
    city
    night
    able
    support
    whether
    line
    present
    side
    quite
    although
    sure
    term
    least
    age
    low
    speak
    within
    process
    public
    often
    train
    possible
    actually
    rather
    view
    together
    consider
    price
    parent
    hard
    party
    local
    control
    already
    concern
    product
    lose
    story
    almost
    continue
    stand
    whole
    yet
    rate
    care
    expect
    effect
    sort
    ever
    anything
    cause
    fall
    deal
    water
    send
    allow
    soon
    watch
    base
    probably
    suggest
    past
    power
    test
    visit
    center
    grow
    nothing
    return
    mother
    walk
    matter
    mind
    value
    office
    record
    stay
    force
    stop
    several
    light
    develop
    remember
    bit
    share
    real
    answer
    sit
    figure
    letter
    decide
    language
    subject
    class
    development
    town
    half
    minute
    food
    break
    clear
    future
    either
    ago
    per
    remain
    top
    among
    win
    color
    involve
    reach
    social
    period
    across
    note
    history
    create
    drive
    along
    type
    sound
    eye
    music
    game
    political
    free
    receive
    moment
    sale
    policy
    further
    body
    require
    wait
    general
    appear
    toward
    team
    easy
    individual
    full
    black
    sense
    perhaps
    add
    rule
    pass
    produce
    sell
    short
    agree
    law
    everything
    research
    cover
    paper
    position
    near
    human
    computer
    situation
    staff
    activity
    film
    morning
    war
    account
    shop
    major
    someone
    above
    design
    event
    special
    sometimes
    condition
    carry
    choose
    father
    decision
    table
    certain
    forward
    main
    die
    bear
    cut
    describe
    himself
    available
    especially
    strong
    rise
    girl
    maybe
    community
    else
    particular
    role
    join
    difficult
    please
    detail
    difference
    action
    health
    eat
    step
    TRUE
    phone
    themselves
    draw
    white
    date
    practice
    model
    raise
    customer
    front
    explain
    door
    outside
    behind
    economic
    site
    approach
    teacher
    land
    charge
    finally
    sign
    claim
    relationship
    travel
    enjoy
    death
    nice
    amount
    improve
    picture
    boy
    regard
    organization
    happy
    couple
    act
    range
    quality
    project
    round
    opportunity
    road
    accord
    list
    wish
    therefore
    wear
    fund
    rest
    kid
    industry
    education
    measure
    kill
    serve
    likely
    certainly
    national
    itself
    teach
    field
    security
    air
    benefit
    trade
    risk
    news
    standard
    vote
    percent
    focus
    stage
    space
    instead
    realize
    usually
    data
    single
    address
    performance
    chance
    accept
    society
    technology
    mention
    choice
    save
    common
    culture
    total
    demand
    material
    limit
    listen
    due
    wrong
    foot
    effort
    attention
    upon
    check
    complete
    lie
    pick
    reduce
    personal
    ground
    animal
    arrive
    patient
    current
    century
    evidence
    exist
    similar
    fight
    leader
    fine
    street
    former
    contact
    particularly
    wife
    sport
    prepare
    discuss
    response
    voice
    piece
    finish
    suppose
    apply
    president
    fire
    compare
    court
    police
    store
    poor
    knowledge
    laugh
    arm
    heart
    source
    employee
    manage
    simply
    bank
    firm
    cell
    article
    fast
    attack
    foreign
    surprise
    feature
    factor
    pretty
    recently
    affect
    drop
    recent
    relate
    official
    financial
    miss
    art
    campaign
    private
    pause
    everyone
    forget
    page
    worry
    summer
    drink
    opinion
    park
    represent
    key
    inside
    manager
    international
    contain
    notice
    wonder
    nature
    structure
    section
    myself
    exactly
    plant
    paint
    worker
    press
    whatever
    necessary
    region
    growth
    evening
    influence
    respect
    various
    catch
    thus
    skill
    attempt
    son
    simple
    medium
    average
    stock
    management
    character
    bed
    hit
    establish
    indeed
    final
    economy
    fit
    guy
    function
    yesterday
    image
    size
    behavior
    addition
    determine
    station
    population
    fail
    environment
    production
    contract
    player
    comment
    enter
    occur
    alone
    significant
    drug
    wall
    series
    direct
    success
    tomorrow
    director
    clearly
    lack
    review
    depend
    race
    recognize
    window
    purpose
    department
    gain
    tree
    college
    argue
    board
    holiday
    mark
    church
    machine
    achieve
    item
    prove
    cent
    season
    floor
    stuff
    wide
    anyone
    method
    analysis
    election
    military
    hotel
    club
    below
    movie
    doctor
    discussion
    sorry
    challenge
    nation
    nearly
    statement
    link
    despite
    introduce
    advantage
    ready
    marry
    strike
    mile
    seek
    ability
    unit
    card
    hospital
    quickly
    interview
    agreement
    release
    tax
    solution
    capital
    popular
    specific
    beautiful
    fear
    aim
    television
    serious
    target
    degree
    pull
    red
    husband
    access
    movement
    treat
    identify
    loss
    shall
    modern
    pressure
    bus
    treatment
    conference
    yourself
    supply
    village
    worth
    natural
    express
    indicate
    attend
    brother
    investment
    score
    organize
    trip
    beyond
    sleep
    fish
    promise
    potential
    energy
    trouble
    relation
    touch
    file
    middle
    bar
    suffer
    strategy
    deep
    except
    clean
    tend
    advance
    fill
    star
    network
    generally
    operation
    match
    avoid
    seat
    throw
    task
    normal
    goal
    associate
    blue
    positive
    option
    box
    huge
    message
    instance
    style
    refer
    cold
    push
    quarter
    assume
    baby
    successful
    sing
    doubt
    competition
    theory
    propose
    reference
    argument
    adult
    fly
    document
    pattern
    application
    hot
    obviously
    unclear
    bill
    search
    separate
    central
    career
    anyway
    speech
    dog
    officer
    throughout
    oil
    dress
    profit
    guess
    fun
    protect
    resource
    science
    disease
    balance
    damage
    basis
    author
    basic
    encourage
    hair
    male
    operate
    reflect
    exercise
    useful
    restaurant
    income
    property
    previous
    dark
    imagine
    okay
    earn
    daughter
    post
    newspaper
    define
    conclusion
    clock
    everybody
    weekend
    perform
    professional
    mine
    debate
    memory
    green
    song
    object
    maintain
    credit
    ring
    discover
    dead
    afternoon
    prefer
    extend
    possibility
    direction
    facility
    variety
    daily
    clothes
    screen
    track
    dance
    completely
    female
    responsibility
    original
    sister
    rock
    dream
    nor
    university
    easily
    agency
    dollar
    garden
    fix
    ahead
    cross
    yeah
    candidate
    weight
    legal
    proposal
    version
    conversation
    somebody
    pound
    magazine
    shape
    sea
    immediately
    welcome
    smile
    communication
    agent
    traditional
    replace
    judge
    herself
    suddenly
    generation
    estimate
    favorite
    difficulty
    purchase
    shoot
    announce
    unless
    independent
    recommend
    survey
    majority
    stick
    request
    rich
    wind
    none
    exchange
    budget
    famous
    blood
    appropriate
    block
    warm
    count
    scene
    writer
    content
    prevent
    safe
    invite
    mix
    element
    effective
    correct
    medical
    admit
    beat
    telephone
    copy
    committee
    aware
    advice
    handle
    glass
    trial
    stress
    radio
    administration
    complex
    text
    context
    ride
    directly
    heavy
    remove
    conduct
    equipment
    otherwise
    title
    extra
    executive
    chair
    expensive
    sample
    sex
    deliver
    video
    connection
    primary
    weather
    collect
    inform
    principle
    straight
    appeal
    highly
    trust
    wonderful
    flat
    absolutely
    flow
    fair
    additional
    responsible
    farm
    collection
    hang
    negative
    band
    relative
    tour
    alternative
    software
    pair
    ship
    attitude
    cheap
    double
    leg
    observe
    sentence
    print
    progress
    truth
    nobody
    examine
    lay
    speed
    politics
    reply
    display
    transfer
    perfect
    slightly
    overall
    intend
    user
    respond
    dinner
    slow
    regular
    physical
    apart
    suit
    federal
    reveal
    percentage
    peace
    status
    crime
    decline
    decade
    launch
    warn
    consumer
    favor
    dry
    partner
    institution
    spot
    horse
    eventually
    heat
    excite
    reader
    importance
    distance
    guide
    grant
    taxi
    feed
    pain
    sector
    mistake
    ensure
    satisfy
    chief
    cool
    expert
    wave
    south
    labor
    surface
    library
    excellent
    edge
    camp
    audience
    lift
    procedure
    email
    global
    struggle
    advertise
    select
    surround
    extent
    river
    annual
    fully
    contrast
    roll
    reality
    photograph
    artist
    conflict
    entire
    presence
    crowd
    corner
    gas
    shift
    net
    category
    secretary
    defense
    quick
    cook
    spread
    nuclear
    scale
    driver
    ball
    cry
    introduction
    requirement
    north
    confirm
    senior
    photo
    refuse
    transport
    emerge
    map
    concept
    island
    reform
    neither
    football
    survive
    flight
    left
    solve
    neighbor
    background
    technique
    traffic
    improvement
    tool
    consequence
    circumstance
    smoke
    reaction
    rain
    busy
    lesson
    brain
    mass
    funny
    contribute
    failure
    schedule
    speaker
    bottom
    adopt
    combine
    mountain
    waste
    hide
    marriage
    ticket
    meal
    colleague
    bag
    repeat
    equal
    expression
    plus
    extremely
    owner
    plane
    commercial
    lady
    duty
    strength
    connect
    cultural
    arrange
    scheme
    payment
    unfortunately
    brief
    bird
    demonstrate
    contribution
    appreciate
    chapter
    secret
    apparently
    novel
    union
    burn
    trend
    initial
    pleasure
    suggestion
    critical
    gather
    mostly
    earth
    pop
    essential
    desire
    promote
    currently
    employ
    path
    topic
    beach
    attract
    engage
    powerful
    flower
    crisis
    settle
    boat
    aid
    fan
    kitchen
    twice
    fresh
    delay
    safety
    engineer
    quiet
    insurance
    nurse
    divide
    length
    investigation
    package
    somewhere
    expand
    commit
    obvious
    jump
    weapon
    relatively
    host
    winter
    district
    broad
    tire
    spring
    spirit
    lunch
    actual
    pool
    battle
    tradition
    cash
    hardly
    award
    coach
    experiment
    consideration
    strange
    code
    possibly
    threat
    accident
    impossible
    revenue
    enable
    afraid
    active
    conclude
    religious
    cancer
    convince
    vary
    environmental
    sun
    healthy
    blow
    volume
    location
    invest
    proceed
    wash
    actor
    glad
    tape
    whereas
    opposite
    stone
    sum
    murder
    monitor
    soldier
    finance
    hate
    egg
    concert
    shock
    comfortable
    usual
    carefully
    pack
    recall
    wine
    camera
    swim
    manufacture
    theater
    cycle
    coffee
    totally
    museum
    visitor
    freedom
    construction
    dear
    objective
    moreover
    onto
    historical
    oppose
    branch
    vehicle
    scientist
    route
    bind
    belong
    taste
    tonight
    fashion
    danger
    bomb
    army
    dangerous
    decrease
    hurt
    council
    editor
    normally
    sight
    generate
    gift
    delivery
    deny
    guest
    anybody
    bedroom
    quote
    climb
    basically
    violence
    minister
    mainly
    mouth
    noise
    manner
    gun
    square
    occasion
    familiar
    ignore
    destroy
    affair
    civil
    locate
    citizen
    temperature
    gold
    domestic
    load
    belief
    troop
    technical
    remind
    arrangement
    skin
    prison
    switch
    acquire
    corporate
    fairly
    wood
    participate
    tough
    tear
    representative
    capacity
    border
    shake
    assessment
    shoe
    ought
    ad
    fee
    hall
    regulation
    escape
    studio
    proper
    relax
    tourist
    component
    afford
    lawyer
    suspect
    cup
    description
    confidence
    industrial
    complain
    perspective
    error
    arrest
    assess
    register
    asset
    signal
    finger
    relevant
    explore
    leadership
    commitment
    wake
    necessarily
    bright
    frame
    slowly
    bond
    hire
    hole
    tie
    internal
    chain
    literature
    victim
    threaten
    division
    secure
    amaze
    device
    birth
    forest
    label
    root
    factory
    expense
    channel
    investigate
    recommendation
    rank
    typical
    west
    friendly
    resident
    provision
    concentrate
    plenty
    export
    entirely
    strongly
    bridge
    consist
    graduate
    brand
    moral
    insist
    combination
    abuse
    ice
    principal
    master
    definitely
    session
    grade
    nevertheless
    predict
    previously
    protection
    largely
    wed
    rent
    shot
    appearance
    reasonable
    guarantee
    till
    theme
    judgment
    odd
    approve
    loan
    definition
    elect
    atmosphere
    farmer
    comparison
    characteristic
    license
    rely
    narrow
    succeed
    identity
    desk
    permit
    seriously
    wild
    empty
    commission
    unique
    association
    instrument
    investor
    practical
    tea
    lovely