feat: enhance admin frontend guidelines for consistent layout and modal usage

Author: sametcn99

.github/agents/frontend-implementer.agent.md

@@ -18,6 +18,8 @@ You are a frontend specialist for booking-calendar.
 - Avoid introducing inconsistent UI patterns.
 - Prefer existing API client patterns in `src/client/src/api.ts`.
 - Keep mobile and desktop behavior stable.
+- Keep admin list pages (`AppointmentsPage`, `LinksPage`, `EventsPage`) consistent in header/action placement and list-card structure.
+- Prefer modal-based create flows for admin pages when matching existing UX.
 
 ## Workflow
 

.github/copilot-instructions.md

@@ -44,6 +44,7 @@
 - Respect route declaration order in `src/server/index.ts`; generic dynamic routes can shadow specific routes.
 - Read environment values through `src/server/config.ts` conventions. Do not assume `dotenv`; this project uses a custom `.env` loader.
 - Treat `VITE_*` variables as build-time client variables. Rebuild frontend when they change.
+- Keep admin frontend pages (`Appointments`, `Links`, `Events`) aligned in layout and interactions; prefer header-level primary actions and modal-based create forms.
 - No dedicated automated test suite is configured yet. Always run `bun run check` before finishing substantial code changes.
 
 ## Key References

.github/instructions/frontend.instructions.md

@@ -10,6 +10,9 @@ applyTo: "src/client/src/**/*.ts, src/client/src/**/*.tsx, src/client/src/**/*.c
 - Keep user-facing copy in translation files (`src/client/src/i18n/*.json`) and use key-based lookups.
 - Keep API access centralized in `src/client/src/api.ts` unless there is an established exception.
 - Prefer extending existing page/component patterns before introducing new abstractions.
+- Keep admin list pages (`AppointmentsPage`, `LinksPage`, `EventsPage`) visually aligned: title/description on the left, primary action on the right.
+- For create actions on admin list pages, prefer opening forms in BaseUI modals instead of inline blocks unless the request explicitly asks otherwise.
+- Reuse existing card-list and empty-state patterns before inventing a new page-specific layout.
 - Preserve PWA behavior and service-worker assumptions when changing app bootstrapping.
 - Treat `VITE_*` values as build-time variables; if behavior depends on them, mention rebuild impact.
 

.github/prompts/add-frontend-page.prompt.md

@@ -13,6 +13,8 @@ Requirements:
 - Use centralized API helpers in `src/client/src/api.ts` where possible.
 - Keep desktop and mobile usability in mind.
 - Preserve existing visual language and avoid unrelated design-system drift.
+- For admin list pages, align header/action layout with existing `Appointments`, `Links`, and `Events` pages.
+- Prefer modal-based create/edit forms on admin pages unless an inline form is explicitly requested.
 
 Expected output: