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.
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.
