Menú
AI Agent guide on using Netlify Edge Functions, Blobs, and AI Gateway functions in the Shamrock ecosystem.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | Netlify Best Practices |
| description | AI Agent guide on using Netlify Edge Functions, Blobs, and AI Gateway functions in the Shamrock ecosystem. |
This document defines the rules, best practices, and integration patterns for building on Netlify within the Shamrock Bail Bonds ecosystem.
@netlify/edge-functions)When to use: Use Edge Functions when you need immediate execution before a page loads or when routing traffic based on Geo-IP.
Agent Rule: Do not use Edge Functions for heavy PDF parsing or integrations that take > 10 seconds. Use GAS for that.
@netlify/blobs)When to use: Use Blobs for unstructured, temporary data caching.
chat_id.Agent Rule: Treat Blobs as ephemeral storage. Permanent records (like signed PDFs or finalized bonds) belong in Google Drive/Sheets.
When to use: Use Netlify Serverless Functions to proxy API calls to OpenAI, Grok, or ElevenLabs.
/netlify/functions/chat.js that receives the prompt from the frontend, injects the server-side API key (from Netlify Environment Variables), queries the LLM, and returns the response.Agent Rule: When adding a new AI integration (e.g., translation, summary), build the proxy as a Netlify Serverless Function first, then let Wix/Telegram call that function.
When working locally with Netlify in this ecosystem:
netlify-cli is installed.netlify dev to test Edge Functions and Serverless Functions locally.netlify.toml file to manage redirects, headers, and function locations. Do NOT hardcode these configurations in JS files.Dynamically manage MCP server limits by toggling disabled states in mcp_config.json. Use when hitting the 100-tool limit, or when needing a specific MCP server that is currently disabled.
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.
Wix Design System component reference. Use when building UI with @wix/design-system, choosing components, or checking props and examples. Triggers on "what component", "how do I make", "WDS", "show me props", or component names like Button, Card, Modal, Box, Text.
Creates HTTP endpoints for Wix CLI apps. Use only when the user specifically asks for a backend endpoint. Use when building REST API endpoints, backend HTTP handlers, or server-side logic. Triggers include backend API, HTTP endpoint, HTTP methods, form handling, file uploads.