jluisflo

class Aliens
{
    private static void Main()
    {
        int[] aliens = [3, 4, 3, 1, 2];
        const int maxDays = 80;
        for (var day = 0; day <= maxDays; day++)
        {
            Console.WriteLine($"Dia: {day}: {string.Join(",", aliens)}");
            

jluisflo

Cursor's Memory Bank

I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.

Memory Bank Structure

The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:

flowchart TD

jluisflo

# Code Documentation Rules - Credits Backend

## Core Documentation Principles

### 🎯 **Documentation Purpose**
- **Explain WHY, not WHAT**: Focus on business context, not implementation details
- **Critical Understanding**: Document complex business logic and non-obvious decisions
- **Future Maintainer**: Write for someone who doesn't know the context
- **Business Value**: Prioritize documenting business-critical code

jluisflo

# Cursor Rules - Credits Backend Development Standards

## Code Documentation Standards

### XML Documentation
- **Classes**: Provide concise but meaningful purpose and context
- **Methods**: Explain what the method does, not how it does it
- **Parameters**: Document only when not obvious from the method name
- **Returns**: Document only for complex return types
- **Keep it concise**: Avoid verbose explanations that repeat the code