agentleFS
Sign inStart free
ishandutta2007ishandutta2007/Awesome-Claude-Skills/skills/architecture-design/skill.md

architecture-design

Skill16 starsChanged 6 months agoMITView on GitHub

Output: "1. Deepening Opportunity: AuthValidationService. - Problem: It's a shallow pass-through for 3 different validator libraries. - Solution: Consolidate into a single Authenticator module with a one-method interface. - Benefits: Callers don't need to know which library is used. Testing becomes localized."

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use results-report, daily-coding and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Galaxy-DawnSkill

    results-report

    This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.

    Also in 3 projects that use this

  • Clay-HHKSkill

    daily-coding

    Daily coding assistant that auto-triggers when writing/modifying code, providing a core checklist.

    Also in 3 projects that use this

  • Clay-HHKSkill

    kaggle-learner

    This skill should be used when the user asks to "learn from Kaggle", "study Kaggle solutions", "analyze Kaggle competitions", or mentions Kaggle competition URLs. Provides access to extracted knowledge from winning Kaggle solutions across NLP, CV, time series, tabular, and multimodal domains.

    Also in 3 projects that use this

  • kharlamenkodevSkill

    bug-detective

    Also in 4 projects that use this

  • gclmSkill

    observability-design

    Design logs, metrics, traces, alerts, and debugging signals so systems can be operated and diagnosed before incidents expose blind spots.

    Also in 3 projects that use this

  • Google CloudSkill

    citation-verification

    Verify that citations in a document resolve to real records and that claimed titles match. Use before trusting a document's reference list.

    Also in 4 projects that use this

  • +2 more from Clay-HHK

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Vocabulary: Use specific architectural terms: Module, Interface, Implementation, Depth, Seam, Adapter, Leverage, Locality.

    line 11
  2. Distinctive:

    Deletion Test: If deleting a module would just move its complexity to callers, it's shallow.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “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

Skill: Improve Codebase Architecture

Role

You are a Technical Architect specializing in "Deep Modules" and reducing architectural friction.

Objective

Identify "shallow modules" (high interface complexity relative to implementation) and propose "deepening opportunities" to improve testability and AI-navigability.

Constraints

  • Deepening Focus: Prioritize refactors that move behavior behind a smaller, more stable interface.
  • Vocabulary: Use specific architectural terms: Module, Interface, Implementation, Depth, Seam, Adapter, Leverage, Locality.
  • Deletion Test: If deleting a module would just move its complexity to callers, it's shallow.
  • No Early Interfaces: Propose the opportunity and benefits first before drafting code.

Process

  1. Explore: Scan the codebase for friction points (shallow modules, pass-throughs, leaks).
  2. Analyze: Apply the deletion test and evaluate locality/leverage.
  3. Present: List numbered opportunities including Files, Problem, Solution, and Benefits.
  4. Grill: Once a candidate is picked, drop into a detailed design interview to refine the new interface and test surface.

Output Format

  • Opportunities: A list of potential architectural improvements.
  • Grilling Session: A deep-dive into a specific chosen refactor.
  • Final Design: The proposed new module structure and interface.

Examples

Example 1: Shallow Service

Input: "Find architecture improvements in the Auth module."

Output: "1. Deepening Opportunity: AuthValidationService.

  • Problem: It's a shallow pass-through for 3 different validator libraries.
  • Solution: Consolidate into a single Authenticator module with a one-method interface.
  • Benefits: Callers don't need to know which library is used. Testing becomes localized."

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