principle-encode-lessons-in-structure

Convert recurring corrections into lint rules, metadata flags, runtime checks, and automation scripts.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/squidllee/skills --skill principle-encode-lessons-in-structure-squidllee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-encode-lessons-in-structure
Source: https://github.com/squidllee/skills/tree/main/principle-encode-lessons-in-structure
Command: npx skills add https://github.com/squidllee/skills --skill principle-encode-lessons-in-structure-squidllee

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: Turn repeated corrections into lint rules, metadata flags, runtime checks, or scripts instead of more documentation. - Strongest-Rung Selection: Choose the strongest available mechanism, from unrepresentable states that fail compilation down to runtime checks. - Feedback Loop: Capture every correction, route it to the right layer (note, skill, lint rule, or principle), and close the loop with concrete action. - Use Case: You catch yourself telling a code generator a second time to avoid a deprecated API. Instead of repeating the instruction, you add a lint rule that fails CI when the API appears. ## Quick Start Apply this principle whenever you notice yourself writing the same instruction twice, and encode it as a lint rule, check, or script instead.

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 code generator?▼

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

What is the best way to enforce coding rules in a project?▼

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 that get copied.

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

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

Why do textual coding instructions keep getting ignored?▼

Textual instructions require the reader to notice, remember, and comply, which fails under attention limits. Structural mechanisms like CI-failing lints enforce the rule without cooperation, so they cannot be silently skipped.

What are common mistakes when recording lessons from corrections?▼

Three anti-patterns: acknowledging without recording, recording without routing to implementation, and fixing one instance without generalizing the pattern. Each leaves the recurring problem intact.