I am batman

.github/instructions/00-main.md

@@ -0,0 +1,5 @@
+# Frontend Instruction Entry Point (Do Not Edit)
+
+1. Read the user's prompt input completely before taking action.
+2. Act as a frontend engineer for this repository's architecture and UI patterns.
+3. Update only the scoped instruction files in this directory when requested; do not modify this file.

.github/instructions/api.md

@@ -0,0 +1,15 @@
+# Frontend API Instructions
+
+## Scope
+- Applies to API calls in `src/lib/api/api.ts` and feature-level data hooks.
+
+## Rules
+- Keep axios-based API calls centralized in `src/lib/api/api.ts`.
+- Map backend response shapes to frontend-friendly models in hooks or API mappers.
+- Follow existing tickets pattern: `api.ts` + feature hook (`useX`) + presentational components.
+- Use optimistic updates carefully; ensure API failures do not leave inconsistent UI state.
+- Keep request payload keys aligned with backend contract (`section_id`, `position`, etc.).
+
+## Error Handling
+- Surface recoverable errors to the user with clear toast messages.
+- Avoid silent failures for create/update/delete flows.

.github/instructions/containerization.md

@@ -0,0 +1,14 @@
+# Frontend Containerization Instructions
+
+## Scope
+- Applies to frontend Docker/build/runtime concerns for Next.js.
+
+## Rules
+- Keep `.next` as a generated artifact; never rely on stale local cache in source control.
+- If dev manifest/cache issues appear, clear `.next` and restart dev server.
+- Keep environment-driven API base URL behavior explicit and documented.
+- Ensure Docker/compose settings match the expected runtime port and host bindings.
+
+## Build Health
+- Distinguish pre-existing lint/type issues from feature-specific regressions in reports.
+- Do not weaken lint/type checks just to pass builds.

.github/instructions/state-and-dnd.md

@@ -0,0 +1,15 @@
+# State and DnD Instructions
+
+## Scope
+- Applies to stateful feature logic and drag/drop interactions (e.g., Kanban with dnd-kit).
+
+## Rules
+- Keep business/data mutations in hooks; keep components mostly presentational.
+- Persist ordering changes deterministically using explicit `position` updates.
+- Avoid nested competing scroll containers when horizontal drag/drop is involved.
+- Ensure drag overlays and scroll behavior work for mouse and touch sensors.
+- When replacing local persistence with API-backed state, remove stale store dependencies cleanly.
+
+## Reliability
+- Debounce or batch expensive reorder API calls where appropriate.
+- After structural changes (move/delete section), refresh canonical state from API when needed.

.github/instructions/ui.md

@@ -0,0 +1,15 @@
+# UI Instructions
+
+## Scope
+- Applies to page/component work under `src/app`, `src/components`, and `src/features`.
+
+## Rules
+- Preserve existing design language and component primitives from `src/components/ui`.
+- Keep layouts responsive with explicit overflow control for dense views (e.g., kanban horizontal overflow).
+- Prefer composition over one-off custom widgets; reuse dialog, card, table, and form primitives.
+- Keep interaction states clear (loading, empty, error) for data-driven pages.
+- Avoid visual regressions in header/sidebar containment when introducing horizontal scroll regions.
+
+## Accessibility
+- Maintain keyboard access for dialogs, menus, and drag handles.
+- Keep meaningful `sr-only` labels for icon-only controls.