software-architecture

Enforce SOLID and Clean Architecture rules with file-size and import-cycle checks.

9|Updated May 24, 2026
One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill software-architecture-picmakpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-architecture
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/software-architecture
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill software-architecture-picmakpro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents AI-assisted code changes from creating regressions, oversized files, unclear boundaries, hidden coupling, and unverified architectural debt.

Core Features & Use Cases

  • AI-safe architecture doctrine: Applies SOLID, separation of concerns, Clean Architecture, Clean Code, DRY, KISS, and YAGNI.
  • Machine-enforced guardrails: Enforces file-size thresholds, import-boundary checks, verification gates, and traceability between decisions and implementation.
  • Refactoring guidance: Provides a structured six-wave playbook for stabilizing tests, decomposing god files, organizing bounded contexts, and strengthening architectural boundaries.
  • Debugging discipline: Requires documented research before intensive debugging of dependency, framework, native, or version-specific issues.
  • Use Case: Apply it when starting a project, editing production code, planning a refactor, or dealing with a codebase that is becoming difficult and risky to change.

Quick Start

Use the software-architecture skill to assess the current codebase, identify architectural risks, and define an enforced plan for improving its structure.

Frequently Asked Questions about software-architecture

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

FAQPage Schema
How do I prevent AI-assisted code changes from creating architectural regressions?

To enforce AI-safe development, apply machine-enforced guardrails like file-size thresholds, import-cycle checks, and verification gates during production edits or refactoring to prevent architectural regressions and hidden coupling.

What is the best way to refactor a codebase with oversized files and unclear boundaries?

Refactoring oversized files and unclear boundaries requires a structured six-wave playbook that stabilizes tests, decomposes god files, organizes bounded contexts, and enforces SOLID and Clean Architecture principles.

How do I enforce SOLID principles and Clean Architecture during software migrations?

Enforcing SOLID principles and Clean Architecture during migrations requires applying path-scoped rules, decision traceability, and documented research to verify technical debt and prevent unauthorized structural drift.

Do I need bash and python3 to run automated architectural guardrails?

Running automated architectural guardrails requires bash and python3 environments to execute scripts that check file-size limits, import boundaries, and verification gates for your codebase.

Why does AI-generated code often introduce hidden coupling and unverified technical debt?

AI-generated code introduces hidden coupling and unverified technical debt when it lacks engineering guardrails, bypassing separation of concerns and creating dependencies without documented research or decision traceability.

Can I use this to debug dependency and framework version conflicts safely?

Debugging dependency, framework, and version-specific issues safely requires documented research before intensive debugging, ensuring changes adhere to architectural boundaries and avoiding new regressions.