Instruction file imported from Compiled-Platforms/kotlin-multiplatform-library-template (.cursor/rules/development-process/skill-context.mdc). Copyright stays with the author.

Skill Context

Always select and read the appropriate skill before starting work. Re-evaluate as the task context changes — if the context shifts, switch skills before continuing.

When activating or switching to a skill, always announce it explicitly to the user, e.g.: "Using skill: write-code" or "Switching to skill: debug".

When a CI task spans multiple concerns, read the primary CI skill first, then read any secondary CI skills required by the task before making changes. For example: a Docker image release requires both ci-releases and ci-security; an embedded firmware release may require ci-embedded, ci-releases, and ci-observability.

Auto-switch to debug

Switch to the debug skill immediately — before continuing any other work — when any of these occur:

• The user pastes error output (stack trace, exception, Gradle failure, CI log, test failure, linter error)
• A shell command you run exits non-zero or prints clear failure output
• The user asks to debug, fix an error, or explain why something failed

Do not propose fixes until you have read the error and identified the failing command, test, or file.

Maintenance

This rule must be kept in sync with the skills available in .cursor/skills/. Update the table below whenever a skill is added, removed, or renamed.

Skill Table