architecture

Diagnose architectural issues like duplication and coupling in codebases.

46|5|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/victoriacity/openakari --skill architecture-victoriacity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/victoriacity/openakari/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/victoriacity/openakari --skill architecture-victoriacity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses issues in code structure, such as overly large files, tangled responsibilities, and the need for cross-cutting architectural redesign, ensuring maintainable and scalable software.

Core Features & Use Cases

  • Autonomous Diagnosis: Automatically scans the codebase for architectural issues like file size violations, duplication, coupling, clarity gaps, and type safety issues.
  • Refactoring: Performs structural, behavior-preserving changes like splitting files and extracting modules.
  • Mapping: Analyzes and visualizes system architecture, tracing dependencies, agent spawns, and data flows.
  • Redesign: Proposes and implements significant architectural changes, requiring a planning and approval phase.
  • Use Case: When a core module becomes unmanageable, use /architecture to automatically diagnose issues, prioritize fixes, and implement the highest-priority refactoring.

Quick Start

Scan the entire codebase for architectural issues and prioritize them for improvement.

Frequently Asked Questions about architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose and fix code structure issues like large files and tight coupling?

To diagnose code structure issues, you can scan the codebase to automatically detect file size violations, duplication, and tight coupling. It then prioritizes these architectural constraints for targeted refactoring.

What is the safest way to refactor a codebase without altering system behavior?

The safest way to refactor a codebase without altering system behavior is through structural, behavior-preserving changes. This involves splitting overly large files and extracting tangled responsibilities into distinct modules.

How do I map and visualize system architecture and data flows?

Mapping system architecture involves analyzing the codebase to trace dependencies, agent spawns, and data flows. This visualizes the existing infrastructure to identify clarity gaps and structural bottlenecks.

When do I need to redesign software architecture instead of just refactoring?

You need to redesign software architecture when cross-cutting structural changes are required, rather than isolated fixes. This involves proposing significant infrastructure changes through a formal planning and approval phase.

Can I automatically scan my codebase to prioritize maintainability improvements?

Yes, you can automatically scan the entire codebase to identify architectural issues like file size violations and clarity gaps. It evaluates maintainability constraints and outputs a prioritized list of improvements.

What are the limitations of autonomous codebase diagnosis for system design?

Autonomous codebase diagnosis is limited to identifying structural issues and proposing refactoring. Significant architectural redesigns require a mandatory planning and approval phase to ensure safety before implementation.