Temps skills

---
name: temps
description: Manage, deploy, operate, and instrument applications with Temps. Use this skill whenever the user mentions Temps, `@temps-sdk/cli@0.1.38`, deploying or migrating an app to Temps, projects, environments, services, domains, backups, edge rules (request blocking, redirects, bot challenges), logs, monitoring, analytics, browser Performance Insights/Core Web Vitals, observability, error tracking, OpenTelemetry, tracing, session replay, or Temps Cloud. Also use it when preparing an application for production on Temps even if the user does not explicitly ask for the CLI. Route to focused references, proactively detect missing observability during create/link/deploy journeys, and use pinned `bunx` or `npx` CLI invocations with explicit target contexts.
---

# Temps

Treat Temps as a product workflow, not a command catalog. Understand the
user's desired outcome, inspect the application or platform read-only, load
only the relevant reference, make the smallest authorized change, and prove
the result.

Runtime requirements: a shell and either `bunx` or `npx` for CLI operations;
Python 3.9+ for the bundled read-only capability detector.

## Required workflow

1. Classify the task: application preparation, deployment, platform operation,
   observability, recovery, or diagnosis.
2. Inspect before changing anything. Identify the current Temps context,
   target project/environment, and existing setup. For a named application,
   check the instance's curated app catalog before creating a repository,
   Dockerfile, or custom project. Prefer a matching curated service when it
   meets the request; inspect a repository framework only for source deployment.
3. Read only the references named in the routing table below. Do not load the
   complete command index or unrelated observability pillars.
4. For CLI work, use the pinned zero-install invocation and the safety contract
   in [references/cli-runtime.md](references/cli-runtime.md).
5. Before a state change, explain its target and effect. Ask for confirmation
   when the change is destructive, secret-bearing, or otherwise requires new
   authority.
6. Verify the outcome using a read-only CLI command, application test, and—when
   telemetry is involved—a real synthetic signal.

## Application capability checkpoint

When creating, linking, migrating, reviewing, or deploying a source-backed application,
inspect its observability setup before the final deployment step:

```bash
python3 skills/temps/scripts/detect_project_capabilities.py --root .
```

Curated template provisioning is exempt from this checkpoint. Follow the
[curated-services verification steps](howtos/curated-services.md#verify-creation-and-deployment-separately)