refactor(skill): generalize component scaffolding guidance beyond Mantine

Author: tmt823

skills/react-clean-architecture-add-component/SKILL.md

@@ -34,7 +34,7 @@ Question requirements:
 
 - Provide the type as options (`ui`, `features`)
 - Require the component name to be in PascalCase
-- For `ui`, ask whether direct Mantine usage in existing `features` should be replaced with the new component
+- For `ui`, ask whether direct usage of Mantine or other UI libraries in existing `features` should be replaced with the new component
 
 ## Procedure
 
@@ -63,7 +63,7 @@ Question requirements:
 
 5. Replace existing usages (only when creating `ui`)
 
-- Only when the user approves, replace equivalent direct Mantine implementations in existing `features` with the new `ui` component.
+- Only when the user approves, replace equivalent direct implementations using Mantine or other UI libraries in existing `features` with the new `ui` component.
 
 6. Validate
 

skills/react-clean-architecture-add-component/references/component-architecture.md

@@ -30,7 +30,7 @@ Ask using these options:
 - Keep components stateless.
 - Accept data and callbacks via props.
 - Do not add side effects or data fetching.
-- Prefer Mantine primitives first; use custom JSX/SCSS only when needed.
+- Prefer primitives from Mantine or other UI libraries first; use custom JSX/SCSS only when needed.
 
 ### features
 

skills/react-clean-architecture-add-component/references/typescript-and-scss-rules.md

@@ -20,7 +20,7 @@ This reference defines coding rules required by the `add-component` skill.
 
 ### Style Constraints
 
-- Prefer Mantine first; use SCSS only when complementing Mantine styles is necessary.
+- Prefer Mantine or other UI libraries first; use SCSS only when complementing library styles is necessary.
 - Do not use negative margins.
 - Prefer unitless `line-height`.
 - Prefer `letter-spacing` in `em`.