Skip to content
cccskills
FreePublished on GitHub

android-compose-playground

Build sample/demo screens that make library options explorable. Add controls, previews, presets, sample data, and QA surfaces in the app module.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md681 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Android Compose Playground

Purpose:

  • Build sample/demo screens that make library options explorable.

When to use:

  • Adding controls, previews, presets, sample data, and QA surfaces in :app

Workflow:

  1. Expose configuration as editable state.
  2. Keep controls grouped and deterministic.
  3. Prefer presets plus fine-grained controls.
  4. Ensure the preview surface reflects the exact library API.

Outputs:

  • Sample screen implementation
  • Preview scenarios
  • Manual QA notes

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Shape reusable library APIs for Compose modules. Design public composables, split sample-app code from reusable library code, review naming and extensibility.

The English summary is being prepared. Showing the original description.

binayshaw7777/Leaflekt-Maps16Updated Aug 8, 2026

Keep module structure, naming, and build configuration ready for future publishing. Handle new Gradle modules, library metadata, namespace and artifact readiness.

The English summary is being prepared. Showing the original description.

binayshaw7777/Leaflekt-Maps16Updated Aug 8, 2026

ALWAYS invoke this skill before writing, editing, generating, or refactoring ANY code. Do not write or modify code directly without first loading and following these Clean Code guidelines. Use when writing new functions/classes, refactoring existing code, reviewing code, fixing bugs, or any task that produces code output.

The English summary is being prepared. Showing the original description.

binayshaw7777/Leaflekt-Maps16Updated Aug 8, 2026

Implement Google's Material Design 3 (Material You) UI system. Primary: Jetpack Compose Material3 (MaterialTheme, components, adaptive layout). Also Flutter and limited web (@material/web, maintenance mode). Covers tokens, 30+ components, layout, theming, M3 Expressive (platform matrix), and accessibility. Use when: "material design", "MD3", "material you", "Jetpack Compose", "MaterialTheme", "material component", "md3 button".

The English summary is being prepared. Showing the original description.

binayshaw7777/Leaflekt-Maps16Updated Aug 8, 2026

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

The English summary is being prepared. Showing the original description.

binayshaw7777/Leaflekt-Maps16Updated Aug 8, 2026

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

The English summary is being prepared. Showing the original description.

binayshaw7777/Leaflekt-Maps16Updated Aug 8, 2026

See all skills by binayshaw7777

Report a problem with this skill