What is the recommended directory structure?

The skill promotes a flat, domain-oriented structure within the App namespace, separating concerns into Core, Entity, Model, Presentation, and Tasks.

How does this skill handle business logic?

It advocates for placing business domain logic in the Model/ namespace, while keeping infrastructure-agnostic code in the Core/ namespace to ensure a clean separation of concerns.

When should I create a new module in Nette?

You should create a new module when you have 5+ related presenters, a distinct user base (like Admin vs Front), or specific authentication requirements.

Which versions of Nette and PHP does this skill support?

This skill is specifically designed for PHP 8.3+, Nette 3.2, and Latte 3.1, utilizing modern features like PHP attributes and the latest DI container patterns.

Nette Application Architecture

Name: Nette Application Architecture
Author: nette

bynette

•

Desarrollo de API

Guides the architectural design of Nette web applications using modern best practices and domain-driven organization.

Acerca de

This skill equips Claude with specialized knowledge of the Nette Framework 3.2+ ecosystem, enabling it to architect scalable, maintainable, and logically organized PHP applications. It emphasizes an organic evolution strategy—starting with a minimal, flat structure and refactoring into modules only when complexity demands it. By providing clear decision matrices for Core vs. Model layers and enforcing best practices for presenters and dependency injection, this skill ensures that your codebase remains robust while avoiding the pitfalls of over-engineering.

Características Principales

Standardizes presenter organization, base presenter usage, and module creation rules.
Provides a decision matrix for separating technology-agnostic Core logic from business Model services.
Enforces organic evolution strategies to prevent premature architectural complexity.
Implements domain-driven organization for App namespaces and directory structures.
Guides the implementation of modern Nette features like #[Requires] attributes and NEON configuration.
29 GitHub stars

Casos de Uso

Refactoring monolithic Nette applications into domain-specific modules and presenters.
Defining service boundaries and dependency injection patterns for complex business logic.
Designing the initial directory structure and namespace hierarchy for new Nette projects.

Acerca de

Características Principales

Standardizes presenter organization, base presenter usage, and module creation rules.
Provides a decision matrix for separating technology-agnostic Core logic from business Model services.
Enforces organic evolution strategies to prevent premature architectural complexity.
Implements domain-driven organization for App namespaces and directory structures.
Guides the implementation of modern Nette features like #[Requires] attributes and NEON configuration.
29 GitHub stars

Casos de Uso

Refactoring monolithic Nette applications into domain-specific modules and presenters.
Defining service boundaries and dependency injection patterns for complex business logic.
Designing the initial directory structure and namespace hierarchy for new Nette projects.