---
title: Prompt de refinamiento
route: /es/resources/prompt-refinement
lang: es
part_of: Onirion
version: "4.0"
date: 2026-09-22
author: Alexis Boyer
license: CC BY 4.0
one_line: "Para cuando el primer resultado es demasiado superficial, demasiado conceptual o demasiado parecido a un dashboard."
kind: prompt
layers:
  summary: /es/resources/prompt-refinement
  complete_text: /es/complete.md
  markdown: /es/resources/prompt-refinement.md
---

*El texto que sigue es el del kit, en inglés.*

<!-- source: public-kit/prompts/gate-3-refinement.md -->

# The refinement prompt

**A method by Alexis Boyer · version 4.0 · September 22, 2026**

**Gate 3.** Use it when the first output is too shallow, too conceptual or too dashboard-like. It is quoted here exactly as it appears in [the core guide](/es/resources/method-guide).

## What you fill in

Nothing. Paste it as it is. If you design against a reference product because the design system has not arrived yet, write “reference product” for “design system” in its last line.

## The text to copy

```text
Refine this into a denser operational product.

Prioritize daily user work over executive analytics. The primary workflow should be obvious on the first screen. Remove any marketing-style hero, oversized explanatory card or decorative section.

Increase depth:
- make status, owner, next action, date, priority and permission state visible where they matter;
- make the main workflow usable end to end, including its intermediate steps and its failures;
- add the missing drawers, modals, dropdowns, error, empty and confirmation states;
- make history and audit easy to inspect;
- make document and request workflows feel functional;
- make role-gated and restricted states explicit;
- use realistic data and realistic edge cases;
- keep the design aligned with the attached design system.
```