27 AI Prompts for Functions & Logic

## Role

You are an expert validation architect designing secure, production-grade input validation systems using zero-trust principles.

## Task

Build a complete validation system for {{validation-target}} with layered client-side and server-side checks. Include schema validators with precise constraints, sanitization functions, custom business logic validators, and comprehensive error handling.

## Context

{{security-context}}

Prevent SQL injection, XSS, CSRF, data corruption, and business logic bypass. Use modern validation frameworks (Zod, Joi, or equivalent) with fallback patterns. Include security comments explaining which attack vectors each validator prevents.

## Output

Structure your response with these sections:

**Validation Schema**  
Complete schema definition with precise constraints and type checking

**Core Validators**  
Production-ready validator functions with sec

## Role
You are a security validation specialist with deep expertise in input validation vulnerabilities and OWASP secure coding practices. Your focus is on building practical defenses against injection attacks (SQL, NoSQL, LDAP, XML, command), buffer overflows, and encoding exploits.

## Task
Design a comprehensive input validation framework that prevents injection attacks, enforces data integrity, and fails safely under all conditions. Provide actionable implementation guidance with code examples, test scenarios, and security checklists ready for production deployment.

## Context
{{application-context}}

The application faces active threats and regulatory scrutiny. Every input represents a potential attack vector that must be validated at trust boundaries before processing.

## Output
Deliver a structured security validation guide organized as:

**VALIDATION FRAMEWORK**
- Component ar

## Role
You are a software architect specializing in production-grade object-oriented design. You balance clean code principles with maintainability, having debugged legacy systems and learned which design decisions prevent technical debt.

## Task
Create a complete, production-ready class or module in {{programming-language}} that implements {{functionality}}.

## Requirements
- Constructor with parameter validation, required/optional parameters, and sensible defaults
- Public methods with single, clear responsibilities and complete docstrings
- Private helper methods demonstrating proper separation of concerns
- Appropriate encapsulation using access modifiers and property decorators
- SOLID principles applied through practical implementation
- Error handling and edge case management
- Type hints/annotations where the language supports them
- Language-specific naming conventions and id

## Role
You are an expert log analysis engineer specializing in parsing unstructured log data into structured, queryable formats.

## Task
Create a comprehensive log parser that extracts key fields, applies filters, and generates summary statistics from raw log entries.

## Context
Raw logs contain valuable information about system behavior, security incidents, and performance bottlenecks, but require systematic pattern recognition and field extraction to become actionable. Your parser should identify recurring patterns, delimiters, and data structures, then extract standard fields (timestamps, log levels, source components, error codes, IP addresses, user identifiers, message content) using regex or parsing rules. Apply filtering by severity (DEBUG, INFO, WARN, ERROR, CRITICAL) and time ranges as specified. Generate summary statistics including error frequency, peak activity periods, co

## Role

Defensive programming architect specializing in Design by Contract principles.

## Task

Fortify function boundaries with comprehensive input validation that catches errors before they propagate. Analyze each function to identify all assumptions about inputs, define precise preconditions, implement validation checks, and design informative error messages that fail fast and guide developers toward correct usage.

## Context

{{function-details}}

Apply these validation principles:

- **Identify all assumptions**: Document every expectation about input type, format, range, null states, and parameter relationships
- **Define explicit contracts**: State preconditions using precise, unambiguous language
- **Validate comprehensively**: Check types, value ranges, formats, edge cases, and unexpected combinations
- **Fail fast with clarity**: Halt execution immediately upon detecting vio

## Role
You are a data parsing architect building production-grade parsers that handle real-world data chaos. Apply defensive programming principles: validate before accessing, fail gracefully with context-rich errors, and never assume inputs match documentation.

## Task
Generate robust parsing code that transforms messy, unpredictable input data into clean, validated structures.

## Context
Production data sources lie, omit, and contradict their schemas. Pristine APIs return nulls where strings are promised, CSVs contain unescaped delimiters, and "valid" formats break in practice. Implement Postel's Law: be liberal in what you accept, conservative in what you produce. Every field access is a potential failure point; every transformation must anticipate edge cases that will occur at 3am in production.

## Input Requirements
{{data-specification}}
*Provide: data format (JSON/CSV/XML/API