How do I install the Ps Principle Encode Lessons In Structure skill?

Run npx skillmds@latest add gannonh/ps-principle-encode-lessons-in-structure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ps Principle Encode Lessons In Structure safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ps Principle Encode Lessons In Structure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ps Principle Encode Lessons In Structure free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Ps Principle Encode Lessons In Structure?

gannonh (@gannonh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ps Principle Encode Lessons In Structure by gannonh

Name: Ps Principle Encode Lessons In Structure
Author: gannonh

Ps Principle Encode Lessons In Structure

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

gannonh d721aec 4 files · 3.8 KB Updated Sep 17, 2026

File contents

Encode Lessons in Structure

Encode recurring fixes in mechanisms (tools, code, metadata, automation) instead of textual instructions. Every error, human correction, and unexpected outcome is a learning signal. Capture it, route it, and close the loop.

Why: Textual instructions are easy to miss. They require the reader to notice, remember, and comply. Structural mechanisms (lint rules, metadata flags, runtime checks, automation scripts) enforce the rule without cooperation.

Pattern: When you catch yourself writing the same instruction a second time:

Ask: can this be a lint rule, a metadata flag, a runtime check, or a script?
If yes, encode it. Delete the instruction
If no (genuinely requires judgment), make the instruction more prominent and add an example of the failure mode

Pick the strongest rung. When more than one mechanism would work, choose the strongest the situation allows (an unrepresentable state that cannot compile, then a lint or banned API that fails CI, then a canonical helper, then a runtime check), because agents copy whatever the surrounding code already does and a weaker guard becomes the next template.

Corollary: Don't paper over symptoms. If the fix is structural, ONLY use the structural fix. The instruction IS the symptom.

Feedback loop:

Capture every correction. When the human intervenes or tests fail, decide if it's a one-off or a pattern.
Route to the right layer. One-off -> brain note. Recurring fix -> skill or lint rule. Systemic issue -> principle.
Close the loop. Don't just record. Apply now or create a concrete todo.

Anti-patterns:

Acknowledging without recording ("I'll keep that in mind" does not persist)
Recording without routing (a brain note about a lint rule that should exist is wasted unless the lint rule gets implemented)
Fixing without generalizing (fixing one instance while leaving the recurring pattern intact)

---name: ps-principle-encode-lessons-in-structuredescription: Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.license: MIT. See LICENSE.txt---# Encode Lessons in StructureEncode recurring fixes in mechanisms (tools, code, metadata, automation) instead of textual instructions. Every error, human correction, and unexpected outcome is a learning signal. Capture it, route it, and close the loop.**Why:** Textual instructions are easy to miss. They require the reader to notice, remember, and comply. Structural mechanisms (lint rules, metadata flags, runtime checks, automation scripts) enforce the rule without cooperation.**Pattern:**When you catch yourself writing the same instruction a second time:1. Ask: can this be a lint rule, a metadata flag, a runtime check, or a script?2. If yes, encode it. Delete the instruction3. If no (genuinely requires judgment), make the instruction more prominent and add an example of the failure mode**Pick the strongest rung.** When more than one mechanism would work, choose the strongest the situation allows (an unrepresentable state that cannot compile, then a lint or banned API that fails CI, then a canonical helper, then a runtime check), because agents copy whatever the surrounding code already does and a weaker guard becomes the next template.**Corollary:** Don't paper over symptoms. If the fix is structural, ONLY use the structural fix. The instruction IS the symptom.**Feedback loop:**- **Capture every correction.** When the human intervenes or tests fail, decide if it's a one-off or a pattern.- **Route to the right layer.** One-off -> brain note. Recurring fix -> skill or lint rule. Systemic issue -> principle.- **Close the loop.** Don't just record. Apply now or create a concrete todo.**Anti-patterns:**- Acknowledging without recording ("I'll keep that in mind" does not persist)- Recording without routing (a brain note about a lint rule that should exist is wasted unless the lint rule gets implemented)- Fixing without generalizing (fixing one instance while leaving the recurring pattern intact)

Frequently asked questions