never

Store never-do rules with NEVER, BECAUSE, and INSTEAD structures.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Nerfherder16/BrickLayer --skill never
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: never
Source: https://github.com/Nerfherder16/BrickLayer/tree/main/.claude/skills/never
Command: npx skills add https://github.com/Nerfherder16/BrickLayer --skill never

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores an anti-pattern that records a standing never-do rule to prevent specific actions in Claude workflows and interactions.

Core Features & Use Cases

  • Forward-looking prohibition: define NEVER with BECAUSE and INSTEAD to guide responses.
  • Persistent guardrails: stores prohibitions for consistent enforcement across sessions.
  • Structured template: provides a clear format for capturing, storing, and recalling rules.

Quick Start

Add a never rule specifying the forbidden action, the reason, and the recommended alternative so Claude permanently avoids the action.

Frequently Asked Questions about never

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up persistent guardrails to prevent unsafe AI actions across sessions?

Persistent guardrails prevent unsafe AI actions by storing explicit never-do rules as anti-patterns. You define a forbidden action, the reason, and an alternative to ensure consistent enforcement across Claude Code sessions.

What is an anti-pattern for enforcing AI prohibitions and when do I need it?

An anti-pattern for enforcing AI prohibitions is a structured never-do rule that prevents specific actions like revealing secrets. You need it when forward-looking guardrails must permanently guide responses and stop unsafe behaviors.

How do I format a never-do rule to block specific actions in Claude workflows?

Format a never-do rule using the NEVER, BECAUSE, INSTEAD structure. Specify the forbidden action, explain the reason, and provide a recommended alternative so Claude permanently avoids the action.

Can I apply standing prohibition rules to ensure AI safety across different sessions?

Yes, standing prohibition rules apply across Claude Code sessions by persisting anti-patterns. These stored prohibitions are consulted before decisions to capture guardrails that should never be triggered.

Does enforcing absolute prohibitions require any specific dependencies or components?

Enforcing absolute prohibitions requires no specific dependencies or components. It relies on a structured template to capture, store, and recall rules, ensuring forward-looking guardrails guide AI behavior.

Why use structured prohibition templates instead of standard policy instructions for AI safety?

Structured prohibition templates provide explicit NEVER, BECAUSE, INSTEAD formatting to guide responses, unlike standard instructions. This ensures persistent guardrails are consistently consulted before decisions to prevent prohibited actions.