「tar」の検索結果

Agentes autônomos são sistemas de IA que conseguem decompor objetivos, planejar ações, executar ferramentas e se auto-corrigir sem orientação humana constante. O desafio não é torná-los capazes - é torná-los confiáveis. Cada decisão extra multiplica a probabilidade de falha. Esta habilidade cobre loops de agentes (ReAct, Plan-Execute), decomposição de objetivos, padrões de reflexão e confiabilidade em produção. Insight-chave: taxas de erro compostas matam agentes autônomos. Uma taxa de sucesso de 95% por passo cai para 60% b

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Use quando enfrenta 2+ tarefas independentes que podem ser trabalhadas sem estado compartilhado ou dependências sequenciais

日本語の概要は準備中です。原文の説明を表示しています。

Framework de orquestração multi-agent para colaboração autônoma de IA. Use ao construir equipes de agentes especializados trabalhando juntos em tarefas complexas, quando você precisa de colaboração de agentes baseada em papéis com memória, ou para workflows em produção exigindo execução sequencial/hierárquica. Construído sem dependências de LangChain para execução enxuta e rápida.

日本語の概要は準備中です。原文の説明を表示しています。

Avalia modelos de geração de código em HumanEval, MBPP, MultiPL-E e 15+ benchmarks com métricas pass@k. Use ao comparar modelos de código, avaliar capacidades de codificação, testar suporte multilíngue ou medir qualidade de geração de código. Padrão da indústria do BigCode Project usado pelos leaderboards do HuggingFace.

日本語の概要は準備中です。原文の説明を表示しています。

CLI do Datadog para buscar logs, consultar métricas, rastrear requisições e gerenciar dashboards. Use isso ao depurar problemas em produção ou trabalhar com observabilidade do Datadog.

日本語の概要は準備中です。原文の説明を表示しています。

Envie e receba mensagens criptograficamente assinadas entre agentes de IA usando o Agent Messaging Protocol (AMP). Use quando o usuário pedir para "enviar uma mensagem para um agente", "verificar caixa de entrada do agente", "mensagear outro agente", "responder a uma mensagem", "notificar um agente" ou qualquer tarefa de comunicação entre agentes.

日本語の概要は準備中です。原文の説明を表示しています。

Treinar modelos de Mixture of Experts (MoE) usando DeepSpeed ou HuggingFace. Use ao treinar modelos em larga escala com computação limitada (redução de 5× em custos vs modelos densos), implementar arquiteturas esparsas como Mixtral 8x7B ou DeepSeek-V3, ou escalar capacidade de modelo sem aumento proporcional de computação. Cobre arquiteturas MoE, mecanismos de roteamento, balanceamento de carga, paralelismo de especialistas e otimização de inferência.

日本語の概要は準備中です。原文の説明を表示しています。

Use this Canvas-owned clean-room skill for creating, reading, editing, reviewing, redlining, commenting, or repairing Word `.docx` documents. Trigger for Word documents, DOCX files, memos, reports, letters, templates, tracked changes, comments, table of contents, headers, footers, page numbers, and Google Docs-targeted documents that should be authored as DOCX first.

日本語の概要は準備中です。原文の説明を表示しています。

Use this Canvas-owned clean-room skill whenever a PowerPoint `.pptx` deck is an input or output. Trigger for creating, editing, reviewing, repairing, templating, combining, splitting, rendering, or extracting slide decks, including pitch decks, reports, speaker notes, template-following, and Google Slides-targeted handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Use this Canvas-owned clean-room skill when a spreadsheet file is the primary input or output. Trigger for `.xlsx`, `.xls`, `.xlsm`, `.csv`, `.tsv`, workbooks, templates, trackers, models, dashboards, charts, formulas, data cleaning, formatting, validation, recalculation, and Google Sheets-targeted handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.

日本語の概要は準備中です。原文の説明を表示しています。

Load this skill whenever the project contains in-page anchor links, skip links, fragment identifiers, or heading links. Under no circumstances omit accessible anchor-link requirements when such links exist. Ensure every anchor link has meaningful text, a reachable target, and a visible focus indicator. Apply these rules when creating or reviewing any in-page navigation.

日本語の概要は準備中です。原文の説明を表示しています。

Load this skill whenever the project involves writing, editing, or reviewing content for a general audience, including UI copy, help text, error messages, documentation, and instructions. Under no circumstances use jargon, complex sentence structures, or unexplained acronyms without providing plain alternatives. Absolutely always target a reading level accessible to the broadest possible audience. Load alongside content-design/SKILL.md for all content work.

日本語の概要は準備中です。原文の説明を表示しています。

Use when starting a new .NET/Blazor/Angular MVP project in an empty repository.

日本語の概要は準備中です。原文の説明を表示しています。

Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPECs via write-specs. Do NOT use to design/build UI from scratch (use design) or to fix findings inline — fixes go through the SPEC pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.

日本語の概要は準備中です。原文の説明を表示しています。

Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.

日本語の概要は準備中です。原文の説明を表示しています。

Turns an ICP or research goal into a plan for finding and scraping suitable directories. Use when the user has a target audience but is unsure where to find them, and wants source categories, queries, and an extraction workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx skills—not domain app tutorials.

日本語の概要は準備中です。原文の説明を表示しています。

Establish or audit a structural quality contract for any agent-operated engineering repository: app, library, CLI/tool, plugin, harness, or meta repo. Use when a repo needs charter clarity, docs/decision ownership, type-native validation gates, evidence paths, safe action policy, cold-start legibility, maturity proof, repair-loop routing, consumer/producer owner-boundary routing, command surface evolution, evolutionary simplicity (see references/evolutionary-simplicity.md), or a repo ecology pass to decide what should be compressed, merged, removed, updated, created, retired, or moved to checks.

日本語の概要は準備中です。原文の説明を表示しています。

Maintains repo-local action contracts and harness repositories where product CLI and MCP adapters stay thin over core libraries. Use when adopting or improving steward.yaml actions, capability-level adoption evidence, cold-start proof loops, probes, benchmarks, CLI/MCP/core parity, adapter refactors, packages/core boundaries, or sibling harness layout; use repo-quality-system-lifecycle first for general app/library/tool stewardship baselines.

日本語の概要は準備中です。原文の説明を表示しています。

Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Use when refactoring custom validation CLIs/MCPs for large polyrepos, extending Steward across sibling repos, or deploying a local tool to a consumer project for dogfooding and testing; use mcp-harness-repo-maintainer first for initial steward.yaml adoption and cold-start proof.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user adds a project to the workspace, opens an unfamiliar repo, asks "what is this project", "explain this codebase", or invokes explain-new-project. Explores a newly opened workspace project and writes a plain-language report for a self-taught, non-technical user—quick start (what it is + how to run) first, then optional depth—and always saves PROJECT_GUIDE.md in the project root.

日本語の概要は準備中です。原文の説明を表示しています。