Results for “solid-principles”

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.

Write PHP following PSR coding standards, SOLID principles, and code-quality guidelines. Use for PHP style, design, refactoring, naming, and guard clauses—not Composer/PSR-4 project configuration.

Strip a problem to its irreducible fundamental truths and rebuild the solution from the ground up — free from analogy, convention, and inherited assumptions. Load when the user feels constrained by how something has always been done, when existing solutions feel expensive or inefficient for no good reason, when the user asks to think from first principles, challenge the fundamentals, or rebuild this from scratch. Also triggers on "why does it have to work this way", "what are the actual constraints here", "ignore what everyone else does", or when deep-thinking diagnoses a convention-break frame. Based on Aristotle's first principles method, popularised by Musk and Feynman. Produces genuinely novel solutions by eliminating convention.

Review C#/.NET code for design pattern implementation and suggest improvements without making changes.

Provides guidelines and best practices for aggregates and aggregate roots, referencing detailed documentation.

Guides module boundaries, dependency direction, and domain structure. Do not use for local edits that leave architecture unchanged.

Define a set of actionable design principles that guide decision-making and resolve trade-offs.

Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

Comprehensive guide to ssd. Master the concepts, implementation, best practices, and real-world applications of ssd in professional environments.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract to build systems that are easy to change, understand, and trust.

Three shapes get argued about as if one were correct.

Guides systematic root-cause investigation before proposing fixes for any technical issue, with a four-phase process and red flags to avoid guessing.

Apply animation principles to UI motion for purposeful, polished interactions.

PC and console game development principles. Engine selection, platform features, optimization strategies.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks

2D game development principles. Sprites, tilemaps, physics, camera.

2D game development principles. Sprites, tilemaps, physics, camera.

Provides principles for 2D game development, covering sprite organization, tilemap design, physics, camera systems, and genre-specific patterns.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Find root causes of bugs, test failures, or unexpected behavior before proposing any fixes.

Consolidates 89 high-integrity SOPs for the Full department of the Galyarder Framework, covering adapter creation, execution protocols, and multi-agent hygiene.

Designs bounded contexts, creates domain models, uses aggregates, and implements value objects for complex domain logic.

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Implements and applies algorithms concepts, designs solutions using algorithmic principles, and optimizes performance for algorithm implementations.

Guides engine selection and platform-specific principles for PC and console game development, covering Steam integration, controller support, and performance optimization.

Structure software around the Dependency Rule so that source code dependencies point inward from frameworks to use cases to entities, keeping business rules independent of databases, UI, and external agencies.