arquitetura-proposta

Enforce a standardized project structure with domain, use_case, application, infra, shared, and tests folders.

Updated Apr 5, 2026

Search Tags:#architecture #software-engineering #domain #layers #project-structure #proposta-arq

Ready to run

npx skills add https://github.com/joleques/northstar-ai --skill arquitetura-proposta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arquitetura-proposta
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/arquitetura
Command: npx skills add https://github.com/joleques/northstar-ai --skill arquitetura-proposta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This front-matter defines a standardized folder structure and dependency rules to guide projects toward the proposta-arq architecture.

Core Features & Use Cases

Establishes a consistent multi-layer layout: domain, use_case, application, infra, shared, tests.
Clarifies dependency direction and responsibilities across layers.
Serves as a reference for new projects or audits of existing ones.

Quick Start

Apply the proposed Arquitetura layout to initialize a new project, creating domain, use_case, application, infra, shared, and tests folders.

Frequently Asked Questions about arquitetura-proposta

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

FAQPage Schema

How do I structure a software project with clear domain and infra layer separation?▼

To structure a software project with clear layer separation, apply a standardized layout using domain, use_case, application, infra, shared, and tests folders. This enforces clear dependency direction from infra to domain while maintaining consistency across the codebase.

What is the correct dependency direction in a multi-layer project architecture?▼

The correct dependency direction in a multi-layer project architecture flows from infra to domain. The standardized layout clarifies responsibilities across layers like use_case, application, and shared, ensuring dependencies point inward toward the domain core.

Can I use a standardized folder layout to refactor an existing software project?▼

You can use a standardized folder layout to refactor an existing software project by aligning the codebase with domain, use_case, application, infra, shared, and tests folders. It serves as a reference during audits to enforce consistent structure and dependency rules.

What's the best way to organize shared modules in a layered software architecture?▼

The best way to organize shared modules in a layered software architecture is to place them in a dedicated shared folder. This provides guidance and supports consistency across domain, use_case, application, and infra layers without violating dependency directions.

When do I need a multi-layer project structure blueprint?▼

You need a multi-layer project structure blueprint when initializing new software projects or refactoring existing ones. It codifies a standardized layout with domain, use_case, application, infra, shared, and tests folders to guide scalable and clean project architecture.