architecture-crosscutting

Document and enforce crosscutting architectural constraints with arc42 §8 content.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill architecture-crosscutting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-crosscutting
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/architecture/architecture-crosscutting
Command: npx skills add https://github.com/pkuppens/pkuppens --skill architecture-crosscutting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document and enforce crosscutting architectural constraints across a codebase. It covers dependency rules, layering boundaries, and architecture tests to help prevent drift and to align with arc42 §8 content.

Core Features & Use Cases

  • Documents crosscutting concepts: dependency rules, layering, and architecture tests. Use when enforcing constraints or detecting architecture drift; produces arc42 §8 content.
  • Outputs guidance and sections for documentation like arc42 architecture artifacts.
  • Provides a scaffold for architecture tests and linter-style checks to prevent forbidden dependencies.

Quick Start

Apply crosscutting architecture rules to enforce layering and dependency constraints across your codebase.

Frequently Asked Questions about architecture-crosscutting

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

FAQPage Schema
How do I enforce layering boundaries and dependency rules in my codebase?

You enforce dependency rules by documenting crosscutting architectural constraints and generating lightweight verification scaffolding, such as architecture tests, that detect forbidden dependencies and layering violations across your codebase.

What are architecture tests and when do I need them?

Architecture tests are linter-style checks that verify your codebase adheres to defined dependency rules and layering boundaries. You need them when detecting architectural drift or communicating crosscutting decisions to teams.

How do I generate arc42 section 8 documentation for crosscutting architecture decisions?

Generate arc42 §8 content by documenting crosscutting concepts like dependency rules, layering boundaries, and architecture tests, producing structured sections that communicate architectural decisions to your team.

Can I use this approach for an existing project with architecture drift?

Yes, you can apply crosscutting architecture rules to existing projects by defining layering boundaries and dependency constraints, then using architecture tests to identify and prevent further drift in the codebase.

What's the best way to prevent forbidden dependencies across architectural layers?

Prevent forbidden dependencies by establishing crosscutting architecture rules with linter-style checks and architecture test scaffolding that automatically verifies layering boundaries and flags violations in the codebase.