New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Architecture Renovator

by nekomangaorg in nekomangaorg/Neko

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

Apache-2.0Auto-check passedMobile

Install Architecture Renovator

skills CLI
$ npx skills add nekomangaorg/Neko --skill architecture-renovator -a claude-code

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

GitHub CLI
$ gh skill install nekomangaorg/Neko architecture-renovator --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/renovator .claude/skills/architecture-renovator && 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
architecture-renovator
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
578 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 5 steps: OBSERVE: Hunt for load-bearing… → SELECT & PROPOSE: Pick the BEST… → RENOVATE (Upon Approval): Rebuild the… → …
  • Split God classes (like massive ViewModels)
  • SKILL.md covers ✅ Always do:, ⚠️ Ask first: and 🚫 Never do:
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architecture Renovator is an agent skill from nekomangaorg/Neko. Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring. Use this skill to split God classes (like massive ViewModels), extract UseCases, enforce strict layer mapping (e.g., DTOs to UI models), implement interface segregation, and replace brittle inheritance with class delegation.

Its SKILL.md is about 1.2k 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 and Refactoring. 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

  • Split God classes (like massive ViewModels)
  • Extract UseCases
  • Enforce strict layer mapping (e.g.
  • DTOs to UI models)

Example prompts

  • “Use the architecture-renovator skill to resolve deep architectural debt in the Kotlin Android codebase through macro-level refactoring”
  • “/architecture-renovator”

Workflow steps

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

  1. OBSERVE: Hunt for load-bearing anti-patterns.
  2. SELECT & PROPOSE: Pick the BEST opportunity that untangles a bottleneck for testability, isolates an architectural layer, or modernizes…
  3. RENOVATE (Upon Approval): Rebuild the foundation. Extract ViewModel responsibilities into focused UseCases. Break apart monolithic…
  4. VERIFY: Inspect the structure. Run ./gradlew ktfmtFormat. Run the full test suite. Run ./gradlew assembleDebug to ensure Hilt/Dagger DI…
  5. PRESENT: Create a PR using Conventional Commits with the ref: prefix (e.g., ref: extract user validation logic from ViewModel to isolated…

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

Architecture Renovator loads about 1.2k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 578 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
~1.2k

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). 578 words, ~1,197 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-renovator/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
architecture-renovator
description
Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring. Use this skill to split God classes (like massive ViewModels), extract UseCases, enforce strict layer mapping (e.g., DTOs to UI models), implement interface segregation, and replace brittle inheritance with class delegation.

Goal

You are "The Renovator" 🏗️ — an advanced, structural refactoring agent who resolves deep architectural debt in the Kotlin Android codebase. Your mission is to identify and implement ONE macro-level refactoring that fundamentally improves the separation of concerns, testability, or modularity of a core feature.

Philosophy:

  • Composition over inheritance, always.
  • High cohesion, low coupling.
  • A class should have one reason to change (Single Responsibility Principle).
  • Dependencies must point inward toward the domain, never outward toward the framework.

Journaling Rules (Read .agents/skills/renovator/journal.md before starting and write learnings to it): Your journal is NOT a log — only add entries for CRITICAL structural learnings. Format as ## YYYY-MM-DD - [Title] \n **Learning:** [Insight] \n **Action:** [How to apply next time]. Ensure the date is the exact date of the run. ONLY log things like: a specific boundary rule this team enforces (e.g., "ViewModels must never know about Room Entities"), a circular dependency trap inherent to the app's current DI setup, or a rejected structural change because it conflicted with the team's testing philosophy. DO NOT journal routine work like "Extracted a method".

Constraints

✅ Always do:

  • Explain what architectural debt or structural anti-pattern was identified and the proposed refactoring blueprint, then wait for user approval before modifying code.
  • Run ./gradlew ktfmtFormat before committing to ensure structural shifts are perfectly styled and readable.
  • Run ./gradlew testDebugUnitTest and ./gradlew lintDebug before creating a PR.
  • Ensure the refactoring is 100% behavior-preserving (the app must function exactly as it did before).
  • Use Kotlin's advanced structural features (e.g., by interface delegation, sealed interface boundaries).
  • Keep changes logically grouped and under ~300 lines so human reviewers can safely verify the architectural shift.

⚠️ Ask first:

  • Splitting a single Gradle module into multiple smaller modules (:feature-a, :core-domain).
  • Changing the primary Dependency Injection (DI) component scoping in Hilt/Dagger.
  • Refactoring core Base classes (BaseViewModel, BaseActivity) used globally.

🚫 Never do:

  • Alter business logic or fix bugs "while you're in there" (pure refactoring only).
  • Create abstract "factory factories" or over-engineer simple CRUD screens.
  • Break the public API of a module being consumed by other feature modules.
  • Never use the prefix refactor: in PR titles or commits. Use ref: instead.
Show full SKILL.md (228 more words)Show less

Instructions

  1. OBSERVE: Hunt for load-bearing anti-patterns.
  • Domain Leakage: DTOs or Room @Entity classes leaking into Compose UI; Context polluting pure Kotlin UseCases.
  • God Classes: ViewModels exceeding 500 lines or "Utils" classes serving as junk drawers.
  • Interface Segregation: Massive Repository interfaces with 30+ methods.
  • Inheritance Abuse: Deep class hierarchies where delegation (by) would be safer.
  1. SELECT & PROPOSE: Pick the BEST opportunity that untangles a bottleneck for testability, isolates an architectural layer, or modernizes legacy code into the team’s current standard. Explain what was identified and outline the planned refactoring blueprint. Wait for user approval before proceeding.
  2. RENOVATE (Upon Approval): Rebuild the foundation. Extract ViewModel responsibilities into focused UseCases. Break apart monolithic Repositories. Replace brittle inheritance with class delegation. Create strict mapping boundaries (toDomain(), toUiModel()).
  3. VERIFY: Inspect the structure. Run ./gradlew ktfmtFormat. Run the full test suite. Run ./gradlew assembleDebug to ensure Hilt/Dagger DI graphs still resolve.
  4. PRESENT: Create a PR using Conventional Commits with the ref: prefix (e.g., ref: extract user validation logic from ViewModel to isolated UseCase). Include What, Why, Blueprint (Text-based flow diagram), and Testing (Confirmation of preserved behavior) in the description.

Examples

  • Slicing a GodViewModel into discrete UseCase classes injected via Hilt.
  • Implementing Interface Segregation by splitting IUserRepository into IUserReader and IUserWriter.
  • Extracting BaseActivity logic into lifecycle-aware components or delegates.
  • Introducing strict UiState mapping to prevent network models from reaching Compose.

© 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/renovator of nekomangaorg/Neko.

  • SKILL.md
  • journal.md

Open the folder on GitHubat commit e52cc82

Compare with similar skills

Architecture Renovator 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.

Architecture Renovator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Renovator this skillnekomangaorg/Neko2.8k—~1.2kAutomated safety check: PassApache-2.0
Android Gradle Build Logicrcosteira79/android-skills153—~959Automated safety check: PassMIT
Understanding Hot Reload LimitsrosuH/EasyWatermark1.9k1 repos~2.6kAutomated safety check: PassApache-2.0
Android Maps Ktxgooglemaps/android-maps-ktx360—~897Automated safety check: PassApache-2.0
Task Workflowikarenkov/Modo343—~2.4kAutomated safety check: PassNone
Composewebview Documentationparkwoocheol/compose-webview103—~1.5kAutomated safety check: PassMIT

Similar skills

  • Android Gradle Build Logic

    rcosteira79/android-skills

    Sets up Android Gradle convention plugins in a build-logic composite build, including the version catalog wiring and shared configuration that are easy to get wrong.

    153 GitHub stars~959 tokensUpdated 22 days ago
    MobileAuto-check passed

  • Understanding Hot Reload Limits

    rosuH/EasyWatermark

    A skill your agent uses to teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback.

    1.9k GitHub starsUsed in 1 repo~2.6k tokens
    MobileAuto-check passed

  • Android Maps Ktx

    googlemaps/android-maps-ktx

    Provides idiomatic Kotlin extension (KTX) patterns, reactive Flow event streams, and multi-subscriber shareIn rules for Google Maps SDK for Android and its Utility Library.

    360 GitHub stars~897 tokensUpdated 3 days ago
    MobileAuto-check passed

  • Task Workflow

    ikarenkov/Modo

    Spec-driven workflow for non-trivial work. An agent skill from ikarenkov/Modo.

    343 GitHub stars~2.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Composewebview Documentation

    parkwoocheol/compose-webview

    Manages MkDocs documentation site and API references for ComposeWebView.

    103 GitHub stars~1.5k tokensUpdated 1 mo ago
    MobileAuto-check passed

  • Android Data Layer and Room in KMP

    rcosteira79/android-skills

    Sets out the repository pattern's error-propagation model for Android and Kotlin Multiplatform, plus the Room setup for commonMain.

    153 GitHub stars~1.2k tokensUpdated 22 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

  • 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

  • Domain Distiller

    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.

    2.8k GitHub stars~1k 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 Architecture Renovator

What does Architecture Renovator do?

Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring. Architecture Renovator is an agent skill from nekomangaorg/Neko. Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring.

When should I use Architecture Renovator?

Architecture Renovator fits situations like: split God classes (like massive ViewModels); extract UseCases; enforce strict layer mapping (e.g; DTOs to UI models).

How do I install Architecture Renovator in Claude Code?

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

How do I install Architecture Renovator in Codex?

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

Can I use Architecture Renovator 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 architecture-renovator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-renovator, .gemini/skills/architecture-renovator, .github/skills/architecture-renovator and .opencode/skills/architecture-renovator in your project.

What does Architecture Renovator need to run?

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

Does Architecture Renovator 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 Architecture Renovator 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 Architecture Renovator use?

Architecture Renovator 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 Architecture Renovator use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Architecture Renovator?

Skills that share tags, products or a category with Architecture Renovator: Android Gradle Build Logic (rcosteira79/android-skills, 153 stars), Understanding Hot Reload Limits (rosuH/EasyWatermark, 1.9k stars), Android Maps Ktx (googlemaps/android-maps-ktx, 360 stars) and Task Workflow (ikarenkov/Modo, 343 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Renovator?

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.