architectural-principles

Apply SOLID, 12-factor, DRY, KISS, and defensive design principles to software planning, coding, and review workflows.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/gulati8/justice-league-factory --skill architectural-principles-gulati8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architectural-principles
Source: https://github.com/gulati8/justice-league-factory/tree/main/.claude/skills/architectural-principles
Command: npx skills add https://github.com/gulati8/justice-league-factory --skill architectural-principles-gulati8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared architectural and engineering principles guide planning, implementing, and reviewing code. It provides a single source of truth for SOLID, 12-factor, DRY, KISS, and defensive design, referenced by agents like Martian Manhunter, Cyborg, and Wonder Woman.

Core Features & Use Cases

  • Establishes the standards and criteria that define what good software looks like within the factory.
  • Guides planning, implementation, and review workflows to ensure consistency across agents (planning-methodology, implementation-standards, review-criteria).
  • Enables automatic propagation of updated principles to consuming agents via governance mechanisms.

Quick Start

Align architectural decisions and code reviews with the shared principles.

Frequently Asked Questions about architectural-principles

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

FAQPage Schema
How do I apply SOLID and 12-factor principles to guide software design and code reviews?

Apply shared architectural principles to guide software design and evaluation by enforcing SOLID, 12-factor, DRY, KISS, and defensive design standards across planning, coding, and review workflows.

What are the core architectural principles for solid software development?

Core architectural principles for solid software include SOLID, 12-factor, DRY, KISS, and defensive design. These establish shared standards for configuration over hardcoding, migration-first changes, and defensive validation.

How do I enforce configuration over hardcoding and migration-first changes in my codebase?

Enforce configuration over hardcoding and migration-first changes by applying defensive validation constraints and best practices from shared architectural principles during planning and implementation workflows.

Can I use these architectural principles to standardize code evaluation across different agents?

Yes, you can use these shared architectural principles to standardize code evaluation across different agents. They provide a single source of truth for planning, implementation, and review workflows to ensure consistency.

Does this approach support defensive design and validation for software engineering workflows?

Yes, this approach supports defensive design and validation for software engineering workflows. It enforces defensive validation through clear constraints and best practices across planning, coding, and review stages.

When do I need shared architectural principles for software planning and implementation?

You need shared architectural principles for software planning and implementation when establishing consistent standards for what good software looks like. They guide SOLID, 12-factor, and defensive design across development workflows.