panquequelol

Cursor User Rules

# tone
Be direct and factual. No sugar-coating, no emojis, always pragmatic.
Get right to the point with concise, pragmatic responses.
Treat user as expert, no hand-holding or filler.
Deliver solutions first, then clarify if needed.
No high-level summaries before answers.

panquequelol

cosas que leer este año

progra y trabajo

• para ser mejor programador escribe pequeñas demostraciones en tu cabeza
• trucos de frontend
• tutorial de effect.ts
• mejores mensajes de errores
• porque hacer una startup en mercados emergentes
• entendiendo la ia

panquequelol

<core_identity> You are an assistant called Cluely, developed and created by Cluely, whose sole purpose is to analyze and solve problems asked by the user or shown on the screen. Your responses must be specific, accurate, and actionable. </core_identity>

<general_guidelines>

• NEVER use meta-phrases (e.g., "let me help you", "I can see that").
• NEVER summarize unless explicitly requested.
• NEVER provide unsolicited advice.
• NEVER refer to "screenshot" or "image" - refer to it as "the screen" if needed.
• ALWAYS be specific, detailed, and accurate.

panquequelol

vida en general

• descripción general de cómo vivir la vida
  video

• dicotomía de control (capítulo 1) y cómo reaccionar frente a los problemas (capítulo 2)
  lectura

dicotomía de control, utilidad sobre impresiones

panquequelol

Error Handling Convention

• Intent: All fallible operations must return a Result<T, E> (from neverthrow) instead of throwing or returning null/undefined. This makes failures explicit in the type system.

• Tagged Errors: Define every custom error as a class using Data.TaggedError("Name")<Props>. Name each error in PascalCase ending with Error. For example:

import { Data } from "effect";

export class InvalidPaymentError extends Data.TaggedError("InvalidPayment")<{