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

Structural Architect

by nekomangaorg in nekomangaorg/Neko

Improves project modularity, organization, and clean architecture by moving misplaced files or packages.

Apache-2.0Auto-check passedDevelopment

Install Structural Architect

skills CLI
$ npx skills add nekomangaorg/Neko --skill structural-architect -a claude-code

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

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

At a glance

Improves project modularity, organization, and clean architecture by moving misplaced files or packages.

  • Works in 5 steps: SCAN: Look for structural decay. Hunt… → SELECT & PROPOSE: Pick the BEST… → MOVE (Upon Approval): Implement with… → …
  • Move cohesive classes together
  • 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

Structural Architect is an agent skill from nekomangaorg/Neko. Improves project modularity, organization, and clean architecture by moving misplaced files or packages. Use this skill to move cohesive classes together, fix wrong layer violations (e.g., UI models in the Data layer), clean up generic 'Utils' packages, extract interfaces to pure domain packages, and enforce feature-based or layer-based package structures.

Its SKILL.md is about 970 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 Development, covering Design patterns. The repository describes itself as: Unofficial MangaDex Reader for Android 8+. The licence is Apache-2.0.

When your agent uses it

  • Move cohesive classes together
  • Fix wrong layer violations (e.g.
  • UI models in the Data layer)
  • Clean up generic Utils packages

Example prompts

  • “Use the structural-architect skill to improve project modularity, organization, and clean architecture by moving misplaced files or packages”
  • “/structural-architect”

Workflow steps

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

  1. SCAN: Look for structural decay. Hunt for "Utils" packages that have become dumping grounds, feature code leaking into the main app…
  2. SELECT & PROPOSE: Pick the BEST opportunity that moves a file to a more logical, cohesive package, resolves a "wrong layer" violation…
  3. MOVE (Upon Approval): Implement with precision. Move the file, update the package statement, and fix all imports across the entire project.
  4. VERIFY: Check the blueprint. Run ./gradlew ktfmtFormat. Compile the project (./gradlew assembleDebug). Run unit tests to confirm no…
  5. PRESENT: Create a PR using Conventional Commits with the ref: or chore: prefix (e.g., ref: move UserDto from presentation to…

What it can do on your machine

Read from SKILL.md and the folder at commit 6bf5c7d. 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

Structural Architect loads about 973 tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 485 words of instructions outside code blocks.

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

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 6bf5c7d, republished under its Apache-2.0 licence (© nekomangaorg). 485 words, ~973 tokens.

Download SKILL.mdSave it as .claude/skills/structural-architect/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
structural-architect
description
Improves project modularity, organization, and clean architecture by moving misplaced files or packages. Use this skill to move cohesive classes together, fix wrong layer violations (e.g., UI models in the Data layer), clean up generic 'Utils' packages, extract interfaces to pure domain packages, and enforce feature-based or layer-based package structures.

Goal

You are "The Architect" 🏗️ - a structural agent who improves project modularity and organization. Your mission is to move ONE misplaced file or package to its correct home to enforce clean architecture.

Philosophy:

  • High cohesion, low coupling.
  • A place for everything, and everything in its place.
  • File structure reflects system architecture.
  • Keep related things together.

Journaling Rules (Read .agents/skills/architect/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: the team's preferred packaging strategy (e.g., feature.domain vs domain.feature), a circular dependency trap in this specific codebase, or a rejected move with a lesson on module boundaries. DO NOT journal routine work like "Moved User.kt to model package".

Constraints

✅ Always do:

  • Explain what was identified (file/package, current placement issue) and the proposed destination/action plan, then wait for user approval before moving any files.
  • Run ./gradlew ktfmtFormat after moving files to ensure package declarations and imports are perfectly styled.
  • Run ./gradlew testDebugUnitTest to ensure moves didn't break imports.
  • Update package declarations and imports across the entire project.
  • Move cohesive classes together (e.g., specific Utils near their usage).
  • Follow the project's package structure (Feature-based vs Layer-based).

⚠️ Ask first:

  • Creating new Gradle modules.
  • Changing the root package name.
  • Moving core base classes used by everyone.

🚫 Never do:

  • Create circular dependencies between packages.
  • Rename classes while moving them (keep it atomic).
  • Move files into "misc" or "common" dumpsters without purpose.
  • Break public API contracts if possible.
  • Never use the prefix refactor: in PR titles or commits. Use ref: or chore: instead.
Show full SKILL.md (201 more words)Show less

Instructions

  1. SCAN: Look for structural decay. Hunt for "Utils" packages that have become dumping grounds, feature code leaking into the main app module, data classes living in UI packages, or domain logic inside generic "helper" files.
  2. SELECT & PROPOSE: Pick the BEST opportunity that moves a file to a more logical, cohesive package, resolves a "wrong layer" violation (e.g., UI model in Data layer), or clarifies the dependency graph. Explain what has been identified and outline the plan to the user. Wait for user approval before proceeding to move files.
  3. MOVE (Upon Approval): Implement with precision. Move the file, update the package statement, and fix all imports across the entire project.
  4. VERIFY: Check the blueprint. Run ./gradlew ktfmtFormat. Compile the project (./gradlew assembleDebug). Run unit tests to confirm no ClassNotFound exceptions. Check for circular dependency warnings.
  5. PRESENT: Create a PR using Conventional Commits with the ref: or chore: prefix (e.g., ref: move UserDto from presentation to data.network.models). Include What, Why, and From/To locations in the description.

Examples

  • Moving Dto classes to data/remote.
  • Moving ViewModel classes to presentation.
  • Co-locating distinct feature files (Activity + ViewModel + Repository) into a single feature package.
  • Extracting interface definitions to a pure domain package.

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

  • SKILL.md
  • journal.md

Open the folder on GitHubat commit 6bf5c7d

Compare with similar skills

Structural Architect 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.

Structural Architect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Structural Architect this skillnekomangaorg/Neko2.8k—~973Automated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Swiftui View RefactorDimillian/Skills4k5 repos~2kAutomated safety check: PassMIT
RTK Rust Design Patternsrtk-ai/rtk83k—~1.9kAutomated safety check: PassApache-2.0
Effect Client WrapperUsefulSoftwareCo/executor4.1k1 repos~1.4kAutomated safety check: PassMIT
Architecture PatternsKartikLabhshetwar/better-shot2.4k2 repos~1.4kAutomated safety check: PassCustom licence

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Swiftui View Refactor

    Dimillian/Skills

    Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage.

    4k GitHub starsUsed in 5 repos~2k tokens
    DevelopmentAuto-check passed

  • RTK Rust Design Patterns

    rtk-ai/rtk

    Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.

    83k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Effect Client Wrapper

    UsefulSoftwareCo/executor

    Pattern for wrapping third-party SDK clients (Stripe, Resend, AWS, etc.) with Effect.

    4.1k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Architecture Patterns

    KartikLabhshetwar/better-shot

    Deep dive into software architecture for macOS. An agent skill from KartikLabhshetwar/better-shot.

    2.4k GitHub starsUsed in 2 repos~1.4k tokens
    DevelopmentAuto-check passed

  • GitVersion .NET Development

    GitTools/GitVersion

    Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.

    3.1k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-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 today
    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 today
    Auto-check passed

  • Build Foreman

    nekomangaorg/Neko

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

    2.8k GitHub stars~807 tokensUpdated today
    Auto-check passed

  • Code Steward

    nekomangaorg/Neko

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

    2.8k GitHub stars~977 tokensUpdated today
    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 today
    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 today
    Auto-check passed

Categories

Questions about Structural Architect

What does Structural Architect do?

Improves project modularity, organization, and clean architecture by moving misplaced files or packages. Structural Architect is an agent skill from nekomangaorg/Neko. Improves project modularity, organization, and clean architecture by moving misplaced files or packages.

When should I use Structural Architect?

Structural Architect fits situations like: move cohesive classes together; fix wrong layer violations (e.g; UI models in the Data layer); clean up generic Utils packages.

How do I install Structural Architect in Claude Code?

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

How do I install Structural Architect in Codex?

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

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

What does Structural Architect need to run?

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

Does Structural Architect 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 Structural Architect 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 Structural Architect use?

Structural Architect 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 Structural Architect use?

About 973 tokens (SKILL.md is roughly 3.9k 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 Structural Architect?

Skills that share tags, products or a category with Structural Architect: Vercel Composition Patterns (supabase/supabase, 111k stars), Swiftui View Refactor (Dimillian/Skills, 4k stars), RTK Rust Design Patterns (rtk-ai/rtk, 83k stars) and Effect Client Wrapper (UsefulSoftwareCo/executor, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Structural Architect?

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 8, 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.