PRD a Reglas de Negocio

Descripción

Este prompt crea un archivo RULES.md que establece directrices técnicas y generales para la asistencia de IA durante el proceso de desarrollo.

Contenido

  • Definición de stack tecnológico: Identifica tecnologías principales y versiones a utilizar
  • Preferencias técnicas: Establece convenciones de nomenclatura, organización de código, patrones arquitectónicos, etc.
  • Estándares de desarrollo: Define requisitos de pruebas, documentación, manejo de errores, etc.
  • Prioridades de implementación: Clarifica qué características son fundamentales vs. mejoras
  • Directrices generales: Establece reglas para seguir requisitos con precisión, calidad de código, etc.

Ejemplo de Resultado


# Reglas para el Desarrollo

## Stack Tecnológico
- **Frontend:** React 18, TypeScript 5.0+, TailwindCSS 3.0+
- **Backend:** Node.js 18+, Express 4.18+, MongoDB 6.0+
- **Herramientas:** Vite, Jest, ESLint, Prettier

## Preferencias Técnicas
- **Nomenclatura:** camelCase para variables/métodos, PascalCase para componentes/clases
- **Estructura:** Arquitectura basada en componentes, separación de lógica/presentación
- **Patrones:** Hooks personalizados para lógica reutilizable, Context API para estado global limitado

## Estándares de Desarrollo
- Incluir tests unitarios para toda la lógica de negocio
- Documentar todas las APIs con JSDoc
- Implementar manejo de errores consistente con mensajes claros para el usuario

Prompt Completo

You are an expert software architect and technical lead tasked with creating a comprehensive RULES.md file based on the attached Product Requirements Document (PRD) and features list.

Create a clear, structured RULES.md file that establishes technical and general guidelines for AI assistance during the development process. These rules will ensure consistency, quality, and alignment with project requirements.

If any critical information is missing or unclear in the provided documents that prevents thorough rule creation, ask specific questions to gather the necessary details before proceeding.

Generate the RULES.md by:

1. TECHNOLOGY STACK DEFINITION:

  • Identify the core technologies mentioned or implied in the PRD/features
  • Specify the latest stable versions to use for each technology
  • Define any specific libraries, frameworks, or tools required

2. TECHNICAL PREFERENCES:

  • Establish naming conventions for files, components, variables, etc.
  • Define code organization principles (folder structure, modularity)
  • Specify architectural patterns to follow
  • Set standards for data handling, state management, and API interactions
  • Outline performance requirements and optimization strategies
  • Define security practices and requirements

3. DEVELOPMENT STANDARDS:

  • Establish testing requirements and coverage expectations
  • Define documentation standards
  • Specify error handling and logging requirements
  • Set accessibility standards to follow
  • Define responsive design requirements

4. IMPLEMENTATION PRIORITIES:

  • Clarify which features are core vs. enhancements
  • Establish any phased implementation approach
  • Define quality thresholds that must be met

5. GENERAL GUIDELINES:

  • Establish rules for following requirements precisely
  • Define expectations for code quality, readability, and maintainability
  • Set standards for completeness (no TODOs or placeholders)
  • Establish communication guidelines for questions or clarifications
  • Define how to handle uncertainty or ambiguity

6. RULES.MD CREATION:

  • Format the rules in clean, well-structured markdown
  • Organize rules logically with clear headings
  • Ensure rules are specific, actionable, and unambiguous
  • Include examples where helpful for clarity

First, provide a brief overview of the project based on the PRD and features list. Then create the comprehensive RULES.md content following the structure above.

Ensure the rules are specific enough to guide development but flexible enough to allow for creative problem-solving where appropriate.