Sammlungen
Sammlung productivity

Top-Produktivitätstools für KI-unterstützte Entwickler | AI Agent Skills

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

Diese Sammlung konzentriert sich auf tägliche Entwicklerproduktivität mit KI-Unterstützung. Sie hebt Tools hervor, die Kontextwechsel reduzieren, typische Coding-Aufgaben beschleunigen und den Ausführungsrhythmus von Einzelnen und Teams verbessern, ohne die Betriebs-Komplexität unnötig zu erhöhen. MCP-Integrationen können sinnvoll sein, Hauptziel sind jedoch praktische Produktivitätsgewinne.

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 related page to open afterwards.

Reviewed On
2026-04-17
Maintained By
Maintained through Killer-Skills curation review with install, documentation, and productivity-workflow checks.
Verification
Validate installability, workflow fit, setup clarity, and maintainer trust before retaining or adding an entry.
Primary Audience
People 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.
Recommended Install Path

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 the next practical step. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

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

Open the Install Path
Recommended Next Steps

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.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against daily execution fit, installation clarity, context-switch reduction, and setup simplicity. This page is now positioned as an installation-focused productivity entry point instead of a soft productivity roundup.

We prioritize this page because productivity-intent users usually want one tool worth keeping in the main workflow, not another broad list they browse and forget.

Trust Signals

  • - Entries are chosen for reducing repeated work, shrinking context switching, and improving execution rhythm inside real coding days.
  • - Selection favors tools with public docs and setup paths that teams can validate before they spread them across everyday workflows.
  • - The page is curated for practical momentum gains, not for soft productivity branding or generic AI adjacency.

Grouping Logic

  • - Lead with tools that can fit the current coding loop without forcing a full stack reset.
  • - Keep the shortlist compact enough for quick comparison while still covering personal acceleration and team execution rhythm.
  • - Use installation as the bridge from productivity discovery into validated daily use.

Maintenance & Review

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

How These Skills Work Together In Practice

Install one daily accelerator before reshaping the whole stack

Use this page when you want one productivity tool that genuinely saves time in the daily loop instead of adding another layer of busywork.

  1. 1. Open the installation docs before opening more productivity-tool repositories.
  2. 2. Choose one tool that best reduces repeated work, context switching, or setup drag.
  3. 3. Install it and verify the CLI write path, sync behavior, and first key validation step.
  4. 4. Only after the base path works, expand the setup across the wider team workflow.

Protect execution rhythm across the team

Use this collection when you need tools that keep developers moving without forcing them into another broad migration or platform reset.

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

Supporting Moves After The Install Path Is Clear

project-guidelines-example

[ Empfohlen ]
Logo of affaan-m
affaan-m

The project-guidelines-example skill provides a template for project-specific skills, leveraging Next.js, FastAPI, and Claude API. It helps developers manage complex projects and improve coding efficiency.

108.5k
0
Entwickler

documentation-criteria

Logo of shinpr
shinpr

Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.

35
0
Produktivität
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 collections to narrow the shortlist toward the install path that best matches your team.

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.