TypeScript Engineering
Native TypeScript 7 qualification, domain types, ESM packages, and a correctly separated quality pipeline.
COMPOSE, DON'T COPY
18 starting points for real engineering work. Each bundle selects canonical skills; it does not load every instruction, run tools, or grant permissions.
Native TypeScript 7 qualification, domain types, ESM packages, and a correctly separated quality pipeline.
Cohesive services, bounded concurrency, deterministic tests, measured performance, and transaction ownership.
Accepted API baselines, reproducible generated consumers, safe schema changes, and authoritative data invariants.
Deterministic orchestration, retry-safe effects, version-aware worker rollouts, and job reconciliation.
Bounded tasks, current context, graph-aware work, precise cache reuse, isolated resources, and verified handoffs.
Reproducible tools, safe container iteration, trusted build caches, schema transitions, and artifact promotion.
Ground reference footage, assemble approved assets, review continuity and verify delivery with capability-aware provider and identity boundaries.
Canonical public skills plus private context bindings, thin authenticated adapters, and bounded execution contracts.
Bounded goals, capability-aware routing, coordinated dispatch, recoverable attempts, and reviewed integration.
Least-privilege delegation, exact approvals, budgets, context recovery, loop detection, and independent evaluation.
Route sources, qualify connector access, read bounded public content, compare feeds, and produce timestamped research evidence.
Audit execution, revalidate context, reconcile readiness and usage, qualify controller failures, and review bounded canaries without another scheduler.
Investigate a change, prioritize the work, explain it clearly, plan a product story and verify the publication.
React and Next.js boundaries, TanStack Query, forms, Tailwind, design-system composition, accessible icons and complete frontend states.
Profile real interactions, control browser concurrency and storage, preserve failure evidence and verify behavior before claiming an improvement.
A coherent design brief, semantic tokens, Tailwind variants, accessible primitives, consistent icons, responsive composition and purposeful motion.
Build source-backed maps and qualify derived indexes against current worktrees, coverage and known answers.
Inspect evaluation datasets and analyze complete paired workloads without hiding failures, unknown usage or sampling limits.
Keep the skills reusable. A project adapter can bind its own repository paths, accepted contracts, approved checks, and permission policy without forking the public instructions.