skills/add-custom-domain/SKILL.md
Configure custom domains for Temps deployments with automatic SSL/TLS certificates via Let's Encrypt. Supports HTTP-01 and DNS-01 challenges, wildcard domains, and Cloudflare DNS integration. Use when the user wants to: (1) Add a custom domain to their Temps app, (2) Set up SSL certificates, (3) Configure DNS for Temps, (4) Add a wildcard domain, (5) Set up HTTPS for their deployment, (6) Configure Cloudflare with Temps. Triggers: "custom domain", "add domain", "ssl certificate", "https setup", "wildcard domain", "dns configuration", "cloudflare temps".
npx skillsauth add gotempsh/temps add-custom-domainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Configure custom domains with automatic SSL/TLS certificates.
app.example.com)Add a CNAME record pointing to your Temps deployment:
| Type | Name | Value | |------|------|-------| | CNAME | app | your-project.temps.io |
For apex domains (example.com without subdomain), use an A record:
| Type | Name | Value | |------|------|-------| | A | @ | [Temps IP address] |
Temps automatically:
Used for standard domains. Temps handles automatically.
Requirements:
Required for wildcard domains (*.example.com).
Setup with Cloudflare:
Add Cloudflare API token in Temps:
Add wildcard domain:
*.example.com
Temps creates DNS TXT record automatically
For *.example.com to match app.example.com, api.example.com, etc:
Create API Token:
Add to Temps:
Settings > DNS Providers > Add Cloudflare
- API Token: [your-token]
- Zone ID: [from Cloudflare domain overview]
Add Wildcard Domain:
*.example.com
app.example.com -> CNAME -> your-project.temps.io
example.com -> A -> [Temps IP]
Or with Cloudflare (CNAME flattening):
example.com -> CNAME -> your-project.temps.io (proxied)
*.example.com -> CNAME -> your-project.temps.io
Temps automatically renews certificates 30 days before expiration.
Check certificate status in Dashboard > Domains:
If needed, manually trigger renewal:
Add multiple domains to the same project:
app.example.com -> Production
staging.example.com -> Staging
api.example.com -> API routes
Each domain gets its own certificate.
Add both domains and configure redirect:
example.com (primary)www.example.com (redirect)www.example.com to redirect to example.comAutomatic - all HTTP requests redirect to HTTPS.
DNS not propagating?
dig app.example.comCertificate stuck pending?
Wildcard not working?
SSL certificate errors?
https://app.example.comcurl -X POST https://your-temps.com/api/projects/123/domains \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"domain": "app.example.com"}'
curl https://your-temps.com/api/projects/123/domains \
-H "Authorization: Bearer $TOKEN"
curl -X DELETE https://your-temps.com/api/projects/123/domains/456 \
-H "Authorization: Bearer $TOKEN"
tools
Build external plugins for the Temps deployment platform. Use when the user wants to create, modify, or debug a Temps plugin binary — a standalone Rust process that communicates with Temps over a Unix domain socket. Also use when the user mentions "temps plugin", "external plugin", "plugin binary", "plugin for temps", "plugin UI", or asks about plugin architecture, plugin events, plugin manifest, or plugin SDK. Covers the full lifecycle: project scaffolding, manifest, router, events, SQLite persistence, embedded React UI, build.rs, testing, and deployment into the plugins directory.
tools
Install, configure, and manage the Temps deployment platform and CLI. Covers self-hosted Temps installation, CLI setup (bunx @temps-sdk/cli), initial configuration, user management, and platform administration. Use when the user wants to: (1) Install Temps on their server, (2) Set up the Temps CLI, (3) Configure Temps for the first time, (4) Manage Temps platform settings, (5) Create admin users, (6) Configure DNS providers, (7) Set up TLS certificates. Triggers: "install temps", "setup temps", "temps cli", "configure temps", "temps platform", "self-hosted deployment platform".
tools
Configure the Temps MCP server to enable AI assistants to interact with the Temps platform. Provides tools for listing projects, viewing project details, and managing deployments directly from Claude or other MCP-compatible clients. Use when the user wants to: (1) Set up Temps MCP server, (2) Configure Claude to manage Temps projects, (3) Add Temps tools to their AI assistant, (4) Enable AI-powered deployment management, (5) Connect Claude Desktop to Temps, (6) Use MCP to interact with Temps API. Triggers: "temps mcp", "configure temps tools", "add temps to claude", "temps ai assistant", "mcp server setup".
tools
Complete command-line reference for managing the Temps deployment platform. Covers all 54+ CLI commands including projects, deployments, environments, services, domains, monitoring, backups, security scanning, error tracking, and platform administration. Use when the user wants to: (1) Find CLI command syntax, (2) Manage projects and deployments via CLI, (3) Configure services and infrastructure, (4) Set up monitoring and logging, (5) Automate deployments with CI/CD, (6) Manage domains and DNS, (7) Configure notifications and webhooks. Triggers: "temps cli", "temps command", "how to use temps", "@temps-sdk/cli", "bunx temps", "npx temps", "temps deploy", "temps projects", "temps services".