skills.rest
oliver-kriska
oliver-kriskaCOMMUNITY
Explore all skills by this author →
Website𝕏@quatermain32GitHub

phx:boundaries

Validate Phoenix context boundaries and dependencies using mix xref.

517|35|Updated Feb 12, 2026
Search Tags:#architecture#code review#refactoring#elixir#phoenix#context boundaries
One-click install
npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-boundaries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phx:boundaries
Source: https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/skills/boundaries
Command: npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-boundaries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain a clean and robust Elixir Phoenix application architecture by enforcing strict boundaries between different contexts and layers of the application.

Core Features & Use Cases

  • Dependency Analysis: Analyzes module dependencies to detect violations of architectural rules.
  • Context Health Scoring: Provides a quantifiable score for the health of your application's contexts.
  • Violation Identification: Pinpoints specific issues like circular dependencies, excessive module counts, or improper layer communication.
  • Use Case: Before merging a large pull request, run this Skill to ensure new code doesn't introduce architectural debt by violating context boundaries.

Quick Start

Run /phx:boundaries to check for context boundary violations in your Phoenix project.

Frequently Asked Questions about phx:boundaries

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

FAQPage Schema
How do I check for circular dependencies in Phoenix contexts?▼

You can detect circular dependencies in Phoenix contexts by running this Skill, which uses `mix xref` to analyze module fan-out, fan-in, and boundary violations to highlight architectural issues.

What is a Phoenix context boundary violation?▼

A Phoenix context boundary violation occurs when application modules bypass clean architectural separation, creating improper layer communication or circular dependencies that negatively impact code health and maintainability.

How do I score the architectural health of my Elixir Phoenix application?▼

You score the architectural health of an Elixir Phoenix application by analyzing module counts, public API surface, and dependency structures to quantify context integrity and identify boundary violations.

Can I get automated fix suggestions for Phoenix context refactoring?▼

Yes, you can get automated fix suggestions for Phoenix context refactoring, as the analysis supports assessment and provides actionable recommendations to resolve architectural boundary violations and clean up dependencies.

Does this Phoenix context analysis require any specific dependencies?▼

No, this Phoenix context analysis does not require any specific external dependencies, as it validates context boundaries and dependencies natively using the built-in `mix xref` tool.

Related Skills

Explore More Software Engineering Skills→
dominicletzdominicletz
26

elixir-cyclic-dependencies

Detect and resolve cyclic compile-time dependencies in Elixir projects using mix xref.

Community
Advanced
CANTAGESTUDIOCANTAGESTUDIO
3

refactor-arch-hotspots

Detect architectural hotspots by analyzing churn, coupling, and layer violations.

Community
Advanced
cdalsoniiicdalsoniii

Architecture Fitness Functions

Evaluate Go project architecture with automated fitness functions for layer boundaries, dependencies, and complexity.

Community
Intermediate
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced