Skip to content
Ali Sadeghi edited this page May 18, 2026 · 7 revisions

Skills

Skills are reusable, multi-phase workflows shipped with the project under .claude/skills/. They auto-activate on intent (e.g. "create a feature") or can be invoked explicitly with a slash command.

New to skills? See Getting-Started for an introduction.

Invocation

Method Example
Auto-activate "create a login feature" → creating-kmp-feature activates
Manual invoke /creating-kmp-feature
Argument-aware /ui-designer myfeature, /verify-ui myfeature

Available Skills

Implementation

Skill Purpose Detail
creating-kmp-feature Build a new feature end-to-end (PRD → tasks → data/UI/integration → spec) Creating-KMP-Feature
modifying-kmp-feature Modify an existing feature using a spec-first review gate Modifying-KMP-Feature

Both skills auto-detect a Stitch design blueprint for the target feature and enter design-aware mode when one is present and unconsumed.

Design

Skill Purpose Detail
ui-designer Design screens in Google Stitch, produce a Compose Implementation Blueprint + token inventories UI-Designer
verify-ui Verify a feature's UI implementation against the Stitch design (HTML ↔ Code, plus X-components compliance) Verify-UI
using-design-system Auto-activates to enforce X-components instead of Material3 when editing feature UI code Using-Design-System

Platform

Skill Purpose Detail
bridging-swift-kotlin Bridge Swift to KMP via Interface Injection (iOS SDKs, biometrics, payments, camera, etc.) Bridging-Swift-Kotlin

How They Fit Together

ui-designer  ─▶  creating-kmp-feature   ─▶  verify-ui
                    or                          
                 modifying-kmp-feature   ─▶  verify-ui

Each skill is independently invocable — no skill calls another skill. You control the pipeline. The design pipeline is glued together via a single stitch-project.json and a blueprintConsumed flag per feature. See Design-Pipeline for the full flow.

Quick Links

Clone this wiki locally