principle-encode-lessons-in-structure
Apply when you write the same instruction a second time or notice a recurring correction.
Skill by hellsan631
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/hellsan631-principle-encode-lessons-in-structure
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/principle-encode-lessons-in-structure
What's inside
- Skill name
principle-encode-lessons-in-structure- Description
- Apply when you write the same instruction a second time or notice a recurring correction. Replace repeated text with a lint, metadata flag, runtime check, or script.
- License
- MIT
- Instructions
- 38 lines in SKILL.md · view on GitHub
Files (2)
- SKILL.md
- openai.yaml · agents/
SKILL.md (first lines)
# Encode lessons in structure Enforce recurring fixes with tools, code, metadata, or automation. Treat every error, human correction, and unexpected outcome as a lesson: record it, decide where it belongs, and act on it. Textual instructions depend on the reader noticing, remembering, and following them. Lint rules, metadata flags, runtime checks, and automation scripts enforce the rule without that cooperation. ## Pattern When you catch yourself writing the same instruction a second time: 1. Ask whether a lint rule, metadata flag, runtime check, or script can enforce it. 2. If one can, implement that mechanism and delete the instruction. 3. If the rule genuinely requires judgment, keep the instruction, make it more prominent, and add an example of the failure mode. ## Choose the mechanism When several mechanisms would work, choose the strongest one the situation allows, in this order: 1. Make the invalid state unrepresentable so it cannot compile. 2. Add a lint or banned API that fails CI. 3. Provide a canonical helper. 4. Add a runtime check. Agents copy what the surrounding code already does, so a weaker guard becomes the next template. When a fix is structural, make only the structural fix and delete the textual instruction that exposed the symptom. ## Handle feedback - When a human intervenes or a test fails, decide whether the correction is a one-off or a pattern. - Put a one-off in a brain note, a recurring fix in a skill or lint rule, and a systemic issue in a principle. - Apply the lesson now or create a concrete todo. Recording it alone does not close the loop. ## Failure modes - Saying "I'll keep that in mind" without recording the correction does not persist. - A brain note cannot enforce a lint rule. Implement the lint rule in the right layer. - Fixing one instance while leaving the recurring pattern intact does not generalize the fix.
From hellsan631/skills, MIT.
More from hellsan631/skills
- 0.570score
game-visual-identity
hellsan631
Develops a recognizable visual identity for video game characters, icons, items, and related art.
SkillAFreshness: AClaude Code +9 - 0.570score
midjourney-prompting
hellsan631
Use when the user requests Midjourney prompts, reference and model setup, guided image generation, or revisions based on generated results.
SkillAFreshness: AClaude Code +9 - 0.570score
game-ui-design
hellsan631
Use when designing or redesigning game HUDs, menus, inventories, character screens, maps, progression screens, or results screens; when creating their…
SkillAFreshness: AClaude Code +9 - 0.539score
visual-identity-grilling
hellsan631
Use when the user wants to quickly iterate on game visual identity through challenging questions and rendered comparisons, or asks to combine grilling with…
SkillAFreshness: AClaude Code +9 - 0.529score
why
hellsan631
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.
SkillBFreshness: BClaude Code +9 - 0.524score
prototype
hellsan631
Use when you need to sanity-check a state model or interaction before building it, or when you need to decide what a UI should look like.
SkillBFreshness: BClaude Code +9 - 0.524score
codebase-design
hellsan631
Use when designing or improving a module's interface, when deciding where a seam goes, when code needs to be more testable or navigable, or when another skill…
SkillBFreshness: BClaude Code +9 - 0.524score
domain-modeling
hellsan631
Use when codebase terminology is in dispute, when writing or editing a CONTEXT.md, or when recording an ADR.
SkillBFreshness: BClaude Code +9 - 0.524score
improve-codebase-architecture
hellsan631
Use when a codebase has architectural friction and the user wants refactoring options.
SkillBFreshness: BClaude Code +9 - 0.524score
wizard
hellsan631
Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or…
SkillBFreshness: BClaude Code +9 - 0.524score
principal-game-designer
hellsan631
Use when drafting a game system's design, revising one, critiquing a design document, or checking whether a spec is buildable.
SkillBFreshness: BClaude Code +9 - 0.521score
principle-build-the-lever
hellsan631
Apply to any non-trivial work, whether one-off or bulk, including edits, migrations, analyses, and checks.
SkillBFreshness: BClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Aug 29, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/hellsan631/skills
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from hellsan631
- 0.570score
game-ui-design
hellsan631
Use when designing or redesigning game HUDs, menus, inventories, character screens, maps, progression screens, or results screens; when creating their…
SkillAFreshness: AClaude Code +9 - 0.570score
midjourney-prompting
hellsan631
Use when the user requests Midjourney prompts, reference and model setup, guided image generation, or revisions based on generated results.
SkillAFreshness: AClaude Code +9 - 0.570score
game-visual-identity
hellsan631
Develops a recognizable visual identity for video game characters, icons, items, and related art.
SkillAFreshness: AClaude Code +9 - 0.539score
visual-identity-grilling
hellsan631
Use when the user wants to quickly iterate on game visual identity through challenging questions and rendered comparisons, or asks to combine grilling with…
SkillAFreshness: AClaude Code +9 - 0.529score
why
hellsan631
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.
SkillBFreshness: BClaude Code +9 - 0.524score
codebase-design
hellsan631
Use when designing or improving a module's interface, when deciding where a seam goes, when code needs to be more testable or navigable, or when another skill…
SkillBFreshness: BClaude Code +9
Cite this page
principle-encode-lessons-in-structure skill. Agent Mart. https://agentmart.dev/skills/hellsan631-principle-encode-lessons-in-structure (last updated 2026-10-24)