Problem
General-purpose coding agents often miss the conventions and constraints that matter in Playdate projects. I wanted a reusable way to teach agents Playdate-specific build workflows, runtime patterns, and architectural norms.
Technical Architecture
Each skill lives in its own directory with a SKILL.md file and optional reference material. The format is lightweight but deliberate: frontmatter controls triggering, while the markdown content provides scoped operational guidance.
Key Decisions
I kept each skill narrow rather than creating one large Playdate guide. That improves trigger quality and makes each skill easier to validate and maintain.
Challenges
The main challenge is balancing specificity with reuse. Skills need to be detailed enough to help an agent make better decisions, but narrow enough that they trigger only when appropriate.
Outcomes
The result is a reusable Playdate knowledge layer that complements live tooling like playdate-mcp and improves the quality of AI-assisted development sessions.