engineering-principles

Scan repository files to detect languages, frameworks, and ORMs, then output a prioritized Markdown checklist of engineering DOs and DON'Ts.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/YuluoY/nimis --skill engineering-principles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-principles
Source: https://github.com/YuluoY/nimis/tree/main/skills-en/engineering-principles
Command: npx skills add https://github.com/YuluoY/nimis --skill engineering-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Engineering Principles Matcher reduces inconsistent engineering decisions by scanning a project's context and producing a concise, actionable checklist of development principles and constraints that are actually applicable to the codebase and task at hand.

Core Features & Use Cases

  • Context-aware Matching: Detects language, framework, test tooling, layering, ORM/DB signals, and project scale to determine which principles apply.
  • Principle Filtering: Selects and ranks principles (Clean Code, SOLID, DDD, TDD, BDD, design patterns, anti-patterns, performance, security, testability) and skips inapplicable ones for legacy or small projects.
  • Actionable Outputs: Emits a Markdown checklist and brief embedded coding constraints for use in specs or automated workflows; useful during planning, coding, refactoring, and code review.
  • Safe, Passive Invocation: Intended for on-demand use; does not auto-trigger disruptive changes.

Quick Start

Use the engineering-principles skill to scan your repository root and write an applicable principles checklist to specs/engineering-principles.md.

Frequently Asked Questions about engineering-principles

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

FAQPage Schema
How do I generate an engineering principles checklist for my codebase?

The tool scans repository files to detect language, test frameworks, layered structure, ORMs, and E2E tools. It then matches applicable engineering principles to your project context, generating a Markdown checklist and concise embedded constraints for planning, coding, refactoring, and code review.

What engineering principles does the matcher filter for during code review?

The matcher selects and ranks principles including Clean Code, SOLID, DDD, TDD, BDD, design patterns, anti-patterns, performance, security, and testability. It skips inapplicable principles, tailoring the output specifically for legacy or small project scale.

Can I use this to apply TDD and DDD constraints to an existing project?

Yes, it scans your existing codebase to detect project scale and test tooling, then applies TDD and DDD principles if relevant. It outputs concise embedded coding constraints useful for refactoring legacy code and improving code quality safely.

Does the engineering principles matcher auto-trigger disruptive codebase changes?

No, the matcher is intended for safe, passive, on-demand invocation. It does not auto-trigger disruptive changes, but rather produces an actionable Markdown checklist for developers to use during planning and coding.

When should I not use automated principle matching for software architecture?

Avoid relying on automated principle matching when your project lacks a clear layered structure or recognizable ORM and E2E tooling signals. The tool skips inapplicable principles, but may yield limited value for projects it cannot accurately scan.

What's the best way to integrate matched engineering principles into my workflow?

Write the output Markdown checklist to specs/engineering-principles.md. You can then use these concise embedded constraints in your automated workflows, planning, and code review processes.