suaveplan/packages/devtools/tooling/install-agent-skills/assets/skills/timing/SKILL.md

name: timing description: Use when implementing or debugging code that uses @suaveplan/timing: Timing and scheduling utilities — stopwatch, throttle, debounce, scheduler, decay, timer, countdown, vector clock.

@suaveplan/timing

Timing and scheduling utilities for application-layer time management. The package covers measurement (stopwatch with lap recording), rate control (throttle and debounce with leading/trailing edge and maxWait), value decay (exponential and linear curves), delayed-task scheduling with drain/dispose lifecycle, repeating interval timers, countdowns with pause/resume, and vector clocks for distributed happens-before ordering. All stateful primitives accept an injectable Clock so they can be driven deterministically in tests using FakeClock from @suaveplan/testing.

When to use this skill

• Implementing or debugging code that imports @suaveplan/timing.
• The task touches: see package README.
• You need API guidance for this package's exports.

Quick reference

import { /* see API Reference below */ } from "@suaveplan/timing";

Dependencies

Workspace dependencies: @suaveplan/error, @suaveplan/events, @suaveplan/types

Where to read more

This skill is intentionally short. The package's own documentation is the authoritative source — read these in order:

1. packages/foundation/timing/README.md — overview, install, quick-start, module index
2. packages/foundation/timing/src/**/*.md — co-located docs per implementation file (Purpose, Features, Basic + Advanced examples, full API reference, Implementation notes — all packages ship ≥200 words per module)
3. packages/foundation/timing/package.json exports map — every subpath you can import from

When the user asks an API question, read the relevant co-located .md first; do not answer from training-data memory.

See also

• @suaveplan/error
• @suaveplan/events
• @suaveplan/types

---

This SKILL.md is auto-generated by suaveplan-skills/scripts/generate-skills.ts from the package's README. Do not edit by hand — re-run the generator after the README changes.