principle-encode-lessons-in-structure

Converts recurring corrections into lint rules, metadata flags, runtime checks, or scripts.

136|8|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/rove --skill principle-encode-lessons-in-structure-sma1lboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-encode-lessons-in-structure
Source: https://github.com/Sma1lboy/rove/tree/main/.agents/skills/pstack/skills/principle-encode-lessons-in-structure
Command: npx skills add https://github.com/Sma1lboy/rove --skill principle-encode-lessons-in-structure-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeatedly writing the same textual instruction wastes effort and fails because readers must notice, remember, and comply. This Skill replaces recurring instructions with structural mechanisms that enforce the rule automatically. ## Core Features & Use Cases - Structural Encoding: Turns repeated corrections into lint rules, metadata flags, runtime checks, or automation scripts instead of more documentation. - Strongest-Rung Selection: Chooses the strongest available mechanism, from unrepresentable states that fail compilation down to canonical helpers and runtime checks. - Feedback Loop Discipline: Captures every correction, routes it to the right layer (brain note, skill, lint rule, or principle), and closes the loop with concrete action. - Use Case: When you catch yourself telling an agent a second time to never edit generated files, encode it as a CI lint rule that fails on edits to those paths and delete the instruction. ## Quick Start Ask the agent to apply the encode-lessons-in-structure principle whenever it notices a repeated instruction or recurring correction during the session.

Frequently Asked Questions about principle-encode-lessons-in-structure

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

FAQPage Schema
How do I stop repeating the same instruction to a coding agent?▼

Encode the rule as a lint rule, metadata flag, runtime check, or script instead of writing it again. Structural mechanisms enforce the rule without requiring the reader to notice, remember, and comply.

What is the best way to enforce coding rules automatically?▼

Pick the strongest mechanism the situation allows: an unrepresentable state that cannot compile, then a lint rule or banned API that fails CI, then a canonical helper, then a runtime check. Weaker guards become templates agents copy.

When should a correction become a lint rule versus a note?▼

Route one-off issues to a brain note, recurring fixes to a skill or lint rule, and systemic issues to a principle. The key test is whether the correction is a one-off or a repeating pattern.

Why do textual instructions fail compared to structural checks?▼

Textual instructions require the reader to notice, remember, and comply, so they are easy to miss. Structural mechanisms like lint rules and runtime checks enforce the rule without cooperation from the reader.

What are common mistakes when encoding lessons in structure?▼

Common anti-patterns include acknowledging a correction without recording it, recording without routing it to implementation, and fixing one instance while leaving the recurring pattern intact. Each breaks the feedback loop.