frontend-design
[ Offiziell ]Die Fähigkeit des Frontend-Designs ist eine Fähigkeit, die es KI-Agents ermöglicht, ansprechende und funktionale Benutzeroberflächen für Webkomponenten, Seiten und Anwendungen zu erstellen.
Durchsuchen und installieren Sie Tausende von AI Agent Skills im Killer-Skills-Verzeichnis. Kompatibel mit Claude Code, Windsurf, Cursor und mehr.
This directory brings installable AI Agent skills into one place so you can filter by search, category, topic, and official source, then install them directly into Claude Code, Cursor, Windsurf, and other supported environments.
Organic recovery should flow through fewer, stronger, first-party entry points instead of a flat bulk-skill corpus.
Curated collection pages carry clearer topical scope, stronger first-party framing, and safer canonical signals than bulk skill listings.
Installation docs prove the site offers first-party setup guidance, not just discovery wrappers.
A workflow-first collection that explains why related skills belong together and what job they solve.
A platform-specific collection for one of the clearest demand clusters in the product ecosystem.
A platform collection that turns IDE demand into a stronger curated hub.
A Gemini-specific collection that turns compatibility research into a curated install path for real delivery teams.
A Python engineering collection built for teams choosing installable workflow helpers instead of browsing raw packages.
A typed-development collection that helps product teams shortlist TypeScript workflow tools with clear next steps.
Die Fähigkeit des Frontend-Designs ist eine Fähigkeit, die es KI-Agents ermöglicht, ansprechende und funktionale Benutzeroberflächen für Webkomponenten, Seiten und Anwendungen zu erstellen.
Die Fähigkeit brand-guidelines ist eine Funktion von AI-Agenten, die die offiziellen Farben und die Typografie von Anthropics auf jedes Artefakt anwendet.
Tensors and Dynamic neural networks in Python with strong GPU acceleration
Generate a single-line commit message for ant-design by reading the projects git staged area and recent commit style. Use when the user asks for a commit message, says msg, commit msg, 写提交信息, or wants one-line text that covers all staged changes. Output should match the repositorys existing commit style and summarize all staged changes in one line.
Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.
The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.
db-migrations ist eine Fähigkeit für KI-Agenten, die die Verwaltung von Datenbanken ermöglicht
Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup, or test-related questions.
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.
Data fetching architecture guide using Service layer + Zustand Store + SWR. Use when implementing data fetching, creating services, working with store hooks, or migrating from useEffect. Triggers on data loading, API calls, service creation, or store data fetching tasks.
Cross-repo testing facilitates end-to-end testing of features spanning SDK and Cloud backend, benefiting developers with efficient AI-driven development. It enables testing of new API endpoints and unreleased SDK packages.
Babysit a GitHub pull request after creation by continuously polling CI checks/workflow runs, new review comments, and mergeability state until the PR is ready to merge (or merged/closed). Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and stop only when user help is required (for example CI infrastructure issues, exhausted flaky retries, or ambiguous/blocking situations). Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.