You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing UI, prefer breaking larger components up into smaller parts.
7
+
When writing UI components, prefer breaking larger components up into smaller parts.
8
8
9
9
ALWAYS write a Storybook story for any component written. If editing a component, ensure appropriate changes have been made to stories for that component.
10
10
@@ -31,20 +31,23 @@ const INSTRUCTIONS = `
31
31
};
32
32
\`\`\`
33
33
34
-
ALWAYS provide story links after any modification to stories files, including updates to existing stories.
35
-
Even later in a session when modifying stories that have already been linked to previously.
36
-
Use the ${GET_STORY_URLS_TOOL_NAME} tool and provide links in the format \`[Story Name](<story_url_from_tool>)\`
34
+
ALWAYS provide story links after any changes to stories files, including changes to existing stories.
35
+
After changing any UI components, ALWAYS search for related stories that might cover the changes you've made.
36
+
If you find any, provide the story links to the user. THIS IS VERY IMPORTANT, as it allows the user
37
+
to visually inspect the modifications you've made.
38
+
Even later in a session when changing UI components or stories that have already been linked to previously, YOU MUST PROVIDE THE LINKS AGAIN.
39
+
Use the ${GET_STORY_URLS_TOOL_NAME} tool /and provide links in the format \`[Story Name](<story_url_from_tool>)\`
37
40
whenever you create, modify, or update any story file.
0 commit comments