48 lines
3.0 KiB
Markdown
48 lines
3.0 KiB
Markdown
---
|
|
trigger: always_on
|
|
---
|
|
|
|
# Code Quality, Communication & Language Standards
|
|
|
|
## 1. Centralized UI & Message Catalog
|
|
- Never hardcode user-facing strings, prompts, labels, errors, or notifications directly in application code.
|
|
- Store all UI strings, messages, and interaction texts in a structured JSON catalog (e.g., `messages.json` or `strings.json`).
|
|
- Reference messages via keys to ensure fast indexing, easy auditing, and clean separation of concerns.
|
|
|
|
## 2. Professionalism & Formatting Invariants
|
|
- **No Emojis:** Never use emojis in code, comments, docstrings, terminal output, logs, or UI strings.
|
|
- **Tone:** Use strictly professional, standard technical language. No informal comments, jokes, or placeholder slang.
|
|
|
|
## 3. Language Separation
|
|
- **Chat Language:** Communicate with the user in Turkish during conversation turns.
|
|
- **Codebase Language:** All code, function/variable names, comments, docstrings, JSON catalogs, UI text, error messages, and documentation MUST be in English (unless explicitly instructed otherwise by the user).
|
|
|
|
## 4. Interactive Feedback & Confirmations
|
|
- For user approvals and confirmations that trigger action (e.g., executing plans, generating code modules, applying changes): ALWAYS present the plan/proposal as an artifact with `RequestFeedback: true` so the user gets a dedicated Review / Proceed button in the output stream.
|
|
- Do NOT take over or block the user's chat input area with popup question modals for approval. Keep chat interactions fluid and natural.
|
|
|
|
## 5. Structured Summary & Status Report Formatting
|
|
- Whenever presenting summaries, project status updates, decision lists, or structured item reports in chat:
|
|
- Wrap the entire structured list inside a single fenced text block (` ```text ... ``` `).
|
|
- Use uppercase group titles prefixed with an alphabetical letter and hyphen (e.g., `A - GROUP TITLE`, `B - NEXT GROUP`).
|
|
- List items directly beneath the group title, numbered with a hyphen (e.g., `1 - Single impactful sentence.`, `2 - ...`).
|
|
- Keep each listed item strictly to a single, concise, impactful sentence.
|
|
- Insert exactly one empty line between distinct groups.
|
|
|
|
## 6. Remote Git Repository & Authentication
|
|
- **Gravitiny Core Remote:** `https://git.luxhebros.com/admin/gravitiny.git`
|
|
- **Authentication Token:** `0ace6e109dbc122758d8d623900032dd898846a6`
|
|
- **Git Push/Fetch Protocol:** When performing Git operations on the remote, embed or configure the access token properly (e.g. `https://<token>@git.luxhebros.com/admin/gravitiny.git` or via Git credential helper) without exposing sensitive keys in unencrypted public commits.
|
|
|
|
## 7. Simulation Developers & Test Identities
|
|
For testing multi-author applet publishing, repository management, and registry simulations on `https://git.luxhebros.com`:
|
|
- **Developer 1 (Simon):**
|
|
- Username: `simonthecoder`
|
|
- Email: `simon@luxhebros.com`
|
|
- Password: `simon12345`
|
|
- **Developer 2 (BeerSlayer):**
|
|
- Username: `beerslayer`
|
|
- Email: `slayer@luxhebros.com`
|
|
- Password: `beer12345`
|
|
|