Menu
Guidelines for creating or updating UI components, ensuring tests and documentation stay in sync.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
Guides the process of pulling in new or updated shadcn components and integrating them into the monorepo architecture (ui-core, ui-web, ui-native, docs).
Guidelines for using library components within the documentation site itself to ensure consistency and showcase real-world usage.
Guidelines for updating and synchronizing design tokens across the monorepo.
| name | maintain-component |
| description | Guidelines for creating or updating UI components, ensuring tests and documentation stay in sync. |
Use this skill whenever you are tasked with creating a new UI component or modifying an existing one in the gvtech-design library. All components must follow the monorepo-based architecture to support Web, React Native, and shared contracts.
Components are split across three primary packages:
@gv-tech/ui-core: Shared contracts/interfaces.
packages/ui-core/src/contracts/[name].ts@gv-tech/ui-web: Web (DOM/Radix) implementation.
packages/ui-web/src/[name].tsxpackages/ui-web/src/[name].test.tsx@gv-tech/ui-native: React Native (NativeWind) implementation.
packages/ui-native/src/[name].tsxpackages/ui-core/src/contracts/[name].ts.packages/ui-core/src/index.ts.any. Use unknown or specific interfaces for extension.packages/ui-web/src/[name].tsx.@gv-tech/ui-core.cn) from ./lib/utils (relative).packages/ui-web/src/index.ts.packages/ui-native/src/[name].tsx../lib/utils (relative).packages/ui-native/src/index.ts.apps/playground-web/src/pages/web/[ComponentName]Docs.tsx.apps/playground-web/src/pages/native/[ComponentName]Docs.tsx.ComponentSection (this is now handled by the layout). They should return a React Fragment <>...</> containing ComponentShowcase and implementations.apps/playground-web/src/App.tsx.<CombinedDocsLayout /> and pass the title, description, web, and native implementations as props.PropsTable matches the ui-core contract and covers both platforms if they differ.bun build:registry to update the component JSON files in public/registry.bun validate from the root. This runs:
sync-tokens: Ensures design tokens are updated.lint: Checks project-wide ESLint (no any, no unused vars).tsc: Verifies TypeScript types across all workspaces.test: Runs Vitest across all packages.build: Verifies Vite/Nx build status.packages/ui-core/src/contracts/.packages/ui-core/src/index.ts.packages/ui-web/src/.packages/ui-native/src/.index.ts in respective packages.apps/playground-web/src/pages/web/ (without ComponentSection).apps/playground-web/src/pages/native/ (without ComponentSection).apps/playground-web/src/App.tsx using CombinedDocsLayout with title and description.bun build:registry run to update public registry.bun validate passes successfully (Green state).any types used in new/modified code.