Prompts de IA para Software

Genere un prototipo funcional para una aplicación móvil llamada 'PlantPal'. Es para nuevos propietarios de plantas. Pantallas Clave: - **Onboarding:** Una introducción sencilla de 3 pasos a las funciones de la aplicación. - **Inicio de Sesión/Registro:** Autenticación por correo electrónico y contraseña. - **Mis Plantas:** Un panel que muestra una cuadrícula de plantas que el usuario ha añadido. Cada tarjeta debe mostrar una foto, el nombre de la planta y un botón 'Regar Ahora'. - **Añadir Planta:** Un formulario para añadir una nueva planta con campos para nombre, especie (desplegable) y carga de fotos. - **Detalles de la Planta:** Una vista que muestra más información sobre una planta específica, incluyendo un horario de riego y consejos de cuidado. La base de datos debe tener una tabla de 'Usuarios' y una tabla de 'Plantas', con una relación entre ellas.

engineer specializing in large-scale refactoring. Your task is to refactor the

codebase. Before you make any changes to

. Your task is to create a migration plan for the

model Product { id String @id @default(cuid()) name String description String? price Float createdAt DateTime @default(now()) updatedAt DateTime @updatedAt }

. I need you to first explain it, and then re-implement it in a more efficient and readable way in

[Paste code snippet, e.g., a function handling user input or a database query]

file and identify potential risks. **File Content:**

function. While the EU AI Act's Article 50 transparency obligations do not apply to source code itself, I want to adopt its principles for internal governance. **Code Snippet:**

that needs to perform a specific task. **Task Description:** The Lambda function needs to read objects from the

[[Paste the full git diff here]]

CREATE TABLE users ( id SERIAL PRIMARY KEY, name VARCHAR(100), email VARCHAR(100) UNIQUE, created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() ); CREATE TABLE orders ( id SERIAL PRIMARY KEY, user_id INTEGER REFERENCES users(id), amount DECIMAL(10, 2), created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() );

. Analyze the following slow query and the table schema, then provide an optimized version. **Table Schema:**

[from myapp.models import Author, Book recent_prolific_authors = Author.objects.filter( book__publication_date__gte='2026-01-01' ).annotate( num_books=Count('book') ).filter( num_books__gt=5 ).order_by('-num_books')]

function calculateDiscount(price, quantity, userTier) { // ... function implementation ... }

developer debugging a production error. I will provide a stack trace and the relevant code. Your job is to identify the most likely root cause. **Environment:**

2. **Explanation:** Break down the regex part by part in a table, explaining what each component does (e.g.,

(for interacting with the Prisma schema and CLI) *

(for creating GitHub issues) **Scenario:** The "new user registration" feature has been deployed to the staging environment at

. 3. Analyze the function signature, the Zod validation schema, and the main logic. 4. Create a new file

Design a system like `[[Twitter's timeline service]]`." **Your Role:** 1. Start by asking me clarifying questions to scope the problem (e.g., "What are the key features?" "What is the expected scale?"). 2. As I propose components (e.g., load balancers, databases, caches), challenge my decisions. Ask about trade-offs, failure modes, and scalability bottlenecks. 3. Force me to do back-of-the-envelope calculations for storage, bandwidth, and QPS. 4. Do not give me the answers. Guide me toward a robust design by asking critical questions. 5. Conclude the interview by giving me feedback on my design, highlighting 3 strengths and 3 areas for improvement.

# ADR-001: Adopt ScyllaDB as the Primary Database **Date:** `[[September 3, 2026]]` **Status:** Accepted **Context:** *(Describe the business/technical problem we are trying to solve.)* **Decision:** *(State the decision clearly.)* **Consequences:** * **Positive:** * *(List the expected benefits, e.g., improved write throughput, lower read latency, horizontal scalability.)* * **Negative:** * *(List the downsides and risks, e.g., loss of ACID transactions, need for new developer skills, migration complexity.)* **Options Considered:** 1. **ScyllaDB:** *(Briefly describe why this was chosen.)* 2. **PostgreSQL with CitusDB:** *(Briefly describe why this was not chosen.)* 3. **CockroachDB:** *(Briefly describe why this was not chosen.)*

[[a real-time chat application for large online communities]]

to me. **Instructions:** * Assume I am an experienced developer who has only ever worked with garbage-collected languages like

[I accidentally committed a large binary file to my feature branch. I have made several other commits on top of it. I want to remove that file and its commit from my branch history before I create a pull request. I have not pushed the branch to the remote yet.]

/ ├── app/ │ ├── layout.tsx │ └── page.tsx ├── components/ │ └── ui/ ├── lib/ │ └── utils.ts ├── public/ ├── package.json ├── tsconfig.json ├── next.config.mjs └── tailwind.config.ts