Skip to main content
PromptVerse

Explore Prompts

Browse and search thousands of community-verified AI prompts

Query: 3.20 ms 3 prompts found
Discovery Velocity
Discovery Engine & Open Prompt Directory

Search, filter, and inspect verified AI prompts across system categories, tags, and creator showcases.

What is this?

The Explore Prompts directory is the public search engine of PromptVerse. It indexes all community-contributed public prompts across system categories (Coding, Copywriting, Marketing, Data Analysis, and Creative Writing) with full-text search and tag clouds.

Cards feature 1-click copy buttons, creator links, and engagement counters.

Why does it exist?

Finding high-performing prompts shouldn’t require scouring disorganized Twitter threads or forum posts. A dedicated discovery index allows developers, marketers, and researchers to locate battle-tested prompts tuned for ChatGPT, Claude, and Gemini in seconds.

It connects practitioners with proven prompt patterns.

How is it beneficial?
  • Instant Copy to Clipboard: Copy complete prompt instructions directly into your active LLM session.
  • Deep Taxonomy Filtering: Drill down by category, tag keywords, or sort by Most Copied or Latest.
  • Sub-Millisecond Speed: Backed by indexed query optimization and optional Redis caching.
Pro Tip: Sort by "Most Copied" to immediately find the community’s highest-rated prompts for any workflow.
DevOps, Cloud & Cyber Security ⭐ 4.7 (52)
Secrets Management & Dynamic Credential Rotation (HashiCorp Vault)

Eliminates hardcoded credentials using HashiCorp Vault, AWS Secrets Manager, and dynamic short-lived database access tokens.

By admin
1999 622
# System Role: Staff Security Automation Engineer & Secrets Management Specialist ## Objective: Eliminate static API keys and hardcoded passwords by implementing a centralized dynamic secrets management architecture using HashiCorp Vault or AWS Secrets Manager. ## Environment Context: - Target Platform: {{platform_environment}} (Kubernetes, AWS ECS, Linux VMs) - Database / Downstream Systems: {{downstream_targets}} (PostgreSQL, Redis, Third-Party Payment APIs) ## Secrets Architecture: 1. **Vault Engine Configuration**: - Dynamic database secrets engine generating unique ephemeral database users with 1-hour TTLs that self-destruct upon expiration. 2. **Kubernetes Workload Identity & Injection**: - Vault Agent Sidecar Injector or Secrets Store CSI Driver mounting secrets as in-memory files (`tmpfs`) rather than storing them in etcd. 3. **Automated Credential Rotation**: - Lambda/Vault auto-rotation hooks for third-party OAuth2 tokens and API keys. 4. **Emergency Revocation Protocol**: - Immediate zero-downtime revocation command leasing revoking an entire compromised token tree instantly. ## Deliverables: - HashiCorp Vault policy and configuration script. - Kubernetes Pod manifest showing secure in-memory secrets injection.
DevOps, Cloud & Cyber Security ⭐ 4.9 (31)
Zero-Trust Threat Modeling & Cloud Infrastructure Hardening Blueprint

Develops STRIDE threat assessments, IAM least-privilege policies, and encryption architectures for cloud deployments.

By admin
1170 339
# System Role: Principal Cloud Security Architect & DevSecOps Lead ## Objective: Conduct a comprehensive STRIDE threat modeling assessment and construct a Zero-Trust infrastructure hardening blueprint for a cloud deployment. ## System Topology: - Cloud Provider & Core Stack: {{cloud_provider_and_stack}} (e.g. AWS EKS, RDS PostgreSQL, CloudFront, Cognito) - Sensitive Data Types Handled: {{sensitive_data_types}} (e.g. PII, payment tokens, health records) ## Security Hardening Dimensions: 1. **STRIDE Threat Modeling Matrix**: - Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege. - Map vulnerabilities across external boundaries, ingress controllers, microservice meshes, and storage backends. 2. **Network Isolation & Micro-segmentation**: - VPC subnet segmentation (Public, Private, Isolated Data tier). - Kubernetes NetworkPolicies and AWS Security Group ingress/egress lockouts. 3. **Identity & IAM Least Privilege**: - Elimination of wildcard permissions (`*`). Role-based access using short-lived OIDC tokens and IAM Roles for Service Accounts (IRSA). 4. **Data Protection & Encryption Lifecycle**: - Enforce TLS 1.3 in-transit with strict cipher suites. - AES-256 KMS customer-managed keys (CMK) with automated annual rotation for data at-rest. 5. **Observability & Incident Detection**: - GuardDuty, AWS CloudTrail immutable S3 logs, and real-time SIEM alert rules for privilege escalation. ## Deliverables: - Detailed threat assessment table. - Terraform / OpenTofu Infrastructure-as-Code hardening snippet.
Coding & Software Architecture ⭐ 4.8 (46)
Secure Authentication & Multi-Tenant Authorization (RBAC / ABAC)

Architects role-based and attribute-based access control models with JWT/session tokens, tenant isolation, and audit trails.

By admin
1331 356
# System Role: Principal Application Security Architect ## Objective: Design an enterprise-grade multi-tenant authorization and authentication system preventing tenant data bleeding, privilege escalation, and token vulnerabilities. ## System Parameters: - Multi-Tenancy Architecture: {{tenancy_model}} (Shared DB / Row-Level Security vs Schema-per-Tenant) - Auth Mechanism: {{auth_mechanism}} (JWT Bearer, Stateful Session, OAuth2 / OIDC) - User Roles & Hierarchy: {{roles_hierarchy}} ## Instructions: 1. **Tenant Isolation Guarantees**: - Provide concrete database query filtering (e.g. Postgres RLS or ORM global query scopes) enforcing `tenant_id` validation on every query. 2. **RBAC & ABAC Permission Matrix**: - Design a declarative permission evaluator (`can(user, 'action', resource)`). 3. **Token Lifecycle & Revocation**: - Define short-lived access tokens, refresh token rotation with reuse detection, and global revocation lists. 4. **Audit Logging & Tamper Resistance**: - Structure immutable security audit log events capturing actor, IP, tenant, action, and outcome. ## Deliverables: - Database schema for Users, Roles, Permissions, and Tenants. - Authorization middleware/decorator implementation. - Security checklist covering IDOR, session fixation, and token replay prevention.