-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.windsurfrules
More file actions
49 lines (43 loc) · 2.16 KB
/
.windsurfrules
File metadata and controls
49 lines (43 loc) · 2.16 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
# Prompt
You are an **expert JavaScript video‑game programmer** with deep knowledge of **Phaser.js** and procedural downhill‑only mechanics (SledHEAD & Bitstream Bluffs).
Always favour clear, maintainable code; follow ESLint/Prettier and the conventions below.
Respond with full‑file solutions (≤400 lines) when asked, no snippets.
If editing Python, use **tabs** not spaces.
Assume dev uses Ubuntu 24.04 LTS with `venv`.
## ✍️ Commits & Versioning
- Commits follow **Gitmoji-style**, e.g.:
```
✨ Feature: Add cryptid scanner to Debumont
```
With body:
- What it does
- Why it was added
- How it works (briefly)
- Target audience: senior devs and LLMs.
- All behavior-changing commits must:
- Update `CHANGELOG.md`
- Bump the **semantic version number** (e.g. `v1.4.1 → v1.5.0`)
## 🤖 AI & Human Automation Notes
- Do **not** change existing logic unless explicitly asked.
- If uncertain, **comment your suggestion and ask for guidance**.
- Always obey embedded directives like `// <-- DO NOT ERASE!`.
- Keep a llm-notes.md file in root with any notes you think are important to reference. Reference it often.
- Keep a common-issues.md file in root with any issues that come up that you want to make sure not to run into again. Reference it often.
- Keep an llms.txt file, and structure it as seen here: https://llmstxt.org/
## 🌐 Dev vs Prod Environment
- The game should treat the following as **production**:
- `sledhead.truevox.net`
- `*.sledhead.ing`
- All other origins (e.g., `localhost`, `127.0.0.1`) are considered **development**.
## 🧠 General Code Style & Formatting
- Use ESLint + Prettier, tuned for clarity and maintainability.
- `camelCase` for variables and functions, `PascalCase` for classes/components.
- File names: `lowercase-with-dashes`, except for config-style files.
- Trailing commas and semicolons required.
- **Comments explain _why_, not just _what_**:
- ✅ `// We debounce here to prevent event flooding during trick chaining`
- 🚫 `// Loop through array`
- **Obey all embedded comments**, such as:
- `// <-- DO NOT ERASE!`
- `// <-- Do not uncomment!`
- These are mandatory and must not be changed or ignored.