claude-android-skill

Enforce Clean Architecture and Offline-First patterns in Android codebases.

1|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/ChooJeongHo/MovieFinder --skill claude-android-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-android-skill
Source: https://github.com/ChooJeongHo/MovieFinder/tree/main/.claude/skills/claude-android-skill
Command: npx skills add https://github.com/ChooJeongHo/MovieFinder --skill claude-android-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces Clean Architecture and Offline-First patterns in the MovieFinder Android codebase by analyzing or applying the ARGUMENTS.

Core Features & Use Cases

  • Enforces layer boundaries (Presentation → Domain; Data → Domain) and forbids direct Presentation-to-Data access.
  • Validates repository interfaces and data mappings to ensure domain models are preserved and business logic remains in UseCase.
  • Supports automated code review and guidance for refactoring to align with the project's architectural rules.

Quick Start

Provide a file path or feature description to analyze and enforce the project's architectural rules against your Android codebase.

Frequently Asked Questions about claude-android-skill

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

FAQPage Schema
How do I enforce Clean Architecture layer boundaries in my Android codebase?

Enforce Clean Architecture layer boundaries by validating Presentation-to-Domain and Data-to-Domain access, forbidding direct Presentation-to-Data access to ensure business logic remains isolated in UseCase layers.

Why does my Android Presentation layer directly accessing the Data layer break architecture rules?

Direct Presentation-to-Data access breaks architecture rules because it bypasses domain models and repository interfaces, degrading separability and preventing business logic from remaining isolated in UseCase layers.

Can I use synchronous repository calls in an offline-first Android app?

No, offline-first Android apps must use Flow or suspend-based use cases and repository interfaces to support RemoteMediator-based caching and asynchronous data mapping.

How do I validate repository interfaces and data mappings to preserve domain models?

Validate repository interfaces and data mappings by analyzing file paths or feature descriptions to ensure domain models are preserved and business logic remains strictly within UseCase implementations.

Does this architecture enforcement restrict Android framework usage in domain code?

Yes, it restricts Android framework usage in domain code to ensure the Domain layer remains pure, validating that dependencies only flow from Presentation or Data layers toward Domain.

How do I refactor an Android feature to align with offline-first and RemoteMediator caching rules?

Refactor Android features by analyzing the provided feature description against project rules, enforcing RemoteMediator-based caching and Clean Architecture patterns to align the codebase automatically.