my-react-rules

Codify and enforce Elixir and Phoenix coding practices for Domain-Driven Design.

Updated Aug 27, 2026

Search Tags:#testing #documentation #elixir #phoenix #design-patterns #coding-practices #enforce

Ready to run

npx skills add https://github.com/Aafff623/yihui-vibe-coding-exer --skill my-react-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: my-react-rules
Source: https://github.com/Aafff623/yihui-vibe-coding-exer/tree/main/.cursor/skills/my-react-rules
Command: npx skills add https://github.com/Aafff623/yihui-vibe-coding-exer --skill my-react-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams codify and enforce software development best practices for Elixir and Phoenix projects, reducing architectural drift and code smells.

Core Features & Use Cases

Domain-Driven Design alignment: Aligns code structure with business domains to improve maintainability.
Pattern-based development: Encourages a functional core with explicit boundaries, clear module responsibilities, and strong typing hints via specs.
Documentation and testing discipline: Promotes thorough public API docs, @doc examples, and solid testing strategies, including Credo and Dialyzer checks.
Use Case: Reorganize a monolithic context into clearly defined domains to reduce coupling and improve testability in a Phoenix app.

Quick Start

Review and apply these guidelines to your next Phoenix context.

Frequently Asked Questions about my-react-rules

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

FAQPage Schema

How do I enforce Domain-Driven Design and explicit module boundaries in Elixir Phoenix projects?▼

Enforce Domain-Driven Design in Elixir Phoenix by codifying high-quality coding practices that align code structure with business domains. This approach defines explicit module boundaries across contexts and APIs to reduce coupling and improve maintainability.

What's the best way to maintain documentation and testing discipline for Elixir public APIs?▼

Maintain testing discipline for Elixir public APIs by applying guidelines that promote thorough @doc examples, comprehensive documentation, and consistent formatting. This practice ensures clearly named public APIs and robust testing strategies including Credo and Dialyzer checks.

How do I reorganize a monolithic Phoenix context into clearly defined domains?▼

Reorganize a monolithic Phoenix context by applying pattern-based development guidelines that establish a functional core with clear module responsibilities. This reduces coupling and improves testability by enforcing strong typing hints via specs and explicit boundaries.

Can I use pattern matching and specs to reduce architectural drift in Elixir applications?▼

Reduce architectural drift in Elixir applications by codifying and enforcing software development best practices. Applying pattern matching and explicit module boundaries across contexts and APIs prevents code smells and maintains consistent architectural decisions.

Does this approach apply to projects using functional core architecture with Phoenix?▼

This approach applies directly to Phoenix projects using a functional core architecture. It enforces pattern-based development with explicit boundaries, clear module responsibilities, and strong typing hints via specs to guide architecture and code organization decisions.