diff --git a/.agent/development/SKILL.md b/.agent/development/SKILL.md
deleted file mode 100644
index 7e172b2..0000000
--- a/.agent/development/SKILL.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-name: CodeBridger Development Skill
-description: Core development guidelines and documentation for the Subturtle/CodeBridger ecosystem. Triggered when working on dashboard-app or server.
----
-
-# Development Guidelines
-
-## General Principles
-
-- **Modularity**: Prioritize modularity in all code changes. Organize logic into distinct modules (Server-side) or reusable components (Frontend).
-- **ClickUp Integration**:
- - Task management primarily relies on ClickUp.
- - Always reference the ClickUp task ID in commit messages. Format: `feat: #taskid message`.
-- **Communication**:
- - Favor answering questions and providing explanations over direct code modifications unless explicitly requested.
- - Ensure all explanations are clear and provide necessary context.
-
-## Framework Documentation
-
-Always refer to the official documentation for package-specific implementations:
-
-### Server-Side (@modular-rest/server)
-- **Primary Docs**: [modular-rest_server.md](./modular-rest_server.md)
-- **Key Patterns**:
- - Use `defineCollection` in `db.ts` for database models.
- - Use `defineFunction` in `functions.ts` for API logic.
- - Avoid manual router creation unless necessary (`router.ts`).
-
-### Frontend-Side (@modular-rest/client)
-- **Primary Docs**: [modular-rest_client.md](./modular-rest_client.md)
-- **Key Patterns**:
- - Reference the JS client for consuming services and calling server functions.
-
-### UI Components (lib-vue-components)
-- **Primary Docs**: [lib-vue-components.md](./lib-vue-components.md)
-- **Key Patterns**:
- - Import components directly from `@codebridger/lib-vue-components` as needed (e.g., `import { Button } from '@codebridger/lib-vue-components'`).
- - Follow the design system guidelines for consistent aesthetics.
-
-
----
-
-You must read the specific documentation files listed above before proposing or implementing any technical changes related to these packages.
\ No newline at end of file
diff --git a/.agent/e2e/SKILL.md b/.agent/e2e/SKILL.md
deleted file mode 100644
index b636dd5..0000000
--- a/.agent/e2e/SKILL.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-name: e2e
-description: End-to-end navigation and testing guide for Subturtle Dashboard
----
-
-This skill provides specific instructions for navigating and testing the Subturtle Dashboard application using browser tools.
-
-## Prerequisites
-1. **Server**: Ensure the server is running (usually on port 8080).
-2. **Frontend**: Ensure the frontend is running (usually on port 3000).
-
-## Authentication Flow
-The application uses hash-based routing (`hashMode: true` in Nuxt config). To authenticate via token, you MUST include the `#` character in the URL.
-
-**Correct URL Template:**
-`http://localhost:3000/#/auth/login_with_token?token={YOUR_TOKEN}`
-
-### Steps for Browser Agents:
-1. **Navigate**: Use the `open_browser_url` tool with the correct hash-based login URL.
-2. **Wait for Redirect**: The `login_with_token` page is a redirection page. Wait at least 3 seconds for the `onMounted` hook to process the token and redirect to the dashboard.
-3. **Verify Dashboard**: After redirection, verify you are on `/#/` or another authenticated route. Use `capture_browser_screenshot` to confirm the UI has loaded.
-4. **Inspect UI**: Once logged in, use the navigation menu or direct hash-links to find the specific page.
-
-## Navigation Structure
-- Home/Overview: `/#/`
-- Board (Learning System): `/#/board`
-- Statistic: `/#/statistic`
-- Sessions: `/#/sessions`
-- Settings: `/#/settings`
-
-## Troubleshooting
-- **Blank Page**: Check browser console for authentication errors.
-- **Login Redirect**: If redirected to `/#/auth/login`, the token might be invalid or expired.
-- **Missing Hash**: Always ensure the URL contains `/#/` after the origin.
-- **Login Issue**: If you are not logged in, try to store the token in the browser's local storage `token={YOUR_TOKEN}` and then navigate to the dashboard.
\ No newline at end of file
diff --git a/.agent/skills/backend/SKILL.md b/.agent/skills/backend/SKILL.md
new file mode 100644
index 0000000..193f733
--- /dev/null
+++ b/.agent/skills/backend/SKILL.md
@@ -0,0 +1,28 @@
+---
+name: Backend Development
+description: Guidelines for Server-side development using Modular Rest, Database schemas, and Business Logic.
+---
+
+# Backend Development Skill
+
+## 1. Core Principles
+- **Modularity**: Organize logic into distinct, independent modules. Each module should have a single responsibility.
+- **Testing**: Write unit tests for core logic and services.
+- **Documentation**: Use JSDoc for functions to document parameters and return values.
+- **Workflow**: Always reference the ClickUp task ID in commit messages (e.g., `feat: #taskid message`).
+
+## 2. Technology Stack
+- **Framework**: Modular Rest Server (@modular-rest/server)
+- **Database**: MongoDB (via `defineCollection`)
+
+## 3. Documentation Reference
+**You MUST read the following file for API details:**
+- [Modular Rest Server Docs](./modular-rest_server.md)
+
+## 4. Key Patterns
+- **Database Models**: Use `defineCollection` in `db.ts` files within modules.
+- **API Functions**: Use `defineFunction` in `functions.ts` files.
+- **Routing**: Avoid manual router creation; let the framework handle it.
+
+## 5. Directory Structure
+Code should be written in `/Users/navid-shad/Projects/CodeBridger/learn-by-subtitle/dashboard-app/server`.
diff --git a/.agent/development/modular-rest_server.md b/.agent/skills/backend/modular-rest_server.md
similarity index 100%
rename from .agent/development/modular-rest_server.md
rename to .agent/skills/backend/modular-rest_server.md
diff --git a/.agent/skills/frontend/SKILL.md b/.agent/skills/frontend/SKILL.md
new file mode 100644
index 0000000..3824523
--- /dev/null
+++ b/.agent/skills/frontend/SKILL.md
@@ -0,0 +1,32 @@
+---
+name: Frontend Logic
+description: Guidelines for Client-side logic, State Management (Pinia), API Integration, and App Navigation.
+---
+
+# Frontend Logic Skill
+
+## 1. Core Principles
+- **State Management**: Use Pinia for global state.
+- **API Integration**: Use `@modular-rest/client` to call server functions.
+- **Testing**: Implement integration tests for complex component interactions.
+- **Workflow**: Always reference the ClickUp task ID in commit messages (e.g., `feat: #taskid message`).
+
+## 2. Documentation Reference
+**You MUST read the following file for API Client details:**
+- [Modular Rest Client Docs](./modular-rest_client.md)
+
+## 3. Navigation & Auth Flow
+The application uses hash-based routing (`/#/`).
+
+### Common Routes
+- Home: `/#/`
+- Board: `/#/board`
+- Settings: `/#/settings`
+
+### Authentication
+- Token is stored in `localStorage` key `token`.
+- If redirected to login, verify token presence.
+
+## 4. Key Patterns
+- **Services**: Import `functionProvider` from `@modular-rest/client` to execute backend functions.
+- **Composables**: Use Vue composables for reusable logic.
diff --git a/.agent/development/modular-rest_client.md b/.agent/skills/frontend/modular-rest_client.md
similarity index 100%
rename from .agent/development/modular-rest_client.md
rename to .agent/skills/frontend/modular-rest_client.md
diff --git a/.agent/skills/frontend_design/SKILL.md b/.agent/skills/frontend_design/SKILL.md
new file mode 100644
index 0000000..dc0317a
--- /dev/null
+++ b/.agent/skills/frontend_design/SKILL.md
@@ -0,0 +1,122 @@
+---
+name: Frontend Design System
+description: Comprehensive guide for creating premium, high-fidelity UI layouts using the project's Vue component library and Tailwind CSS.
+---
+
+# Frontend Design System
+
+This skill provides the standards and patterns for building user interfaces in the dashboard application. The goal is to create a **premium, dynamic, and highly polished** user experience that "wows" the user.
+
+## 1. Design Philosophy
+
+- **High-End Aesthetics**: We do not build "MVP-looking" apps. We build refined, polished interfaces.
+- **Glassmorphism & Depth**: Utilize layers, blurs (`backdrop-blur-xl`), and subtle transparencies (`bg-white/40`) to create depth.
+- **Vibrant Colors**: Use the project's `primary` and `secondary` palette, but often via gradients or low-opacity tints (`bg-primary/10`) rather than solid blocks of harsh color.
+- **Dynamic Motion**: Nothing should feel static. Smooth transitions (`duration-500`, `duration-700`), micro-interactions on hover, and entrance animations are required.
+
+## 2. Component Usage
+
+All standard UI elements must come from the internal component library.
+
+**Reference Documentation:**
+- [UI Component Library (lib-vue-components)](./lib-vue-components.md) - Contains full list of available components and their props.
+
+```typescript
+// Import path
+import { Card, Button, Icon } from '@codebridger/lib-vue-components/elements.ts';
+import { Modal } from '@codebridger/lib-vue-components/complex.ts';
+```
+
+### Key Components
+- **Card**: The building block for content.
+- **Button**: Use for actions.
+- **Icon**: Wrapper for Iconify icons. PREFERRED SET: `iconify solar--*-bold-duotone` or `*-bold`.
+- **PageHeader**: Standard top-of-page layout with title, subtitle, and actions.
+- **Breadcrumb**: Navigation hierarchy component.
+
+## 3. Layout Patterns
+
+### Main Page Shell
+Pages normally live within a `DashboardShell` (via `default` layout). Content should be centered with max-width.
+
+```vue
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+### Card Styling
+Cards should rarely be just plain rectangles.
+
+**Premium Card Recipe:**
+- **Rounding**: `rounded-[2.5rem]` or `rounded-3xl` (generous curves).
+- **Background**: `bg-white dark:bg-gray-800`.
+- **Shadow**: Light idle shadow `shadow-[0_4px_20px_rgba(0,0,0,0.03)]` -> Deep hover shadow `hover:shadow-[0_40px_80px_rgba(var(--primary-rgb),0.15)]`.
+- **Interaction**: `group hover:-translate-y-3 transition-all duration-700`.
+- **Decorations**: Use absolute positioned gradients or icons in the background of cards to add texture.
+
+## 4. Typography Standards
+
+- **Titles (H1-H2)**: `font-black`, `tracking-tight`.
+- **Body**: `font-medium` (avoid thin weights for body text to maintain legibility and premium feel).
+- **Labels/Meta**: `text-[10px]` or `text-xs`, `font-bold`, `uppercase`, `tracking-widest` (typographic spacing is key for the premium look).
+- **Colors**:
+ - Primary text: `text-gray-900` / `dark:text-white`
+ - Secondary text: `text-gray-500` / `dark:text-gray-400`
+ - Accent text: `text-primary`
+
+## 5. Visual Effects & Assets
+
+### Gradients
+Use gradients to create "glows".
+- *Example*: `bg-gradient-to-br from-primary via-primary-dark to-secondary`
+
+### Glassmorphism
+- Use `backdrop-blur-md` or `backdrop-blur-xl`.
+- Combine with `bg-white/10` or `bg-white/70`.
+- Add `border border-white/20` for the "glass edge" look.
+
+### Background Elements
+Add "blobs" behind the main content to avoid empty whitespace looking boring.
+```html
+
+```
+
+## 6. Development Checklist
+
+When creating a new page or component:
+1. [ ] Did I use `Card` and `Button` from the library?
+2. [ ] Are the borders rounded enough (`rounded-2xl+`)?
+3. [ ] Is there an entrance animation (e.g., `animate-fade-in-up`)?
+4. [ ] Are interactable elements responsive to hover (scale, shadow, lift)?
+5. [ ] Is Dark Mode supported (`dark:` variants)?
+6. [ ] Did I use the "Solar" icon set (`iconify solar--...`)?
+7. [ ] Is the typography hierarchy clear (Big titles, tiny uppercase labels)?
diff --git a/.agent/development/lib-vue-components.md b/.agent/skills/frontend_design/lib-vue-components.md
similarity index 100%
rename from .agent/development/lib-vue-components.md
rename to .agent/skills/frontend_design/lib-vue-components.md
diff --git a/frontend/components/Leitner/BoxStats.vue b/frontend/components/Leitner/BoxStats.vue
index 41f44de..be45c70 100644
--- a/frontend/components/Leitner/BoxStats.vue
+++ b/frontend/components/Leitner/BoxStats.vue
@@ -3,12 +3,13 @@
- Are you sure you want to reset your entire Leitner system?
+ {{ $t('smart_review.reset_confirm') }}
- This cannot be undone. All progress, card
- levels, and history will be cleared.
+ {{ $t('smart_review.reset_warning') }} {{
+ $t('smart_review.settings_desc') }}
- You are about to update your Leitner intervals.
- Existing items might be rescheduled to align with your new configuration.
+ {{ $t('smart_review.save_confirm_desc') }}