All authors
Claude Skills by GuillemRoca
github.com/GuillemRoca30 skills1 installs9 views
- Android AccessibilityUse when building or reviewing Android UI for accessibility. Covers TalkBack, content descriptions, touch targets, Compose semantics, focus order, and Accessibility Scanner testing.Votes: 0GitHub stars: 2
- Android ArchitectureUse when designing module structure, choosing architecture patterns (MVVM/MVI), setting up dependency injection, or defining layer boundaries in an Android project.Votes: 0GitHub stars: 2
- Android Background WorkUse when work must run outside the visible UI — sync, uploads, periodic jobs, long-running tasks. Covers WorkManager constraints and expedited work, foreground service types, exact alarms policy, Doze/App Standby, and testing background work deterministically.Votes: 0GitHub stars: 2
- Android Data PersistenceUse when implementing local data storage with Room, DataStore, or offline-first patterns. Covers entities, DAOs, migrations, Paging3, and the repository pattern for data management.Votes: 0GitHub stars: 2
- Android Device TestingUse when writing or debugging instrumented tests (Espresso, UI Automator, Compose test rules), using ADB, managing emulators, or inspecting UI with Layout Inspector.Votes: 0GitHub stars: 2
- Android E2e VerificationUse when a feature slice needs proof it works end-to-end on a device, or when closing the implement → run → assert loop for any UI-facing change. Maestro YAML flows turn acceptance criteria into executable checks that run against release builds locally, in CI, and via MCP from the agent.Votes: 0GitHub stars: 2
- Android Ui EngineeringUse when building UI with Jetpack Compose. Covers component design, state hoisting, recomposition optimization, Material 3 theming, Navigation 3, adaptive layouts for large screens, previews, screenshot verification, and XML interop.Votes: 0GitHub stars: 2
- Api And Interface DesignUse when designing interfaces between layers (Repository, UseCase, API client) or defining data contracts. Covers Retrofit interfaces, Room DAOs, Kotlin sealed classes, backward compatibility, and idempotency keys for safely retried writes.Votes: 0GitHub stars: 2
- Ci Cd And AutomationUse when setting up or improving CI/CD pipelines for Android. Covers sequential quality gates, Gradle caching, emulator testing in CI, feature flags, and automated deployment to Play Store.Votes: 0GitHub stars: 2
- Code Review And QualityUse when reviewing Android code (own or others'). Five-axis review framework: Correctness, Readability, Architecture, Security, Performance. Categorized findings with Kotlin/Compose-specific checks.Votes: 0GitHub stars: 2
- Code SimplificationUse when code is harder to understand than it needs to be. Guides incremental simplification that preserves behavior exactly, following project conventions and Kotlin idioms.Votes: 0GitHub stars: 2
- Constraint Driven DevelopmentUse when an Android project has no written quality bar, when the user says "set up constraints" or "define our standards", when coverage, performance, or accessibility should become enforced gates instead of per-PR arguments, when an agent keeps silencing checks or skipping tests to get to green, or when a threshold is needed and nobody knows what number to pick. Records the bar in CONSTRAINTS.md with a number and a Gradle command behind every rule, installs the de facto Android tool per dime...Votes: 0GitHub stars: 2
- Context EngineeringUse when setting up a project for AI-assisted development or when agent output quality is poor. Guides writing rules files, structuring context, and managing the information agents need to produce accurate work.Votes: 0GitHub stars: 2
- Debugging And Error RecoveryUse when encountering unexpected behavior, crashes, or test failures in Android. Six-step triage from reproduction to regression guard, using Logcat, Android Studio debugger, and profiling tools.Votes: 0GitHub stars: 2
- Deprecation And MigrationUse when deprecating APIs, bumping minSdk, migrating libraries (AndroidX, Compose, Kotlin versions), changing an API contract or database schema, or removing legacy code. Covers Kotlin @Deprecated annotation, strangler pattern, expand/contract for API and schema changes, and incremental migration.Votes: 0GitHub stars: 2
- Documentation And AdrsUse when making architectural trade-offs, changing public APIs, shipping user-facing features, or onboarding developers. Guides writing ADRs, inline documentation, and API docs.Votes: 0GitHub stars: 2
- Doubt Driven DevelopmentUse when a decision is high-stakes and hard to reverse — architecture choices, data migrations, dependency adoption, public API contracts. Adversarial self-review that attacks the chosen approach before the code does, instead of defending the first idea that worked.Votes: 0GitHub stars: 2
- Git Workflow And VersioningUse when managing branches, commits, versioning, and release workflows for Android projects, or when cutting a release, choosing a version bump, tagging, or writing a changelog. Covers trunk-based development, atomic commits, versionCode/versionName derived from tags, semver for library modules, changelogs and Play release notes, and signing configurations.Votes: 0GitHub stars: 2
- Idea RefineUse when a feature idea, project concept, or product direction is vague and needs sharpening before spec or implementation. Guides divergent exploration, convergent evaluation, and a final one-pager.Votes: 0GitHub stars: 2
- Incremental ImplementationUse when building features incrementally. Each increment leaves the system in a working, testable state. Covers vertical slicing, feature flags, and rollback-friendly development for Android.Votes: 0GitHub stars: 2
- Interview MeUse when requirements are vague, contradictory, or thinner than the work deserves — before writing a spec or starting implementation. Iterative questioning that raises requirement confidence to ~95% instead of guessing and building the wrong thing.Votes: 0GitHub stars: 2
- Observability And InstrumentationUse when adding logging, crash reporting, or performance monitoring, or before shipping a release that must be watched in production. Covers Crashlytics, Play Vitals thresholds, structured logging with Timber, reportFullyDrawn, release-health monitoring, and CI performance gates.Votes: 0GitHub stars: 2
- Performance OptimizationUse when measuring or improving Android app performance. Covers Android Vitals (startup, jank, ANR), Macrobenchmark, APK size, recomposition tracing, and profiling with Android Studio tools.Votes: 0GitHub stars: 2
- Planning And Task BreakdownUse when starting implementation of a feature or change that involves multiple files or steps. Produces a structured task list with vertical slices, acceptance criteria, and verification steps.Votes: 0GitHub stars: 2
- Security And HardeningUse when handling sensitive data, authentication, network communication, or before shipping to the Play Store. Three-tier framework (Always Do, Ask First, Never Do) with Android-specific security patterns, plus data privacy and compliance (GDPR/CCPA, Play Data safety, account deletion).Votes: 0GitHub stars: 2
- Shipping And LaunchUse when preparing to release an Android app to production. Pre-launch checklist covering code quality, security, performance, accessibility, Play Store requirements, staged rollout, and rollback planning.Votes: 0GitHub stars: 2
- Source Driven DevelopmentUse when implementing framework-specific code (Jetpack Compose, Room, Hilt, Navigation, etc.). Every API usage must be backed by official documentation, not memory or Stack Overflow.Votes: 0GitHub stars: 2
- Spec Driven DevelopmentUse when starting new Android projects, features, or changes with unclear requirements. Guides writing a structured spec (SPEC.md) that becomes the shared source of truth before any code is written. Also use when one request spans several independently testable capabilities and needs a capability map of modules before specifying.Votes: 0GitHub stars: 2
- Test Driven DevelopmentUse when implementing new features or fixing bugs. Write tests before implementation following Red-Green-Refactor. Covers JUnit5, MockK, Compose test rules, and the Prove-It pattern for bugs.Votes: 0GitHub stars: 2
- Using Agent SkillsUse when starting a session or selecting a skill for a task. Meta-skill defining five core agent behaviors: assumption surfacing, confusion management, constructive pushback, simplicity enforcement, and scope discipline. Includes the skill discovery flowchart for all 30 Android skills.Votes: 0GitHub stars: 2