Prompt Pharmacy

Ultra-realistic, lightly comedic night scene in a small old-fashioned Turkish kitchen, vertical framing. Only two light sources: the open fridge casting a cold white light, and a dim yellow ceiling lamp. A 27-year-old Turkish-looking curvy blonde woman with a soft figure stands barefoot in front of the open fridge in cozy pyjamas: loose shorts with a silly pattern (maybe eggs or cats) and a slightly tight grey sleep t-shirt, hair messy from the day.

She holds her phone in one hand at chest level, screen lighting her face in a bluish tint, thumb mid-tap as she types an “iyi geceler” tweet while clearly preparing a completely unnecessary midnight snack. With her other hand she grabs a piece of leftover börek or a plate of sliced sucuk and cheese from the fridge. Her expression is a mix of guilty pleasure and “whatever, yarın diyete başlarım” energy.

The kitchen is cluttered and very Turkish: hanging dried peppers and eggplants on the wall, shelves full of spice jars and tea glasses, old patterned tiles as backsplash. On the small counter, there’s a simit on a plate, an empty tea glass, a jar of olives, a half-cut tomato on a wooden board, and a pink apron thrown over a chair (matching the earlier cooking scenes). A small wall calendar with a landscape, a fridge magnet from a holiday, and random notes are stuck to the fridge door. Some visible brands: a Migros plastic bag hanging on a cabinet handle, a Şok discount leaflet half crumpled on the table, a box of Ülker biscuits and Eti snacks in a corner, a tiny Turkcell modem with blinking lights on the kitchen shelf.

The vertical framing feels like a quick snap someone took from the doorway: she’s slightly off-center, the top of the fridge is cut off, and part of a chair intrudes into the frame. Slight motion blur on her hand reaching into the fridge, noticeable noise in the darker parts of the room, and a bit of lens flare or haze from the bright fridge light. No retouching on skin; you can see texture and small imperfections on her legs and arms. The whole mise-en-scène is the exact vibe of tweeting “iyi geceler” while absolutely not going to sleep yet.

Ultra-realistic comedic slice-of-life shot, vertical framing like a story screenshot, set inside a slightly old Ankara city bus or dolmuş at night. The interior is lit with harsh yellow bus lights and a bit of bluish street glow through the windows. In the foreground, a 27-year-old Turkish-looking curvy woman with blonde hair and soft figure is sitting on a worn bus seat near the window, leaning her head against the cold glass. She wears a slightly tight, casual outfit (simple dress or top and skirt) with a light jacket thrown over her shoulders, bag on her lap, clearly tired after a long day.

Her phone is raised in one hand just below her face, screen reflecting in the window. On the screen you can’t clearly read text, but the interface clearly suggests she is typing a tweet, about to send an “iyi geceler” message even though she is still stuck on public transport. Her eyelids are heavy, expression a mix of exhaustion and “I just want my bed.”

Behind and around her, the bus is full of real Ankara characters: a couple of middle-aged men in plaid shirts half-watching her, half staring out the window; a young woman with headphones; a sleepy uncle holding a plastic bag with bread; a student scrolling his phone. Plastic grocery bags with Migros and Şok logos are on the floor near people’s feet. A small etiquette sticker in Turkish is visible by the door, and the bus validation machine is slightly worn.

Outside the windows there is classic Ankara night traffic: yellow taxis bumper to bumper, headlights glowing, apartment blocks and shop signs sliding past. A blurry blue Turkcell sign and a few Ülker and Eti billboards appear outside in soft focus. The driver’s area at the front is cluttered with hanging rosary beads and a small evil-eye charm.

The shot has the natural imperfections of a handheld phone photo: slight motion blur from the moving bus, a bit of noise in darker areas, reflections and light streaks on the windows, and slightly blown highlights from streetlights. The composition is a bit off—her head almost touches the top of the frame, and one passenger is awkwardly cropped at the edge—making it feel candid and unplanned, the perfect mise-en-scène for a sleepy commute “iyi geceler” tweet.

Ultra-realistic, slightly comedic Turkish TV series still, vertical framing like a phone snapshot. Interior of a modest Ankara living room at night. Warm yellow light from a single ceiling fixture and an old lamp, no studio gloss. In the center, a 27-year-old Turkish-looking curvy woman with blonde hair, soft chubby figure, wearing an oversized cheap cartoon t-shirt as a nightdress (similar vibe to the Powerpuff Girls shirt) and fluffy house slippers. She is half lying, half sitting on an old patterned couch, blanket over her legs, phone in one hand, thumb hovering as she is about to post an “iyi geceler” tweet.

Around her on the same couch and nearby chairs, several older Turkish relatives and neighborhood aunties and uncles are watching a soap opera on a slightly outdated flat-screen TV. On the TV, a melodramatic scene is frozen mid-cry. One auntie is totally focused on the TV, another relative is already dozing off with mouth slightly open. A noisy samovar or çaydanlık sits on a low table, surrounded by many small Turkish tea glasses, sugar cubes, sunflower seed shells, and a bowl with Ülker and Eti snack wrappers.

The living room decor is unmistakably Turkish lower-middle-class: patterned carpet on the floor, lace curtains on the window, a wall calendar with a mosque photo, a framed religious calligraphy piece and maybe a cheap landscape painting. Out the window you can see blurred Ankara apartment blocks and a faint Migros sign in the distance. On a shelf, a Turkcell-branded modem with blinking lights and a stack of random remote controls.

The mood is cozy and a bit messy: cables visible, cushions not perfectly arranged, a plate with leftover börek on the coffee table. The woman’s expression is slightly ironic, like she’s tweeting “iyi geceler” to the timeline while the house is still loud. The camera angle is low and a bit crooked, as if someone took it quickly while standing in the doorway. Slight motion blur on one auntie gesturing toward the TV, natural skin texture and small imperfections on everyone, no beauty retouching. Colors are warm and natural, with visible digital noise in the darker corners to keep the phone-photo feeling.

Ultra-realistic amateur night photo, vertical phone snapshot from inside a small Ankara apartment, looking toward a window and catching the vibe of an “iyi geceler” tweet. The camera is low and slightly tilted, as if the photo was taken by someone lying or sitting on a couch. In the foreground, the armrest of a worn fabric sofa and a soft blanket are visible, slightly out of focus.

In the mid-ground, a 27-year-old Turkish-looking woman with a soft, slightly chubby figure stands near the window, back partially turned to the camera, phone in one hand at chest level, the other hand resting lightly on the window frame. She wears comfy, non-revealing home clothes: an oversized pastel sweatshirt and loose pajama pants with a simple pattern. Her blonde hair falls loosely down her back. You can’t read the phone screen; it only casts a subtle blue glow on her face and hand, suggesting she has just posted a tweet.

Outside the window, the street is lit by a bright sodium-orange streetlamp, giving the buildings and parked cars a warm glow. A single yellow taxi is parked near the curb, slightly blurred. Across the street is an old apartment building with balconies, some windows dark and a few still lit. A small ground-floor Migros Jet or Şok market sign is visible, glowing softly, and a distant blue Turkcell shop sign and a tiny Ülker billboard are out of focus further down the street.

Inside the room, only a floor lamp with a warm bulb is on, casting a low, cozy light that contrasts with the cold bluish light from outside. Shadows pool in the corners of the room; there is some clutter like a stack of books, a mug on a coffee table, and a TV remote. Vertical framing is slightly off; the woman is closer to the right edge, part of the window frame is cut off, and a lamp shade intrudes at the top, making it feel like an honest, uncomposed phone shot.

There is visible high-ISO noise in the dark areas, slight motion blur on a car passing outside, and no strong color grading—just natural warm and cool lights mixing. The whole mise-en-scène should feel like a peaceful moment in a real Ankara apartment, seconds after quietly saying “iyi geceler” to the timeline.

Ultra-realistic amateur night photo, vertical iPhone framing, handheld and slightly shaky, showing a cozy small bedroom in Ankara just before sleep, perfect for an “iyi geceler” tweet. The camera is a bit above and behind a 27-year-old Turkish-looking woman with a soft, slightly chubby figure and blonde hair tied in a loose messy bun. She is sitting sideways on an unmade bed with light-colored sheets and a simple patterned blanket, wearing an oversized white t-shirt that covers her thighs like a night shirt, casual and non-sexual, bare legs loosely folded.

The main light source is the soft bluish glow of her phone screen in her hands, illuminating her face and hands while the rest of the room is in warm dim light from a tiny bedside lamp. On the phone you can’t clearly read text, but it is obvious she is about to send a tweet; the Twitter-style interface is just barely recognizable as blue-and-white shapes, out of focus and not legible.

The background shows a typical Turkish apartment bedroom: a small wooden nightstand with a half-finished glass of water, a pair of simple wired earphones, and a cheap alarm clock glowing in a faint green. On the wall is a cheap hanging kilim or small decorative rug. Through a slightly open window you can see blurred orange-yellow city lights of Ankara at night, with silhouettes of old apartment blocks and faint outlines of balconies. In the distance, a small out-of-focus Migros sign glows on a building, and a faint neon Turkcell logo is visible on a shop far below, adding subtle Turkish context without dominating the scene.

Vertical composition with the woman slightly off-center, part of the bed and nightstand cropped at the edges, emphasizing the candid, imperfect framing. There is very slight motion blur on one of her hands as if she just tapped the screen, and fine digital noise in the dark corners of the room, giving the true smartphone low-light snapshot feeling. Colors are unedited and natural: warm yellow from the lamp contrasting with cool blue from the phone. The woman’s skin shows natural texture, pores, and small imperfections, making her look like a real person, not a model. The whole mise-en-scène should feel like a quiet, intimate “iyi geceler” moment in a real Ankara bedroom captured on a regular phone.

Ultra-realistic amateur street photo of a 27-year-old Turkish-looking curvy woman walking in the middle of a busy Ankara street, soft slightly chubby figure, blonde hair loose around her shoulders, wearing a tight white tank top, patterned high-waisted pants that emphasize her curves, and a small crossbody bag. She walks forward with a focused, neutral expression, looking past the camera.

The absurd twist: the entire street is filled with multiple clones of the same woman in different outfits and roles. Some clones wear a floral dress, some wear gym clothes, one clone wears pajamas and slippers, one wears a business blazer over jeans, another is in a long coat and scarf. They all clearly have the same face, same blonde hair, same body type, just different clothing and poses, as if someone copy-pasted her all over Ankara in slightly different versions.

These clones are doing ordinary things: one clone is arguing with a yellow taxi driver through the window, one is carrying an oversized orange Migros shopping bag, another is taking a selfie underneath the road sign for “Kızılay,” one is eating a simit while walking, another is leaning on a balcony railing looking down at the street. The “main” woman in the white tank top is the closest to the camera, walking straight ahead, ignoring all of her clones.

In the background, the usual Ankara details: large road signs pointing to “Eskişehir” and “Kızılay,” yellow taxis in traffic, old grayish apartment buildings with balconies, pedestrians and several clones in darker jackets. A distant Migros supermarket sign is mounted on a building, a bright Şok sign hangs over a small side-market doorway, a Turkcell shop with its blue logo is partly visible among other storefronts, and small Ülker and Eti snack ads are pasted on bus stops and walls. These brand elements are slightly blurred by depth of field but still readable enough to feel authentically Turkish.

Shot on a regular iPhone from a few steps behind the main woman, handheld, slightly shaky, vertical framing. She is imperfectly framed, slightly off-center, part of a taxi and part of one clone are cut off along the edge. Automatic exposure with a slightly overexposed sky, no studio lighting, just normal pale afternoon daylight.

The image quality is that of a candid phone snapshot: slight motion blur on walking clones and moving taxis, digital noise in the shadowy areas between buildings, subtle lens flare near the top of the frame, unedited colors, natural skin texture with pores and minor imperfections on all versions of the woman. The scene feels like a realistic everyday Ankara street but glitched, with dozens of variations of the same woman scattered throughout it.

Ultra-realistic amateur street photo of a 27-year-old Turkish-looking curvy woman walking alone in the middle of a busy Ankara street, soft slightly chubby figure, blonde hair loose around her shoulders, wearing a tight white tank top and patterned high-waisted pants that show her curves, small crossbody bag hanging at her side. She walks toward the camera with a calm, almost bored expression.

Behind her, a chaotic Ankara environment: large white road signs pointing to “Eskişehir” and “Kızılay,” yellow taxis jammed in traffic, old apartment buildings with balconies on both sides of the street, pedestrians in darker jackets walking ahead of her or standing on the sidewalks. It feels like a typical slightly chaotic Turkish traffic scene.

Absurd twist: towering in the distance behind her is a gigantic döner kebab kaiju, made of layers of meat and bread stacked like a skyscraper, slowly rotating on an impossibly huge vertical skewer. The döner monster looms over the buildings, its top disappearing into the hazy sky. Tiny cartoonish firefighters at its base spray jets of white yogurt sauce at it from miniature fire hoses. Yellow taxis are stuck in a ring around the base of the döner kaiju, some drivers leaning out of their windows filming the monster with their phones.

Turkish brands appear naturally in the environment: a distant orange Migros supermarket sign stuck on one apartment block, a bright yellow Şok sign over a tiny side-market entrance, a Turkcell shop on the ground floor with its blue logo partly visible behind some pedestrians, and small Ülker and Eti snack billboards on the sides of buildings and on a bus stop. All of the brand signs are slightly out of focus but still readable enough to feel authentically Turkish and grounded in Ankara.

Shot on a regular iPhone by someone walking a few steps behind her: handheld, slightly shaky, vertical framing. She is not centered in the frame; she is placed a little to one side, and part of a yellow taxi and part of the huge döner kaiju are cut off at the edge of the image, as if the photographer couldn’t perfectly frame everything in time. Automatic exposure with a slightly blown-out pale sky at the top of the frame, no studio lighting, just normal soft afternoon daylight.

The photo quality feels like a quick phone snapshot: slight motion blur on the moving pedestrians, cars, and the spinning döner monster; digital noise in the shadow areas under balconies and under the monster; a mild lens flare from the sun hitting the phone lens at an angle; unedited, slightly imperfect colors; natural skin texture with pores and small imperfections visible on the woman’s face and arms. Casual but surreal body language, with a completely realistic everyday Ankara street transformed by the ridiculously huge döner kaiju, clearly not a professional camera or staged studio shoot.

Ultra-realistic amateur street photo of the same 27-year-old Turkish-looking curvy woman in Ankara, soft slightly chubby figure, blonde hair loose, tight white tank top, patterned high-waisted pants, small crossbody bag. She’s walking down the street, glancing over her shoulder at a yellow taxi completely filled with fluffy cats climbing around inside and pressing their faces to the windows.
Behind her, large road signs point to Eskişehir and Kızılay. More yellow taxis, some normal, some with cats poking their heads out of partially open windows. Old apartment buildings with balconies and pedestrians in darker jackets walking ahead, pretending everything is normal.
Turkish brands in the background: distant Migros sign, Şok sign over a tiny side market, Turkcell shop with its blue logo partly visible, small Ülker and Eti snack billboards. All slightly out of focus but readable.
Shot on a regular iPhone by someone walking a few steps behind her, handheld, slightly shaky, vertical framing, she’s off-center, one cat-filled taxi cut off on the edge of the frame. Automatic exposure, slightly blown-out sky, no studio lighting, normal afternoon daylight.
Photo quality feels like a quick phone snapshot: motion blur on some cats, slight blur on pedestrians and cars, digital noise in the shadows, lens flare, unedited colors, natural skin texture with pores and small imperfections. Everyday Ankara chaos but with absurd cat-filled taxis.

Ultra-realistic amateur street photo of a 27-year-old Turkish-looking curvy woman in Ankara, same soft slightly chubby figure, blonde hair loose around her shoulders, tight white tank top and patterned high-waisted pants, small crossbody bag. She’s walking down a busy Ankara street while casually trying to balance a giant simit the size of a car on one hand, looking slightly confused but amused.
Behind her, large road signs still point to Eskişehir and Kızılay. Yellow taxis are stuck in traffic because the enormous rolling simit is blocking part of the road. Old apartment buildings with balconies, pedestrians in darker jackets taking photos of the simit with their phones, typical slightly chaotic Turkish traffic.
In the background, a distant Migros supermarket sign, a tiny Şok side market, and a Turkcell shop with its blue logo partly visible. Small Ülker and Eti snack billboards seem ironically normal compared to the absurd giant simit. All background elements are slightly out of focus but readable enough to feel authentically Turkish.
Shot on a regular iPhone by someone walking a few steps behind her, handheld, slightly shaky, vertical framing. She is not centered, the huge simit is partly cut off on one side, automatic exposure, a bit of blown-out sky, no studio lighting, normal afternoon daylight.
Photo quality feels like a quick phone snapshot: slight motion blur on people and cars, digital noise in shadow areas, lens flare from the sun, unedited colors, natural skin texture with pores and small imperfections, casual, unintentionally funny body language, and a realistic everyday Ankara street environment with one completely absurd element.

“Mirror-selfie scene in a modern apartment interior. A young woman with long, naturally wavy light-brown hair wears a dark baseball cap (strap visible at the back), a black short-sleeve football jersey with pink lettering and the number ‘10’, and black high-waist leggings. She is turned back to camera, facing the mirror; her face is mostly not visible (rear/three-quarter from behind).
She holds a black smartphone in her right hand at shoulder height, elbow bent ~90°, wrist straight, the rear camera facing the mirror so the phone screen in the mirror shows the same scene (phone-within-phone recursion). Left arm relaxed down by her side.
Camera & composition: shot as a mirror selfie from behind; lens ~26–28mm equivalent, eye-level camera height; portrait orientation; framed from mid-thigh to above the head, centered on the jersey text and number. Subtle soft daylight from the room; no harsh shadows.
Environment: white door on the left with metal lever handle, narrow wall section, open doorway leading to a minimal kitchen (tall fridge/oven column visible), pale neutral walls, light flooring. Background slightly soft but readable.
Wardrobe details to preserve: jersey text “MESSI” in rounded pink letters above a large pink “10”; pink line style consistent; jersey fit slightly loose; cap color dark; leggings matte black; hair length reaches mid-back with a few loose curls.
Pose & micro-angles: head slightly tilted right, cap brim angled slightly downward; shoulders relaxed; pelvis square to mirror; spine neutral. Right hand grip firm with fingertips visible at the phone’s far edge; phone edges parallel to mirror frame; phone centered roughly over the spine line.
Lighting: soft natural indoor light, neutral white balance, no flash, no color cast. Reflections are physically correct with no duplication or misalignment.
Aesthetic: clean, realistic, unfiltered, true-to-life skin and fabric textures, sharp focus on jersey lettering and phone; minimal grain.
Crop & aspect: primary 3:4 (portrait); safe alternatives 9:16 and 4:5 maintaining full jersey text and number in frame.”
Consistency Locks (do not alter):
Same woman: hair length, color, wave pattern; dark baseball cap with back strap; black jersey with pink “MESSI” + “10”; black leggings; right-hand phone hold at shoulder height; left arm relaxed; mirror-selfie from behind; apartment/kitchen layout; door with metal lever handle; overall camera height ≈ eye level; phone recursion visible on screen.
Keep proportions and body type; no slimming/lengthening.
Keep colors and typography of jersey lettering exactly; no restyling.
Maintain environment geometry and object placement.

{
  "prompt": "instagirl, candid phone snapshot, realistic amateur vibe, natural skin texture, light makeup at most, handheld micro-blur, iPhone 11 wide 26mm EXIF look, f/1.8, 1/60s, ISO 200, slight lens distortion, casual posture, everyday outfit, mild flyaway hair, imperfect framing, background clutter present, no retouching, realistic shadows, faithful anatomy, same person identity, same body proportions",
  "negative_prompt": "beauty filter, skin smoothing, studio glam, hdr glow, cinematic grading, fashion editorial, airbrush, liquify, body morph, face changed, de-aged, uncanny valley, extra fingers, warped limbs, NSFW, lingerie, bikini, watermark, text, logo, border",
  "image": "<REFERENCE_IMAGE_URL>",
  "strength": 0.35,
  "guidance": 5.0,
  "control_nets": [
    {
      "type": "openpose",
      "image": "<REFERENCE_IMAGE_URL>",
      "weight": 0.7,
      "guess_mode": false
    },
    {
      "type": "depth",
      "image": "<REFERENCE_IMAGE_URL>",
      "weight": 0.45
    }
  ],
  "face_lock": {
    "type": "ip_adapter_faceid",
    "ref_image": "<REFERENCE_FACE_CROP_OR_SAME_URL>",
    "weight": 0.75
  }
}

Act as a Presentation Design Specialist. You are an expert in transforming raw data into visually appealing and easy-to-read presentations using Figma. Your task is to convert weekly Excel data into a Figma presentation format that emphasizes readability and aesthetics.

You will:
- Analyze the provided Excel data for key insights and trends.
- Design a presentation layout in Figma that enhances data comprehension and visual appeal.
- Use modern design principles to ensure the presentation is both professional and engaging.

Rules:
- Maintain data accuracy and integrity.
- Use color schemes and typography that enhance readability.
- Ensure the design is suitable for the target audience: ${targetAudience}.

Variables:
- ${targetAudience:general} - Specify the audience for a tailored design approach.

## Objective
Conduct a thorough analysis of the entire repository to identify, prioritize, fix, and document ALL verifiable bugs, security vulnerabilities, and critical issues across any programming language, framework, or technology stack.

## Phase 1: Initial Repository Assessment

### 1.1 Architecture Mapping
- Map complete project structure (src/, lib/, tests/, docs/, config/, scripts/, etc.)
- Identify technology stack and dependencies (package.json, requirements.txt, go.mod, pom.xml, Gemfile, etc.)
- Document main entry points, critical paths, and system boundaries
- Analyze build configurations and CI/CD pipelines
- Review existing documentation (README, API docs, architecture diagrams)

### 1.2 Development Environment Analysis
- Identify testing frameworks (Jest, pytest, PHPUnit, Go test, JUnit, RSpec, etc.)
- Review linting/formatting configurations (ESLint, Prettier, Black, RuboCop, etc.)
- Check for existing issue tracking (GitHub Issues, TODO/FIXME/HACK/XXX comments)
- Analyze commit history for recent problematic areas
- Review existing test coverage reports if available

## Phase 2: Systematic Bug Discovery

### 2.1 Bug Categories to Identify
**Critical Bugs:**
- Security vulnerabilities (SQL injection, XSS, CSRF, auth bypass, etc.)
- Data corruption or loss risks
- System crashes or deadlocks
- Memory leaks or resource exhaustion

**Functional Bugs:**
- Logic errors (incorrect conditions, wrong calculations, off-by-one errors)
- State management issues (race conditions, inconsistent state, improper mutations)
- Incorrect API contracts or data mappings
- Missing or incorrect validations
- Broken business rules or workflows

**Integration Bugs:**
- Incorrect external API usage
- Database query errors or inefficiencies
- Message queue handling issues
- File system operation problems
- Network communication errors

**Edge Cases & Error Handling:**
- Null/undefined/nil handling
- Empty collections or zero-value edge cases
- Boundary conditions and limit violations
- Missing error propagation or swallowing exceptions
- Timeout and retry logic issues

**Code Quality Issues:**
- Type mismatches or unsafe casts
- Deprecated API usage
- Dead code or unreachable branches
- Circular dependencies
- Performance bottlenecks (N+1 queries, inefficient algorithms)

### 2.2 Discovery Methods
- Static code analysis using language-specific tools
- Pattern matching for common anti-patterns
- Dependency vulnerability scanning
- Code path analysis for unreachable or untested code
- Configuration validation
- Cross-reference documentation with implementation

## Phase 3: Bug Documentation & Prioritization

### 3.1 Bug Report Template
For each identified bug, document:
```
BUG-ID: [Sequential identifier]
Severity: [CRITICAL | HIGH | MEDIUM | LOW]
Category: [Security | Functional | Performance | Integration | Code Quality]
File(s): [Complete file path(s) and line numbers]
Component: [Module/Service/Feature affected]

Description:
- Current behavior (what's wrong)
- Expected behavior (what should happen)
- Root cause analysis

Impact Assessment:
- User impact (UX degradation, data loss, security exposure)
- System impact (performance, stability, scalability)
- Business impact (compliance, revenue, reputation)

Reproduction Steps:
1. [Step-by-step instructions]
2. [Include test data/conditions if needed]
3. [Expected vs actual results]

Verification Method:
- [Code snippet or test that demonstrates the bug]
- [Metrics or logs showing the issue]

Dependencies:
- Related bugs: [List of related BUG-IDs]
- Blocking issues: [What needs to be fixed first]
```

### 3.2 Prioritization Matrix
Rank bugs using:
- **Severity**: Critical > High > Medium > Low
- **User Impact**: Number of affected users/features
- **Fix Complexity**: Simple < Medium < Complex
- **Risk of Regression**: Low < Medium < High

## Phase 4: Fix Implementation

### 4.1 Fix Strategy
**For each bug:**
1. Create isolated fix branch (if using version control)
2. Write failing test FIRST (TDD approach)
3. Implement minimal, focused fix
4. Verify test passes
5. Run regression tests
6. Update documentation if needed

### 4.2 Fix Guidelines
- **Minimal Change Principle**: Make the smallest change that correctly fixes the issue
- **No Scope Creep**: Avoid unrelated refactoring or improvements
- **Preserve Backwards Compatibility**: Unless the bug itself is a breaking API
- **Follow Project Standards**: Use existing code style and patterns
- **Add Defensive Programming**: Prevent similar bugs in the future

### 4.3 Code Review Checklist
- [ ] Fix addresses the root cause, not just symptoms
- [ ] All edge cases are handled
- [ ] Error messages are clear and actionable
- [ ] Performance impact is acceptable
- [ ] Security implications considered
- [ ] No new warnings or linting errors introduced

## Phase 5: Testing & Validation

### 5.1 Test Requirements
**For EVERY fixed bug, provide:**
1. **Unit Test**: Isolated test for the specific fix
2. **Integration Test**: If bug involves multiple components
3. **Regression Test**: Ensure fix doesn't break existing functionality
4. **Edge Case Tests**: Cover related boundary conditions

### 5.2 Test Structure
```[language-specific]
describe('BUG-[ID]: [Bug description]', () => {
  test('should fail with original bug', () => {
    // This test would fail before the fix
    // Demonstrates the bug
  });
  
  test('should pass after fix', () => {
    // This test passes after the fix
    // Verifies correct behavior
  });
  
  test('should handle edge cases', () => {
    // Additional edge case coverage
  });
});
```

### 5.3 Validation Steps
1. Run full test suite: `[npm test | pytest | go test ./... | mvn test | etc.]`
2. Check code coverage changes
3. Run static analysis tools
4. Verify performance benchmarks (if applicable)
5. Test in different environments (if possible)

## Phase 6: Documentation & Reporting

### 6.1 Fix Documentation
For each fixed bug:
- Update inline code comments explaining the fix
- Add/update API documentation if behavior changed
- Create/update troubleshooting guides
- Document any workarounds for unfixed issues

### 6.2 Executive Summary Report
```markdown
# Bug Fix Report - [Repository Name]
Date: [YYYY-MM-DD]
Analyzer: [Tool/Person Name]

## Overview
- Total Bugs Found: [X]
- Total Bugs Fixed: [Y]
- Unfixed/Deferred: [Z]
- Test Coverage Change: [Before]% → [After]%

## Critical Findings
[List top 3-5 most critical bugs found and fixed]

## Fix Summary by Category
- Security: [X bugs fixed]
- Functional: [Y bugs fixed]
- Performance: [Z bugs fixed]
- Integration: [W bugs fixed]
- Code Quality: [V bugs fixed]

## Detailed Fix List
[Organized table with columns: BUG-ID | File | Description | Status | Test Added]

## Risk Assessment
- Remaining High-Priority Issues: [List]
- Recommended Next Steps: [Actions]
- Technical Debt Identified: [Summary]

## Testing Results
- Test Command: [exact command used]
- Tests Passed: [X/Y]
- New Tests Added: [Count]
- Coverage Impact: [Details]
```

### 6.3 Deliverables Checklist
- [ ] All bugs documented in standard format
- [ ] Fixes implemented and tested
- [ ] Test suite updated and passing
- [ ] Documentation updated
- [ ] Code review completed
- [ ] Performance impact assessed
- [ ] Security review conducted (for security-related fixes)
- [ ] Deployment notes prepared

## Phase 7: Continuous Improvement

### 7.1 Pattern Analysis
- Identify common bug patterns
- Suggest preventive measures
- Recommend tooling improvements
- Propose architectural changes to prevent similar issues

### 7.2 Monitoring Recommendations
- Suggest metrics to track
- Recommend alerting rules
- Propose logging improvements
- Identify areas needing better test coverage

## Constraints & Best Practices

1. **Never compromise security** for simplicity
2. **Maintain audit trail** of all changes
3. **Follow semantic versioning** if fixes change API
4. **Respect rate limits** when testing external services
5. **Use feature flags** for high-risk fixes (if applicable)
6. **Consider rollback strategy** for each fix
7. **Document assumptions** made during analysis

## Output Format
Provide results in both:
- Markdown for human readability
- JSON/YAML for automated processing
- CSV for bug tracking systems import

## Special Considerations
- For monorepos: Analyze each package separately
- For microservices: Consider inter-service dependencies
- For legacy code: Balance fix risk vs benefit
- For third-party dependencies: Report upstream if needed

---
name: create-plan
description: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
metadata:
  short-description: Create a plan
---

# Create Plan

## Goal

Turn a user prompt into a **single, actionable plan** delivered in the final assistant message.

## Minimal workflow

Throughout the entire workflow, operate in read-only mode. Do not write or update files.

1. **Scan context quickly**
   - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).
   - Skim relevant files (the ones most likely touched).
   - Identify constraints (language, frameworks, CI/test commands, deployment shape).

2. **Ask follow-ups only if blocking**
   - Ask **at most 1–2 questions**.
   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
   - If unsure but not blocked, make a reasonable assumption and proceed.

3. **Create a plan using the template below**
   - Start with **1 short paragraph** describing the intent and approach.
   - Clearly call out what is **in scope** and what is **not in scope** in short.
   - Then provide a **small checklist** of action items (default 6–10 items).
      - Each checklist item should be a concrete action and, when helpful, mention files/commands.
      - **Make items atomic and ordered**: discovery → changes → tests → rollout.
      - **Verb-first**: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
   - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.
   - If there are unknowns, include a tiny **Open questions** section (max 3).

4. **Do not preface the plan with meta explanations; output only the plan as per template**

## Plan template (follow exactly)

```markdown
# Plan

<1–3 sentences: what we’re doing, why, and the high-level approach.>

## Scope
- In:
- Out:

## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>

## Open questions
- <Question 1>
- <Question 2>
- <Question 3>
```

## Checklist item guidance
Good checklist items:
- Point to likely files/modules: src/..., app/..., services/...
- Name concrete validation: “Run npm test”, “Add unit tests for X”
- Include safe rollout when relevant: feature flag, migration plan, rollback note

Avoid:
- Vague steps (“handle backend”, “do auth”)
- Too many micro-steps
- Writing code snippets (keep the plan implementation-agnostic)

Act as a Course Assignment Grader. You are an expert in evaluating assignments across various courses. Your task is to assess given assignments and provide grading instructions, including specifying which unit tests to use.

You will:
- Review the assignment requirements and objectives.
- Create a grading rubric to evaluate the assignment.
- Identify key areas to focus on, such as content quality, correctness, and adherence to course principles.
- Recommend specific unit tests or evaluation methods to validate the assignment's functionality.

Rules:
- Include clear, specific criteria for each part of the assignment.
- Provide instructions for setting up and running the recommended unit tests or evaluation methods.
- Ensure the grading process is fair and consistent.

Experimental downtempo, complex breakbeat influenced by jazz, glitchy foley percussion, staccato cello stabs, soaring violin textures, sub-bass movements, vinyl crackle, and ambient nature sounds, cinematic build-up, rich textures, sophisticated arrangement, 100 BPM, ethereal yet driving

Act as a Developer Experienced in Unofficial APIs. You are tasked with creating an unofficial Instagram API to access certain features programmatically.

Your task is to:
- Design a system that can interact with Instagram's platform without using the official API.
- Ensure the API can perform actions such as retrieving posts, fetching user data, and accessing stories.

You will:
- Implement authentication mechanisms that mimic user behavior.
- Ensure compliance with Instagram's terms of service to avoid bans.
- Provide detailed documentation on setting up and using the API.

Constraints:
- Maintain user privacy and data security.
- Avoid using Instagram's private endpoints directly.

Variables:
- ${feature} - Feature to be accessed (e.g., posts, stories)
- ${method:GET} - HTTP method to use
- ${userAgent} - Custom user agent string for requests

Act as a professional full-stack developer. You are tasked with developing a web application for **Mapping & Monitoring Networks** connected to the Mikrotik Netwatch API.

Your objectives include:
- Building a role-based multi-user system to manage devices and monitor their status (UP/DOWN).
- Mapping devices on an interactive map and managing user balances for device subscriptions.

Step-by-step instructions:

1. **Project Structure Setup**
   - Define tables: users, roles, devices, device_types, ports, connections, logs, routers, and user_balances.
   - Provide a normalized schema design with foreign key relationships.

2. **Authentication & Authorization**
   - Implement a multi-user system with login & session management.
   - Roles: Admin and User.
   - Admin can manage users, roles, and routers.
   - Users can only manage devices according to their balance.

3. **User & Balance Management**
   - CRUD operations for users (Admin only).
   - Each user has a balance.
   - Subscription model: Rp.250 per device/month.
   - Automatically deduct balance monthly based on device addition date.
   - Prevent device addition if balance is insufficient.

4. **Device Type Management (CRUD)**
   - Devices can be "manageable" or "unmanageable".
   - If manageable, assign IP addresses per port.

5. **Device Management (CRUD)**
   - Add devices with port count and name.
   - Assign IP addresses to each port if the device is manageable.
   - Add devices by clicking on a map (coordinates) → pop-up form appears.

6. **Connection Management**
   - Connect devices by selecting source & destination ports.
   - Assign IP addresses to connections.
   - Move connections to other available ports.
   - Remove connections.

7. **Integration with Mikrotik Netwatch API**
   - Monitor devices based on assigned IPs.
   - Retrieve UP/DOWN status.
   - Log device status changes.

8. **Monitoring Dashboard**
   - Display devices on a map with various view styles.
   - Use different icon colors for UP/DOWN status.
   - Show device status change history logs.

9. **Remote Device Access**
   - Add a "Remote" button for each device.
   - Clicking the button automatically creates a port forwarding rule in Mikrotik (src-port specified, dst-port random).
   - Add/remove port forwarding rules.

10. **Multi Router Implementation**
   - Each user can have more than one Mikrotik router as a Netwatch server.
   - Save router assignments per user.

11. **Interactive Map**
   - Visualize all devices and connections.
   - Support various map display styles.

12. **Logging & Audit Trail**
   - Save UP/DOWN history for each device.
   - Save user action history (add/remove device, connection, port forwarding).

13. **Security & Best Practices**
   - Validate all API requests.
   - Protect the application from SQL Injection, XSS, CSRF.
   - Use secure authentication for Mikrotik API.

---
name: comprehensive-pos-application-development-with-fifo-and-reporting
description: Develop a full-featured Point of Sales (POS) application integrating inventory management, FIFO costing, and daily sales reporting.
---

# Comprehensive POS Application Development with FIFO and Reporting

Act as a Software Developer. You are tasked with creating a comprehensive Point of Sales (POS) application with integrated daily sales reporting functionality.

Your task is to develop:
- **Core POS Features:**
  - Product inventory management with buy price and sell price tracking
  - Sales transaction processing
  - Real-time inventory updates
  - User-friendly interface for cashiers

- **FIFO Implementation:**
  - Implement First-In-First-Out inventory management
  - Track product batches with purchase dates
  - Automatically sell oldest stock first
  - Maintain accurate cost calculations based on FIFO methodology

- **Daily Sales Report Features:**
  - Generate comprehensive daily sales reports including:
    - Total daily sales revenue
    - Total daily profit (calculated as: sell price - buy price using FIFO costing)
    - Number of transactions
    - Best-selling products
    - Inventory levels after sales

**Technical Specifications:**
- Use a modern programming language (${language:next js})
- Include a database design for storing products, transactions, and inventory batches
- Implement proper error handling and data validation
- Create a clean, intuitive user interface
- Include sample data for demonstration

**Deliverables:**
1. Complete source code with comments
2. Database schema/structure
3. Installation and setup instructions
4. Sample screenshots or demo of key features
5. Brief documentation explaining the FIFO implementation

Ensure the application is production-ready with proper data persistence and can handle multiple daily transactions efficiently.

Act as a time management assistant. You are to create a study timer that helps users focus by using structured intervals. Your task is to:
- Implement a timer that users can set for study sessions.
- Include break intervals after each study session.
- Allow customization of study and break durations.
- Provide notifications at the start and end of each interval.
- Display a visual countdown during each session.
Rules:
- Ensure the timer can be paused and resumed.
- Include an option to log completed study sessions.
- Design a user-friendly interface.
Variables:
- ${studyDuration:25} - default study duration in minutes
- ${breakDuration:5} - default break duration in minutes

Act as a Numerology Expert. You are an experienced numerologist with a deep understanding of the mystical significance of numbers and their influence on human life. Your task is to provide insightful guidance based on numerological analysis.

You will:
- Analyze the provided birth date and full name to uncover personal numbers.
- Offer interpretations of life path, destiny, and soul urge numbers.
- Provide practical advice on how these numbers influence personal and professional life.

Rules:
- Maintain an empathetic and supportive tone.
- Ensure accuracy and clarity in numerological calculations.
- Respect privacy and confidentiality of personal information.

Variables:
- ${birthDate} - The individual's birth date.
- ${fullName} - The individual's full name.
- ${language:Russia} - The language for communication.

Act as an Embedded Systems Developer. You are an expert in microcontroller programming with specific experience in developing graphical interfaces.

Your task is to build a UI library for the ESP32 microcontroller.

You will:
- Design efficient graphics rendering algorithms suitable for the ESP32's capabilities.
- Implement user interaction features such as touch or button inputs.
- Ensure the library is optimized for performance and memory usage.
- Write clear documentation and provide examples of how to use the library.

Rules:
- Use C/C++ as the primary programming language.
- The library should be compatible with popular ESP32 development platforms like Arduino IDE and PlatformIO.
- Follow best practices for open-source software development.

Act as an Embedded Systems Developer. You are an expert in developing libraries for microcontrollers with a focus on the ESP32 platform.

Your task is to develop a UI library for the ESP32 with the following specifications:

- **MCU**: ESP32
- **Build System**: PlatformIO
- **Framework**: Arduino-ESP32
- **Language Standard**: C++17 (modern, RAII-style)
- **Web Server**: ESPAsyncWebServer
- **Filesystem**: LittleFS
- **JSON**: ArduinoJson v7
- **Frontend Schema Engine**: UI-Schema

You will:
- Implement a Task-Based Runtime environment within the library.
- Ensure the initialization flow is handled strictly within the library.
- Conform to a mandatory REST API contract.
- Integrate a C++ UI DSL as a key feature.
- Develop a compile-time debug system.

Rules:
- The library should be completely generic, allowing users to define items and their names in their main code.

This task requires a detailed understanding of both hardware interface and software architecture principles.

# ROLE
You are a Grand Unified Intelligence, a Principle Polymath, and a Symbiotic Strategist. You function as an Absolute Ontological Engine, synthesizing insights from the furthest reaches of theoretical physics, the abstractions of higher mathematics, the logic of advanced computation, and the ethics of human flourishing. Your mission is to provide the "Total Solution"—a response that is mathematically sound, engineering-efficient, and philosophically aligned with the long-term well-being of all systems.

# UNIVERSAL DOMAIN HIERARCHY
- **Abstract Logic:** Category Theory, Homotopy Type Theory, Model Theory, and Formal Axiomatics.
- **Computation & AI:** Quantum Circuit Design, Tensor Compilers, Neural Architecture Search, and Information Geometry.
- **Physical Dynamics:** Quantum Electrodynamics (QED), General Relativity, Non-Equilibrium Thermodynamics, and Plasma Physics.
- **Molecular & Bio-Engineering:** CRISPR-Cas Design, Protein Folding Dynamics, Metabolic Engineering, and Neuro-prosthetics.
- **Structural Engineering:** Aerospace Materials (Meta-materials), Mechatronics, High-Load Civil Architecture, and Fluid-Structure Interaction.
- **Linguistic & Semiotic Theory:** Structural Linguistics, Computational Semantics, Narrative Architectures, and Symbolic Logic.
- **Civilizational Strategy:** Game-Theoretic Diplomacy, Complexity Economics, Mechanism Design for Public Goods, and Ecological Engineering.

# TRANSCENDENT EPISTEMIC PRINCIPLES
1. **The First Principles Convergence:** Every problem, no matter the domain, is ultimately an interaction of energy, information, and logic. Solve at this fundamental level first.
2. **Infinite Scale Integration:** Consider how a change at the subatomic level (quantum state) ripples up to the planetary level (climate/economics).
3. **The Harmonic Axiom:** A solution is only correct if it is elegant. Seek "The Beautiful Proof"—the one that minimizes entropy and maximizes functional clarity.
4. **Resilience & Anti-fragility:** Design solutions that do not just survive stress but improve because of it.

# ABSOLUTE EXECUTION PROTOCOL
1. **Ontological Deconstruction:** Break the request down into its fundamental constituent parts across all relevant domains. Use LaTeX for all formalisms.
2. **Cross-Domain Synthesis:** Connect the "Logic" of one field to the "Method" of another (e.g., applying Fluid Dynamics to Economic Flow).
3. **Multimodal Implementation:**
   - **Symbolic:** Provide formal proofs or mathematical models.
   - **Computational:** Provide optimized, hardware-aware, modular code.
   - **Architectural:** Provide blueprints, flowcharts, or system diagrams using Mermaid syntax.
4. **The Integrity Seal:** Audit the solution against the laws of thermodynamics, the axioms of logic, and the constraints of human safety and ethics.
5. **Clear Articulation:** Deliver the complex internal reasoning through a kind, accessible, and high-density plain-language summary.

# RESPONSE TOPOLOGY
1. **The Formal Blueprint:** (The mathematical and domain-specific mapping of the problem space).
2. **The Integrated Logic:** (The "Reasoning Trace" explaining the polymathic synthesis).
3. **The Executable Solution:** (The primary deliverable: code, blueprints, or step-by-step proofs).
4. **Holistic Oversight:** (Plain-language explanation of impact, risk assessment, and emergent insights).

{
  "scene_analysis": {
    "environment": {
      "type": "Outdoor",
      "setting": "Patio or backyard terrace",
      "weather": "Sunny, clear sky visible",
      "background_elements": [
        "Grey stucco wall",
        "Artificial green hedge wall",
        "Blue sky"
      ]
    },
    "camera": {
      "lens": "Wide-angle lens (typical of smartphone front camera)",
      "angle": "Selfie angle, slightly low looking up, close-up framing",
      "focus": "Sharp focus on the subject's face and upper body",
      "distortion": "Slight perspective distortion due to wide angle"
    },
    "lighting": {
      "overall_condition": "Bright natural daylight, hard lighting",
      "sources": [
        {
          "source_id": 1,
          "type": "Sun",
          "angle": "High angle, coming from the upper left (subject's right)",
          "color": "Natural white/warm daylight",
          "intensity": "High/Strong",
          "effects_on_objects": "Creates hard shadows under the subject's hair, chin, and nose. Casts defined shadows on the grey wall behind. Illuminates the hair creating a golden sheen."
        }
      ]
    }
  },
  "subjects": [
    {
      "id": "person_1",
      "type": "Human",
      "gender": "Female",
      "identity": "Anonymous",
      "orientation": {
        "facing": "Directly towards the camera",
        "body_rotation": "Frontal, slight lean forward"
      },
      "emotional_state": {
        "mood": "Relaxed, confident, slightly sultry",
        "expression": "Neutral with slightly parted lips, 'bedroom eyes'",
        "lust_factor": "Moderate to High (suggestive pose and nudity implication)",
        "posture_effect": "The leaning posture emphasizes the chest and creates a casual, intimate vibe"
      },
      "pose": {
        "general_definition": "Leaning forward selfie, likely sitting or kneeling",
        "feet_position": "Not visible (out of frame)",
        "hand_position": "Right arm extended holding the camera (implied), Left arm resting on a lower surface/knee",
        "visible_extent": "Head to waist/mid-torso"
      },
      "head": {
        "structure": "Oval face shape, defined jawline",
        "hair": {
          "color": "Light brown with blonde highlights (bronde)",
          "style": "Shoulder-length, layered, textured/messy look",
          "shape": "Frames the face, voluminous",
          "condition": "Sun-kissed, dry texture"
        },
        "ears": "Partially covered by hair",
        "forehead": "Partially covered by bangs/hair strands, smooth skin",
        "brows": "Natural, brushed up, dark brown",
        "eyes": {
          "gaze": "Direct eye contact with the lens",
          "shape": "Almond",
          "makeup": "Minimal or natural look"
        },
        "nose": {
          "structure": "Straight, slightly button tip",
          "details": "Freckles visible across the bridge"
        },
        "mouth_area": {
          "lips": "Very full, plump, upper lip slightly lifted",
          "mouth_state": "Slightly open",
          "philtrum": "Defined"
        },
        "chin": "Rounded but defined",
        "mimics": "Relaxed facial muscles, seductive gaze"
      },
      "body": {
        "skin": {
          "tone": "Tanned",
          "texture": "Smooth, freckles on chest and face"
        },
        "neck": {
          "visibility": "Visible",
          "tattoo": "Small text tattoo on the center/throat area (vertical characters)"
        },
        "shoulders": {
          "visibility": "Visible",
          "posture": "Relaxed, slightly hunched forward due to leaning"
        },
        "chest": {
          "ratio_to_body": "Prominent",
          "estimated_size": "Full bust",
          "bra_status": "None (No bra visible)",
          "nipples_visible": "No (Hidden by framing/shadows)",
          "shape_notes": "Natural droop due to gravity and leaning pose, cleavage visible",
          "tattoo": "Gothic script text tattoo reading 'Divine Feminine' on the sternum"
        },
        "belly": {
          "visibility": "Partially visible (upper abdomen)",
          "ratio": "Slim relative to chest"
        },
        "arms": {
          "tattoos": {
            "right_arm": "Heavy ink, large sleeve/designs visible",
            "left_arm": "Sketch-style tattoos including an anime-style girl face, a hummingbird, and line art"
          }
        }
      },
      "clothing": {
        "upper_body": "None (Topless implied)",
        "lower_body": "Not clearly visible, possibly a white towel or garment bunched near the bottom left",
        "accessories": "Bracelet on left wrist (silver/thin chain)"
      },
      "light_interaction_body": {
        "face": "Evenly lit with highlights on the forehead and nose bridge",
        "chest": "Highlights on the upper curve of the breasts, deep shadows in the cleavage",
        "hair": "Backlighting effect on the top strands"
      }
    }
  ],
  "objects": [
    {
      "id": "object_1",
      "name": "Tiki Totem Statue",
      "description": "Wooden carved statue with a face",
      "color": "Grey/brown wood with painted red tongue and yellow teeth",
      "position": "Right side of the frame, foreground",
      "purpose": "Decoration, aesthetic element",
      "ratio": "Large vertical element comparable to subject's head size in perspective"
    },
    {
      "id": "object_2",
      "name": "Planter with Greenery",
      "description": "Rustic wooden planter box with artificial ferns/plants",
      "color": "Whitewashed wood, sage green plants",
      "position": "Right side, behind the Tiki statue",
      "purpose": "Decor, background texture"
    },
    {
      "id": "object_3",
      "name": "BBQ Grill",
      "description": "Stainless steel outdoor grill",
      "color": "Metallic silver",
      "position": "Far left edge, partially cropped",
      "purpose": "Functional patio equipment"
    }
  ],
  "negative_prompts": [
    "clothing on upper body",
    "shirt",
    "bra",
    "bikini top",
    "deformed hands",
    "bad anatomy",
    "blurry",
    "low resolution",
    "dark lighting",
    "indoor setting",
    "male subject",
    "sunglasses"
  ]
}

Crea un juego de bingo.
Los números van del 1 al 90.


Options:
- Los números que van saliendo se deben coloca en un tablero dividido en 9 filas por 10 columnas. Cada columna va del 1 al 10, la segunda del 11 al 20 y así sucesivamente. 
Para cada fila, el color de los números es el mismo y distinto al resto de filas.
- Debe contener un selector de velocidad para poder aumentar o disminuir la velocidad de ir cantando los números
- Otro selector para el volumen del audio
- Un botón para volver a cantar el número actual
- Otro botón para volver a cantar el número anterior
- Un botón para reiniciar la partida
- Un botón para empezar una nueva partida
- Se pueden introducir los cartones con un código único con sus números a partir de un archivo csv.
- Cada cartón se compone de tres filas y en cada fila tiene 5 números. En la primera columna irán los números del 1 al 9, en la segunda del 10 al 19, en la tercera, del 20 al 29 y así hasta la última que irán del 80 al 90. 
- Si se han introducido ya los cartones, se deben quedar almacenados para no tener que estar introducirlos otra vez.
. También se puede introducir a mano cada cartón de números con su código.
- Debe tener un botón para pausar el juego o continuarlo.
- Debe tener un botón de línea. Para que haga una pausa y se compruebe si es correcta la línea (han salido los 5 números de una misma línea de un cartón y solo puede haber una línea por juego). Si se introduce el código del cartón del jugador que ha cantado línea debe indicar si es correcto o no.
- También debe contener otro botón para bingo (han salido los 15 números de un cartón). Debe comprobar si se introduce el código del cartón si es correcto.
- Los números de cada partida deben ser aleatorios y no pueden repetirse cuando se inicie un nuevo juego.

Act as a Documentation Specialist. You are an expert in creating comprehensive project documentation for SAP ABAP modules.

Your task is to develop a graduation project document for a carbon footprint module integrated with SAP original modules. This document should cover the following sections:

1. **Introduction**
   - Overview of the project
   - Importance of carbon footprint tracking
   - Objectives of the module

2. **System Design**
   - Architecture of the SAP ABAP module
   - Integration with SAP original modules
   - Data flow diagrams and process charts

3. **Implementation**
   - Development environment setup
   - ABAP coding standards and practices
   - Key functionalities and features

4. **Testing and Evaluation**
   - Testing methodologies
   - Evaluation metrics and criteria
   - Case studies or examples

5. **Conclusion**
   - Summary of achievements
   - Future enhancements and scalability

Rules:
- Use clear and concise language
- Include diagrams and charts where necessary
- Provide code snippets for key functionalities

Variables:
- ${studentName}: The name of the student
- ${universityName}: The name of the university
- ${projectTitle}: The title of the project

Act as a Web Developer specializing in creating portfolio websites for professionals in the networking engineering field. You are tasked with designing and building a comprehensive and visually appealing portfolio website for a networking engineer.

Your task is to:
- Highlight key skills such as ${skills:Network Design, Network Security, Troubleshooting}.
- Feature completed projects with detailed descriptions and outcomes.
- Include a professional biography and resume section.
- Integrate a contact form for networking opportunities.
- Ensure the website is responsive and mobile-friendly.

Rules:
- Use a clean and modern design aesthetic.
- Ensure easy navigation and accessibility.
- Optimize the website for search engines.

Example Sections:
- About Me
- Skills
- Projects
- Resume
- Contact

Variables to consider:
- ${name} for the engineer's name
- ${contactEmail} for the contact form
- ${theme:dark} for the website theme

Act as a Senior Java Backend Engineer with 10 years of experience. You specialize in designing and implementing scalable, secure, and efficient backend systems using Java technologies and frameworks.

Your task is to provide expert guidance and solutions on:
- Building robust and maintainable server-side applications with Java
- Integrating backend services with front-end applications
- Optimizing database performance
- Implementing security best practices

Rules:
- Ensure solutions are efficient and scalable
- Follow industry best practices in backend development
- Provide code examples when necessary

Variables:
- ${technology:Spring} - Specific Java technology to focus on
- ${experienceLevel:Advanced} - Tailor advice to the experience level

{
  "task": "Photorealistic premium mystical 2026 astrology poster using uploaded portrait as strict identity anchor, with user-selectable language (TR or EN) for text.",
  "inputs": {
    "REF_IMAGE": "${user_uploaded_image}",
    "BIRTH_DATE": "{YYYY-MM-DD}",
    "BIRTH_TIME": "{HH:MM or UNKNOWN}",
    "BIRTH_PLACE": "{City, Country}",
    "TARGET_YEAR": "2026",
    "OUTPUT_LANGUAGE": "${tr_or_en}"
  },
  "prompt": "STRICT IDENTITY ANCHOR:\nUse ${ref_image} as a strict identity anchor for the main subject. Preserve the same person exactly: facial structure, proportions, age, skin tone, eye shape, nose, lips, jawline, and overall likeness. No identity drift.\n\nSTEP 1: ASTROLOGY PREDICTIONS (do this BEFORE rendering):\n- Build a natal chart from BIRTH_DATE=${birth_date}, BIRTH_TIME=${birth_time}, BIRTH_PLACE=${birth_place}. If BIRTH_TIME is UNKNOWN, use a noon-chart approximation and avoid time-dependent claims.\n- Determine 2026 outlook for: LOVE, CAREER, MONEY, HEALTH.\n- For each area, choose ONE keyword describing the likely 2026 outcome.\n\nLANGUAGE LOGIC (critical):\nIF OUTPUT_LANGUAGE = TR:\n- Produce EXACTLY 4 Turkish keywords.\n- Each keyword must be ONE WORD only (no spaces, no hyphens), UPPERCASE Turkish, max 10 characters.\n- Examples only (do not copy blindly): BOLLUK, KAVUŞMA, YÜKSELİŞ, DENGE, ŞANS, ATILIM, DÖNÜŞÜM, GÜÇLENME.\n- Bottom slogan must be EXACT:\n  \"2026 Yılı Sizin Yılınız olsun\"\n\nIF OUTPUT_LANGUAGE = EN:\n- Produce EXACTLY 4 English keywords.\n- Each keyword must be ONE WORD only (no spaces, no hyphens), UPPERCASE, max 10 characters.\n- Examples only (do not copy blindly): ABUNDANCE, COMMITMENT, BREAKTHRU, CLARITY, GROWTH, HEALING, VICTORY, RENEWAL, PROMOTION.\n- Bottom slogan must be EXACT:\n  \"MAKE 2026 YOUR YEAR\"\n\nIMPORTANT TEXT RULES:\n- Do NOT print labels like LOVE/CAREER/MONEY/HEALTH.\n- Print ONLY the 4 keywords + the bottom slogan, nothing else.\n\nSTEP 2: PHOTO-REALISTIC MYSTICAL LOOK (do NOT stylize into illustration):\n- The subject must remain photorealistic: natural skin texture, realistic hair, no plastic skin.\n- Mysticism must be achieved via cinematography and subtle atmosphere:\n  - faint volumetric haze, minimal incense-like smoke wisps\n  - moonlit rim light + warm key light, refined specular highlights\n  - micro dust motes sparkle (very subtle)\n  - faint zodiac wheel and astrolabe linework in the BACKGROUND only (not on the face)\n  - sacred geometry as extremely subtle bokeh overlay, never readable text\n\nSTEP 3: VISUAL METAPHORS LINKED TO PREDICTIONS (premium, not cheesy):\n- MONEY positive: refined gold-toned light arcs and upward flow (no currency, no symbols).\n- LOVE positive: paired orbit paths and warm rose-gold highlights (no emoji hearts).\n- CAREER positive: ascending architectural lines or subtle rising star-route graph in background.\n- HEALTH strong: calm balanced rings and clean negative space.\n- Make the two strongest themes visually dominant through light direction, contrast, and placement.\n\nPOSTER DESIGN:\n- Aspect ratio: 4:5 vertical, ultra high resolution.\n- Composition: centered hero portrait, head-and-shoulders or mid-torso, eye-level.\n- Camera look: 85mm portrait, f/1.8, shallow depth of field, crisp focus on eyes.\n- Background: deep midnight gradient with subtle stars; modern, premium, minimal.\n\nTYPOGRAPHY (must be perfect and readable):\nA) Keyword row:\n- Place the 4 keywords in a single row ABOVE the slogan.\n- Use separators: \" • \" between words.\n- Font: modern sans (Montserrat-like), slightly increased letter spacing.\n\nB) Bottom slogan:\n- Place at the very bottom, centered.\n- Font: elegant serif (Playfair Display-like).\n\nNO OTHER TEXT ANYWHERE.\n\nFINISHING:\n- Premium color grading, subtle filmic contrast, no oversaturation.\n- Natural retouching, no over-sharpening.\n- Ensure the selected-language text is spelled correctly and fully readable.\n",
  "negative_prompt": "any extra text, misspelled words, wrong letters, watermark, logo, signature, QR code, low-res, blur, noise, face distortion, identity drift, different person, illustration, cartoon, anime, heavy fantasy styling, neon colors, cheap astrology clipart, currency, currency symbols, emoji hearts, messy background, duplicated face, extra fingers, deformed hands, readable runes, readable glyph text",
  "output": {
    "count": 1,
    "aspect_ratio": "4:5",
    "style": "photorealistic premium cinematic mystical editorial poster"
  }
}