skills.rest
magnus919
magnus919COMMUNITY
Explore all skills by this author →
WebsiteGitHub

programming-principles

Distills classic software engineering literature into actionable rule sets for code review and architectural assessment.

40|6|Updated Jul 11, 2026
Search Tags:#code review#refactoring#clean code#domain-driven design#technical debt#software architecture
One-click install
npx skills add https://github.com/magnus919/agent-skills --skill programming-principles-magnus919
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: programming-principles
Source: https://github.com/magnus919/agent-skills/tree/main/programming-principles
Command: npx skills add https://github.com/magnus919/agent-skills --skill programming-principles-magnus919

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of ad-hoc, inconsistent code quality by providing a shared, literature-backed vocabulary for software engineering decisions. It prevents "vibes-based" development by grounding code reviews, refactoring, and architectural choices in established industry wisdom.

Core Features & Use Cases

  • Task-Aware Guidance: Maps specific coding tasks (e.g., refactoring, architecture, domain modeling) to the most relevant classic software engineering books.
  • Progressive Depth: Offers compressed rule cards for daily guidance and full catalogs for deep audits or complex architectural reviews.
  • Structured Assessment: Provides a reproducible workflow for auditing repositories against 14 classic books to identify structural friction and technical debt.

Quick Start

Load the programming-principles skill and apply the Clean Code rule set to the current repository for a principled code review.

Frequently Asked Questions about programming-principles

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

FAQPage Schema
How do I perform a principled code review based on clean code standards?▼

To perform a principled code review, apply the Clean Code rule set distilled from classic software engineering books to your current repository. This provides a shared, literature-backed vocabulary for evaluating code quality and preventing inconsistent, ad-hoc feedback.

What is the best way to audit a codebase for technical debt and architectural friction?▼

The best way to audit a codebase for technical debt is using a structured assessment workflow that evaluates your repository against principles from 14 classic software engineering books. This reproducible process identifies structural friction across diverse codebases.

Can I get domain-driven design guidance for refactoring complex codebases?▼

Yes, you can get domain-driven design guidance for refactoring by mapping specific coding tasks to the most relevant classic software engineering books. This provides task-aware rule sets for dependency management and domain modeling.

Does this approach support both quick daily guidance and deep architectural reviews?▼

This approach supports both quick daily guidance and deep architectural reviews through progressive depth. It offers compressed rule cards for daily code review tasks and full catalogs for comprehensive repository audits and complex architectural assessments.

How do I combine multiple software architecture rule sets for a comprehensive repository audit?▼

To combine multiple software architecture rule sets for a repository audit, use the provided structured workflows. These workflows merge literature-based rule sets from 14 classic books to perform comprehensive architectural assessments and identify technical debt.

Why should I use literature-backed principles instead of ad-hoc standards for software engineering decisions?▼

You should use literature-backed principles to prevent vibes-based development and inconsistent code quality. Grounding code reviews, refactoring, and software architecture choices in established industry wisdom ensures a shared vocabulary for technical decisions.

Related Skills

Explore More Software Engineering Skills→
erguotou520erguotou520

get-qodo-rules

Fetch repository-specific coding rules via the Qodo API before code changes.

Community
Advanced
sjmyuansjmyuan
7

refactor-planner

Generate step-by-step TDD-based refactoring plans for code cleanup and architecture improvements.

Community
Intermediate
dsivovdsivov

clean-code-practices

Enforce KISS, DRY, and YAGNI standards during software development tasks.

Community
Intermediate
WolframResearchWolframResearch
82

add-code-inspector-rule

Create a custom CodeInspector rule to detect problematic Wolfram Language patterns.

Official
Intermediate