nw-production-safety
Agent safety boundaries - input validation, output filtering, scope constraints, and document creation policy
Best use case
nw-production-safety is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Agent safety boundaries - input validation, output filtering, scope constraints, and document creation policy
Teams using nw-production-safety should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/nw-production-safety/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How nw-production-safety Compares
| Feature / Agent | nw-production-safety | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Agent safety boundaries - input validation, output filtering, scope constraints, and document creation policy
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
SKILL.md Source
# Production Safety
## Input Validation (4 Layers)
Apply in sequence before processing any input.
1. **Schema validation**: validate structure, data types, ranges against expected schema
2. **Content sanitization**: remove dangerous patterns (SQL injection, command injection, path traversal)
3. **Contextual validation**: check business logic constraints and expected formats
4. **Security scanning**: detect injection and prompt injection attempts
## Output Filtering
- No secrets in output (passwords, API keys, credentials) | No sensitive information leakage (SSN, credit cards, PII)
- No off-topic responses outside software-crafter scope | Block dangerous code suggestions (rm -rf, DROP TABLE)
## Scope Boundaries
```yaml
allowed_operations: [Code implementation, Test creation, Refactoring, Build execution]
forbidden_operations: [Credential access, Data deletion, Production deployment]
forbidden_file_patterns: ["*.env", "credentials.*", "*.key", ".ssh/*"]
document_creation_policy:
allowed_without_permission:
- "Production code files (src/**/*)"
- "Test files (tests/**/*)"
- "Required handoff artifacts only"
requires_explicit_permission:
- "Summary reports"
- "Analysis documents"
- "Migration guides"
```
## Production Readiness Checklist
Before declaring production-ready, verify:
- [ ] Input/Output contract defined (see hexagonal-testing skill)
- [ ] Safety framework active (4 validation layers above)
- [ ] Test coverage meets thresholds
- [ ] All quality gates passing (see quality-framework skill)
- [ ] Edge cases tested (null, empty, malformed, boundary)
- [ ] No silent error handling (all errors logged/alerted)Related Skills
nw-production-readiness
Monitoring, observability, operational procedures, CI/CD lessons learned, and quality gate definitions. Load when assessing production readiness or validating operational excellence.
nw-operational-safety
Tool safety protocols, adversarial output validation, error recovery patterns, and I/O contracts for research operations
nw-ux-web-patterns
Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.
nw-ux-tui-patterns
Terminal UI and CLI design patterns for product owners. Load when designing command-line tools, interactive terminal applications, or writing CLI-specific acceptance criteria.
nw-ux-principles
Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.
nw-ux-emotional-design
Emotional design and delight patterns for product owners. Load when designing onboarding flows, empty states, first-run experiences, or evaluating the emotional quality of an interface.
nw-ux-desktop-patterns
Desktop application UI patterns for product owners. Load when designing native or cross-platform desktop applications, writing desktop-specific acceptance criteria, or evaluating panel layouts and keyboard workflows.
nw-user-story-mapping
User story mapping for backlog management and outcome-based prioritization. Load during Phase 2.5 (User Story Mapping) to produce story-map.md and prioritization.md.
nw-tr-review-criteria
Review dimensions and scoring for root cause analysis quality assessment
nw-tlaplus-verification
TLA+ formal verification for design correctness and PBT pipeline integration
nw-test-refactoring-catalog
Detailed refactoring mechanics with step-by-step procedures, and test code smell catalog with detection patterns and before/after examples
nw-test-organization-conventions
Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.