Temps Best Practices
Best-practices reference for preparing and instrumenting applications on Temps.
Install
npx skills add gotempsh/temps --skill temps-best-practices -g -a claude-code -y- Repository
- gotempsh/temps887
- Category
- DevOps
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,858 tokens
- Runs scripts
- No, instructions only
What it does
Best-practices reference for preparing and instrumenting applications on Temps. Covers the app runtime contract (`.temps.yaml` health, HOST/PORT, readiness, SIGTERM, replicas, migrations) and production observability (errors, traces, metrics, logs, analytics, privacy, sampling, cardinality, credential boundaries). Use whenever building or reviewing an app for Temps, configuring health checks, adding telemetry, diagnosing missing/noisy signals, or checking OTLP/Sentry/analytics ingestion. Triggers include "temps best practices", "prepare this app for Temps", ".temps.yaml health", "temps health check", "ignore health checks in otel", "temps observability", "wire up telemetry", and "instrument this app for temps". Prefer focused setup skills for a single SDK. Use temps-cli for executing deploy and resource-management commands.
Temps Best Practices
Best practices for application code that runs on Temps. This skill owns the runtime contract and production observability; use temps-cli for platform operations.
Required workflow
- For any deployable application, read references/runtime-contract.md.
- When any telemetry or replay is enabled, read references/telemetry-hygiene.md.
- Read only the reference for each observability pillar in scope.
- Determine the deployment source. For repository builds, inspect and merge
.temps.yaml; for image/static deployments, inspect the deployment health-path override because no repository config is available. - Run the runtime and telemetry verification checklists before considering the work complete.
Runtime contract summary
Every web application should expose a dedicated health endpoint. Repository builds configure it in .temps.yaml under the project's effective Temps Root Directory / Docker build context:
health:
path: /healthz
Use health.path; do not rely on the currently parsed-but-unapplied status, interval, timeout, or retries fields. If OpenTelemetry server tracing is enabled, exclude the exact health path from incoming spans and routine access-log/request-metric noise. Keep the route, .temps.yaml, and filters synchronized.
Image and static deployments cannot read .temps.yaml; set the same route through their deployment health_check_path / CLI --health-check-path override instead.
Also require the app to read PORT, bind to HOST/0.0.0.0, align a custom image's EXPOSE, handle SIGTERM, flush telemetry, and exit inside Temps' 10-second shutdown window. See the runtime reference for readiness semantics, scale-to-zero caveats, replicas, migrations, stdout/stderr, and cron authentication.
