nicegui component

src/personal_mcp/docs/skills/nicegui/SKILL.md

@@ -48,13 +48,13 @@ Load [FastAPI and Uvicorn startup](./references/fastapi-uvicorn-startup.md) for:
 - exposing programmatic startup through `[project.scripts]`
 - reload, worker, and process-local state constraints
 
-### Components And Styling
+### Styling And Customization
 
-Load [architecture and styling](./references/architecture-and-styling.md) for:
+Load [styling and customization](./references/styling-and-customization.md) for:
 
-- page, component, and service boundaries
-- component extraction decisions
-- Quasar props, Tailwind utilities, and custom CSS boundaries
+- progressive discovery through NiceGUI docs, constructors, and Quasar docs
+- Quasar props, slots, events, and NiceGUI customization methods
+- Tailwind for structural styling and static stylesheets for fine tuning
 - responsive layout and static asset conventions
 - Tailwind and Quasar breakpoint scales, container queries, and responsive testing
 - uniformly scaling dialogs on mobile
@@ -63,6 +63,15 @@ Load [architecture and styling](./references/architecture-and-styling.md) for:
 - sizing scrollable dialog cards under CSS `zoom`
 - validating zoomed controls with Playwright or a browser
 
+### Special Component Customization
+
+Load [special component customization](./references/special-component-customization.md) for:
+
+- the required source-research gate before generating component customizations
+- `ui.select` constructors, Quasar props, slots, detached popups, and option caveats
+- `ui.icon` names, icon families, sizing, colors, assets, and Material Symbol variants
+- component-specific accessibility, sanitization, and validation checks
+
 ### Bindable State
 
 Load [bindable dataclasses](./references/binding-dataclasses.md) for:
@@ -103,12 +112,14 @@ Load [source documentation](./references/source-documentation.md) when:
 
 1. Load [application architecture](./references/architecture.md).
 2. Add [FastAPI and Uvicorn startup](./references/fastapi-uvicorn-startup.md) when FastAPI owns the application or startup must be exposed as a project command.
-3. Add [architecture and styling](./references/architecture-and-styling.md) only when page and component design is in scope.
+3. Add [styling and customization](./references/styling-and-customization.md) only when page layout or visual customization is in scope.
 
 ### Page Or Component Work
 
-1. Load [architecture and styling](./references/architecture-and-styling.md).
-2. Add [interaction patterns](./references/interaction-patterns.md) or [bindable dataclasses](./references/binding-dataclasses.md) according to the page behavior.
+1. Load [application architecture](./references/architecture.md) for page and component ownership decisions.
+2. Load [styling and customization](./references/styling-and-customization.md) for layout, responsive behavior, or visual customization.
+3. Add [special component customization](./references/special-component-customization.md) when the work targets `ui.select`, `ui.icon`, or another component with specialized Quasar behavior.
+4. Add [interaction patterns](./references/interaction-patterns.md) or [bindable dataclasses](./references/binding-dataclasses.md) according to the page behavior.
 
 ### Debugging Or Production Review
 
@@ -122,7 +133,9 @@ Load [source documentation](./references/source-documentation.md) when:
 - Keep business logic out of UI components and event handlers.
 - Avoid blocking I/O and CPU-heavy work in the UI event loop.
 - Prefer event-driven updates and explicit refreshes over unrelated polling.
-- Prefer Tailwind utilities, then Quasar props, then reusable component helpers; use minimal shared CSS when those are insufficient.
+- Discover component capabilities through NiceGUI docs and constructors, then the wrapped Quasar API.
+- Research the current NiceGUI and Quasar source documentation before generating component-specific code or CSS.
+- Prefer constructor arguments and native Quasar features through NiceGUI; use Tailwind for structure and scoped static CSS for stable fine tuning.
 - Provide loading, success, and failure states for user-triggered work.
 - Treat version-specific guidance as a prompt to verify the project's dependency version.