This repository is a collection of prompts that can be combined in different ways in order to use agentic generative AI for software development in Moodle. Its first version is only tested with Claude Code, but with little modifications, it could be made work with other agent software and backends as well. Pull requests welcome!

├── AGENTS.md                        # Main orchestrator file
├── CLAUDE.md                        # Redirect to AGENTS.md
└── .prompts/  
    ├── core/
    │   ├── base-instructions.md     # Core Moodle development principles
    │   ├── security-checklist.md    # Security requirements
    │   └── ci-validation.md         # Automated CI quality checks
    ├── plugins/
    │   ├── block.md                 # Block plugin development guide
    │   ├── enrol.md                 # Enrolment plugin development guide
    │   ├── enrol_patterns.md        # Enrolment plugin patterns and anti-patterns
    │   ├── filter.md                # Filter plugin development guide
    │   ├── filter_patterns.md       # Filter plugin patterns and anti-patterns
    │   ├── mod.md                   # Activity module plugin development guide
    │   ├── mod_patterns.md          # Activity module plugin patterns and anti-patterns
    │   ├── qbank.md                 # Question bank plugin development guide
    │   ├── qbank_patterns.md        # Question bank plugin patterns and anti-patterns
    │   ├── qtype.md                 # Question type plugin development guide
    │   ├── qtype_patterns.md        # Question type plugin patterns and anti-patterns
    │   ├── report.md                # Report plugin development guide
    │   ├── report_patterns.md       # Report plugin patterns and anti-patterns
    │   ├── tiny.md                  # TinyMCE editor plugin development guide
    │   └── tiny_patterns.md         # TinyMCE editor plugin patterns and anti-patterns
    ├── tasks/
    │   ├── create.md                # New plugin creation
    │   ├── bugfix.md                # Bug fixing workflow
    │   ├── test.md                  # Test creation
    │   ├── enhance.md               # Feature enhancement
    │   └── refactor.md              # Code refactoring
    └── patterns/
        ├── database.md              # Database operation patterns
        ├── forms.md                 # Moodle forms patterns
        ├── navigation.md            # Navigation integration
        ├── api-usage.md             # Common API usage patterns
        └── html_writer.md           # HTML generation best practices

The Moodle core repository should be cloned alongside this repository for reference:

../moodle/          # Moodle core repository
./                  # This plugin repository

This way the agent can access Moodle code for reference, if needed.

Detected: block_ repository name Loads:

• core/base-instructions.md
• plugins/block.md
• tasks/create.md
• core/security-checklist.md

Detected: qtype repository name + git branch "fix/calculation-error" Loads:

• core/base-instructions.md
• plugins/qtype.md
• plugins/qtype_patterns.md
• tasks/bugfix.md
• patterns/database.md (if DB operations detected)
• core/security-checklist.md

Detected: enrol_ repository name Loads:

• core/base-instructions.md
• plugins/enrol.md
• plugins/enrol_patterns.md
• tasks/create.md
• core/security-checklist.md

Detected: tiny_ repository name + request mentions "add feature" Loads:

• core/base-instructions.md
• plugins/tiny.md
• plugins/tiny_patterns.md
• tasks/enhance.md
• patterns/forms.md (if form integration detected)
• core/security-checklist.md

Detected: Request mentions "tests" or "phpunit" Loads:

• core/base-instructions.md
• plugins/{detected_type}.md
• plugins/{detected_type}_patterns.md (if available)
• tasks/test.md
• core/security-checklist.md

MoMoPDA provides comprehensive development guides and pattern documentation for the following Moodle plugin types:

• Activity Modules (mod_*) - Custom learning activities and assignments
• Block Plugins (block_*) - Custom dashboard and course blocks
• Question Types (qtype_*) - Custom question types for quizzes and assignments
• Question Bank Plugins (qbank_*) - Question bank management and organization tools

• Enrolment Plugins (enrol_*) - Custom user enrolment methods and workflows

• Filter Plugins (filter_*) - Content processing and transformation filters
• TinyMCE Editor Plugins (tiny_*) - Rich text editor extensions and tools

• Report Plugins (report_*) - Administrative reports and analytics dashboards

• Development Guide - Complete implementation instructions with code examples
• Patterns & Anti-Patterns - Best practices, common pitfalls, and security considerations
• Testing Strategies - Unit testing, integration testing, and quality assurance
• Performance Guidelines - Optimization techniques and database best practices
• Security Checklists - Vulnerability prevention and secure coding practices

All guides are based on analysis of Moodle 5.x core implementations and follow official Moodle development standards.

• Claude Code or compatible agentic AI development environment
• Git
• Moodle development environment (optional but recommended)

1. Clone the MoMoPDA repository

   git clone https://github.com/your-org/momopda.git
   cd momopda

2. Create your plugin repository

   Rename or create a new repository following Moodle plugin naming conventions:

   # E.g., for a new block plugin
   git clone https://github.com/your-org/momopda.git moodle-block_your_plugin_name
   cd moodle-block_your_plugin_name
   

   Plugin Naming Convention Examples:

   • Activity modules: moodle-mod_interactive_lesson
   • Block plugins: moodle-block_nice_new_block
   • Question types: moodle-qtype_custom_quiz
   • Enrolment plugins: moodle-enrol_company_sso
   • Filter plugins: moodle-filter_content_enhancer
   • TinyMCE plugins: moodle-tiny_equation_editor
   • Report plugins: moodle-report_analytics_dashboard
   • Question bank plugins: moodle-qbank_question_organizer

3. Optional: Clone Moodle core for reference

   # In parent directory
   cd ..
   git clone https://github.com/moodle/moodle.git

   Your directory structure should look like:

   .
   ├── moodle/                           # Moodle core (optional reference)
   └── moodle-block_your_plugin_name/    # Your plugin with MoMoPDA
       ├── AGENTS.md
       ├── CLAUDE.md
       └── .prompts/
   

4. Optional but recommended: Install Moodle Plugin CI

   MoMoPDA includes automated quality validation using Moodle Plugin CI. The AI agent will automatically use these tools if available to validate code quality before completing tasks.

   Requirements:

   • PHP 7.4 or later
   • Composer

   Installation (Composer method):

   # In parent directory (alongside your plugin and Moodle core)
   cd ..
   php composer.phar create-project moodlehq/moodle-plugin-ci moodle-plugin-ci ^4

   Alternative: PHAR package

   # Download pre-built package
   wget https://github.com/moodlehq/moodle-plugin-ci/releases/download/4.1.6/moodle-plugin-ci.phar

   Your directory structure with CI tools:

   .
   ├── moodle/                           # Moodle core (optional reference)
   ├── moodle-plugin-ci/                 # CI tools (recommended)
   └── moodle-block_your_plugin_name/    # Your plugin with MoMoPDA
       ├── AGENTS.md
       ├── CLAUDE.md
       └── .prompts/
   

   Configure environment variable:

   The CI tools require the MOODLE_DIR environment variable to point to your Moodle core installation:

   # Add to your ~/.bashrc or ~/.zshrc
   export MOODLE_DIR=$HOME/git/moodle
   
   # Or set it for the current session
   export MOODLE_DIR=/home/$USER/git/moodle
   
   # Reload your shell configuration
   source ~/.bashrc  # or source ~/.zshrc

   Adjust the path to match your actual Moodle installation location.

   What CI tools provide:

   • Automated coding standards validation (codechecker)
   • PHP syntax checking (phplint)
   • PHPUnit test execution
   • Behat acceptance testing
   • Plugin validation
   • And more (see .prompts/core/ci-validation.md)

   For more information, visit the Moodle Plugin CI documentation.

5. Start your coding agent from the root of the repository

6. Begin development

   Start by describing what you want to build. MoMoPDA will automatically detect your plugin type from the repository name and load the appropriate guides:

   "I want to create a new block plugin that displays student progress charts"
   "Help me add a new question type for mathematical expressions"
   "I need to fix a bug in my enrolment plugin's user sync feature"
   

MoMoPDA automatically detects your plugin type and development context:

• Plugin Type Detection: Based on repository name (e.g., block_*, qtype_*, enrol_*)
• Task Detection: Based on git branch names, file changes, and user requests
• Context Loading: Automatically loads relevant guides, patterns, and best practices
• Security & Quality: Always includes security checklists and quality standards

1. Use descriptive repository names following Moodle conventions
2. Be specific in your requests - mention features, requirements, and constraints
3. Reference existing Moodle plugins if you want similar functionality
4. Ask for tests - MoMoPDA includes comprehensive testing guidance
5. Request security reviews when handling user data or permissions

• Plugin type not detected? Ensure your repository name follows the moodle-{plugintype}_{pluginname} convention
• Missing guidance? Check if your plugin type is supported in the list above
• Need custom patterns? The guides include extension points for custom functionality
• Your new plugin has bugs? Fix them and ask your coding agent to improve the patterns files!

I want to create a question bank (qbank) plugin, which adds a bulk edit functionality to the question bank. The idea is to use the questiongeneration purpose of the ../moodle-local_ai_manager plugin, and the logic of the ../moodle-qbank_questiongen plugin, to attain the following functionality: 1. bulk select which questions to modify 2. add a modification prompt 3. generate new versions of the questions according to the modification prompt. 4. add a prefix to the new questions, so they can be distinguished from the old ones. For example: "Add feedback to all answer options of these questions". MVP would be to add support to the multichoice questions, but create similar architecture to the questiongen plugin so that other question types can be added later. The plugin must be dependent on the local_ai_manager plugin, and it can be dependent on the qbank_questiongen plugin as well, if it makes the implementation simpler.

Notes: This worked, and the resulting plugin is here: https://github.com/wilenius/moodle-qbank_bulk_ai_edit.

This repo has a modular prompt system for developing Moodle plugins. I need to develop a local plugin that adds User overrides to all the quizzes on the course area. To understand User overrides, look at the /home/hwileniu/git/moodle/public/mod/quiz. To understand local plugins, look at ../moodle-local_aiquestions. It needs to be added as a view to the course navigation. MVP: add custom quiz time limit for a user.

Notes: This worked very well. It might be that it makes sense to note that the initial contents of the repo (momopda) and the end product (plugin) are different, but they'll be done in the same repo, so that the agent needs one step less to get on the right track. Resulting code here: https://github.com/wilenius/moodle-local_course_overrides