Ferramentas dev e skills de workflow compatíveis com Gemini | AI Agent Skills
Coleção de AI Agent Skills instaláveis para workflows de desenvolvimento em gemini compatible dev no Claude Code, Cursor e Windsurf.
Esta coleção focada em Gemini foi feita para execução de desenvolvimento real: skills reutilizáveis, camadas de integração e componentes de automação para código, review e controle de entrega. Não é ranking genérico; é para times que entregam software com agentes de IA. MCP pode ser útil em casos específicos, mas o foco principal é confiabilidade de workflow.
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 Gemini workflow fit, installation clarity, operator handoff, and day-to-day delivery usefulness. This page is now positioned as an install-first Gemini entry point instead of a generic compatibility list.
We prioritize this page because Gemini-intent users usually need a shortlist they can install, validate, and carry into real development loops quickly.
Trust Signals
- Entries are chosen for practical Gemini workflow value such as coding support, review loops, handoff, and repeatable execution.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable developer execution, not for vague compatibility keyword stuffing.
Grouping Logic
- Lead with tools that can enter a Gemini-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering coding, review, handoff, and automation.
- Use installation as the bridge from Gemini discovery into validated daily execution.
Maintenance & Review
Last Reviewed
2026-04-17
Cadence
Re-check when install flow, maintainer posture, or Gemini 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 Gemini workflow companion first
Use this page when you want one Gemini companion that can enter real development work without turning evaluation into another endless tooling loop.
1. Open the installation docs before opening more Gemini-related repositories.
2. Choose one tool that best supports coding, review, handoff, or automation.
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 team workflow.
Reduce workflow drift around Gemini
Treat the collection as an editorial filter when you need Gemini-adjacent tools that improve output quality 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 projects or more teammates.
4. Document the chosen Gemini workflow baseline after the first clean rollout.
The component-refactoring skill simplifies high-complexity React components, improving code quality and reducing maintenance efforts for developers. It utilizes patterns and workflows to refactor components, making them more efficient and easier to understand.
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
Guide for implementing oRPC contract-first API patterns in Dify frontend. Trigger when creating or updating contracts in web/contract, wiring router composition, integrating TanStack Query with typed contracts, migrating legacy service calls to oRPC, or deciding whether to call queryOptions directly vs extracting a helper or use-* hook in web/service.
This frontend-code-review skill reviews frontend files, such as .tsx, .ts, and .js, and applies a checklist to ensure code quality, performance, and business logic, helping developers and teams maintain high standards.
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.
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.
Guide for adding keyboard shortcuts. Use when implementing new hotkeys, registering shortcuts, or working with keyboard interactions. Triggers on hotkey implementation or keyboard shortcut tasks.
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.
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.
Para quais fluxos de trabalho essas coleções foram criadas?
Essas coleções são construídas em torno de automação de fluxos, processos, documentos, dados e pilhas de habilidades reutilizáveis.
Qual a diferença entre uma coleção e o diretório principal?
O diretório é melhor para busca direta, enquanto coleções ajudam a encontrar habilidades complementares agrupadas por fluxo completo.
Posso instalar essas coleções para Claude Code ou Cursor?
Sim. As habilidades dessas coleções geralmente funcionam no Claude Code, Cursor, Windsurf e outros ambientes com instalação unificada.
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.
