How jushbjj/mr.-ranedeer-ai-tutor works
1. This repository is not an application with executable code; it is a prompt-product package for ChatGPT/GPT-4. The “architecture” is primarily a set of text artifacts that define a tutoring persona, its configuration surface, and the instructions users paste into an LLM chat session.
2. The core runtime boundary is external: OpenAI’s ChatGPT interface. The repo does not host a backend, model, or API service. Instead, the main prompt files are consumed manually by the user inside ChatGPT or through a custom GPT link referenced in the README.
3. The central asset is Mr_Ranedeer.txt. This is the primary tutor system prompt: it defines the AI tutor’s identity, behavior, lesson structure, command handling, and pedagogy. In architecture terms, this is the “engine” of the product.
4. GPT_Prompt.txt appears to be a more generic or alternate prompt entrypoint, likely used to feed the same tutoring behavior into different contexts. It functions as a sibling prompt artifact rather than a separate subsystem.
5. My_Information.txt is the user-specific configuration boundary. This is where learner preferences, background, or personalization inputs are stored so the tutor can adapt depth, tone, style, and language. It is effectively the data input layer for the prompt system.
6. Extensions/Wizard.txt represents a configuration assistant or prompt extension. Based on the README’s “Wizard” reference, this is the subsystem that helps users choose settings and personalize the tutor before learning begins.
7. The Guides/ folder is the documentation and onboarding layer. How to use Mr. Ranedeer.md explains the usage flow, while Config Guide.md documents the configuration schema and available options. These files support the main prompt by defining how users should prepare and interact with it.
8. Prompt Analysis.md is likely an internal design note explaining how the prompt behaves or how its structure is intended to work. This is a meta-documentation boundary, useful for understanding prompt composition but not part of the user-facing tutoring flow.
9. The repository’s interaction model is command-driven. The README documents slash commands like /test, /config, /plan, /start, /continue, and /language. These commands are interpreted by the prompt instructions rather than by code, so the control plane is embedded in text and executed by the model’s response logic.
10. Content flow is: user selects or edits configuration, optionally uses the wizard, then pastes the main prompt into ChatGPT, after which the model generates lessons, tests, and plans according to the configured behavior. The learning session is stateful only within the chat context, not in repository code.
11. .github/ contains issue and pull request templates. These support community feedback and contribution workflows, but they do not affect the tutoring architecture itself.
12. The README also serves as the public product front door. It establishes that the project is discontinued, points users to the main prompt and guides, and documents compatibility expectations such as GPT-4 with Code Interpreter. That makes the repository a distributed prompt system with documentation, not a deployed software stack.
Main entry points: README.md README · Mr_Ranedeer.txt Mr. Ranedeer · GPT_Prompt.txt GPT Prompt · Wizard.txt Wizard
Components 12
Front Door
Public entrypoint and product overview.
- README · Public front door, status note, and links into the prompt system.
README.md
Prompt Core
Primary tutoring prompts and control logic.
- Mr. Ranedeer · Primary system prompt that defines the tutor persona, lesson flow, commands, and behavior.
Mr_Ranedeer.txt - GPT Prompt · Secondary prompt entrypoint that carries similar tutoring behavior into other contexts.
GPT_Prompt.txt
Personalization
User-specific inputs and configuration assistant.
- My Information · User-specific configuration and learner preferences used to personalize tutoring.
My_Information.txt - Wizard · Extension that helps users choose settings and personalize the tutor before learning begins.
Extensions/Wizard.txt
Docs & Meta
Usage guides and design notes.
- Config Guide · Documents the configuration options and how to populate the user profile.
Guides/Config Guide.md - How to Use · Explains the manual workflow for loading and using the tutor prompt.
Guides/How to use Mr. Ranedeer.md - Prompt Analysis · Meta-analysis of the prompt structure and intended behavior.
Prompt Analysis.md - CHANGES · Project change log and historical updates.
CHANGES.md
Community
Contribution workflow templates.
- Bug Report · Template for reporting problems with the prompt package.
.github/ISSUE_TEMPLATE/bug_report.md - Feature Request · Template for suggesting enhancements or new prompt capabilities.
.github/ISSUE_TEMPLATE/feature_request.md - PR Template · Template for pull requests and contribution workflow.
.github/PULL_REQUEST_TEMPLATE.md
Connections 19
- README → Mr. Ranedeer: points to · The README directs users to the core tutor prompt.
- README → How to Use: introduces · The README frames the expected manual usage flow.
- README → Config Guide: references · The README surfaces configuration guidance for users.
- README → Wizard: mentions · The README points to the Wizard as a setup aid.
- README → GPT Prompt: offers · A secondary prompt entrypoint is surfaced alongside the main prompt.
- Mr. Ranedeer → My Information: consumes · The tutor prompt reads personalization inputs from the user profile.
- Mr. Ranedeer → Wizard: works with · The Wizard helps prepare settings used by the main prompt.
- Mr. Ranedeer → How to Use: explained by · Usage instructions describe how to run the prompt in chat.
- Mr. Ranedeer → Config Guide: configured by · Configuration schema shapes the behavior of the prompt.
- GPT Prompt → Mr. Ranedeer: mirrors · The alternate prompt reuses the core tutoring behavior.
- Wizard → My Information: writes · The Wizard helps populate the personalization layer.
- Config Guide → My Information: defines · The guide documents the fields stored in the user profile.
- How to Use → Mr. Ranedeer: operates · The usage guide describes the main prompt workflow.
- Prompt Analysis → Mr. Ranedeer: analyzes · Design notes explain the structure of the primary prompt.
- Prompt Analysis → GPT Prompt: analyzes · Design notes also cover the alternate prompt entrypoint.
- CHANGES → README: supports · Release history complements the public product overview.
- Bug Report → README: supports · Issue workflow supports the documented project surface.
- Feature Request → README: supports · Feature requests feed improvements to the prompt package.
- PR Template → README: supports · Pull request template supports repository contributions.