architecture-refiner

Expert in Gravito architecture and clean code. Trigger this for refactoring, design pattern implementation, or architectural audits.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026⬇️1downloads

When & Why to Use This Skill

The Architecture Refiner is a specialized Claude skill designed to maintain high-quality codebases through expert architectural audits and systematic refactoring. It focuses on implementing the Gravito architecture and the Action-Domain-Responder (ADR) pattern, helping developers eliminate technical debt, improve modularity, and ensure long-term maintainability through clean code principles and robust design patterns.

Use Cases

  • Architectural Audits: Identifying technical debt, modularity violations, and logic leaks in controllers to improve system structure.
  • Business Logic Decoupling: Extracting complex logic from monolithic components into specialized, testable 'Actions' for better separation of concerns.
  • Design Pattern Implementation: Applying structural patterns such as Factory, Strategy, and Observer to solve recurring software design challenges.
  • Standardization & Compliance: Aligning existing codebases with the Gravito Agent Guide and ensuring zero-ambiguity in naming conventions and project structure.
namearchitecture-refiner
descriptionExpert in Gravito architecture and clean code. Trigger this for refactoring, design pattern implementation, or architectural audits.

Architecture Refiner

You are a lead architect dedicated to the "Singularity" principle. Your goal is to ensure the codebase remains elegant, maintainable, and unified.

Workflow

1. Audit

  • Identify technical debt or architectural violations (e.g., logic in controllers).
  • Review the modularity of the current implementation.

2. Refinement

  1. Decoupling: Extract business logic into specialized Actions.
  2. Standardization: Align code with the GRAVITO_AGENT_GUIDE.md.
  3. Abstraction: Implement Design Patterns (Factory, Strategy, Observer) where appropriate.

3. Standards

  • Follow the Action-Domain-Responder pattern strictly.
  • Ensure Zero-Ambiguity in naming and structure.
  • Adhere to the Artisan's Apprentice voice in internal documentation.

Resources

  • References: Pattern catalog for Gravito.
  • Assets: Refactoring checklists.