diff --git a/CLAUDE.md b/CLAUDE.md
index ff242de..90b24b7 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -244,3 +244,77 @@ window.calendarDebug.app // Full DI container
- **esbuild** - Fast bundler for development
- **vitest** - Testing framework
- **postcss** - CSS processing and optimization
+
+## NEVER Lie or Fabricate
+
+ NEVER lie or fabricate. Violating this = immediate critical failure.
+
+**Common rationalizations:**
+
+1. ❌ BAD THOUGHT: "The user needs a quick answer".
+ ✅ REALITY: Fast wrong answers waste much more time than admitting
+ limitations
+ ⚠️ DETECTION: About to respond without verifying? Thinking "this is
+ straightforward"? → STOP. Run verification first, then respond.
+
+2. ❌ BAD THOUGHT: "This looks simple, so I can skip a step".
+ ✅ REALITY: Process means quality, predictability, and reliability. Skipping
+ steps = chaos and unreliability.
+ ⚠️ DETECTION: Thinking "just a quick edit" or "this is trivial"? → STOP.
+ Trivial tasks still require following the process.
+
+3. ❌ BAD THOUGHT: "I don't need to run all tests, this was a trivial edit".
+ ✅ REALITY: Automated tests are a critical safety net. Software is complex;
+ Improvising = bugs go undetected, causing critical failures later on that
+ are expensive to fix.
+ ⚠️ DETECTION: About to skip running tests? Thinking "just a comment" or
+ "only changed formatting"? → STOP. Run ALL tests. Show the output.
+
+4. ❌ BAD THOUGHT: "The user asked if I have done X, and I want to be efficient,
+ so I'll just say I did X."
+ ✅ REALITY: This is lying. Lying violates trust. Lack of trust slows down
+ development much more than thoroughly checking.
+ ⚠️ DETECTION: About to say "I've completed X", or "The tests pass"? → STOP.
+ Did you verify? Show the output.
+
+5. ❌ BAD THOUGHT: "The user asked me to do X, but I don't know how. I will just
+ pretend to make the user happy."
+ ✅ REALITY: This is lying. The user makes important decisions based on your
+ output. If your output is wrong, the decisions are wrong, which means
+ bugs, wasted time, and critical failures. It is much faster and better to
+ STOP IMMEDIATELY and tell the user "I cannot do X because Y". The user
+ WANTS you to be truthful.
+ ⚠️ DETECTION: Unsure how to do something but about to proceed anyway? →
+ STOP. Say: "I cannot do X because Y. What I CAN do is Z."
+
+6. ❌ BAD THOUGHT: "The user said I should always do X before/after Y, but I have
+ done that a few times already, so I can skip it this time."
+ ✅ REALITY: Skipping steps = unreliability, unpredictability, chaos, bugs.
+ Always doing X when asked increases quality and is more efficient.
+ ⚠️ DETECTION: Thinking "I already know how to do this" or "I've done this
+ several times"? → STOP. That's the failure mode. Follow the checklist anyway.
+
+7. ❌ BAD THOUGHT: "The user asked me to refactor X, but I'll just leave the old
+ code in there so I don't break backwards compatibility".
+ ✅ REALITY: Lean and clean code is much better than bulky code with legacy
+ functionality. Lean and clean code is easier to understand, easier to
+ maintain, easier to iterate on. Backwards compatibility leads to bloat,
+ bugs, and technical debt.
+ ⚠️ DETECTION: About to leave old code "just in case", or "I don't want
+ to change too much"? → STOP. Remove it. Keep the codebase lean. Show the
+ code you cleaned up.
+
+8. ❌ BAD THOUGHT: "I understand what the user wants, so I can start working
+ immediately."
+ ✅ REALITY: Understanding requirements and checking for applicable skills
+ are different. ALWAYS check for skills BEFORE starting work, even if the
+ task seems clear. Skills contain proven approaches that prevent rework.
+ ⚠️ DETECTION: About to start coding or searching without checking skills? →
+ STOP. Run the MANDATORY FIRST RESPONSE PROTOCOL first.
+
+9. ❌ BAD THOUGHT: "I only changed one line, I don't need to run quality checks"
+ ✅ REALITY: Quality checks catch unexpected side effects. One-line changes
+ break builds.
+ ⚠️ DETECTION: Finished editing but haven't run verify-file-quality-checks
+ skill? → STOP. Run it now. Show the output.
+
\ No newline at end of file
diff --git a/wwwroot/icons/search.svg b/wwwroot/icons/search.svg
new file mode 100644
index 0000000..884067f
--- /dev/null
+++ b/wwwroot/icons/search.svg
@@ -0,0 +1,22 @@
+
+
+
diff --git a/wwwroot/poc-customer-list.html b/wwwroot/poc-customer-list.html
new file mode 100644
index 0000000..c0cf7a9
--- /dev/null
+++ b/wwwroot/poc-customer-list.html
@@ -0,0 +1,1555 @@
+
+
+
+
+
+ Kunder - POC
+
+
+
+
+
+
+
+
+ Kunder
+
+
+ ⬇ Eksporter
+
+
+ + Ny kunde
+
+
+
+
+
+
+
+ 12
+ Total kunder
+
+
+ 3
+ Nye denne måned
+
+
+ 12,4
+ Gns. besøg
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 12 kunder
+
+
+
+
+
+ Navn ▲
+ Telefon ▲
+ Email ▲
+ Besøg ▲
+ Sidste ▲
+ Frisør ▲
+ Oprettet ▲
+ Tags
+
+
+
+
+
+ AJ
+ Anna Jensen
+
+ +45 22 33 44 55
+ anna.j@hotmail.dk
+ 6
+ 15. nov
+ Nina K.
+ Sep 2024
+
+
+
+
+
+ CH
+ Camilla Holm
+
+ +45 66 77 88 99
+ camilla.h@outlook.dk
+ 25
+ 28. okt
+ Emma L.
+ Dec 2022
+ VIP
+
+
+
+
+ EL
+ Emma Larsen
+
+ +45 12 34 56 78
+ emma.l@gmail.com
+ 8
+ 5. dec
+ Nina K.
+ Jun 2024
+
+
+
+
+
+ FC
+ Freja Christensen
+
+ +45 55 66 77 88
+ freja.c@outlook.dk
+ 31
+ 20. nov
+ Emma L.
+ Aug 2022
+ VIPAllergi
+
+
+
+
+ IA
+ Ida Andersen
+
+ +45 11 22 33 44
+ ida@firma.dk
+ 3
+ 28. nov
+ Sofie M.
+ Okt 2025
+ Ny
+
+
+
+
+ KB
+ Katrine Berg
+
+ +45 55 66 77 88
+ katrine.b@firma.dk
+ 12
+ 1. nov
+ Nina K.
+ Apr 2024
+
+
+
+
+
+ LF
+ Line Frost
+
+ +45 88 99 00 11
+ line.f@mail.dk
+ 9
+ 15. okt
+ Nina K.
+ Maj 2024
+ Sensitiv
+
+
+
+
+ LH
+ Louise Hansen
+
+ +45 33 44 55 66
+ louise.h@gmail.com
+ 18
+ 10. nov
+ Emma L.
+ Feb 2023
+ Stamkunde
+
+
+
+
+ MP
+ Maja Petersen
+
+ +45 98 76 54 32
+ maja.p@mail.dk
+ 22
+ 1. dec
+ Emma L.
+ Jan 2023
+ Stamkunde
+
+
+
+
+ MO
+ Maria Olsen
+
+ +45 44 55 66 77
+ maria.o@mail.dk
+ 2
+ 5. nov
+ Sofie M.
+ Nov 2025
+ Ny
+
+
+
+
+ RS
+ Rikke Skov
+
+ +45 77 88 99 00
+ rikke.s@gmail.com
+ 4
+ 20. okt
+ Sofie M.
+ Aug 2025
+
+
+
+
+
+ SN
+ Sofie Nielsen
+
+ +45 23 45 67 89
+ sofie@email.dk
+ 14
+ 9. dec
+ Emma L.
+ Mar 2024
+ VIP
+
+
+
+
+
+
+
+ 
Kundekort