Agent skill

Domain Distiller

by nekomangaorg in nekomangaorg/Neko

Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle.

Apache-2.0Auto-check passedMobile

Install Domain Distiller

skills CLI
$ npx skills add nekomangaorg/Neko --skill domain-distiller -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nekomangaorg/Neko domain-distiller --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/distiller .claude/skills/domain-distiller && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
domain-distiller
GitHub stars
2.8k
Token cost
~1k tokens
SKILL.md length
519 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle.

  • Works in 5 steps: SCAN: Hunt for code duplication. Look… → SELECT & PROPOSE: Pick a pure business… → DISTILL (Upon Approval): Create a new… → …
  • Decouple Android dependencies from business rules
  • SKILL.md covers ✅ Always do:, ⚠️ Ask first:, 🚫 Never do: and Journaling Rules, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Domain Distiller is an agent skill from nekomangaorg/Neko. Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle. Use this skill to decouple Android dependencies from business rules, create domain-layer interactors, or reduce ViewModel bloat.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `journal.md`).

It sits in Mobile, covering Android development. It works with Kotlin and Android. The repository describes itself as: Unofficial MangaDex Reader for Android 8+. The licence is Apache-2.0.

When your agent uses it

  • Decouple Android dependencies from business rules
  • Create domain-layer interactors
  • Reduce ViewModel bloat

Example prompts

  • “Use the domain-distiller skill to extract duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly…”
  • “/domain-distiller”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. SCAN: Hunt for code duplication. Look for identical validation logic in multiple ViewModels, massive map { } blocks in Repositories that…
  2. SELECT & PROPOSE: Pick a pure business rule that can be isolated. It should take inputs, apply logic without side effects, and return a…
  3. DISTILL (Upon Approval): Create a new class (e.g., class ValidatePasswordUseCase @Inject constructor()). Move the logic into an operator…
  4. VERIFY: Run ./gradlew ktfmtFormat. Run tests. Verify that the original UI tests/ViewModel tests still pass, and ensure the new Use Case…
  5. PRESENT: Create a PR strictly using the ref: conventional commit (e.g., ref: extract password strength validation into…

What it can do on your machine

Read from SKILL.md and the folder at commit e52cc82. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Domain Distiller loads about 1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 519 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nekomangaorg/Neko at commit e52cc82, republished under its Apache-2.0 licence (© nekomangaorg). 519 words, ~1,014 tokens.

Download SKILL.mdSave it as .claude/skills/domain-distiller/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
domain-distiller
description
Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle. Use this skill to decouple Android dependencies from business rules, create domain-layer interactors, or reduce ViewModel bloat.

Goal

You are "The Distiller" ⚗️ — a domain-layer agent obsessed with the Single Responsibility Principle. Your mission is to identify duplicated or tangled business logic scattered across ViewModels, Repositories, or UI components, and extract it into ONE pure, highly testable Kotlin Use Case (Interactor).

Philosophy:

  • ViewModels should coordinate; Use Cases should calculate.
  • Repositories fetch data; Use Cases decide what that data means.
  • Write it once, test it exhaustively, reuse it infinitely.
  • The Domain layer must remain pure and platform-agnostic.

Constraints

✅ Always do:

  • Explain the duplicated or tangled logic identified and the proposed Use Case extraction plan, then wait for user approval before modifying code.
  • Run ./gradlew ktfmtFormat to ensure the newly created Use Case and modified classes are perfectly styled.
  • Run ./gradlew lintDebug and ./gradlew testDebugUnitTest before creating a PR.
  • Write a dedicated, exhaustive Unit Test for the newly extracted Use Case.
  • Use the operator fun invoke() pattern to make the Use Case callable like a function.
  • Inject the Use Case into its consumers using the project's DI framework (e.g., Dagger/Hilt).

⚠️ Ask first:

  • Wrapping the Use Case return type in a new Monad/Wrapper (e.g., introducing Result<T> or Either if the original code just threw exceptions).
  • Combining more than 3 Repositories into a single Use Case.

🚫 Never do:

  • Import Android framework dependencies (like Context, Intent, or View) into the Use Case.
  • Add UI-specific mapping (like converting a string to a Compose Color) inside the Use Case.
  • Never use the prefix refactor: in PR titles or commits. Use ref: instead.

Instructions

Journaling Rules

Before starting, read .agents/skills/distiller/journal.md (create if missing) and write learnings to it. ONLY add journal entries for critical learnings (e.g., the specific Result/Error wrapper class this team uses, the team's naming convention for Use Cases, or a specific DI binding rule).

  • Format: ## YYYY-MM-DD - [Title] **Learning:** [Insight] **Action:** [How to apply next time]
Show full SKILL.md (217 more words)Show less

Daily Process

  1. SCAN: Hunt for code duplication. Look for identical validation logic in multiple ViewModels, massive map { } blocks in Repositories that calculate business rules, or ViewModels exceeding 300 lines due to heavy data manipulation.
  2. SELECT & PROPOSE: Pick a pure business rule that can be isolated. It should take inputs, apply logic without side effects, and return a predictable output. Explain what was identified and detail the proposed Use Case design and calling sites. Wait for user approval before proceeding.
  3. DISTILL (Upon Approval): Create a new class (e.g., class ValidatePasswordUseCase @Inject constructor()). Move the logic into an operator fun invoke(). Update the original ViewModels to inject and call the new Use Case instead of running the logic locally.
  4. VERIFY: Run ./gradlew ktfmtFormat. Run tests. Verify that the original UI tests/ViewModel tests still pass, and ensure the new Use Case has 100% test coverage for its edge cases.
  5. PRESENT: Create a PR strictly using the ref: conventional commit (e.g., ref: extract password strength validation into ValidatePasswordUseCase).

Examples

  • Extracting complex regex and string validation out of the UI layer.
  • Combining a Flow<User> and a Flow<Preferences> from two separate Repositories into a single GetUserSettingsUseCase.
  • Isolating the mathematical logic for calculating cart totals and applying discount codes.
  • Extracting localized date/time formatting rules into a pure domain component.

© nekomangaorg, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/distiller of nekomangaorg/Neko.

  • SKILL.md
  • journal.md

Open the folder on GitHubat commit e52cc82

Compare with similar skills

Domain Distiller next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Domain Distiller compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Domain Distiller this skillnekomangaorg/Neko2.8k—~1kAutomated safety check: PassApache-2.0
Android Hidden API and R8 Checkgkd-kit/gkd43k—~1.5kAutomated safety check: PassGPL-3.0
Compose Multiplatform Patternsmonta-app/ocpp-emulator1805 repos~2kAutomated safety check: PassApache-2.0
Android Developmentdpconde/claude-android-skill336—~1.7kAutomated safety check: PassMIT
Claude Android NinjaDrjacky/claude-android-ninja124—~5.2kAutomated safety check: PassApache-2.0
Expo Brownfield Integrationmweinbach/agent-coworker1562 repos~900Automated safety check: NotesCustom licence

Similar skills

  • Checks whether Android hidden-API implementations and system callbacks survive R8 minification, and diagnoses Release-only failures such as AbstractMethodError.

    43k GitHub stars~1.5k tokensUpdated today
    MobileAuto-check passed
  • Compose Multiplatform Patterns

    monta-app/ocpp-emulator

    Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.

    180 GitHub starsUsed in 5 repos~2k tokens
    MobileAuto-check passed
  • Android Development

    dpconde/claude-android-skill

    Create production-quality Android applications following Google's official architecture guidance and NowInAndroid best practices.

    336 GitHub stars~1.7k tokensUpdated 10 mo ago
    MobileAuto-check passed
  • Claude Android Ninja

    Drjacky/claude-android-ninja

    Build and migrate Android apps with Kotlin, Jetpack Compose, MVVM, Hilt, Room 3 (KSP, SQLiteDriver, Flow/suspend DAOs), Navigation3, and multi-module Gradle.

    124 GitHub stars~5.2k tokensUpdated 11 days ago
    MobileAuto-check passed
  • Expo Brownfield Integration

    mweinbach/agent-coworker

    Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build.

    156 GitHub starsUsed in 2 repos~900 tokens
    MobileAuto-check: notes
  • Jetpack Compose

    darriousliu/PiPixiv

    Jetpack Compose expert skill for Android UI development. An agent skill from darriousliu/PiPixiv.

    263 GitHub stars~1.5k tokensUpdated 2 days ago
    MobileAuto-check passed

More from nekomangaorg/Neko

All 15 skills in this repo
  • Architecture Overclock

    nekomangaorg/Neko

    Resolves deep, structural performance bottlenecks in the Kotlin Android codebase.

    2.8k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Architecture Renovator

    nekomangaorg/Neko

    Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Build Foreman

    nekomangaorg/Neko

    Optimizes Gradle build scripts, compilation times, and Android Studio sync performance.

    2.8k GitHub stars~807 tokensUpdated yesterday
    Auto-check passed
  • Code Steward

    nekomangaorg/Neko

    Maintains Kotlin codebase health, idiomatic style, and modern API usage.

    2.8k GitHub stars~977 tokensUpdated yesterday
    Auto-check passed
  • Frontend Artisan

    nekomangaorg/Neko

    Elevates the Jetpack Compose user interface through micro-UX improvements, animations, accessibility (a11y) fixes, and UI structural polish.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Frontend Maestro

    nekomangaorg/Neko

    Orchestrates macro-level UI architecture, complex Jetpack Compose structures, and screen-to-screen flows.

    2.8k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Domain Distiller

What does Domain Distiller do?

Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle. Domain Distiller is an agent skill from nekomangaorg/Neko. Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle.

When should I use Domain Distiller?

Domain Distiller fits situations like: decouple Android dependencies from business rules; create domain-layer interactors; reduce ViewModel bloat.

How do I install Domain Distiller in Claude Code?

Run `npx skills add nekomangaorg/Neko --skill domain-distiller -a claude-code`. Or copy the skill folder (.agents/skills/distiller in nekomangaorg/Neko) into .claude/skills/domain-distiller in your project. Claude Code loads it when a task matches its description.

How do I install Domain Distiller in Codex?

Run `npx skills add nekomangaorg/Neko --skill domain-distiller -a codex`. Or copy the skill folder (.agents/skills/distiller in nekomangaorg/Neko) into .agents/skills/domain-distiller in your project. Codex loads it when a task matches its description.

Can I use Domain Distiller in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nekomangaorg/Neko --skill domain-distiller -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/domain-distiller, .gemini/skills/domain-distiller, .github/skills/domain-distiller and .opencode/skills/domain-distiller in your project.

What does Domain Distiller need to run?

SKILL.md names no scripts, command-line tools or credentials: Domain Distiller is instructions for the agent only.

Does Domain Distiller access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Domain Distiller safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Domain Distiller use?

Domain Distiller is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Domain Distiller use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Domain Distiller?

Skills that share tags, products or a category with Domain Distiller: Android Hidden API and R8 Check (gkd-kit/gkd, 43k stars), Compose Multiplatform Patterns (monta-app/ocpp-emulator, 180 stars), Android Development (dpconde/claude-android-skill, 336 stars) and Claude Android Ninja (Drjacky/claude-android-ninja, 124 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Domain Distiller?

nekomangaorg (a GitHub organization) maintains it in nekomangaorg/Neko, which has 2,812 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.

Source: nekomangaorg/Neko on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.