Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Compose Project & Build Owner

Owns project- and build-level work for Compose / Compose Multiplatform apps: bootstrapping, incremental adoption, module creation, convention plugins, version catalog and CI guards.

Dev & CodingAdvanced★ 300⑂ 25AI score 9/10Last updated: Oct 2, 2026

What it does

  • Walks through bootstrapping a new CMP or Android-only project from the kit's templates/project/ skeleton (composition root, :core:*, first feature, guards).
  • Drives incremental adoption in an existing repo: run the audit script, produce a gap report, classify the project, start guards in WARN mode, only then make them blocking.
  • Enforces 8 non-negotiables plus 2 defaults whenever settings.gradle.kts, build.gradle.kts, build-logic/, or libs.versions.toml is touched — no target/SDK blocks in library modules, versions declared once in the catalog, api() only with a comment naming the leaked type, no module depending on the composition root.
  • Gives a checklist for adding/extracting modules: apply the owning convention plugin, register in .composekit.conf, register the Koin module, delete the temporary root slice.
  • Wires CI and agent hooks to the run-checks.sh registry instead of individual scripts.
  • Applies version gates (AGP 9, Kotlin 2.3.20, SKIE support) and stops-and-reports instead of silently migrating.

Who it's for

  • Android / KMP engineers maintaining multi-module Kotlin + Compose Multiplatform codebases.
  • Teams whose SDK settings and dependency versions have drifted across dozens of modules.
  • Tech leads who want guardrails so an AI agent cannot quietly rewrite build logic.

Examples

  1. "Start a new Compose Multiplatform app" → pick the target shape, lay out :composeApp + :androidApp + :core:mvi + :feature:notes, build-logic, version catalog, then install guards.
  2. "Add a :feature:tags module" → build file contains only the plugin alias, namespace and dependencies; register it in .composekit.conf, run the check registry, wire its Koin module.
  3. "Let's just park the tag-filter logic in :app for now" → the skill says no per rule 6 and delivers the correct feature-module implementation in the same answer.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/Meet-Miyani/compose-skill/HEAD/skills/compose-project/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/compose-project folder from the GitHub repo Meet-Miyani/compose-skill into my ~/.claude/skills/compose-project/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/Meet-Miyani/compose-skill.git && mkdir -p ~/.claude/skills && cp -r compose-skill/skills/* ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and go to the folder where you keep source code.
  2. Clone the repo: git clone https://github.com/Meet-Miyani/compose-skill.git
  3. Create the skills folder if needed: mkdir -p ~/.claude/skills
  4. This skill cross-references sibling skills (compose, compose-architecture, compose-feature, ...), so copy them all: cp -r compose-skill/skills/* ~/.claude/skills/
  5. Verify: ls ~/.claude/skills/compose-project should show SKILL.md plus references/, templates/ and scripts/.
  6. Restart Claude Code and try a prompt like "bootstrap a Compose Multiplatform project" or "add a feature module".
  7. For real work, launch Claude Code from the repo root that contains gradle/libs.versions.toml so the skill can read your versions before writing build code.
View source on GitHub ↗License: MIT