principles

Enforces always-loaded coding principles for surgical changes, testing, and commit discipline.

3|Updated May 2, 2026
One-click install
npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill principles-juantrujillodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principles
Source: https://github.com/JuanTrujilloDev/agent-config-template/tree/main/plugin/skills/principles
Command: npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill principles-juantrujillodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coding agents often over-engineer solutions, refactor unrelated code, or declare tasks done without verification. This Skill provides a non-negotiable set of operating principles that govern every coding task, preventing scope creep, premature abstraction, and unverified completions. ## Core Features & Use Cases - Simplicity and Surgical Changes: Enforces YAGNI via a leverage ladder (reuse codebase code, standard library, platform features, existing dependencies before writing new code) and forbids touching code outside the task scope. - Goal-Driven Execution and Definition of Done: Requires verifiable success criteria per task and a strict completion checklist covering format, lint, tests with coverage, judge review, security review, and live browser verification. - Branch and Commit Discipline: Mandates typed branches (feature/, fix/, hotfix/, refactor/, chore/, docs/), conventional commits, and micro-PRs under 12 files and 3000 lines. - Use Case: When starting any non-trivial coding task, the agent restates the goal, lists success criteria, reads target files before editing, and loops through verification until all Definition of Done checks pass. ## Quick Start Ask the agent to implement a small feature and require it to follow the core operating principles including branch discipline and the Definition of Done checklist.

Frequently Asked Questions about principles

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

FAQPage Schema
How do I enforce coding principles on an AI coding agent?▼

Load an always-on principles document that the agent must follow for every task. This Skill defines rules like Think Before Coding, Simplicity First, and Surgical Changes, and requires the agent to surface conflicts rather than silently override them.

What is a Definition of Done checklist for coding tasks?▼

A Definition of Done is an ordered checklist a task must pass before completion: format, lint with zero new warnings, green unit tests with coverage maintained, a judge code review, security review for sensitive changes, and live browser verification for frontend work.

How do I keep pull requests small and reviewable?▼

Apply micro-PR discipline: every PR stays under 12 changed files and 3000 changed lines. Larger features are broken into sequential mini-features by a PMO agent, each shipped as its own PR with one logical conventional commit per green point.

When should an agent avoid adding abstractions or design patterns?▼

Avoid abstractions without a present force such as a real second caller or variation. Single-implementation Strategy, speculative Repository, and unnecessary Factory patterns are rejected by default, and the rule of three governs extraction of duplicated code.

Can the agent skip the code walkthrough before editing?▼

The human can say "just go" to skip the narration for low-risk changes, and trivial edits under 50 lines need no reporting. However, reading the target file and its callers before editing is never skipped.