Skip to content
OrtivoSign in · My saved prompts

AI prompt library · Coding & architecture

Coding & Software Architecture AI Prompts

Frame a technical problem with enough context for useful analysis. Include the language, framework, constraints and relevant code or schema. Treat generated changes as proposals to review and test in your own environment.

How to use these prompts

  1. Choose a template and open Preview & customise.
  2. Fill the named fields with your details and check the completed draft.
  3. Copy it into your preferred AI tool, or sign in to prepare a Chat draft in Ortivo.

Copying is free and does not call an AI. Generating an answer requires your own configured provider or an available trial. Review important facts and every draft before use.

10 starter prompts in Coding & architecture

Coding & architecture

System Architecture & Scalability Trade-Off Review

Review our proposed architecture ({{system_design}}) for an expected load of {{expected_load}}, latency target of {{latency_target}}, and budget ceiling of {{budget_ceiling}}. Ide…

Suggested: Multi-Model Compare
Read template
Review our proposed architecture ({{system_design}}) for an expected load of {{expected_load}}, latency target of {{latency_target}}, and budget ceiling of {{budget_ceiling}}. Identify single points of failure, database contention bottlenecks, and simpler alternatives.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

Code Security & OWASP Vulnerability Audit

Perform a security review of the following {{language_framework}} implementation using {{auth_model}}: {{code_or_endpoint}}. Check for injection vectors, broken access control, SS…

Suggested: Multi-Model Compare
Read template
Perform a security review of the following {{language_framework}} implementation using {{auth_model}}: {{code_or_endpoint}}. Check for injection vectors, broken access control, SSRF, insecure deserialization, and race conditions, providing patched remediation code.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

Legacy Code Refactoring Plan

Propose an incremental, zero-downtime refactoring strategy to migrate {{legacy_module}} toward {{target_architecture}} given {{test_coverage_status}}. Sequence the strangler-fig s…

Suggested: Single AI / Compare
Read template
Propose an incremental, zero-downtime refactoring strategy to migrate {{legacy_module}} toward {{target_architecture}} given {{test_coverage_status}}. Sequence the strangler-fig steps, characterization tests needed first, and rollback checkpoints.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

SQL & Database Query Performance Optimizer

Optimize this query on {{db_engine}}: {{sql_query}} given schema and row counts {{table_schema_and_row_counts}}. Explain why full table scans or expensive joins occur, rewrite the…

Suggested: Single AI
Read template
Optimize this query on {{db_engine}}: {{sql_query}} given schema and row counts {{table_schema_and_row_counts}}. Explain why full table scans or expensive joins occur, rewrite the query, and specify the exact composite indexes to create.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

Production Incident Root-Cause Post-Mortem

Draft a blameless technical post-mortem from {{incident_timeline}}, {{symptoms_and_logs}}, and {{immediate_fix}}. Apply the 5 Whys to separate proximate triggers from systemic arc…

Suggested: Single AI → Decision Notebook
Read template
Draft a blameless technical post-mortem from {{incident_timeline}}, {{symptoms_and_logs}}, and {{immediate_fix}}. Apply the 5 Whys to separate proximate triggers from systemic architectural weaknesses, and define preventative engineering tasks.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

Unit & Property-Based Edge-Case Test Generator

Write a comprehensive test suite in {{test_framework}} for {{function_signature_and_code}}. Cover standard happy paths, boundary values, null/malformed inputs, concurrency edge ca…

Suggested: Single AI
Read template
Write a comprehensive test suite in {{test_framework}} for {{function_signature_and_code}}. Cover standard happy paths, boundary values, null/malformed inputs, concurrency edge cases, and error-throwing assertions.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

API Schema & Idempotency Design Review

Audit this REST/GraphQL API specification ({{api_spec}}) consumed by {{client_consumers}} under {{versioning_strategy}}. Check for pagination consistency, idempotency keys on muta…

Suggested: Multi-Model Compare
Read template
Audit this REST/GraphQL API specification ({{api_spec}}) consumed by {{client_consumers}} under {{versioning_strategy}}. Check for pagination consistency, idempotency keys on mutating endpoints, clear error payload schemas, and backward-compatibility risks.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

Cloud Infrastructure Cost Optimization Audit

Analyze our {{cloud_provider}} footprint ({{current_services_and_spend}}) serving a {{traffic_pattern}} traffic pattern. Recommend concrete architecture adjustments, reserved/spot…

Suggested: Multi-Model Compare
Read template
Analyze our {{cloud_provider}} footprint ({{current_services_and_spend}}) serving a {{traffic_pattern}} traffic pattern. Recommend concrete architecture adjustments, reserved/spot instance sizing, storage tiering, and egress reductions ranked by savings vs. engineering effort.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

Data Pipeline & Migration Integrity Checklist

Design a safe data migration plan from {{source_system}} to {{destination_system}} for {{data_volume}} within a {{downtime_window}} window. Detail dual-writing, backfill batching,…

Suggested: Single AI
Read template
Design a safe data migration plan from {{source_system}} to {{destination_system}} for {{data_volume}} within a {{downtime_window}} window. Detail dual-writing, backfill batching, checksum reconciliation queries, and instant cutover rollback steps.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.
Coding & architecture

LLM Prompt & Token Cost Optimization Audit

Optimize this production prompt ({{current_system_prompt}}) running on {{target_model}} returning {{required_output_schema}}. Compress token overhead by 30% without losing instruc…

Suggested: Multi-Model Compare
Read template
Optimize this production prompt ({{current_system_prompt}}) running on {{target_model}} returning {{required_output_schema}}. Compress token overhead by 30% without losing instruction fidelity, eliminate ambiguous directives, and harden against prompt injection.

Use only supplied material or sources actually accessed. Distinguish evidence, estimates and assumptions. Do not invent facts, citations, test results or actions performed. Flag missing information and tool limitations.