Sammlung typescript

TypeScript KI-Tools für Entwickler-Workflows | AI Agent Skills

Installierbare AI Agent Skills für typescript Developer Workflows in Claude Code, Cursor und Windsurf.

Diese TypeScript-Sammlung ist auf Ergebnisse im Entwickler-Workflow ausgerichtet, nicht auf Infrastruktur-Labels. Sie fokussiert Tools für SDK-Implementierung, typisierte API-Integrationen, Testautomatisierung, Release-Checks und Dokumentationspipelines für echte Produktteams. MCP-kompatible Funktionen können ergänzend genutzt werden, doch der Kern ist skills-first Engineering: sicherer ausliefern, Integrationsaufwand reduzieren und die Zusammenarbeit zwischen Frontend und Backend in Produktion verbessern.

Page-Level Review Standard

This Page Is a Curated Decision Surface, Not Just a Themed List

A collection page should not just add more cards to the screen. It should explain why these skills belong together, how the next step moves into installation and validation, and which path should continue the decision afterwards.

Reviewed On

2026-04-17

Maintained By

Maintained through Killer-Skills editorial review with install, documentation, and TypeScript workflow checks.

Verification

Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Primary Audience

High-intent users who roughly know the direction and need a faster path to an installable shortlist.

Three Minimum Standards For This Collection

- A collection page must narrow users into a better shortlist instead of flattening more repositories onto the screen.
- The next click should continue into installation docs, CLI validation, or a better-fit solution page instead of resetting back to a broad directory.
- This collection page works best when its selection logic, maintenance notes, and next steps are all clear.

Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from TypeScript workflow discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path

Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution page, CLI docs, or the next collection that best matches this theme. That keeps platform, framework, and operations needs easier to compare and verify.

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Process Automation Solution

A solution page for teams turning SOPs, handoffs, and operations into repeatable AI-assisted execution paths.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against TypeScript workflow fit, installation clarity, operator handoff, and day-to-day product engineering usefulness. This page is now positioned as an install-first TypeScript entry point instead of a broad language roundup.

We prioritize this page because TypeScript-intent users usually need a shortlist they can install, validate, and carry into real typed delivery loops quickly.

Trust Signals

- Entries are chosen for practical TypeScript workflow value such as typed APIs, SDK work, release checks, review loops, and safe refactors.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable product engineering, not for vague language keyword coverage or generic repository popularity.

Grouping Logic

- Lead with tools that can enter a TypeScript-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering typed APIs, release checks, review, and refactor support.
- Use installation as the bridge from TypeScript discovery into validated daily execution.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or TypeScript workflow relevance changes upstream; otherwise review monthly.
Maintained By: Maintained through Killer-Skills editorial review with install, documentation, and TypeScript workflow checks.
Verification: Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Execution Examples

How These Skills Work Together In Practice

Install one TypeScript workflow helper first

Use this page when you want one TypeScript companion that can enter real product work without turning evaluation into another endless typed-tool comparison.

1. Open the installation docs before opening more TypeScript-related repositories.
2. Choose one tool that best supports typed APIs, SDK work, release checks, or review flow.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider TypeScript workflow.

Harden a TypeScript release loop

Treat the collection as an editorial filter when you need TypeScript-adjacent tools that improve delivery safety without overcomplicating the stack.

1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more services, packages, or teammates.
4. Document the chosen TypeScript workflow baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check workflow choices before you standardize a team stack.

spec-driven-development

n8n-io

Die spezifikationsgetriebene Entwicklung ermöglicht eine effizientere Integration von APIs und Datenflüssen

★ 181.1k

⑂ 0

Künstliche Intelligenz

upgrade-stripe

[ Offiziell ]

stripe

Guide for upgrading Stripe API versions and SDKs

★ 1.4k

⑂ 0

Finanzen

write-docs

inkeep

Write or update documentation for the Inkeep docs site (agents-docs package). Use when: creating new docs, modifying existing docs, introducing features that need documentation, touching MDX files in agents-docs/content/. Triggers on: docs, documentation, MDX, agents-docs, write docs, update docs, add page, new tutorial, API reference, integration guide.

★ 968

⑂ 0

Künstliche Intelligenz

testing-with-api-mocks

stacklok

Start here for all API mocking in tests. Covers auto-generation, fixtures, and when to use other skills. Required reading before creating, refactoring, or modifying any test involving API calls.

★ 116

⑂ 0

Künstliche Intelligenz

omni-executor

automagik-dev

Omni v2 message execution specialist — use for sending messages (text, TTS, media, reactions, stickers, polls), searching messages, batch operations, and testing automations via the omni CLI.

★ 6

⑂ 0

Communication

widget-generator

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k

⑂ 0

Künstliche Intelligenz

Related Collections

If This Page Is Close, Keep Narrowing With Related Collections

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

Next.js Workflow Tools to Install First

A full-stack workflow collection for Next.js teams that need a faster path from evaluation into install and rollout.

React Workflow Tools to Install First

A UI-focused React collection for teams comparing component, review, and interface workflow tools.

Agent Framework Tools to Install First

A framework and SDK collection for teams building agent foundations, not just browsing vendor names.

DevOps Workflow Tools to Install First

An operations-first collection for platform teams choosing release, incident, and automation helpers.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

Für welche Workflows sind diese Sammlungen gedacht?

Diese Sammlungen sind rund um Workflow-Automatisierung, Prozessautomatisierung, Dokumentenoperationen, Datenworkflows und wiederverwendbare Skill-Stacks aufgebaut.

Was unterscheidet eine Sammlung vom Hauptverzeichnis?

Das Verzeichnis eignet sich besser für direkte Suche, während Sammlungen komplementäre Skills um einen vollständigen Workflow bündeln.

Kann ich diese Sammlungen für Claude Code oder Cursor installieren?

Ja. Die Skills in diesen Sammlungen funktionieren in der Regel in Claude Code, Cursor, Windsurf und anderen unterstützten Umgebungen über einen einheitlichen Installationsablauf.

Additional Next Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.

Agent Workflow Building Tools

A curated collection for building multi-step agent workflows with clearer tool selection and execution paths.

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.