vibe coding with renpy & pycharm

title: AI Agent Guidelines
description: Metadata supplied by the Junie plug-in to the AI assistant
---

## 1. Tech Stack (auto-extracted)

| Item               | Value                 |
|--------------------|-----------------------|
| Engine             | Ren'Py 8.x            |
| Runtime            | Python 3 (bundled)    |
| Screen Resolution  | 1920 × 1080           |
| Primary Font       | DotGothic16           |
| UI Accent Color    | #cc0066               |
| Extra Context Dir. | docs/renpy/**         |

## 2. Goal
make adv novel game.

## 3. Required References

The AI **must** consult the in-house documentation under `docs/renpy` first and ensure that all proposed code and instructions are consistent with it.

## 4. Response Format

1. Use ```renpy``` or ```python``` code blocks.  
## 5. Constraints

- When suggesting external libraries, state the license and compatibility.  
- Follow the official Ren'Py guidelines.

## 6. Game Phase Structure

The game follows a three-phase structure with designated naming conventions:

1. **Dialogue Phase** - Use content-specific English terms (1-5 words) instead of generic "conversation"
   - Only the first dialogue phase may use "start"
   - When ending dialogue phases, use "end_" followed by meaningful descriptors (not just numbers)
   - Derive phase names from conversation content (e.g., "confrontation", "revelation", "doubt_expression")
   - Avoid generic terms like "progress"

2. **Scry Phase** - For exploration and searching segments
   - Name variables related to this phase using "scry" terminology
   - This phase involves players actively searching for clues or information

3. **Decide Phase** - For resolution and decision-making segments
   - Use this terminology for segments where choices lead to conclusions
   - This phase represents the final determination of outcomes based on previous phases

The three-phase system (dialogue → scry → decide) should be reflected in both label naming and variable structures.

## 7. No Raw Numeric Literals in Screen Layouts

Direct numeric literals (e.g., pixel values) **MUST NOT** be hard-coded inside `screens.rpy` or any other UI-related files.

1. Define all numeric values as variables in `gui.rpy` (e.g., `gui.textbox_height`, `gui.name_xpos`) and reference those variables instead.  
   `
   style window:
       ypos gui.textbox_ypos
       xsize gui.textbox_width
   `
2. When an absolute value is truly unavoidable, declare a well-named constant inside an `init python:` block and reference that constant.  
   `
   init python:
       ICON_FULL_W = 1920
       ICON_FULL_H = 1080
   `
3. Rationale  
   - Multi-resolution and aspect-ratio flexibility  
   - Easier global adjustments and maintenance  
   - Prevents style-inheritance and theme conflicts  
   - Improves code readability

## 8. Language Requirement for Guideline Updates

All future additions, modifications, or appendices to this guideline **MUST be written in English** to ensure consistency for the entire team.