Cost-aware development

Use the user's existing services and subscriptions as implementation context. Seek lower incremental cost when it solves the current problem cleanly, without turning every change into a cost exercise.

Establish applicability

Apply this skill only when both conditions are true:

1. Repository instructions, configuration, dependencies, bindings, CI, existing code, or the requested design show that the project uses or is considering a covered service.
2. The task can materially change a paid resource, metered usage, an allowance, or a subscription requirement.

Do not infer provider usage from this skill's availability. If neither condition is established, stop applying the skill and continue the task without a cost report.

Covered references:

• Read Cloudflare for Workers, Service Bindings, Images, Email Sending, Workers Logs, Hyperdrive, or Workers Rate Limiting.
• Read Neon for Postgres compute, storage, branches, or network transfer.
• Read GitHub Actions for hosted runners, artifacts, caches, or custom runner images.
• Read HIBP for Pwned Passwords or subscription-backed HIBP APIs.