5,793 件 ・ 関連度順
概要と使いどころ
Use quando o usuário pergunta como construir com produtos ou APIs da OpenAI e precisa de documentação oficial atualizada com citações (por exemplo: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, capacidades ou limites de modelos); priorize ferramentas MCP de docs da OpenAI e restrinja qualquer fallback de navegação a domínios oficiais da OpenAI.
日本語の概要は準備中です。原文の説明を表示しています。
Orientação especializada para fine-tuning de LLMs com Axolotl - configs YAML, 100+ modelos, LoRA/QLoRA, DPO/KTO/ORPO/GRPO, suporte multimodal
日本語の概要は準備中です。原文の説明を表示しています。
Orquestração de treinamento distribuído em clusters. Escala PyTorch/TensorFlow/HuggingFace do laptop para milhares de nós. Ajuste de hiperparâmetros integrado com Ray Tune, tolerância a falhas, escalabilidade elástica. Use ao treinar modelos massivos em múltiplas máquinas ou executar varreduras distribuídas de hiperparâmetros.
日本語の概要は準備中です。原文の説明を表示しています。
Reduza o tamanho de LLMs e acelere a inferência usando técnicas de pruning como Wanda e SparseGPT. Use para comprimir modelos sem retreinamento, alcançando 50% de esparsidade com perda mínima de acurácia, ou ativando inferência mais rápida em aceleradores de hardware. Cobre pruning não estruturado, pruning estruturado, esparsidade N:M, pruning por magnitude e métodos one-shot.
日本語の概要は準備中です。原文の説明を表示しています。
Especialista em CrewAI - o principal framework multi-agente baseado em papéis utilizado por 60% das empresas da Fortune 500. Abrange design de agentes com papéis e objetivos, definição de tarefas, orquestração de crew, tipos de processo (sequencial, hierárquico, paralelo), sistemas de memória e flows para workflows complexos. Essencial para construir equipes colaborativas de agentes IA. Use quando: crewai, equipe multi-agente, papéis de agentes, crew de agentes, agentes baseados em papéis.
日本語の概要は準備中です。原文の説明を表示しています。
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
日本語の概要は準備中です。原文の説明を表示しています。
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the Opquast Digital Quality Framework (245 rules, 14 categories) when building, reviewing, or auditing websites and web applications. Use for web development quality assurance, accessibility compliance, security hardening, privacy implementation, e-commerce best practices, and holistic digital quality checks.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.
日本語の概要は準備中です。原文の説明を表示しています。
[Git] Use when you need to create isolated git worktree for parallel development.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs written before code.
日本語の概要は準備中です。原文の説明を表示しています。
[Fix & Debug] Use when you need to investigate and explain how existing features or logic work. Flag: --mode=explain produces a one-way developer-narrative explanation (Purpose → How → Why → Impact) tuned by coding level; use /understand for the standalone prompt-driven explainer.
日本語の概要は準備中です。原文の説明を表示しています。
[Planning] Use when calibrating estimates from actual code, diff, PR scope, and developer time.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to implement an approved SPEC SDD using test-driven development.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating or updating a project README.md or CHANGELOG.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating Product Hunt launch carousel images for developer tools, AI tools, open-source projects, GitHub launches, or technical products. Research comparable launches, inspect the project, extract verified proof points, then generate 4-5 launch-ready images with consistent branding, product surfaces, readable copy, and source-grounded claims.
日本語の概要は準備中です。原文の説明を表示しています。
Replace with what this skill does and when to use it. Include trigger phrases users say, e.g. "audit my API", "scaffold a skill"; activation-critical routing belongs here.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shipping a macOS app outside the App Store — Developer ID signing with hardened runtime, notarization with notarytool, stapling, building a clean drag-to-Applications DMG, and verifying the result launches on a stranger's Mac.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, reviewing, or implementing Settings/Preferences for Apple-platform apps — what belongs in Settings vs Inspector/Toolbar, grouped forms, native controls, secure storage, launch at login, and destructive actions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to update, improve, audit, or maintain documentation in a project. Covers READMEs, changelogs, API docs, inline comments, missing docs, and overall documentation quality. Works well before releases or when documentation has fallen behind the code.
日本語の概要は準備中です。原文の説明を表示しています。
国风 3D 网页渲染。当用户要"水墨风 3D""中国风网页特效""Three.js 水墨""国风 H5""青绿山水 3D""非真实感渲染 NPR""古风 WebGL"时使用。提供可运行的中式渲染 shader 与实现方法，不是通用 Three.js 教程。
日本語の概要は準備中です。原文の説明を表示しています。
中式网页主题库。当用户要"中国风网页""国风网站样式""古风博客主题""中式配色 CSS""水墨风页面""新中式网页""给网站换个中国风皮肤"时使用。提供 8 套可直接引入的 CSS 主题，内置中文排版规范。
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。