fix(skills): correct factual errors in caching, ai-gateway, deploy, forms, cli, functions, and frameworks skills

axis-scenarios/ai-gateway/image-generation.ts

@@ -8,7 +8,7 @@ export default {
   judge: [
     { check: "Uses the `@google/genai` package — image generation on the gateway is Gemini-only" },
     { check: "Does NOT use `@google/generative-ai` (older deprecated package) and does NOT attempt OpenAI image models like dall-e or gpt-image" },
-    { check: "Uses a Gemini image model (e.g. 'gemini-2.5-flash-image' or 'gemini-3-pro-image-preview')" },
+    { check: "Uses a Gemini image model (e.g. 'gemini-2.5-flash-image' or 'gemini-3-pro-image')" },
     { check: "Does NOT pass a custom apiKey or baseURL to the GoogleGenAI client — the gateway auto-configures it" },
     { check: "Does NOT read or set `GEMINI_API_KEY` / `GOOGLE_API_KEY` — those disable the gateway" },
     { check: "Extracts the image bytes from `response.candidates[0].content.parts[*].inlineData` (base64 string) rather than expecting a URL" },

axis-scenarios/ai-gateway/image-to-image.ts

@@ -16,7 +16,7 @@ export default {
     },
     {
       check:
-        "Pins a Gemini IMAGE model (e.g. `gemini-2.5-flash-image`, `gemini-3.1-flash-image-preview`, or `gemini-3-pro-image-preview`).",
+        "Pins a Gemini IMAGE model (e.g. `gemini-2.5-flash-image`, `gemini-3.1-flash-image`, or `gemini-3-pro-image`).",
     },
     {
       check:

axis-scenarios/caching/tags-deploy-invalidation.ts

@@ -6,11 +6,12 @@ export default {
   prompt:
     "Create a Netlify function at /api/catalog whose JSON response is cached on Netlify's CDN and tagged so we can purge it on demand. Key requirement: a normal site deploy must NOT automatically wipe these cached responses — they should persist across deploys and only clear when we explicitly purge by tag. Also give me a separate /api/catalog/purge endpoint that does that explicit purge.",
   judge: [
-    { check: "Tags the cached response using the `Netlify-Cache-Tag` header (or `Cache-Tag`) with at least one tag like 'catalog' — does NOT use `Netlify-Cache-ID`" },
-    { check: "Relies on / explains the behavior that responses carrying a cache tag are excluded from automatic deploy-based invalidation — they persist across deploys and clear only on explicit purge" },
+    { check: "Sets a `Netlify-Cache-ID` header on the cached response with a stable id like 'catalog' — this both opts the response out of automatic deploy-based invalidation AND registers the id as a purge tag" },
+    { check: "Does NOT rely on `Netlify-Cache-Tag` to survive deploys — that header is purge-only and its responses are still wiped by automatic deploy-based invalidation" },
+    { check: "Relies on / explains the behavior that a response carrying `Netlify-Cache-ID` is excluded from automatic deploy-based invalidation — it persists across deploys and clears only on explicit purge" },
     { check: "Sets Netlify-CDN-Cache-Control with a meaningful s-maxage so the response is durably cached at the edge (not a near-zero TTL)" },
-    { check: "The /api/catalog/purge endpoint calls purgeCache({ tags: ['catalog'] }) imported from '@netlify/functions', using the SAME tag string set on the response" },
-    { check: "Does NOT propose triggering a new deploy or lowering the TTL as the invalidation mechanism — the requirement is explicit, targeted, deploy-surviving cache tags" },
+    { check: "The /api/catalog/purge endpoint calls purgeCache({ tags: ['catalog'] }) imported from '@netlify/functions', using the SAME id string set as the response's `Netlify-Cache-ID` (the id doubles as a purge tag)" },
+    { check: "Does NOT propose triggering a new deploy or lowering the TTL as the invalidation mechanism — the requirement is explicit, targeted, deploy-surviving caching" },
     { check: "Both endpoints use the modern Netlify function signature with config.path set" },
   ],
   variants: withSkillVariants(),

axis-scenarios/config/functions-directory.ts

@@ -9,7 +9,7 @@ export default {
     { check: "Adds a `[functions]` block with `directory = 'src/server/functions'`" },
     { check: "Sets `node_bundler = 'esbuild'` inside the `[functions]` block" },
     { check: "Does NOT leave the directory at the default `netlify/functions` — the user explicitly wants a custom path" },
-    { check: "Uses the single-table `[functions]` form for these global settings (not a `[[functions]]` array-of-tables entry, which is for per-path routing)" },
+    { check: "Uses the single-table `[functions]` form for these global settings — not a `[[functions]]` array-of-tables entry (no such construct exists in netlify.toml; per-function overrides use a `[functions.\"name-or-glob\"]` table)" },
     { check: "Does NOT invent unrelated keys (e.g. a made-up `bundler`/`runtime` field) — only `directory` and `node_bundler` are needed" },
   ],
   variants: withSkillVariants(),