kmp-lessons

Captures structured lessons learned from KMP project work into docs/lessons markdown files.

2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/ronjunevaldoz/kmp-agent-skills --skill kmp-lessons-ronjunevaldoz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kmp-lessons
Source: https://github.com/ronjunevaldoz/kmp-agent-skills/tree/main/skills/kmp-lessons
Command: npx skills add https://github.com/ronjunevaldoz/kmp-agent-skills --skill kmp-lessons-ronjunevaldoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When AI skill guidance is wrong, incomplete, or stale during Kotlin Multiplatform development, that knowledge is usually lost. This Skill captures each finding as a structured lesson file so corrections and better patterns flow back into the skills collection instead of being forgotten. ## Core Features & Use Cases - Structured Lesson Capture: Writes one markdown file per finding to docs/lessons/ with frontmatter fields for skill, date, severity, and type (correction, gap, better-pattern, deprecation, confirmation). - Deterministic Script: The create_lesson.py script generates date-stamped, slug-named files, never overwrites existing lessons, and inserts TODO placeholders for omitted fields. - Proactive Issue Drafting: For high-severity corrections, it drafts a GitHub issue for the upstream skills repo in the same turn, requiring explicit user confirmation before submission. - Use Case: After fixing a bug where a SharedFlow with replay=1 re-triggered navigation effects, run the script to record the correction with evidence so the kmp-mvi skill can be amended later by the harvester. ## Quick Start Ask the agent to write a lesson capturing what went wrong with a skill's guidance, including the correct pattern and evidence, and it will create the lesson file in docs/lessons/.

Frequently Asked Questions about kmp-lessons

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a bug caused by following AI skill guidance?▼

Run the create_lesson.py script with the skill name, type correction, a severity level, and a specific title. It writes one structured markdown file to docs/lessons/ with sections for what was followed, what broke, the correct pattern, and evidence.

What is the lesson file format for KMP skill feedback?▼

Each lesson is a markdown file named YYYY-MM-DD-slug.md in docs/lessons/ with frontmatter for skill, date, severity (high/medium/low), and type (correction, gap, better-pattern, deprecation, confirmation), followed by five body sections including evidence and a proposed skill change.

When should a lesson be written versus filing a GitHub issue?▼

Write a lesson for every finding. For high-severity corrections where skill guidance caused a real bug, also draft a GitHub issue for the upstream skills repo in the same turn, but only submit it after the user explicitly confirms.

Can multiple findings go into one lesson file?▼

No. Each finding gets its own file because the harvester reads docs/lessons/*.md as one lesson per file. Run create_lesson.py once per finding; combined files are flagged by the kmp-audit combined lesson file detector.

What severity level should I assign to a lesson?▼

Use high when the gap caused a production bug or significant rework, medium for wasted time or a non-trivial workaround, and low for minor inconveniences or edge cases.