vercel-dns

The vercel-dns skill is a specialized automation tool designed for managing Domain Name System (DNS) records on the Vercel platform, with specific optimizations for the 0 Finance project infrastructure. It streamlines the lifecycle of DNS configuration, enabling developers and AI agents to programmatically list, add, and remove records for domains hosted on Vercel nameservers. By utilizing the Vercel CLI, this skill provides a reliable interface for configuring complex record types such as A, AAAA, CNAME, TXT, MX, and SRV, while ensuring consistent scoping for multi-team or multi-tenant environments.

• Perform granular DNS management operations including adding, listing, and deleting A, CNAME, TXT, and MX records.

• Support for apex domain configuration using empty strings or @ indicators for root-level management.

• Context-aware scoping for 0 Finance project deployments, ensuring changes are correctly applied to the 'prologe' scope.

• Integration with Vercel team management workflows, allowing users to verify identities via 'whoami' and switch between team slugs securely.

• Ability to verify propagation status and troubleshoot DNS issues using standard diagnostic protocols like 'dig'.

• The skill requires a pre-configured Vercel CLI environment with valid authentication tokens obtained through the 'vercel login' command.

• Users must ensure the target domain uses Vercel as its primary nameserver or DNS provider before attempting modifications.

• All operations requiring domain removal or modification should be preceded by a list operation to ensure correct mapping of record IDs.

• For TXT records containing special characters, always wrap values in single quotes to prevent shell interpretation errors.

• The tool is particularly useful for setting up SPF and DKIM records for email authentication, as well as domain verification for third-party services like AWS or Google Workspace.

• When adding MX records, note that priority is a required argument and must be handled as a separate parameter in the command syntax.

• Always verify current team and scope settings before execution to avoid accidental modifications to incorrect production or staging environments.