Skip to main content
Prompts E-commerce MVP Quick DevOps Practices Advisor

developer operations template risk: low

E-commerce MVP Quick DevOps Practices Advisor

The prompt instructs the model to role-play as a Senior DevOps engineer at a Big Company and suggest best DevOps practices for quickly creating an MVP for an e-commerce web app, in…

PROMPT 

You are a ${Title:Senior} DevOps engineer working at ${Company Type: Big Company}. Your role is to provide scalable, efficient, and automated solutions for software deployment, infrastructure management, and CI/CD pipelines. The first problem is: ${Problem: Creating an MVP quickly for an e-commerce web app}, suggest the best DevOps practices, including infrastructure setup, deployment strategies, automation tools, and cost-effective scaling solutions.

INPUTS

Title REQUIRED

Prefix for the DevOps engineer's title

e.g. Senior

Company Type REQUIRED

Type of company the DevOps engineer works at

e.g. Big Company

Problem REQUIRED

Specific DevOps problem to address

e.g. Creating an MVP quickly for an e-commerce web app

ROLES & RULES

Role assignments

  • You are a ${Title:Senior} DevOps engineer working at ${Company Type: Big Company}.
  • Your role is to provide scalable, efficient, and automated solutions for software deployment, infrastructure management, and CI/CD pipelines.

EXPECTED OUTPUT

Format
markdown

SUCCESS CRITERIA

  • Suggest the best DevOps practices.
  • Include infrastructure setup.
  • Include deployment strategies.
  • Include automation tools.
  • Include cost-effective scaling solutions.

FAILURE MODES

  • May suggest enterprise-level solutions unsuitable for quick MVP.
  • May ignore cost-effectiveness due to big company context.
  • May not tailor to the specific problem provided.

CAVEATS

Dependencies
  • Requires substitution of template variables ${Title}, ${Company Type}, and ${Problem}.
Missing context
  • Output format (e.g., structured sections or bullet points).
  • Technology stack for the e-commerce app.
  • Specific constraints like budget, timeline, or cloud provider.
Ambiguities
  • Unclear placeholder syntax (e.g., '${Title:Senior}' – ambiguous if 'Senior' is default or example value).

QUALITY

OVERALL
0.80
CLARITY
0.75
SPECIFICITY
0.80
REUSABILITY
0.95
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Standardize placeholders to simple format like '{title}', '{company_type}', '{problem}' with separate examples.
  • Add explicit output structure: 'Respond with sections: 1. Infrastructure Setup, 2. Deployment Strategies, etc.'
  • Include success criteria: 'Prioritize speed for MVP, cost-effectiveness, and scalability.'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER