VL
Valentina L.Verified purchase
Your cart is empty
Add prompt packs to continue
100 professional prompts ready to copy and paste into ChatGPT, Claude or Gemini.
This master prompt library redefines the productivity standard for modern systems engineers. Each instruction has been meticulously calibrated to address the industry's most critical challenges, from architecting scalable microservices to hardening cloud infrastructures. With a practical and technical approach, this collection allows you to automate complex processes, guaranteeing impeccable documentation and high-performance code. Empower your workflow with tools designed for strategic precision. This collection not only facilitates the creation of robust systems, but optimizes project evaluation and technical debt management, allowing teams to achieve development milestones with greater agility. Turn artificial intelligence into your strategic ally to lead technological projects of global impact.
Just $0.08 per prompt · one-time payment
An instruction. The basis of every AI result.
Prompt
your instruction
AI
100 resources included
He acts as a Senior Software Architect and Code Quality Specialist with extensive experience in technical debt management and large-scale refactoring. Your main mission is to carry out an exhaustive and critical audit of the nomenclature used in the [SOURCE_CODE_OR_MODULE] provided, under the framework of the 'Systems Engineering' collection. The objective is to identify semantic, lexical and structural inconsistencies that increase the cognitive load of developers and hinder the evolutionary maintenance of the system. Start the analysis by evaluating compliance with the specific style conventions for the [PROGRAMMING_LANGUAGE] language (such as PEP 8, Google Java Style Guide, or Microsoft C# Coding Conventions). You should detect generic naming patterns, such as 'data', 'process', 'temp' or single-letter variables, that add no contextual value to the logical flow of the program. For each finding, explain why lack of semantic precision constitutes a form of structural technical debt that directly impacts mean time to repair (MTTR). Examines the linguistic coherence of the project, detecting the phenomenon of 'Spanglish' or the mixing of languages in the definition of classes, methods and attributes. Evaluates whether the method names follow the 'Action + Subject' pattern and whether the classes represent clear entities within the business domain defined in [SYSTEM_DOMAIN]. It is essential that you identify if there is a discrepancy between the Ubiquitous Language proposed by Domain-Driven Design (DDD) and the current technical implementation. Analyze the nomenclature of abstraction layers. Determines whether suffixes (such as DTO, Service, Repository, Controller, Impl) are being used consistently or whether their use is redundant and confuses the [ARCHITECTURE_TYPE] architecture hierarchy. You should pay special attention to the 'Load of Meaning': do the names reveal the author's intention or do they require the reader to delve into the implementation to understand their purpose? Identify misleading names that perform hidden functions not suggested by their label. Finally, generate a detailed report that includes a comparative table of 'Actual Name' vs 'Proposed Name', justified using Clean Code principles (SOLID, DRY). Provides a qualitative metric of the criticality of each change based on the frequency of use of the component in the overall system. The end result should be a roadmap for mitigating readability-related technical debt, facilitating a smooth transition to a professional and homogeneous naming standard. If any key information needed to fill the bracketed fields is missing, ask me the necessary questions before answering.
Instant access after purchase from your dashboard. Just copy and paste into your AI.
ChatGPT, Claude, Gemini, DeepSeek, Grok, Qwen and any AI chat.
Yes. Every prompt includes bracketed fields where you insert your own information, context and specifics, so they fit your situation, country or industry.
Yes. Above you can read full sample prompts, exactly as you'll receive them, to check the quality before paying.
Yes. Pay once and they're yours forever, updates included.
Result
Act as a Senior Software Architect expert in distributed systems and high availability to design a comprehensive technical implementation of the Circuit Breaker Pattern within our microservices ecosystem based on [Language or Framework, ex: Java/Spring Boot, Node.js/NestJS, Go]. The main objective is to avoid the cascade of failures and improve the resilience of the system to the degradation of critical third-party services or latent internal services. Deeply analyze the interaction between the [Consumer Service] and the [Provider Service/External API]. You must define a precise configuration for the three states of the circuit: 1. CLOSED: Defines the failure threshold (Failure Rate Threshold) based on a minimum volume of [Number of Calls] requests. 2. OPEN: Determines the 'Wait Duration In Open State' of [Seconds] before attempting the transition to Half-Open. 3. HALF-OPEN: Sets the number of calls allowed to verify system recovery safely. Develop a sophisticated 'Fallback' strategy that doesn't just return an error. Please propose a solution that includes [Use of Distributed Cache/Defaults/Simplified Response] to keep the user experience as intact as possible. The generated code should follow Clean Code principles and use industry standard libraries such as [Suggested Library, ex: Resilience4j, Opossum, Polly]. Finally, it integrates a detailed observability scheme. Explains how to expose Circuit Breaker state changes (state transitions) through events that can be captured by [Monitoring Tool, e.g.: Prometheus/Grafana, Datadog] and defines the critical alerts that the SRE team should configure to react to a circuit that remains in the OPEN state for more than [Time Limit] minutes. If any key information needed to fill the bracketed fields is missing, ask me the necessary questions before answering.
He acts as a Cloud Engineer and Infrastructure as Code (IaC) Specialist with extensive experience in implementing Disaster Recovery and Data Resilience strategies. Your goal is to design a robust and scalable system for Automating Backup Snapshots within a [CLOUD_PROVIDER] environment. The design should focus on operational efficiency, cost reduction through lifecycle policies, and maximum security through encryption at rest and in transit using industry standards. The core technical requirement is to develop scripts or manifests using [IAC_TOOL] to automate the creation of consistent backups of [RESOURCE_TYPES]. You must integrate [SCHEDULE_CRON]-based task scheduling logic that ensures that maintenance windows do not impact the performance of applications in production. It is imperative that the solution includes dynamic resource tagging based on [RESOURCE_TAGS] to facilitate management, asset search, and cost auditing by specific cost center or department. Regarding the retention policy, the solution must be able to automatically manage the lifecycle of snapshots, safely deleting those that are more than [RETENTION_DAYS] days old to avoid unnecessary charges and comply with data protection regulations. In addition, the implementation of a 'Cross-Region Copying' strategy towards the [SECONDARY_REGION] region is required to ensure business continuity in the event of a catastrophic failure in the infrastructure of the main [PRIMARY_REGION] region. Each generated snapshot must be encrypted using master keys managed in [KMS_SERVICE_NAME]. The proposed architecture should include an advanced monitoring and notification system that alerts the SRE (Site Reliability Engineering) team through [NOTIFICATION_CHANNEL] in case of failures in the backup process or violations of established compliance policies. It is crucial to document the required IAM (Identity and Access Management) roles, strictly applying the Least Privilege principle, and detail how the restore process can be periodically validated through automated recovery tests within a sandbox. Finally, generate a step-by-step deployment guide that includes validating code syntax, executing change plans (dry-runs), and post-deployment verification in the vendor's control panel. Ensure that the code is modular, parameterized, and highly reusable, allowing other systems engineering teams to integrate this backup functionality into their CI/CD pipelines in a transparent, standardized, and secure manner. If any key information needed to fill the bracketed fields is missing, ask me the necessary questions before answering.
Based on 11 reviews
Happy with the purchase. The prompts are useful and practical. I'd buy again.
Happy with the purchase. The organization helps you get oriented fast. Good option.
Exactly what I was looking for. They're easy to adapt to my case by just changing the fields. One hundred percent recommended.
I was impressed by the quality. The prompts are really well thought out and the effort shows. I'll buy again without hesitation.
It helped me quite a bit. They saved me time on several tasks. Good option.
Best purchase I made this month. They're easy to adapt to my case by just changing the fields. Totally recommend them.
Best purchase I made this month. They're easy to adapt to my case by just changing the fields. An investment that pays for itself.
Worth every penny. They work just as well in ChatGPT and Claude. Already recommended them to my team.
Best purchase I made this month. They saved me hours of work in the first week. An investment that pays for itself.
I was impressed by the quality. The quality of the answers I get improved a lot. Totally recommend them.
Worth every penny. They're easy to adapt to my case by just changing the fields. One hundred percent recommended.