@oriro/orirocli 0.1.11 → 0.1.12

package/skills/craft/vercel-optimize/references/support-topics/middleware-proxy-edge-cost.md

@@ -1,30 +1,30 @@
----
-id: middleware-proxy-edge-cost
-title: Middleware edge cost
-status: active
-candidateKinds: ["middleware_heavy"]
-frameworks: ["next@>=12.0.0"]
-priority: 90
-citations:
-  [
-    "https://nextjs.org/docs/app/building-your-application/routing/middleware",
-    "https://vercel.com/docs/routing-middleware",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-Middleware recommendations should reduce unnecessary interception, not remove required request handling.
-
-## Evidence To Check
-
-Use `topMiddlewarePaths` and the matcher config. Confirm which paths need auth, rewrites, headers, or locale handling. Check whether static assets, images, or routes with no middleware need are being matched.
-
-## Do Not Recommend When
-
-Do not narrow the matcher in a way that bypasses required auth or routing behavior. Do not move middleware work into every route if the current matcher is already scoped.
-
-## Verification
-
-State the current middleware share, the dominant matched paths, and the exact matcher line to change.
+---
+id: middleware-proxy-edge-cost
+title: Middleware edge cost
+status: active
+candidateKinds: ["middleware_heavy"]
+frameworks: ["next@>=12.0.0"]
+priority: 90
+citations:
+  [
+    "https://nextjs.org/docs/app/building-your-application/routing/middleware",
+    "https://vercel.com/docs/routing-middleware",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+Middleware recommendations should reduce unnecessary interception, not remove required request handling.
+
+## Evidence To Check
+
+Use `topMiddlewarePaths` and the matcher config. Confirm which paths need auth, rewrites, headers, or locale handling. Check whether static assets, images, or routes with no middleware need are being matched.
+
+## Do Not Recommend When
+
+Do not narrow the matcher in a way that bypasses required auth or routing behavior. Do not move middleware work into every route if the current matcher is already scoped.
+
+## Verification
+
+State the current middleware share, the dominant matched paths, and the exact matcher line to change.

package/skills/craft/vercel-optimize/references/support-topics/next-fetch-revalidate-floor.md

@@ -1,30 +1,30 @@
----
-id: next-fetch-revalidate-floor
-title: Next.js fetch revalidation floor
-status: active
-candidateKinds: ["uncached_route", "isr_overrevalidation"]
-frameworks: ["next@>=13.0.0"]
-priority: 88
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/functions/fetch",
-    "https://nextjs.org/docs/app/building-your-application/caching",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-Next.js `fetch` options can set the route's effective cache floor. Low `revalidate`, `revalidate: 0`, or `cache: 'no-store'` can explain uncached traffic and excessive ISR work.
-
-## Evidence To Check
-
-Inspect route-tree `fetch` calls. Compare route revalidation with per-fetch `cache`, `next.revalidate`, tags, dynamic APIs, and duplicated URLs with conflicting options.
-
-## Do Not Recommend When
-
-Do not raise freshness windows for pricing, inventory, auth, draft, or user-specific data unless the source proves stale reads are acceptable.
-
-## Verification
-
-Name the observed cache or ISR signal, the lowest cache setting that controls the route, and the exact fetch line to change.
+---
+id: next-fetch-revalidate-floor
+title: Next.js fetch revalidation floor
+status: active
+candidateKinds: ["uncached_route", "isr_overrevalidation"]
+frameworks: ["next@>=13.0.0"]
+priority: 88
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/functions/fetch",
+    "https://nextjs.org/docs/app/building-your-application/caching",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+Next.js `fetch` options can set the route's effective cache floor. Low `revalidate`, `revalidate: 0`, or `cache: 'no-store'` can explain uncached traffic and excessive ISR work.
+
+## Evidence To Check
+
+Inspect route-tree `fetch` calls. Compare route revalidation with per-fetch `cache`, `next.revalidate`, tags, dynamic APIs, and duplicated URLs with conflicting options.
+
+## Do Not Recommend When
+
+Do not raise freshness windows for pricing, inventory, auth, draft, or user-specific data unless the source proves stale reads are acceptable.
+
+## Verification
+
+Name the observed cache or ISR signal, the lowest cache setting that controls the route, and the exact fetch line to change.

package/skills/craft/vercel-optimize/references/support-topics/next-font-cls-self-hosting.md

@@ -1,31 +1,31 @@
----
-id: next-font-cls-self-hosting
-title: Next.js font CLS guardrail
-status: active
-candidateKinds: ["cwv_poor"]
-frameworks: ["next@>=13.2.0"]
-metrics: ["CLS"]
-priority: 86
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/components/font",
-    "https://web.dev/articles/optimize-cls",
-  ]
-maxBriefChars: 800
----
-
-## Investigation Brief
-
-For poor CLS, check fonts only when the route actually loads external font CSS or swaps text after render.
-
-## Evidence To Check
-
-Inspect layouts and global styles for external font links, CSS imports, custom font-face rules, late-loading font classes, and whether `next/font` is already used.
-
-## Do Not Recommend When
-
-Do not migrate fonts when CLS is caused by images, ads, embeds, or injected UI. Do not suggest `next/font` for unsupported Next.js versions.
-
-## Verification
-
-Name the CLS value, font-loading mechanism, and the exact layout or stylesheet line to change.
+---
+id: next-font-cls-self-hosting
+title: Next.js font CLS guardrail
+status: active
+candidateKinds: ["cwv_poor"]
+frameworks: ["next@>=13.2.0"]
+metrics: ["CLS"]
+priority: 86
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/components/font",
+    "https://web.dev/articles/optimize-cls",
+  ]
+maxBriefChars: 800
+---
+
+## Investigation Brief
+
+For poor CLS, check fonts only when the route actually loads external font CSS or swaps text after render.
+
+## Evidence To Check
+
+Inspect layouts and global styles for external font links, CSS imports, custom font-face rules, late-loading font classes, and whether `next/font` is already used.
+
+## Do Not Recommend When
+
+Do not migrate fonts when CLS is caused by images, ads, embeds, or injected UI. Do not suggest `next/font` for unsupported Next.js versions.
+
+## Verification
+
+Name the CLS value, font-loading mechanism, and the exact layout or stylesheet line to change.

package/skills/craft/vercel-optimize/references/support-topics/next-heavy-ui-lazy-load-boundaries.md

@@ -1,28 +1,28 @@
----
-id: next-heavy-ui-lazy-load-boundaries
-title: Next.js heavy UI lazy-load boundaries
-status: active
-candidateKinds: ["cwv_poor"]
-frameworks: ["next@*"]
-metrics: ["LCP", "INP"]
-priority: 82
-citations:
-  ["https://nextjs.org/docs/app/guides/lazy-loading", "https://web.dev/articles/optimize-inp"]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-Heavy above-the-fold or rarely used UI can hurt LCP and INP when it ships too much JavaScript on first load. Look for concrete route-local UI, not generic bundle advice.
-
-## Evidence To Check
-
-Inspect client components, menus, search overlays, personalization widgets, maps, editors, and large imported libraries. Check whether they can load on interaction, viewport, or route entry with `next/dynamic` or dynamic import.
-
-## Do Not Recommend When
-
-Do not lazy-load essential above-the-fold content needed for initial meaning or accessibility. Do not use `ssr: false` from a Server Component.
-
-## Verification
-
-Name the poor metric, heavy UI boundary, imported library or component, and exact line to split.
+---
+id: next-heavy-ui-lazy-load-boundaries
+title: Next.js heavy UI lazy-load boundaries
+status: active
+candidateKinds: ["cwv_poor"]
+frameworks: ["next@*"]
+metrics: ["LCP", "INP"]
+priority: 82
+citations:
+  ["https://nextjs.org/docs/app/guides/lazy-loading", "https://web.dev/articles/optimize-inp"]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+Heavy above-the-fold or rarely used UI can hurt LCP and INP when it ships too much JavaScript on first load. Look for concrete route-local UI, not generic bundle advice.
+
+## Evidence To Check
+
+Inspect client components, menus, search overlays, personalization widgets, maps, editors, and large imported libraries. Check whether they can load on interaction, viewport, or route entry with `next/dynamic` or dynamic import.
+
+## Do Not Recommend When
+
+Do not lazy-load essential above-the-fold content needed for initial meaning or accessibility. Do not use `ssr: false` from a Server Component.
+
+## Verification
+
+Name the poor metric, heavy UI boundary, imported library or component, and exact line to split.

package/skills/craft/vercel-optimize/references/support-topics/next-image-lcp-preload-sizes.md

@@ -1,31 +1,31 @@
----
-id: next-image-lcp-preload-sizes
-title: Next.js image LCP preload and sizes
-status: active
-candidateKinds: ["cwv_poor"]
-frameworks: ["next@*"]
-metrics: ["LCP"]
-priority: 86
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/components/image",
-    "https://web.dev/articles/optimize-lcp",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-For poor LCP, identify whether the LCP element is an image before touching unrelated JavaScript. Hero images need correct sizing, priority behavior, and source-cache hygiene.
-
-## Evidence To Check
-
-Inspect above-the-fold media for `next/image`, `fill` without `sizes`, deprecated `priority` on Next.js 16, missing `preload` or `fetchPriority`, oversized dimensions, and remote-image TTL/source behavior.
-
-## Do Not Recommend When
-
-Do not preload multiple possible LCP images or route tiny icons/SVG UI assets through image optimization. Do not change quality or TTL without checking source-update semantics.
-
-## Verification
-
-Name the LCP value, image element or component, current props/config, and the exact line to change.
+---
+id: next-image-lcp-preload-sizes
+title: Next.js image LCP preload and sizes
+status: active
+candidateKinds: ["cwv_poor"]
+frameworks: ["next@*"]
+metrics: ["LCP"]
+priority: 86
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/components/image",
+    "https://web.dev/articles/optimize-lcp",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+For poor LCP, identify whether the LCP element is an image before touching unrelated JavaScript. Hero images need correct sizing, priority behavior, and source-cache hygiene.
+
+## Evidence To Check
+
+Inspect above-the-fold media for `next/image`, `fill` without `sizes`, deprecated `priority` on Next.js 16, missing `preload` or `fetchPriority`, oversized dimensions, and remote-image TTL/source behavior.
+
+## Do Not Recommend When
+
+Do not preload multiple possible LCP images or route tiny icons/SVG UI assets through image optimization. Do not change quality or TTL without checking source-update semantics.
+
+## Verification
+
+Name the LCP value, image element or component, current props/config, and the exact line to change.

package/skills/craft/vercel-optimize/references/support-topics/next-route-handler-get-cache-defaults.md

@@ -1,30 +1,30 @@
----
-id: next-route-handler-get-cache-defaults
-title: Next.js Route Handler GET cache defaults
-status: active
-candidateKinds: ["uncached_route", "cache_header_gap"]
-frameworks: ["next@>=15.0.0"]
-priority: 91
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/file-conventions/route",
-    "https://vercel.com/docs/caching/cdn-cache",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-On Next.js 15+, GET Route Handlers are dynamic by default. For hot public GET handlers, verify whether uncached behavior is intentional before recommending cache headers or route config.
-
-## Evidence To Check
-
-Use method share, cache result, and source. Check `GET`, `revalidate`, `dynamic`, request headers, cookies, auth, query params, and response `Cache-Control`.
-
-## Do Not Recommend When
-
-Do not cache POST-style handlers, webhooks, per-user APIs, streaming responses, search requests with user-specific params, or handlers that read auth/cookies.
-
-## Verification
-
-Name the Next.js version, GET share, cache result mix, and the exact handler or header line that makes public caching safe.
+---
+id: next-route-handler-get-cache-defaults
+title: Next.js Route Handler GET cache defaults
+status: active
+candidateKinds: ["uncached_route", "cache_header_gap"]
+frameworks: ["next@>=15.0.0"]
+priority: 91
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/file-conventions/route",
+    "https://vercel.com/docs/caching/cdn-cache",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+On Next.js 15+, GET Route Handlers are dynamic by default. For hot public GET handlers, verify whether uncached behavior is intentional before recommending cache headers or route config.
+
+## Evidence To Check
+
+Use method share, cache result, and source. Check `GET`, `revalidate`, `dynamic`, request headers, cookies, auth, query params, and response `Cache-Control`.
+
+## Do Not Recommend When
+
+Do not cache POST-style handlers, webhooks, per-user APIs, streaming responses, search requests with user-specific params, or handlers that read auth/cookies.
+
+## Verification
+
+Name the Next.js version, GET share, cache result mix, and the exact handler or header line that makes public caching safe.

package/skills/craft/vercel-optimize/references/support-topics/next-script-third-party-strategy.md

@@ -1,31 +1,31 @@
----
-id: next-script-third-party-strategy
-title: Next.js third-party script strategy
-status: active
-candidateKinds: ["cwv_poor"]
-frameworks: ["next@*"]
-metrics: ["LCP", "INP"]
-priority: 85
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/components/script",
-    "https://web.dev/articles/optimize-inp",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-Third-party scripts are only actionable when they line up with the poor metric and route. For LCP or INP, prove a specific script blocks critical rendering, hydration, or interaction.
-
-## Evidence To Check
-
-Inspect `next/script`, raw `<script>`, tag managers, chat widgets, analytics, and consent code. Check `beforeInteractive`, `afterInteractive`, `lazyOnload`, and whether the script is route-local or global.
-
-## Do Not Recommend When
-
-Do not move required bot detection, consent, auth, or payment scripts later without product evidence. Do not recommend `worker` for App Router.
-
-## Verification
-
-Name the poor metric, script source, current strategy, and the exact route or layout line to change.
+---
+id: next-script-third-party-strategy
+title: Next.js third-party script strategy
+status: active
+candidateKinds: ["cwv_poor"]
+frameworks: ["next@*"]
+metrics: ["LCP", "INP"]
+priority: 85
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/components/script",
+    "https://web.dev/articles/optimize-inp",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+Third-party scripts are only actionable when they line up with the poor metric and route. For LCP or INP, prove a specific script blocks critical rendering, hydration, or interaction.
+
+## Evidence To Check
+
+Inspect `next/script`, raw `<script>`, tag managers, chat widgets, analytics, and consent code. Check `beforeInteractive`, `afterInteractive`, `lazyOnload`, and whether the script is route-local or global.
+
+## Do Not Recommend When
+
+Do not move required bot detection, consent, auth, or payment scripts later without product evidence. Do not recommend `worker` for App Router.
+
+## Verification
+
+Name the poor metric, script source, current strategy, and the exact route or layout line to change.

package/skills/craft/vercel-optimize/references/support-topics/nextjs-version-cache-semantics.md

@@ -1,31 +1,31 @@
----
-id: nextjs-version-cache-semantics
-title: Next.js cache semantics by version
-status: active
-candidateKinds: ["uncached_route"]
-frameworks: ["next@>=15.0.0"]
-priority: 85
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/directives/use-cache",
-    "https://nextjs.org/docs/app/api-reference/functions/cacheLife",
-    "https://nextjs.org/docs/app/building-your-application/caching",
-  ]
-maxBriefChars: 800
----
-
-## Investigation Brief
-
-On Next.js 15+, match the fix to the cache primitive already in use.
-
-## Evidence To Check
-
-Check `'use cache'`, `cacheLife`, `cacheTag`, `fetch` cache options, route handlers, and dynamic APIs.
-
-## Do Not Recommend When
-
-Do not suggest APIs outside the detected Next.js version. Do not claim `cacheLife()` emits CDN `Cache-Control` headers or that missing `cacheLife()` alone makes a `'use cache'` route run per request. Omitted `cacheLife()` calls use the default profile.
-
-## Verification
-
-Name the detected Next.js version and exact cache primitive or route header.
+---
+id: nextjs-version-cache-semantics
+title: Next.js cache semantics by version
+status: active
+candidateKinds: ["uncached_route"]
+frameworks: ["next@>=15.0.0"]
+priority: 85
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/directives/use-cache",
+    "https://nextjs.org/docs/app/api-reference/functions/cacheLife",
+    "https://nextjs.org/docs/app/building-your-application/caching",
+  ]
+maxBriefChars: 800
+---
+
+## Investigation Brief
+
+On Next.js 15+, match the fix to the cache primitive already in use.
+
+## Evidence To Check
+
+Check `'use cache'`, `cacheLife`, `cacheTag`, `fetch` cache options, route handlers, and dynamic APIs.
+
+## Do Not Recommend When
+
+Do not suggest APIs outside the detected Next.js version. Do not claim `cacheLife()` emits CDN `Cache-Control` headers or that missing `cacheLife()` alone makes a `'use cache'` route run per request. Omitted `cacheLife()` calls use the default profile.
+
+## Verification
+
+Name the detected Next.js version and exact cache primitive or route header.

package/skills/craft/vercel-optimize/references/support-topics/not-found-catchall-request-waste.md

@@ -1,33 +1,33 @@
----
-id: not-found-catchall-request-waste
-title: Not-found and catch-all request waste
-status: active
-candidateKinds: ["uncached_route"]
-frameworks: ["*"]
-routePatterns: ["(^|/)404$", "not-found", "\\[\\.\\.\\."]
-priority: 92
-citations:
-  [
-    "https://vercel.com/docs/routing/",
-    "https://vercel.com/docs/redirects/bulk-redirects/",
-    "https://vercel.com/docs/vercel-firewall/vercel-waf/custom-rules",
-    "https://vercel.com/docs/vercel-firewall/vercel-waf/managed-rulesets",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-High-volume 404 or catch-all traffic is often request waste. First determine whether the traffic is legacy URLs, bots, broken links, or a real product route.
-
-## Evidence To Check
-
-Use route volume, method share, cache result, bot share, and top request paths. Inspect redirects, rewrites, catch-all routes, sitemap/robots output, and any WAF rules already logging or blocking the pattern.
-
-## Do Not Recommend When
-
-Do not block or redirect legitimate product routes, search crawlers, or unknown traffic without a log-mode validation path. Do not replace a useful 404 page with a blanket rewrite.
-
-## Verification
-
-Name the dominant bad path pattern, observed request or bot volume, and the redirect, routing, or WAF rule that would stop the wasted function path.
+---
+id: not-found-catchall-request-waste
+title: Not-found and catch-all request waste
+status: active
+candidateKinds: ["uncached_route"]
+frameworks: ["*"]
+routePatterns: ["(^|/)404$", "not-found", "\\[\\.\\.\\."]
+priority: 92
+citations:
+  [
+    "https://vercel.com/docs/routing/",
+    "https://vercel.com/docs/redirects/bulk-redirects/",
+    "https://vercel.com/docs/vercel-firewall/vercel-waf/custom-rules",
+    "https://vercel.com/docs/vercel-firewall/vercel-waf/managed-rulesets",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+High-volume 404 or catch-all traffic is often request waste. First determine whether the traffic is legacy URLs, bots, broken links, or a real product route.
+
+## Evidence To Check
+
+Use route volume, method share, cache result, bot share, and top request paths. Inspect redirects, rewrites, catch-all routes, sitemap/robots output, and any WAF rules already logging or blocking the pattern.
+
+## Do Not Recommend When
+
+Do not block or redirect legitimate product routes, search crawlers, or unknown traffic without a log-mode validation path. Do not replace a useful 404 page with a blanket rewrite.
+
+## Verification
+
+Name the dominant bad path pattern, observed request or bot volume, and the redirect, routing, or WAF rule that would stop the wasted function path.

package/skills/craft/vercel-optimize/references/support-topics/nuxt-route-rules-cache-isr.md

@@ -1,31 +1,31 @@
----
-id: nuxt-route-rules-cache-isr
-title: Nuxt routeRules cache and ISR
-status: active
-candidateKinds: ["uncached_route", "isr_overrevalidation", "rendering_candidate"]
-frameworks: ["nuxt@>=3.0.0"]
-priority: 90
-citations:
-  [
-    "https://vercel.com/docs/frameworks/full-stack/nuxt",
-    "https://nuxt.com/docs/4.x/api/utils/define-route-rules",
-    "https://nuxt.com/docs/4.x/guide/concepts/rendering",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-For Nuxt on Vercel, route-level caching usually belongs in `routeRules`. Match the lever to the route: prerender for static pages, ISR for shared content, and SSR for request-specific views.
-
-## Evidence To Check
-
-Inspect `nuxt.config`, inline route rules, server routes, pages, auth/session reads, and observed cache or ISR read/write patterns. Verify whether the route should be Vercel cache-backed ISR rather than generic SWR.
-
-## Do Not Recommend When
-
-Do not cache authenticated, cart, checkout, preview, or per-user routes. Do not add routeRules without proving the route is public and the freshness window is acceptable.
-
-## Verification
-
-Name the observed route signal, current routeRule or missing rule, chosen cache mode, and exact config line.
+---
+id: nuxt-route-rules-cache-isr
+title: Nuxt routeRules cache and ISR
+status: active
+candidateKinds: ["uncached_route", "isr_overrevalidation", "rendering_candidate"]
+frameworks: ["nuxt@>=3.0.0"]
+priority: 90
+citations:
+  [
+    "https://vercel.com/docs/frameworks/full-stack/nuxt",
+    "https://nuxt.com/docs/4.x/api/utils/define-route-rules",
+    "https://nuxt.com/docs/4.x/guide/concepts/rendering",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+For Nuxt on Vercel, route-level caching usually belongs in `routeRules`. Match the lever to the route: prerender for static pages, ISR for shared content, and SSR for request-specific views.
+
+## Evidence To Check
+
+Inspect `nuxt.config`, inline route rules, server routes, pages, auth/session reads, and observed cache or ISR read/write patterns. Verify whether the route should be Vercel cache-backed ISR rather than generic SWR.
+
+## Do Not Recommend When
+
+Do not cache authenticated, cart, checkout, preview, or per-user routes. Do not add routeRules without proving the route is public and the freshness window is acceptable.
+
+## Verification
+
+Name the observed route signal, current routeRule or missing rule, chosen cache mode, and exact config line.