بنقرة واحدة
new-story
Generate a Storybook story for a component using real components and project CSS classes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Generate a Storybook story for a component using real components and project CSS classes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when wanting to systematically improve the React/TypeScript frontend - scans for security vulnerabilities, stability risks, performance issues, and code simplification opportunities, then presents 5 ranked findings for the user to choose from
Add support for a Kubernetes resource type by choosing the required catalog, refresh, detail, object-map, permission, frontend, docs, and test surfaces
Guide for safely modifying the refresh/streaming subsystem — covers the full domain lifecycle, registration points, and known fragility areas
Use when eliminating representable-but-invalid states in Luxury Yacht — converting boolean flag-soup to discriminated unions, making required identity fields non-optional, replacing stringly-typed states with literal/typed enums, and pushing scattered runtime guards into the type system or a single chokepoint. Triggers — "make impossible states impossible", flag soup (isLoading/isError/isEmpty), contradictory nullable fields, kind-only/name-only object refs, stringly-typed status, or the docs/todo.md item of the same name.
Work on Luxury Yacht object-panel details, YAML, actions, logs, shell/debug tabs, docked panels, related objects, and tests
Use for large-scale structural Luxury Yacht app reviews that audit broad systems or cross-cutting concerns, identify major simplification, hardening, optimization, or refactoring opportunities, and optionally write temporary phased plans in docs/plans
| name | new-story |
| description | Generate a Storybook story for a component using real components and project CSS classes |
Generate a Storybook story for a given component.
/new-story <ComponentPath> — path to the component (e.g. frontend/src/ui/modals/MyModal.tsx)
window.__storybookGoOverrides, mock props with realistic data. Never mock the component's visual output.frontend/.storybook/decorators/ for providers:
SidebarProvidersDecorator — KubeconfigProvider + NamespaceProviderAppearanceModeProviderDecorator — appearance mode contextKeyboardProviderDecorator — keyboard shortcutsKubeconfigProviderDecorator — kubeconfig onlyZoomProviderDecorator — zoom contextfrontend/.storybook/mocks/ for Go backend mocks (wailsBackendApp.ts, wailsBackendSettings.ts, wailsModels.ts)..stories.tsx file next to the component it tests./**
* <file path>
*
* Storybook stories for the <ComponentName> component.
*/
import type { Meta, StoryObj } from '@storybook/react';
import <ComponentName> from './<ComponentName>';
// import decorators as needed
const meta: Meta<typeof <ComponentName>> = {
title: '<Category>/<ComponentName>',
component: <ComponentName>,
// decorators: [SidebarProvidersDecorator],
};
export default meta;
type Story = StoryObj<typeof <ComponentName>>;
/** Default state. */
export const Default: Story = {
args: {
// realistic props
},
};
After creating the story, run npx tsc --noEmit from the frontend/ directory to confirm it compiles without errors.