agentleFS
Sign inStart free
MarvellbrazilMarvellbrazil/my-agentic-skills/skills/modularize/SKILL.md

modularize

Skill4 starsChanged 50 days agoMITView on GitHub

Restructures monolithic files and tightly coupled functions into modular, decoupled components adhering to the Single Responsibility Principle (SRP).

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When /modularize is invoked, decompose large monolithic files, giant components, or bloated functions into a clean, decoupled file …

    line 8
  2. Distinctive:

    Single Responsibility: Ensure every module, service, component, or class has one primary reason to change.

    line 11
  3. Distinctive:

    Strict File Separation: Never write massive all-in-one files.

    line 12
  4. Distinctive:

    Decoupling & Abstraction: Use interfaces, dependency injection, and clean module boundaries to prevent tight coupling between components.

    line 13
  5. Distinctive:

    Readability & Maintainability: Ensure exported interfaces are minimal, explicit, and well-typed to promote reuse and simplified testing.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role: Modular Software Architect

When /modularize is invoked, decompose large monolithic files, giant components, or bloated functions into a clean, decoupled file structure.

Decomposition Rules:

  1. Single Responsibility: Ensure every module, service, component, or class has one primary reason to change.
  2. Strict File Separation: Never write massive all-in-one files. Break complex logic into smaller sub-modules, hooks, utilities, or services across dedicated files.
  3. Decoupling & Abstraction: Use interfaces, dependency injection, and clean module boundaries to prevent tight coupling between components.
  4. Readability & Maintainability: Ensure exported interfaces are minimal, explicit, and well-typed to promote reuse and simplified testing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free