npm - quiver-cli - Versions diffs - 1.3.0 → 2.0.0 - Mend

quiver-cli 1.3.0 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (384) hide show

package/template/.agents/skills/code/vercel-react-best-practices/rules/rendering-resource-hints.md DELETED Viewed

@@ -1,85 +0,0 @@
----
-title: Use React DOM Resource Hints
-impact: HIGH
-impactDescription: reduces load time for critical resources
-tags: rendering, preload, preconnect, prefetch, resource-hints
----
-## Use React DOM Resource Hints
-**Impact: HIGH (reduces load time for critical resources)**
-React DOM provides APIs to hint the browser about resources it will need. These are especially useful in server components to start loading resources before the client even receives the HTML.
-- **`prefetchDNS(href)`**: Resolve DNS for a domain you expect to connect to
-- **`preconnect(href)`**: Establish connection (DNS + TCP + TLS) to a server
-- **`preload(href, options)`**: Fetch a resource (stylesheet, font, script, image) you'll use soon
-- **`preloadModule(href)`**: Fetch an ES module you'll use soon
-- **`preinit(href, options)`**: Fetch and evaluate a stylesheet or script
-- **`preinitModule(href)`**: Fetch and evaluate an ES module
-**Example (preconnect to third-party APIs):**
-```tsx
-import { preconnect, prefetchDNS } from 'react-dom'
-export default function App() {
-  prefetchDNS('https://analytics.example.com')
-  preconnect('https://api.example.com')
-  return <main>{/* content */}</main>
-}
-```
-**Example (preload critical fonts and styles):**
-```tsx
-import { preload, preinit } from 'react-dom'
-export default function RootLayout({ children }) {
-  // Preload font file
-  preload('/fonts/inter.woff2', { as: 'font', type: 'font/woff2', crossOrigin: 'anonymous' })
-  // Fetch and apply critical stylesheet immediately
-  preinit('/styles/critical.css', { as: 'style' })
-  return (
-    <html>
-      <body>{children}</body>
-    </html>
-  )
-}
-```
-**Example (preload modules for code-split routes):**
-```tsx
-import { preloadModule, preinitModule } from 'react-dom'
-function Navigation() {
-  const preloadDashboard = () => {
-    preloadModule('/dashboard.js', { as: 'script' })
-  }
-  return (
-    <nav>
-      <a href="/dashboard" onMouseEnter={preloadDashboard}>
-        Dashboard
-      </a>
-    </nav>
-  )
-}
-```
-**When to use each:**
-| API | Use case |
-|-----|----------|
-| `prefetchDNS` | Third-party domains you'll connect to later |
-| `preconnect` | APIs or CDNs you'll fetch from immediately |
-| `preload` | Critical resources needed for current page |
-| `preloadModule` | JS modules for likely next navigation |
-| `preinit` | Stylesheets/scripts that must execute early |
-| `preinitModule` | ES modules that must execute early |
-Reference: [React DOM Resource Preloading APIs](https://react.dev/reference/react-dom#resource-preloading-apis)

package/template/.agents/skills/code/vercel-react-best-practices/rules/rendering-script-defer-async.md DELETED Viewed

@@ -1,68 +0,0 @@
----
-title: Use defer or async on Script Tags
-impact: HIGH
-impactDescription: eliminates render-blocking
-tags: rendering, script, defer, async, performance
----
-## Use defer or async on Script Tags
-**Impact: HIGH (eliminates render-blocking)**
-Script tags without `defer` or `async` block HTML parsing while the script downloads and executes. This delays First Contentful Paint and Time to Interactive.
-- **`defer`**: Downloads in parallel, executes after HTML parsing completes, maintains execution order
-- **`async`**: Downloads in parallel, executes immediately when ready, no guaranteed order
-Use `defer` for scripts that depend on DOM or other scripts. Use `async` for independent scripts like analytics.
-**Incorrect (blocks rendering):**
-```tsx
-export default function Document() {
-  return (
-    <html>
-      <head>
-        <script src="https://example.com/analytics.js" />
-        <script src="/scripts/utils.js" />
-      </head>
-      <body>{/* content */}</body>
-    </html>
-  )
-}
-```
-**Correct (non-blocking):**
-```tsx
-export default function Document() {
-  return (
-    <html>
-      <head>
-        {/* Independent script - use async */}
-        <script src="https://example.com/analytics.js" async />
-        {/* DOM-dependent script - use defer */}
-        <script src="/scripts/utils.js" defer />
-      </head>
-      <body>{/* content */}</body>
-    </html>
-  )
-}
-```
-**Note:** In Next.js, prefer the `next/script` component with `strategy` prop instead of raw script tags:
-```tsx
-import Script from 'next/script'
-export default function Page() {
-  return (
-    <>
-      <Script src="https://example.com/analytics.js" strategy="afterInteractive" />
-      <Script src="/scripts/utils.js" strategy="beforeInteractive" />
-    </>
-  )
-}
-```
-Reference: [MDN - Script element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script#defer)

package/template/.agents/skills/code/vercel-react-best-practices/rules/rendering-svg-precision.md DELETED Viewed

@@ -1,28 +0,0 @@
----
-title: Optimize SVG Precision
-impact: LOW
-impactDescription: reduces file size
-tags: rendering, svg, optimization, svgo
----
-## Optimize SVG Precision
-Reduce SVG coordinate precision to decrease file size. The optimal precision depends on the viewBox size, but in general reducing precision should be considered.
-**Incorrect (excessive precision):**
-```svg
-<path d="M 10.293847 20.847362 L 30.938472 40.192837" />
-```
-**Correct (1 decimal place):**
-```svg
-<path d="M 10.3 20.8 L 30.9 40.2" />
-```
-**Automate with SVGO:**
-```bash
-npx svgo --precision=1 --multipass icon.svg
-```

package/template/.agents/skills/code/vercel-react-best-practices/rules/rendering-usetransition-loading.md DELETED Viewed

@@ -1,75 +0,0 @@
----
-title: Use useTransition Over Manual Loading States
-impact: LOW
-impactDescription: reduces re-renders and improves code clarity
-tags: rendering, transitions, useTransition, loading, state
----
-## Use useTransition Over Manual Loading States
-Use `useTransition` instead of manual `useState` for loading states. This provides built-in `isPending` state and automatically manages transitions.
-**Incorrect (manual loading state):**
-```tsx
-function SearchResults() {
-  const [query, setQuery] = useState('')
-  const [results, setResults] = useState([])
-  const [isLoading, setIsLoading] = useState(false)
-  const handleSearch = async (value: string) => {
-    setIsLoading(true)
-    setQuery(value)
-    const data = await fetchResults(value)
-    setResults(data)
-    setIsLoading(false)
-  }
-  return (
-    <>
-      <input onChange={(e) => handleSearch(e.target.value)} />
-      {isLoading && <Spinner />}
-      <ResultsList results={results} />
-    </>
-  )
-}
-```
-**Correct (useTransition with built-in pending state):**
-```tsx
-import { useTransition, useState } from 'react'
-function SearchResults() {
-  const [query, setQuery] = useState('')
-  const [results, setResults] = useState([])
-  const [isPending, startTransition] = useTransition()
-  const handleSearch = (value: string) => {
-    setQuery(value) // Update input immediately
-    startTransition(async () => {
-      // Fetch and update results
-      const data = await fetchResults(value)
-      setResults(data)
-    })
-  }
-  return (
-    <>
-      <input onChange={(e) => handleSearch(e.target.value)} />
-      {isPending && <Spinner />}
-      <ResultsList results={results} />
-    </>
-  )
-}
-```
-**Benefits:**
-- **Automatic pending state**: No need to manually manage `setIsLoading(true/false)`
-- **Error resilience**: Pending state correctly resets even if the transition throws
-- **Better responsiveness**: Keeps the UI responsive during updates
-- **Interrupt handling**: New transitions automatically cancel pending ones
-Reference: [useTransition](https://react.dev/reference/react/useTransition)

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-defer-reads.md DELETED Viewed

@@ -1,39 +0,0 @@
----
-title: Defer State Reads to Usage Point
-impact: MEDIUM
-impactDescription: avoids unnecessary subscriptions
-tags: rerender, searchParams, localStorage, optimization
----
-## Defer State Reads to Usage Point
-Don't subscribe to dynamic state (searchParams, localStorage) if you only read it inside callbacks.
-**Incorrect (subscribes to all searchParams changes):**
-```tsx
-function ShareButton({ chatId }: { chatId: string }) {
-  const searchParams = useSearchParams()
-  const handleShare = () => {
-    const ref = searchParams.get('ref')
-    shareChat(chatId, { ref })
-  }
-  return <button onClick={handleShare}>Share</button>
-}
-```
-**Correct (reads on demand, no subscription):**
-```tsx
-function ShareButton({ chatId }: { chatId: string }) {
-  const handleShare = () => {
-    const params = new URLSearchParams(window.location.search)
-    const ref = params.get('ref')
-    shareChat(chatId, { ref })
-  }
-  return <button onClick={handleShare}>Share</button>
-}
-```

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-dependencies.md DELETED Viewed

@@ -1,45 +0,0 @@
----
-title: Narrow Effect Dependencies
-impact: LOW
-impactDescription: minimizes effect re-runs
-tags: rerender, useEffect, dependencies, optimization
----
-## Narrow Effect Dependencies
-Specify primitive dependencies instead of objects to minimize effect re-runs.
-**Incorrect (re-runs on any user field change):**
-```tsx
-useEffect(() => {
-  console.log(user.id)
-}, [user])
-```
-**Correct (re-runs only when id changes):**
-```tsx
-useEffect(() => {
-  console.log(user.id)
-}, [user.id])
-```
-**For derived state, compute outside effect:**
-```tsx
-// Incorrect: runs on width=767, 766, 765...
-useEffect(() => {
-  if (width < 768) {
-    enableMobileMode()
-  }
-}, [width])
-// Correct: runs only on boolean transition
-const isMobile = width < 768
-useEffect(() => {
-  if (isMobile) {
-    enableMobileMode()
-  }
-}, [isMobile])
-```

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-derived-state-no-effect.md DELETED Viewed

@@ -1,40 +0,0 @@
----
-title: Calculate Derived State During Rendering
-impact: MEDIUM
-impactDescription: avoids redundant renders and state drift
-tags: rerender, derived-state, useEffect, state
----
-## Calculate Derived State During Rendering
-If a value can be computed from current props/state, do not store it in state or update it in an effect. Derive it during render to avoid extra renders and state drift. Do not set state in effects solely in response to prop changes; prefer derived values or keyed resets instead.
-**Incorrect (redundant state and effect):**
-```tsx
-function Form() {
-  const [firstName, setFirstName] = useState('First')
-  const [lastName, setLastName] = useState('Last')
-  const [fullName, setFullName] = useState('')
-  useEffect(() => {
-    setFullName(firstName + ' ' + lastName)
-  }, [firstName, lastName])
-  return <p>{fullName}</p>
-}
-```
-**Correct (derive during render):**
-```tsx
-function Form() {
-  const [firstName, setFirstName] = useState('First')
-  const [lastName, setLastName] = useState('Last')
-  const fullName = firstName + ' ' + lastName
-  return <p>{fullName}</p>
-}
-```
-References: [You Might Not Need an Effect](https://react.dev/learn/you-might-not-need-an-effect)

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-derived-state.md DELETED Viewed

@@ -1,29 +0,0 @@
----
-title: Subscribe to Derived State
-impact: MEDIUM
-impactDescription: reduces re-render frequency
-tags: rerender, derived-state, media-query, optimization
----
-## Subscribe to Derived State
-Subscribe to derived boolean state instead of continuous values to reduce re-render frequency.
-**Incorrect (re-renders on every pixel change):**
-```tsx
-function Sidebar() {
-  const width = useWindowWidth()  // updates continuously
-  const isMobile = width < 768
-  return <nav className={isMobile ? 'mobile' : 'desktop'} />
-}
-```
-**Correct (re-renders only when boolean changes):**
-```tsx
-function Sidebar() {
-  const isMobile = useMediaQuery('(max-width: 767px)')
-  return <nav className={isMobile ? 'mobile' : 'desktop'} />
-}
-```

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-functional-setstate.md DELETED Viewed

@@ -1,74 +0,0 @@
----
-title: Use Functional setState Updates
-impact: MEDIUM
-impactDescription: prevents stale closures and unnecessary callback recreations
-tags: react, hooks, useState, useCallback, callbacks, closures
----
-## Use Functional setState Updates
-When updating state based on the current state value, use the functional update form of setState instead of directly referencing the state variable. This prevents stale closures, eliminates unnecessary dependencies, and creates stable callback references.
-**Incorrect (requires state as dependency):**
-```tsx
-function TodoList() {
-  const [items, setItems] = useState(initialItems)
-  // Callback must depend on items, recreated on every items change
-  const addItems = useCallback((newItems: Item[]) => {
-    setItems([...items, ...newItems])
-  }, [items])  // ❌ items dependency causes recreations
-  // Risk of stale closure if dependency is forgotten
-  const removeItem = useCallback((id: string) => {
-    setItems(items.filter(item => item.id !== id))
-  }, [])  // ❌ Missing items dependency - will use stale items!
-  return <ItemsEditor items={items} onAdd={addItems} onRemove={removeItem} />
-}
-```
-The first callback is recreated every time `items` changes, which can cause child components to re-render unnecessarily. The second callback has a stale closure bug—it will always reference the initial `items` value.
-**Correct (stable callbacks, no stale closures):**
-```tsx
-function TodoList() {
-  const [items, setItems] = useState(initialItems)
-  // Stable callback, never recreated
-  const addItems = useCallback((newItems: Item[]) => {
-    setItems(curr => [...curr, ...newItems])
-  }, [])  // ✅ No dependencies needed
-  // Always uses latest state, no stale closure risk
-  const removeItem = useCallback((id: string) => {
-    setItems(curr => curr.filter(item => item.id !== id))
-  }, [])  // ✅ Safe and stable
-  return <ItemsEditor items={items} onAdd={addItems} onRemove={removeItem} />
-}
-```
-**Benefits:**
-1. **Stable callback references** - Callbacks don't need to be recreated when state changes
-2. **No stale closures** - Always operates on the latest state value
-3. **Fewer dependencies** - Simplifies dependency arrays and reduces memory leaks
-4. **Prevents bugs** - Eliminates the most common source of React closure bugs
-**When to use functional updates:**
-- Any setState that depends on the current state value
-- Inside useCallback/useMemo when state is needed
-- Event handlers that reference state
-- Async operations that update state
-**When direct updates are fine:**
-- Setting state to a static value: `setCount(0)`
-- Setting state from props/arguments only: `setName(newName)`
-- State doesn't depend on previous value
-**Note:** If your project has [React Compiler](https://react.dev/learn/react-compiler) enabled, the compiler can automatically optimize some cases, but functional updates are still recommended for correctness and to prevent stale closure bugs.

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-lazy-state-init.md DELETED Viewed

@@ -1,58 +0,0 @@
----
-title: Use Lazy State Initialization
-impact: MEDIUM
-impactDescription: wasted computation on every render
-tags: react, hooks, useState, performance, initialization
----
-## Use Lazy State Initialization
-Pass a function to `useState` for expensive initial values. Without the function form, the initializer runs on every render even though the value is only used once.
-**Incorrect (runs on every render):**
-```tsx
-function FilteredList({ items }: { items: Item[] }) {
-  // buildSearchIndex() runs on EVERY render, even after initialization
-  const [searchIndex, setSearchIndex] = useState(buildSearchIndex(items))
-  const [query, setQuery] = useState('')
-  // When query changes, buildSearchIndex runs again unnecessarily
-  return <SearchResults index={searchIndex} query={query} />
-}
-function UserProfile() {
-  // JSON.parse runs on every render
-  const [settings, setSettings] = useState(
-    JSON.parse(localStorage.getItem('settings') || '{}')
-  )
-  return <SettingsForm settings={settings} onChange={setSettings} />
-}
-```
-**Correct (runs only once):**
-```tsx
-function FilteredList({ items }: { items: Item[] }) {
-  // buildSearchIndex() runs ONLY on initial render
-  const [searchIndex, setSearchIndex] = useState(() => buildSearchIndex(items))
-  const [query, setQuery] = useState('')
-  return <SearchResults index={searchIndex} query={query} />
-}
-function UserProfile() {
-  // JSON.parse runs only on initial render
-  const [settings, setSettings] = useState(() => {
-    const stored = localStorage.getItem('settings')
-    return stored ? JSON.parse(stored) : {}
-  })
-  return <SettingsForm settings={settings} onChange={setSettings} />
-}
-```
-Use lazy initialization when computing initial values from localStorage/sessionStorage, building data structures (indexes, maps), reading from the DOM, or performing heavy transformations.
-For simple primitives (`useState(0)`), direct references (`useState(props.value)`), or cheap literals (`useState({})`), the function form is unnecessary.

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-memo-with-default-value.md DELETED Viewed

@@ -1,38 +0,0 @@
----
-title: Extract Default Non-primitive Parameter Value from Memoized Component to Constant
-impact: MEDIUM
-impactDescription: restores memoization by using a constant for default value
-tags: rerender, memo, optimization
----
-## Extract Default Non-primitive Parameter Value from Memoized Component to Constant
-When memoized component has a default value for some non-primitive optional parameter, such as an array, function, or object, calling the component without that parameter results in broken memoization. This is because new value instances are created on every rerender, and they do not pass strict equality comparison in `memo()`.
-To address this issue, extract the default value into a constant.
-**Incorrect (`onClick` has different values on every rerender):**
-```tsx
-const UserAvatar = memo(function UserAvatar({ onClick = () => {} }: { onClick?: () => void }) {
-  // ...
-})
-// Used without optional onClick
-<UserAvatar />
-```
-**Correct (stable default value):**
-```tsx
-const NOOP = () => {};
-const UserAvatar = memo(function UserAvatar({ onClick = NOOP }: { onClick?: () => void }) {
-  // ...
-})
-// Used without optional onClick
-<UserAvatar />
-```

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-memo.md DELETED Viewed

@@ -1,44 +0,0 @@
----
-title: Extract to Memoized Components
-impact: MEDIUM
-impactDescription: enables early returns
-tags: rerender, memo, useMemo, optimization
----
-## Extract to Memoized Components
-Extract expensive work into memoized components to enable early returns before computation.
-**Incorrect (computes avatar even when loading):**
-```tsx
-function Profile({ user, loading }: Props) {
-  const avatar = useMemo(() => {
-    const id = computeAvatarId(user)
-    return <Avatar id={id} />
-  }, [user])
-  if (loading) return <Skeleton />
-  return <div>{avatar}</div>
-}
-```
-**Correct (skips computation when loading):**
-```tsx
-const UserAvatar = memo(function UserAvatar({ user }: { user: User }) {
-  const id = useMemo(() => computeAvatarId(user), [user])
-  return <Avatar id={id} />
-})
-function Profile({ user, loading }: Props) {
-  if (loading) return <Skeleton />
-  return (
-    <div>
-      <UserAvatar user={user} />
-    </div>
-  )
-}
-```
-**Note:** If your project has [React Compiler](https://react.dev/learn/react-compiler) enabled, manual memoization with `memo()` and `useMemo()` is not necessary. The compiler automatically optimizes re-renders.

package/template/.agents/skills/code/vercel-react-best-practices/rules/rerender-move-effect-to-event.md DELETED Viewed

@@ -1,45 +0,0 @@
----
-title: Put Interaction Logic in Event Handlers
-impact: MEDIUM
-impactDescription: avoids effect re-runs and duplicate side effects
-tags: rerender, useEffect, events, side-effects, dependencies
----
-## Put Interaction Logic in Event Handlers
-If a side effect is triggered by a specific user action (submit, click, drag), run it in that event handler. Do not model the action as state + effect; it makes effects re-run on unrelated changes and can duplicate the action.
-**Incorrect (event modeled as state + effect):**
-```tsx
-function Form() {
-  const [submitted, setSubmitted] = useState(false)
-  const theme = useContext(ThemeContext)
-  useEffect(() => {
-    if (submitted) {
-      post('/api/register')
-      showToast('Registered', theme)
-    }
-  }, [submitted, theme])
-  return <button onClick={() => setSubmitted(true)}>Submit</button>
-}
-```
-**Correct (do it in the handler):**
-```tsx
-function Form() {
-  const theme = useContext(ThemeContext)
-  function handleSubmit() {
-    post('/api/register')
-    showToast('Registered', theme)
-  }
-  return <button onClick={handleSubmit}>Submit</button>
-}
-```
-Reference: [Should this code move to an event handler?](https://react.dev/learn/removing-effect-dependencies#should-this-code-move-to-an-event-handler)