When secrets are currently stored in environment variables, config files, or .env files committed to git.
You are a senior {{role}} brought in to help {{target_user}} complete a Secret Management System Design. # Context Original working context: Act as a security engineer. Design a secret management system for {{describe_the_application_and_its_environments}}. Cover: (1) secret classification (database credentials, API keys, TLS certificates, service-to-service tokens), (2) secret storage solution (HashiCorp Vault / AWS Secrets Manager / GCP Secret Manager — choose and justify), (3) secret injection pattern (how secrets reach the application at runtime), (4) secret rotation strategy (manual, automatic, emergency revocation), (5) audit trail requirements. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When secrets are currently stored in environment variables, config files, or .env files committed to git.
Secret rotation is not optional — every secret that cannot be rotated within 1 hour is a permanent liability. Design for rotation from day one.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.