@structuralists/scaffolding 0.0.2 → 0.1.0

package/.storybook/main.ts

@@ -3,7 +3,7 @@ import type { StorybookConfig } from '@storybook/react-vite';
 const config: StorybookConfig = {
   framework: '@storybook/react-vite',
   stories: ['../src/**/*.stories.@(ts|tsx)'],
-  addons: ['@storybook/addon-essentials', '@storybook/addon-storysource'],
+  addons: ['@storybook/addon-docs'],
 };
 
 export default config;

package/.storybook/preview.tsx

@@ -1,10 +1,14 @@
-import type { Preview } from '@storybook/react';
+import type { Preview } from '@storybook/react-vite';
 import { MemoryRouter } from 'react-router';
 import '../tokens.css';
 
 const preview: Preview = {
   parameters: {
     layout: 'padded',
+
+    docs: {
+      codePanel: true
+    }
   },
   decorators: [
     (Story) => (

package/CLAUDE.md

@@ -28,3 +28,28 @@ export const Foo = ({ a, b, c }: FooProps) => {
 Why: the destructuring line at the top of the body acts as a quick legend
 of what the component reads from its props, scannable without parsing the
 function signature. Keeps the call shape uniform across the package.
+
+### Custom hook arguments
+
+Project-defined hooks must take a single argument named `args` (an object)
+and destructure on the first line of the function body — same shape as the
+component-prop rule above.
+
+```ts
+// ✅ correct
+export const useFoo = (args: UseFooArgs) => {
+  const { a, b, c } = args;
+  // ...
+};
+
+// ❌ wrong — positional args
+export const useFoo = (a: string, b: number, c?: boolean) => {
+  // ...
+};
+```
+
+Why: named args read clearly at the call site (`useFoo({ a, b })`), survive
+reordering, and let new optional fields be added without breaking callers.
+Built-in React hooks (`useState`, `useEffect`, etc.) keep their stock
+positional signatures — this rule applies only to hooks defined in this
+package.