ledgerrz/GEMINI.md
Daan Meijer a1adf1da1c
Some checks failed
linter / quality (push) Failing after 1m3s
tests / ci (8.3) (push) Failing after 48s
tests / ci (8.4) (push) Failing after 1m5s
tests / ci (8.5) (push) Failing after 1m4s
added media, mutation events, agent instructions
2026-06-15 22:30:17 +02:00

1.6 KiB

Ledgerrz Project Instructions & Conventions

Welcome to the Ledgerrz codebase! This file defines the persistent guidelines, architectural rules, and context directories loaded in every Gemini session.


1. Context Persistence Mandate

  • Business Logic & Goals (IDEA.md): You MUST read and follow the application concept, features, and user workflow goals outlined in IDEA.md at the start of any new session.
  • Design & Architecture Decisions (DECISIONS.md): You MUST strictly adhere to the established style architecture (BEM methodology with scoped styles and @apply), package deduplication rules, and controller structures documented in DECISIONS.md. Update this file with any new major design decisions made during your session.

2. Key Technology Stack & Conventions

  • PHP/Laravel: PHP 8.4 & Laravel 13. Adhere to typed parameters and return values. Ensure controllers extend properly and use required authorization traits (e.g., AuthorizesRequests).
  • Frontend Styling (BEM): Replaced direct Tailwind inline utility-class markup with BEM (Block, Element, Modifier). All custom component styles must live inside <style scoped> blocks with a relative @reference "../../css/app.css" directive to pull variables without duplications.
  • Real-time Broadcasting: Powered by @laravel/echo-vue with fallback configurations and Vite deduplication rules configured in vite.config.ts.
  • Testing: Powered by Pest PHP (v4). Every backend controller, event, or model change must be validated by running vendor/bin/pest.