From 9765ba50b501e8528b2013a9083ecb16cff6f885 Mon Sep 17 00:00:00 2001 From: Claudio Ortolina Date: Tue, 15 Jul 2025 11:12:38 +0100 Subject: [PATCH] Add CLAUDE changes for DB design and UI markup --- CLAUDE.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index d1adc5b8..ad8c8f63 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -180,6 +180,10 @@ Code Style and Structure - Structure files according to Phoenix conventions (controllers, contexts, views, etc.). - Where possible use Fluxon components instead of rolling your own +Database design + +- Do not add columns for properties that are not specified in the requirements. Keep database changes to a minimum. + Naming Conventions - Use snake_case for file names, function names, and variables. @@ -208,9 +212,12 @@ Error Handling and Validation UI and Styling - Use Phoenix LiveView for dynamic, real-time interactions. -- Implement responsive design with Tailwind CSS. +- Implement responsive design with Tailwind CSS. When screen space is limited, + prefer content-focused flexible layouts over rigid tabular structures. + Reorganize information hierarchically within each item, grouping related data + visually while maintaining scanability and preserving all functionality. - Use Phoenix view helpers and templates to keep views DRY. -- **Responsive Design**: When screen space is limited, prefer content-focused flexible layouts over rigid tabular structures. Reorganize information hierarchically within each item, grouping related data visually while maintaining scanability and preserving all functionality. +- Use minimal markup and avoid nesting DIVs unnecessarily. Performance Optimization