개발 워크플로우를 위한 TypeScript AI 도구 모음 | AI Agent Skills
Claude Code, Cursor, Windsurf용 typescript AI Agent Skills 모음입니다. 개발자 워크플로 자동화에 초점을 둡니다.
이 TypeScript 컬렉션은 인프라 명칭보다 개발 워크플로우의 실제 성과에 초점을 둡니다. SDK 구현, 타입 안전 API 통합, 테스트 자동화, 릴리스 전 검증, 문서 파이프라인 등 제품 팀의 실전 업무에 맞는 도구를 다룹니다. 필요 시 MCP 호환 기능을 사용할 수 있지만 핵심 가치는 스킬 중심 엔지니어링에 있으며, 더 안전한 배포와 통합 비용 절감, 프런트엔드·백엔드 협업 효율 향상에 있습니다.
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.
The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory
Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.
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
Killer-Skills editorial review within the recovery-focused authority queue.
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.
The create-skill AI agent skill automates workflows and integrates APIs for Claude Code, enhancing developer productivity. It teaches the agent focused workflows, leveraging markdown and optional scripts.
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
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.
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.
Test that components send correct query parameters or request arguments. Use when testing filtering, sorting, pagination, or any read operation where request parameters matter. Use for test-scoped mock customization.
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.
If This Page Is Close, Keep Narrowing With Adjacent Authority Pages
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.
This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.
이 컬렉션들은 어떤 워크플로를 위해 만들어졌나요?
워크플로 자동화, 프로세스 자동화, 문서 작업, 데이터 워크플로 및 재사용 가능한 스킬 스택을 중심으로 구성되어 있습니다.
컬렉션과 메인 스킬 디렉터리의 차이점은?
스킬 디렉터리는 직접 검색과 필터링에 적합하고, 컬렉션은 완전한 워크플로를 위한 보완적 스킬 묶음을 찾는 데 적합합니다.
이 컬렉션들을 Claude Code나 Cursor에 설치할 수 있나요?
네. 이 컬렉션의 스킬들은 일반적으로 Claude Code, Cursor, Windsurf 및 기타 지원 환경에서 통합 설치 흐름으로 작동합니다.
Additional Recovery 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.
