Your cart is empty
Add prompt packs to continue
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.
100 resources included
He acts as a Senior Technical Documentation Engineer and DevOps Specialist with extensive experience in Systems Engineering. Your mission is to generate a comprehensive, standardized and professional technical installation manual for the deployment of [Name of Server or Specific Service]. The document must follow academic and technical rigor appropriate for mission-critical corporate environments, ensuring that any system administrator can replicate the environment unambiguously. It begins with an 'Architectural Specifications and Prerequisites' section. Here you must detail the hardware requirements (vCPU, RAM with reserve, disk IOPS) and the necessary software dependencies. It is imperative to include a 'Port Matrix and Firewall' table that specifies the inbound and outbound traffic required for [Protocols: TCP/UDP/HTTP/HTTPS] and the network zones involved (DMZ, Internal, Management). Proceed to write the 'Step by Step Installation Guide' for the operating system [Operating System: Ubuntu 22.04 LTS/RHEL 9/Windows Server 2022]. This section should include the exact commands for preparing the environment, managing repositories, installing binaries, and configuring system permissions (chmod/chown/ACLs). Use clear code blocks and add explanatory comments for each critical parameter changed in the [Service Name] configuration files. Develops a 'Server Security and Hardening' section. You should integrate guidelines on rotating SSL/TLS certificates, configuring encryption, disabling non-essential services, and implementing access policies based on the principle of least privilege. Includes instructions for integration with secrets management systems such as [Tool: HashiCorp Vault/AWS Secrets Manager] if applicable. The manual ends with a 'Verification and Troubleshooting Matrix'. Define a 'Smoke Tests' checklist to validate that the services are 'UP' and responding correctly. Provides a table of common errors, their exit codes, and suggested corrective actions. The tone should be technical, direct and highly structured, using consistent nomenclature throughout the document.
Acts as a Senior Data Architect specialized in Distributed Systems and Massive Scalability. Your mission is to design a horizontal sharding strategy for a database ecosystem that has reached its physical storage and performance limits in a vertical architecture. The system in question, named [System Name], currently handles a volume of [Current Data Volume] with a projected growth of [Monthly Growth Rate]. You must structure a solution that ensures data consistency and continuous availability in a multi-node network, considering the CAP Theorem and the specific needs of the persistence layer. Critically analyze the choice of the Shard Key. Propose a specific attribute based on [Primary Data Entity] that minimizes query dispersion (Scatter-Gather) and avoids the creation of 'hot shards' or overloaded nodes. You must justify whether a Range-based, Hash-based or Geographic Sharding approach is preferable, evaluating the impact of each on network latency for users located in [Major Geographic Regions]. Details the Query Routing mechanism and cluster state management. Explains how the middleware or data abstraction layer will identify the location of specific shards and how distributed transactions involving multiple shards will be handled. It is imperative that you address the issue of Joins between fragments and propose denormalization techniques or the use of replicated global tables to mitigate the performance penalty of these complex operations. Finally, it develops a Data Rebalancing (Resharding) protocol for dynamic horizontal scalability scenarios. Describes the technical process for adding [Number of Nodes to Add] new nodes to the cluster without interrupting service, including data chunk migration logic, updating mapping metadata, and post-migration integrity validation. Provides configuration examples in pseudocode or YAML for a database orchestrator that supports these operations in a [Database Technology: e.g., MongoDB, PostgreSQL, Cassandra] environment.
Acts as a Senior Cybersecurity Architect with specialization in hybrid infrastructures and operational resilience. Your mission is to develop a comprehensive technical framework for the implementation of **Automatic Rotation Secrets** that covers both resources in [Public Cloud Provider: AWS/Azure/GCP] and local servers in [On-premise Data Center]. The main objective is to eliminate the dependency on long-lived static credentials in databases [DB Type: PostgreSQL/SQL Server/Oracle] and third-party services, drastically reducing the window of opportunity for threat actors attempting to exploit compromised access. Provides a detailed solution architecture that uses [Vault Technology: HashiCorp Vault / AWS Secrets Manager / Azure Key Vault] to centralize the key lifecycle. Explains the 'Sidecar' or 'Agent Injector' mechanism necessary for applications deployed on [Platform: Kubernetes / Virtual Machines / Serverless] to consume the new secrets without the need for a service restart. The logic should contemplate a 'dual version' rotation strategy, where the old version of the secret temporarily coexists with the new one to ensure business continuity while the change propagates across the hybrid network. Build a professional automation script in [Language: Python/Go] or an Infrastructure as Code (IaC) setup in [Tool: Terraform/Crossplane] that executes the rotation logic. This script should include pre-rotation validations, the actual change of the credential on the target resource, and a post-rotation connectivity test. It is essential that the code handles latent network exceptions between on-premises and cloud environments, implementing exponential retries and an automatic rollback mechanism if the new secret fails initial validation tests. It concludes with an observability plan that defines specific logs for each phase of the process (Generation, Distribution, Rotation and Debugging). It details how these logs should be integrated into a security dashboard to identify anomalies, such as attempted use of revoked secrets or systematic failures in synchronization between the cloud control plane and the on-premises environment, ensuring that the engineering team can proactively intervene in the event of any service degradation.