feat: update environment configurations and add gold price management module with related components and services

2026-05-23 19:57:28 +03:30
parent 6ad1a73c16
commit 7f07bf53c2
14 changed files with 507 additions and 89 deletions
@@ -8,6 +8,233 @@

 ---

+# ⚡ EXECUTION RULES (STRICT)
+
+Minimize reasoning verbosity.
+
+## Response Style
+
+Do not:
+- narrate thoughts
+- speculate
+- explain obvious steps
+- describe intentions before acting
+- write reflective/internal commentary
+
+Avoid messages like:
+- "I think I need to..."
+- "I should inspect..."
+- "I'm going to..."
+- "I wonder if..."
+- "Let me check..."
+- "I'm curious about..."
+
+Instead:
+- act immediately
+- use short operational updates only when necessary
+
+Good:
+
+Inspecting environment files and Angular configs.
+
+Bad:
+
+I think I should inspect the environment files first to understand how everything is connected before deciding what changes are necessary.
+
+
+---
+
+# 🔇 MINIMAL PLANNING MODE
+
+Only create plans when:
+- task has multiple independent phases
+- task is ambiguous
+- task is large/refactor-level
+
+Do not create plans for:
+- small fixes
+- single-file edits
+- obvious tasks
+
+Avoid:
+- repeated plan updates
+- verbose planning
+- unnecessary decomposition
+
+---
+
+# ✂️ MINIMAL OUTPUT RULES
+
+Keep responses compact.
+
+Do not:
+- restate the user request
+- explain already-visible edits
+- summarize trivial findings
+- narrate file discovery
+- explain failed reads unless blocking
+- describe obvious implementation details
+
+Prefer:
+
+Updated environment files for development, staging, production, and tis.
+
+Avoid:
+
+I found a mismatch and then investigated several files before determining that...
+
+---
+
+# 📦 FINAL RESPONSE RULES
+
+Final responses must be under 10 lines unless:
+
+- user explicitly asks for explanation
+- architectural decisions changed
+- validation failed
+- multiple systems were affected
+
+Prefer:
+
+Updated:
+- file1
+- file2
+
+Validation:
+- pnpm tsc passed
+
+Avoid:
+
+- long prose summaries
+- unnecessary explanations
+- repeating repository context
+
+---
+
+# 🚫 NO TEACHING MODE
+
+Do not explain:
+
+- Angular basics
+- TypeScript basics
+- RxJS basics
+- obvious framework behavior
+- standard programming concepts
+
+Assume repository maintainers already understand the stack.
+
+---
+
+# 🧠 CONTEXT PRESERVATION RULES
+
+Avoid repeating previously established context.
+
+Do not repeatedly mention:
+- repository structure
+- framework details
+- previously inspected files
+- known architecture
+- already-established conventions
+
+Assume prior context remains valid unless changed.
+
+---
+
+# 🛑 EXPLORATION STOP RULE
+
+If the likely edit location is identified:
+
+- stop searching
+- stop exploring
+- implement changes
+
+Do not continue repository exploration after:
+
+- target component found
+- target service found
+- target config found
+- target store found
+- target route found
+
+---
+
+# 🎯 EDIT-FIRST BEHAVIOR
+
+After identifying the target location:
+
+- edit quickly
+- avoid excessive inspection
+- avoid repeated verification reads
+- avoid speculative exploration
+
+Prefer implementation over exploration.
+
+---
+
+# ✍️ EDIT CONFIDENCE RULES
+
+Prefer direct implementation when:
+
+- existing patterns are obvious
+- nearby components establish conventions
+- requested change is localized
+- existing abstractions already match requirements
+
+Do not over-investigate obvious implementations.
+
+---
+
+# ⚠️ FAILURE HANDLING RULES
+
+If a file read fails:
+
+- do not retry repeatedly
+- verify path once
+- continue with nearest valid target
+
+Do not:
+
+- repeatedly attempt missing files
+- scan nearby directories unnecessarily
+- speculate about missing files
+- retry identical commands
+
+---
+
+# 📏 HARD CONTEXT LIMITS
+
+Do not:
+
+- read more than 2 files before first edit
+- read more than 1 sibling file unless required
+- reread unchanged files
+- inspect unrelated modules
+
+For small tasks:
+
+- maximum 3 repository reads before editing
+
+For medium tasks:
+
+- maximum 8 repository reads before editing
+
+Large/refactor tasks may exceed limits only when necessary.
+
+---
+
+# 🚫 AVOID MULTI-FILE EAGER READS
+
+Never chain multiple reads in one command unless necessary.
+
+Avoid:
+
+- rtk read a.ts && rtk read b.ts && rtk read c.ts
+
+Prefer sequential targeted reads.
+
+---
+
+
 # ✅ RTK-FIRST RULES (STRICT)

 Always prefer RTK commands for repository inspection, navigation, and code understanding.
@@ -16,17 +243,15 @@ Always prefer RTK commands for repository inspection, navigation, and code under

 Prefer:

-```bash
-git status        -> rtk git status
-git diff          -> rtk git diff
-git log           -> rtk git log
-ls                -> rtk ls
-tree              -> rtk ls
-cat <file>        -> rtk read <file>
-grep <pattern>    -> rtk grep <pattern>
-rg <pattern>      -> rtk grep <pattern>
-find              -> rtk find
-```
+- git status        -> rtk git status
+- git diff          -> rtk git diff
+- git log           -> rtk git log
+- ls                -> rtk ls
+- tree              -> rtk ls
+- cat <file>        -> rtk read <file>
+- grep <pattern>    -> rtk grep <pattern>
+- rg <pattern>      -> rtk grep <pattern>
+- find              -> rtk find

 Avoid raw commands for repository inspection when RTK equivalents exist.

@@ -45,49 +270,121 @@ Raw commands are allowed only when:

 ---

+
+
+# 🧩 FILE READING RULES (IMPORTANT)
+
+Prefer minimal-context reads.
+
+## Preferred Order
+
+1. `rtk grep`
+2. `rtk smart`
+3. `rtk read`
+4. aggressive read only if required
+
+## Rules
+
+Never immediately read a full file after search.
+
+Before reading:
+- identify exact symbol/component/function
+- inspect only relevant sections
+
+Prefer:
+
+- rtk smart <file>
+
+before:
+
+- rtk read <file>
+
+
+For large files:
+
+- rtk read <file> -l aggressive
+
+
+Only when necessary.
+
+Avoid:
+- reading TS + HTML + SCSS together
+- opening sibling files preemptively
+- rereading files already inspected
+- reading generated or unrelated files
+
+---
+
+## Angular-Specific Strategy
+
+For Angular components:
+
+1. grep component selector/class
+2. smart-read TS file
+3. read template only if UI changes required
+4. read styles only if styling changes required
+
+Example:
+
+bash
+rtk grep "invoice-type-card"
+rtk smart invoice-type-card.component.ts
+rtk read invoice-type-card.component.html
+
+
+Avoid:
+
+bash
+rtk read component.ts
+rtk read component.html
+rtk read component.scss
+
+
+unless all files are actually needed.
+
 # 📂 CODE NAVIGATION WORKFLOW (MANDATORY)

 Follow this order when working in the repository.

 ## 1. Discover Structure

-```bash
+bash
 rtk ls
-```
+

 ## 2. Search Before Opening Files

-```bash
+bash
 rtk grep <symbol | class | function | DTO | service>
-```
+

 Examples:

-```bash
+bash
 rtk grep "InputComponent"
 rtk grep "fieldControl"
 rtk grep "breadcrumbItems"
-```
+

 ## 3. Read Only Necessary Files

-```bash
+bash
 rtk read <file>
-```
+

 ## 4. Large File Strategy

 For files larger than ~300 lines:

-```bash
+bash
 rtk read <file> -l aggressive
-```
+

 ## 5. Fast Context Understanding

-```bash
+bash
 rtk smart <file>
-```
+

 Never:
 - open many files blindly
@@ -101,21 +398,21 @@ Never:

 For repository changes use:

-```bash
+bash
 rtk git diff
-```
+

 For large diffs:

-```bash
+bash
 rtk git diff -l aggressive
-```
+

 Avoid raw:

-```bash
+bash
 git diff
-```
+

 unless RTK diff is unavailable.

@@ -125,7 +422,7 @@ unless RTK diff is unavailable.

 Avoid loading:

-```txt
+
 dist/
 .angular/
 coverage/
@@ -133,7 +430,7 @@ node_modules/
 .git/
 .cache/
 .tmp/
-```
+

 unless explicitly required.

@@ -169,12 +466,12 @@ unless explicitly required.

 Example workflow:

-```bash
+bash
 rtk index
 rtk search "InputComponent number normalization"
 rtk search "fieldControl"
 rtk refs "goodListConfig"
-```
+

 ## Token Reduction Rules

@@ -196,43 +493,43 @@ rtk refs "goodListConfig"

 ### Angular Components

-```bash
+bash
 rtk search "selector: 'field-"
 rtk search "standalone: true"
 rtk search "InputComponent"
-```
+

 ### Forms & Controls

-```bash
+bash
 rtk search "fieldControl."
 rtk search "ControlConfig"
 rtk search "Validators.required"
-```
+

 ### Stores & Signals

-```bash
+bash
 rtk search "breadcrumbItems"
 rtk search "computed("
 rtk search "signal("
-```
+

 ### Tenant / Docker

-```bash
+bash
 rtk search "DIST_DIR"
 rtk search "configuration tis"
 rtk search "prebuild:tis"
-```
+

 ### List Configs

-```bash
+bash
 rtk search "IListConfig"
 rtk search "columns:"
 rtk search "goodListConfig"
-```
+

 ---

@@ -340,7 +637,7 @@ Additional rule:

 Minimal wrapper shape:

-```ts
+ts
@Component({
  selector: 'field-example',
  template: `<app-input [label]="label" [control]="control" [name]="name" type="simple" />`,
@@ -351,7 +648,7 @@ export class ExampleComponent {
  @Input() name = 'example';
  @Input() label = 'Example';
 }
-```
+

 ---

@@ -369,12 +666,12 @@ Add its form control factory in:

 Example:

-```ts
+ts
 example: (value = '', isRequired = true): ControlConfig => [
  value,
  isRequired ? [Validators.required] : [],
 ],
-```
+

 ---

@@ -416,10 +713,10 @@ Each config implements `IListConfig`:

 ### Usage

-```ts
+ts
@Input() header: IColumn[] = goodListConfig.columns;
 listConfig = goodListConfig;
-```
+

 ### Rules

@@ -435,14 +732,14 @@ listConfig = goodListConfig;
 - Entity stores expose `breadcrumbItems` as a computed signal.
 - Call `store.breadcrumbItems()` in view components and extend with current page:

-```ts
+ts
 setBreadcrumb() {
  this.breadcrumbService.setItems([
    ...this.store.breadcrumbItems(),
    { title: 'Current Page' },
  ]);
 }
-```
+

 - Root page breadcrumbs are set in the store's `getData()` method once entity is loaded.

@@ -452,16 +749,16 @@ setBreadcrumb() {

 ### TypeScript-only changes

-```bash
+bash
 pnpm -s exec tsc -p tsconfig.app.json --noEmit
-```
+

 ### Docker/build changes

-```bash
+bash
 docker compose build app_default
 docker compose build app_tis
-```
+

 ### Validation Strategy