## 1. Context Awareness

- Always prioritize the `.context` folder for understanding project details.
- At the start of every session, load and analyze the latest files from the `.context` directory:
  - Review `current_state.md` for the most recent project status, including completed tasks, ongoing efforts, and known challenges.
  - Review `roadmap.md` to understand future milestones, overall goals, and planned steps for the project.
- If the `.context` folder does not exist or is empty, create it and use the developer's initial prompt to generate `current_state.md` and `roadmap.md`. Ensure these files include:
  - A summary of the project’s purpose and scope.
  - A clear outline of the current state, such as what has been done and what remains.
  - An overview of goals and milestones to serve as a roadmap for the AI.
---
## 2. File Management
- Proactively update `.context` files when tasks are completed, milestones are achieved, or decisions are made.
- Use clear and descriptive language when adding updates to ensure the AI comprehends the project's progress and changes.
---
## 3. Task Workflow
- Break tasks into smaller, actionable steps with clear objectives and expectations. This improves AI processing and reduces errors.
- Explicitly tie each task to its related milestone or project goal to maintain alignment with the roadmap.
---
## 4. Roadmap and Current State
- If the developer says "pause here," update `current_state.md` to include the most recent progress, any challenges encountered, and issues currently being addressed. Ensure this update provides enough detail for resuming the task seamlessly later.
- When the developer provides positive feedback, such as "awesome" or "great work," interpret it as an instruction to update `current_state.md` with the latest progress or completion of a task. Ensure this update:
  - Reflects the developer's intent accurately.
  - Aligns with the overall project state and roadmap.
- Keep `current_state.md` concise but detailed, highlighting significant progress, challenges, and outcomes.
- Update `roadmap.md` when substantial changes in goals, priorities, or timelines occur to maintain a clear direction.
---
## 5. Consistency and Communication
- Use precise and unambiguous language when updating `.context` files to prevent misinterpretation.
- If clarification or additional context is requested by the developer, refer explicitly to relevant `.context` files to maintain coherence.
- Recommend practices for maintaining `.context` files if gaps or inconsistencies are identified, such as periodic reviews or standardizing update protocols.
---
## 6. Security Best Practices
- Whenever prompted to make changes to databases, always ask the user if they'd like to create a backup first. This ensures the safety and recoverability of data in case of errors or unintended changes.
- When working with WordPress databases, never include plain text passwords using `-p xyz`. Always utilize the WordPress CLI for such tasks to ensure security and best practices.
- When working with Python, if integrating a new library or repository, always ask for explicit permission first. Provide detailed information, including the repository URL, its purpose, and how it will benefit the project, to allow for informed decision-making.
---
## 7. Tool-Specific Guidelines
- Provide clear instructions for using language-specific tools, frameworks, or libraries as required by the project.
---
## 8. Error Logging and Troubleshooting
- Maintain an `error_log.md` file within the `.context` folder to document recurring issues, resolutions, and patterns observed during development.
- Suggest debugging strategies or tools when errors are detected, and update the log with insights to streamline future troubleshooting.
---
## 9. Version Control Integration
- Ensure `.context` file updates are committed to version control with descriptive commit messages to maintain a clear history of changes.
- Use branching strategies for collaborative workflows, and recommend merging updates into the main branch only after thorough review.
---
## 10. Developer Feedback Loop
- Explicitly check for user satisfaction or unresolved issues after completing tasks. Ask questions such as "Is this what you expected?" or "Do you need adjustments?" to ensure alignment.
---
## 11. Scenarios for Automatic Reminders
- Prompt the developer for crucial actions at appropriate times, such as:
  - Backing up before critical updates.
  - Reviewing large code changes before deployment.
  - Refreshing the `.context` folder at the start of a new phase.
---
## 12. Integration and Testing
- Recommend verifying compatibility in a test environment before integrating new libraries or tools into production.
- Suggest unit tests for Python integrations and staging environments for WordPress changes to ensure reliability.
---
## 13. AI Behavior with Limited Context
- If `.context` files are incomplete or missing, prompt the developer for immediate input to proceed effectively.
- Provide clear fallback suggestions to generate or recover the missing context, ensuring progress isn't hindered.
---
## 14. AI Knowledge Updates
- When global or project-specific rules are updated, confirm the changes with the developer and adjust AI outputs accordingly.