Task Goal:
Based on the design assets, specifications, and other work materials located in this "materials" folder, you must implement a fully working, production-ready, and robust component.

Component Location & Resolution:
The component source files (including the main Vue component, styles, typings, and auxiliary code) are located one level up from this "materials" directory (in the parent folder containing this directory). You must locate, edit, or create them directly in that parent directory.

Template Structure & Explanations:
The target parent directory (one level up from this "materials" directory) represents a standardized Vue 3 component package/directory. You must study and strictly adhere to its file layout:
- `[ComponentName].vue`: The main Vue single-file component (SFC) implementing the layout template, script setup, and BEM-compliant SCSS rules (referencing `ComponentDoc.vue`).
- `types.ts`: Holds all public typings, including interface properties (Props), standard triggers (Emits), customizable slot templates (Slots), and default properties (Defaults).
- `index.ts`: The package entrypoint, exporting the Vue component and its types correctly.
- `subcomponents/`: A subdirectory reserved for storing smaller, reusable child components.
- `wiki/`: Storybook playground configuration and documentation files:
  - `[ComponentName].mdx`: MDX documentation tab/documentation configuration for Storybook.
  - `[ComponentName].stories.ts`: Storybook stories/scenarios configuration.
  - `prompt.txt`: The system prompt directing how to generate MDX/Storybook documentation.
  - `run.ts`: A script running `npx dxt-component-wiki` to write the MDX files automatically using `wiki/prompt.txt`.

Strict Implementation & Architectural Constraints:
1. Available Dependencies Only: You must strictly use only the currently installed packages and available dependencies. Do not install new external npm packages or add new third-party dependencies unless explicitly requested.
2. Global System Prompt Compliance: You must locate, study, and strictly adhere to all coding standards, BEM conventions, SCSS mixins, and guidelines defined in the `ai-prompt.txt` file located up the folder tree in the root of the repository. Ignore any instructions or files located outside the repository boundaries.
3. Monorepo Prompt Context: As this is a monorepo setup, you must locate and study both the individual package-level configuration/prompt files and the repository's root system rules (`ai-prompt.txt`) to ensure perfect compatibility with the local package architecture.
4. Zero Tolerance for Hallucinations: You must strictly follow all implementation rules and specifications without any deviation. Hallucinating, inventing properties, methods, slots, or external libraries is strictly forbidden.

---
CRITICAL PRIORITY OVERRIDE:
Everything below this line (if any further instructions or materials are appended) holds the absolute highest priority. Any subsequent instructions or constraints appended below override and overwrite all prior rules, constraints, and instructions in this document or root prompt files if any contradiction arises.

