Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
Passed 22 of 23 test cases with the skill, and 12 of 23 without it.
and 13 more in the full report
11 fixed11 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should unit tests for a newly added store be placed in the project directory hierarchy?
| Checked | Without skill | With skill |
|---|---|---|
| The test file is placed in src/frontend/src/store/ with a .test.ts extension. | Missed | Passed |
The instructions your model reads when the skill loads.
Create Zustand stores following established patterns with proper TypeScript types and middleware.
Copy the template from assets/template.ts and replace placeholders:
{{StoreName}} → PascalCase store name (e.g., Project){{description}} → Brief description for JSDocimport { create } from 'zustand';
import { subscribeWithSelector } from 'zustand/middleware';
export const useMyStore = create<MyStore>()(
subscribeWithSelector((set, get) => ({
// state and actions
}))
);
export interface MyState {
items: Item[];
isLoading: boolean;
}
export interface MyActions {
addItem: (item: Item) => void;
loadItems: () => Promise<void>;
}
export type MyStore = MyState & MyActions;
test cases passed, vs 12 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.