Loading...
Loading...
Found 6,175 Skills
ShapeUp: Facilitate the complete ShapeUp workflow with triad collaboration
Crée, récupère, met à jour et gère les issues GitHub avec collecte complète du contexte. À utiliser quand l'utilisateur veut créer une nouvelle issue, voir les détails d'une issue, mettre à jour des issues existantes, lister les issues du projet, ajouter des commentaires ou gérer les workflows d'issues dans GitHub.
Upstash Workflow implementation guide. Use when creating async workflows with QStash, implementing fan-out patterns, or building 3-layer workflow architecture (process → paginate → execute).
Bitrise integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bitrise data.
Insperity Premier integration. Manage data, records, and automate workflows. Use when the user wants to interact with Insperity Premier data.
Backblaze integration. Manage data, records, and automate workflows. Use when the user wants to interact with Backblaze data.
Toucan Toco integration. Manage data, records, and automate workflows. Use when the user wants to interact with Toucan Toco data.
Wit.ai integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wit.ai data.
Lean Technologies integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lean Technologies data.
Awesome Support integration. Manage data, records, and automate workflows. Use when the user wants to interact with Awesome Support data.
Full optimization workflow, sub-agent launch templates, agent communication contracts, default configurations, tuning strategy, and knowledge base update protocol. Use when: (1) starting an optimization cycle, (2) launching a Profiler or Designer sub-agent, (3) interpreting or formatting agent communication, (4) updating the knowledge base after a profiling or implementation iteration, (5) deciding default configurations or tuning strategy for a kernel.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, which can be accessed by both AI and humans when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — including bugs, configuration traps, environment issues, and integration failures; The knowledge track records findings that "should be the default approach going forward" — including best practices, workflow improvements, and reusable patterns. Trigger scenarios: Proactively prompt at the end of feature-acceptance or issue-fix workflows, or when the user mentions phrases like "document knowledge", "learning", "document learnings", or "record this experience". Spec documents record what was done, while learning documents record what pitfalls were encountered / what was learned — they complement each other and are not interchangeable.