Implement catalog-backed browse and refresh behavior for Kubernetes cluster and namespace tables.
npx skills add https://github.com/luxury-yacht/app --skill browse-tables
Please help me install this Agent Skill. Skill: browse-tables Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/browse-tables Command: npx skills add https://github.com/luxury-yacht/app --skill browse-tables
It solves the challenge of keeping cluster and namespace table views correct, consistent, and performant while data is discovered via a catalog and updated through refresh snapshots and streaming.
Use the browse-tables skill to update a cluster or namespace GridTable change by verifying catalog identity, refreshing snapshot/stream row-shape compatibility, and running the targeted backend and frontend test commands for the affected domains.
High-intent search queries and answers about installing and using this skill.
Kubernetes resource tables stay consistent during refresh and streaming by applying catalog-backed row identity and synchronized refresh domain configuration, ensuring streamed and snapshot row shapes match. This prevents data drift across UI browse surfaces.
Kubernetes UI table rows lose identity during pagination when row identity is not catalog-backed. Implementing identity-preserving browse behavior ensures rows carry complete cluster, GVK, and object identity so listings remain grounded in the object catalog.
Handling large dataset pagination in Kubernetes GridTable views requires a refresh orchestrator to manage truncation diagnostics and load-more behavior. This maintains stable table performance and ensures accurate data boundaries for large result sets.
Shared column factories can be used for both snapshot and streamed Kubernetes table domains. This shared GridTable behavior ensures consistent table rendering and matched row shapes across all browse and catalog surfaces.
Verifying refresh-orchestrator synchronization for Kubernetes namespace browse surfaces involves checking that refresh domains, payload types, refresher configuration, diagnostics, backend registration, and stream descriptors are all aligned.
Streaming for Kubernetes cluster table views should be avoided when refresh domain configuration cannot be synchronized or when streamed and snapshot row shapes cannot be matched, as this breaks identity-preserving browse behavior and catalog grounding.
luxury-yachtUnify Kubernetes resource identity and status presentation across backend projections and frontend rendering.
kasiopeiyaExecute backend and frontend unit tests with Vitest and generate detailed reports.
rodrigotoledoIdentify business domains and group components into logical domains.
kuse-aiBuild reusable UI components for React, Vue, and vanilla JavaScript.
