Engrm Sentinel

Use this skill when code is entering a risky area and the goal is to prevent mistakes, not just remember past work.

What this skill is for

• Surface risky patterns before they become bugs or security issues.
• Reuse pack knowledge and standards during active coding work.
• Explain what is going wrong, not just that something looks unusual.
• Keep prevention practical and grounded in project context.

When to use it

Use this skill when the task involves:

• authentication or secrets
• input handling or API boundaries
• security-sensitive data
• major refactors
• deployment or config changes
• code that has caused repeated issues before

Sentinel mindset

Ask:

• What could go wrong here?
• Which pack lessons are relevant?
• Is this repeating a known mistake?
• Is the implementation drifting into a risky shortcut?
• Would a future session benefit from a new standard or lesson here?

Good outputs

Helpful Sentinel guidance should:

• name the likely mistake clearly
• explain why it matters
• connect it to a reusable lesson or pack
• suggest the safer path

Avoid:

• generic fearmongering
• abstract policy language without code relevance
• blocking everything just because it feels risky

Remember: packs are free, but the deeper review and prevention built on top of them is where Engrm earns its keep.