architecture

Detect frameworks and generate decision rules for Clean Architecture reviews.

Updated Jun 19, 2023
One-click install
npx skills add https://github.com/JeroenJochems/modelwise --skill architecture-jeroenjochems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/JeroenJochems/modelwise/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/JeroenJochems/modelwise --skill architecture-jeroenjochems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you map abstract architectural principles like Clean Architecture to your specific technology stack, ensuring your codebase is maintainable, scalable, and easy to change.

Core Features & Use Cases

  • Context Detection: Automatically identifies your framework (PHP, TypeScript), deployment model (monolith, microservices), and directory conventions.
  • Rule Generation: Translates architectural principles into verifiable, context-specific decision rules.
  • Dependency Analysis: Detects violations of the Dependency Rule, framework coupling, and database coupling.
  • Use Case: When designing a new feature, use this Skill to ensure your proposed module structure adheres to Clean Architecture principles and doesn't introduce unwanted dependencies on the UI or database layers.

Quick Start

Analyze the current project's directory structure and detect its framework and deployment model.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I map Clean Architecture principles to my specific code stack?

Map Clean Architecture by detecting your project's framework, deployment model, and directory conventions to generate context-specific decision rules. This verifies dependency direction and prevents unwanted coupling to UI or database layers.

How do I detect violations of the Dependency Rule in my codebase?

Detect Dependency Rule violations by analyzing your directory structure to identify framework coupling and database coupling. This generates verifiable decision rules to check if dependencies point in the correct direction for maintainability.

Does this approach work with both PHP and TypeScript frameworks?

Yes, context detection works with PHP and TypeScript frameworks by identifying your specific deployment model and directory conventions. It translates abstract architectural principles into verifiable rules tailored to your stack.

What is the best way to ensure a new module doesn't introduce database coupling?

Ensure a new module avoids database coupling by using generated decision rules to verify architectural compliance during design. This validates your proposed module structure against Clean Architecture principles before implementation.

When do I need to generate context-specific architectural decision rules?

Generate context-specific architectural decision rules when designing new features or conducting refactoring for maintainability. This ensures your code changes adhere to dependency direction and avoids framework coupling.

Can I use this for architectural reviews of a microservices deployment model?

Yes, you can use this for architectural reviews of a microservices deployment model by detecting your specific context. It helps verify dependency direction and identifies framework or database coupling across your services.