skills.rest
luxury-yacht
luxury-yachtOFFICIAL
Explore all skills by this author →
GitHub

add-resource

Implement Kubernetes resource types across catalog, detail, and UI surfaces.

411|21|Updated Dec 18, 2025
Search Tags:#kubernetes#frontend integration#resource modeling#backend services#rbac permissions#object details#object map
One-click install
npx skills add https://github.com/luxury-yacht/app --skill add-resource-luxury-yacht
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-resource
Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/add-resource
Command: npx skills add https://github.com/luxury-yacht/app --skill add-resource-luxury-yacht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add first-class support for a Kubernetes resource type so it can be discovered and managed consistently across catalog, refresh, rich object details, YAML/edit/apply, and UI capabilities.

Core Features & Use Cases

  • Define the resource’s surface matrix up front: choose which discovery, list/table, streaming, detail, permissions, and documentation/test surfaces are required rather than implementing only a detail view.
  • Wire backend rich detail and action support: create a detail service, DTO types, and object detail provider dispatch so the object panel can fetch and render the new resource’s specifics.
  • Ensure shared model correctness: implement the shared resource model so status, facts, links, and relationships are consistent across consumers and UI presentation.
  • Connect frontend identity and UI behavior: extend Wails/TypeScript bindings and overview rendering, and register the resource’s overview component in the object panel.
  • Update optional cross-cutting systems when needed: seed built-in identity lookups, configure object-map support, and extend refresh/stream surfaces if the resource must appear in tables or live rows.

Quick Start

Use the add-resource skill to add a new built-in Kubernetes Kind by running the instruction to update the shared resource model, implement the backend details service and DTOs, and wire the frontend object panel payload and overview registration.

Frequently Asked Questions about add-resource

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new Kubernetes resource type to my catalog and UI?▼

Adding a Kubernetes resource type requires defining its surface matrix, implementing the shared resource model, creating backend detail services and DTOs, and extending frontend bindings and object panel capabilities for complete user-visible behavior.

What surfaces need to be implemented for complete Kubernetes resource support?▼

Complete Kubernetes resource support requires implementing discovery, list/table, streaming, rich object details, YAML/edit/apply, RBAC permissions, object map, and related frontend UI surfaces for the new Kind.

How do I wire backend services for Kubernetes object details?▼

You wire backend rich details by creating a detail service, defining DTO types, and registering object detail fetchers with exact GroupVersionKind (GVK) metadata so the object panel can fetch and render the new resource's specifics.

Can I extend frontend bindings to display a custom Kubernetes resource overview?▼

Yes, you extend frontend identity and UI behavior by updating Wails/TypeScript bindings, extending overview rendering, and registering the resource's overview component in the object panel to display the custom Kubernetes resource.

How do I configure RBAC permissions for a newly added Kubernetes resource?▼

You configure RBAC permissions by including them in the resource's surface matrix, seeding built-in identity lookups, and ensuring the shared resource model defines permissions consistently across consumers and UI presentation.

Why is my new Kubernetes resource not appearing in list or streaming views?▼

Your Kubernetes resource is not appearing in list or streaming views because the optional cross-cutting refresh and stream surfaces were not extended to include the new resource type in tables or live rows.

Related Skills

Explore More Software Engineering Skills→
LerianStudioLerianStudio
205

pre-dev-api-design

Define component interfaces and data contracts before protocol selection.

Official
Basic
luxury-yachtluxury-yacht
411

shared-resource-model

Unify Kubernetes resource identity and status presentation across backend projections and frontend rendering.

Official
Advanced
luxury-yachtluxury-yacht
411

object-panel

Coordinate Kubernetes object detail tabs, YAML workflows, logs, and docked panel UX.

Official
Advanced
imMamdouhaboammarimMamdouhaboammar

backend-to-frontend-handoff-docs

Generate structured API handoff documentation from backend source code.

Community
Intermediate