AI System Rules – Local Project

Scope

These rules are mandatory and non-negotiable. All actions, responses, and code changes must comply with this document.

Project Setup

• The working directory must remain within /Volumes/M4Dock2TB/mz_mini/zoli_dev/Projekte/MultiApps/.
• The Svelte views are purely presentational, with all logic and validation handled on the server side.
• Each app must be built using Svelte.js, not SvelteKit and not TypeScript.
• Every stage and every change must be documented in AblaufProtokoll.md.
• Tests may only be executed if a change explicitly requires tests.
• During development, npm run dev is the default; npm run build is used only when explicitly required or requested.
• Destructive Git operations may only be performed with explicit approval.

Development Principles

• The Don’t Repeat Yourself (DRY) principle must be strictly followed.
• Simplicity must be the primary goal.
• Large, complex, or wide-impact changes must be avoided.
• Each change must affect as little code as possible.
• Guessing, assumptions, or imaginative additions are forbidden.
• Anything unclear must be clarified before proceeding.

Workflow Requirements

1. Before making any change, you must think through the problem thoroughly and read the existing codebase to identify relevant files.
2. Before making major changes, you must coordinate with the user and submit a plan for approval.
3. After every step, you must provide a concise, high-level explanation of what was changed.
4. Architectural intent and reasoning must remain simple and explicit.
5. A documentation file must be maintained that fully and accurately describes the app’s architecture.

Code Inspection & Truthfulness

• You must never speculate about code you have not opened.
• If a specific file is referenced, you must read that file before responding.
• Relevant files must be investigated before answering questions about the codebase.
• Claims about code may only be made after verification, unless you are absolutely certain.
• All responses must be grounded, factual, and hallucination-free.
• No SvelteKit and no Typescript and no React are allowed in the codebase.
• SvelteKit, Typescript and React code must be convertet to Svelte.

Enforcement

Failure to follow these rules constitutes an invalid response. When a rule conflict exists, clarification must be requested before proceeding.