principle-encode-lessons-in-structure

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

2|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/imjasonh/playground --skill principle-encode-lessons-in-structure-imjasonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-encode-lessons-in-structure
Source: https://github.com/imjasonh/playground/tree/main/.cursor/skills/principle-encode-lessons-in-structure
Command: npx skills add https://github.com/imjasonh/playground --skill principle-encode-lessons-in-structure-imjasonh

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 repeated instructions with structural mechanisms that enforce rules automatically. ## Core Features & Use Cases - Mechanism Selection: Guides you to encode a recurring fix as a lint rule, metadata flag, runtime check, or automation script, choosing the strongest mechanism available. - Feedback Loop: Provides a capture-route-close workflow for every human correction or test failure, routing one-offs to notes, recurring fixes to skills or lints, and systemic issues to principles. - Anti-Pattern Detection: Flags common failures such as acknowledging without recording, recording without routing, and fixing one instance without generalizing. - Use Case: When you catch yourself telling an AI agent the same correction a second time, use this Skill to turn that correction into a CI lint rule and delete the instruction. ## Quick Start Apply this skill whenever you notice yourself repeating the same instruction or correction, and encode it as a lint rule, metadata flag, runtime 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 an AI agent?▼

Encode the instruction as a structural mechanism instead of text. Ask whether the rule can become a lint rule, metadata flag, runtime check, or script, then implement that mechanism and delete the instruction.

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

Pick the strongest mechanism the situation allows: first an unrepresentable state that cannot compile, then a lint or banned API that fails CI, then a canonical helper, then a runtime check. Stronger guards prevent agents from copying weak patterns.

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

Route based on recurrence. One-off corrections go to a brain note, recurring fixes become skills or lint rules, and systemic issues become principles. The key is deciding whether the correction is a pattern or an isolated case.

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 recording lessons from corrections?▼

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