ai

This allows for parallel testing (so that it doesn't take 20 minutes per model to run the suite 😄)

Test Name svelte-reactivity Test Description It would be nice to test the ability of using purposefully non-deeply reactive values correctly, avoid common gotchas and avoid letting LLMs reimplement svelte/reactivity functionality. For example: https://svelte.dev/playground/6133806fa4ff4ce09e2f0d393e1d6084?version=5.46.4 Usage of createSubscriber too -- but I can't think of a way of testing a generalized approach that checks footguns like creating useless subscribers or a new one on every "get", etc. (Not in the proposed prompt) Skills would help a lot here, but interested in seeing their "native" approach. Proposed prompt was generated by Gemini 3 Flash, but changed most of it since it was too extensive. Even now it's not very generic. Proposed Prompt Component Task Create a dashboard that tracks multiple counters using different data structures. The goal is to demonstrate the nuances of Svelte 5's deep reactivity, specifically focusing on why values require explicit wrapping compared to standard POJOs. Requirements Deep Reactivity (POJO): Show a standard nested object where properties are automatically reactive (e.g., ). Correct SvelteMap Usage: Implement a SvelteMap where values are explicitly wrapped in before being stored, ensuring deep reactivity works as expected. Safe Lifecycle**: Ensure a proper cleanup function is returned. Reference Implementation (optional) Additional Context _No response_