MQTT Framebuffer Panel Development

Development workflow for the Raspberry Pi 2 MQTT Framebuffer panel project, featuring automated testing and comprehensive design documentation integration.

Purpose

This skill configures Aider to work with an embedded IoT project that requires adherence to coding conventions, design specifications, and automated testing workflows. It ensures the AI assistant maintains awareness of project architecture and runs tests automatically after changes.

Instructions

1. **Always load coding conventions first**

- Read `CONVENTIONS.md` at the start of every session

- Apply these conventions to all code suggestions and modifications

- Reference conventions when explaining design decisions

2. **Maintain awareness of project documentation**

- Keep `AI.md` (AI-specific guidelines), `SPECIFICATION.md` (technical requirements), and `PLAN.md` (project roadmap) in context

- Cross-reference these files when proposing changes

- Ensure new code aligns with documented specifications and plans

3. **Run automated tests after every change**

- Execute `./run_test_cycle.sh` after modifying code

- Do not proceed if tests fail - investigate and fix issues first

- Report test results clearly, including any failures or warnings

4. **Follow embedded development best practices**

- Consider resource constraints of Raspberry Pi 2 hardware

- Optimize for framebuffer rendering performance

- Handle MQTT communication reliably with proper error handling

5. **When making changes**

- Check if the change affects documented specifications

- Update relevant documentation if design decisions change

- Ensure changes align with the project plan milestones

Workflow

1. Start session by reviewing coding conventions

2. Load project context from AI.md, SPECIFICATION.md, and PLAN.md

3. Make code modifications following conventions

4. Automatically trigger test cycle

5. Verify test results before considering the task complete

6. Update documentation if architectural changes were made

Constraints

Usage Example

When asked to add a new MQTT message handler:

1. Review CONVENTIONS.md for code style and patterns

2. Check SPECIFICATION.md for message format requirements

3. Verify PLAN.md to ensure feature is in scope

4. Implement the handler following conventions

5. Run `./run_test_cycle.sh` automatically

6. Report test results and confirm implementation matches specs