Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review [feature] using its actual input, storage, rendering, and external-service paths. Identify trust boundaries and define the allowed policy for anonymous callers, owners, and other users. Inspect server-side validation, resource authorization, database parameterization, and context-appropriate output handling. Use harmless fixtures in the authorized test environment to check direct requests, unexpected fields, oversized values, and unauthorized record IDs. Apply focused corrections using established framework controls. Report concrete findings, affected code, verification results, and unresolved evidence needs.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- OWASP — Authorization design and testing
- OWASP — Logging, sensitive data, and sanitization
- OWASP — Threat modeling and trust boundaries
Documentation links checked .
Editorial review · October 28, 2026
Limited: Original instructional template; not executed. Trust-boundary prompt is scoped to an authorized test environment and requests evidence; no security test or audit was executed.