「engineer」の検索結果

Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.

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

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

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

Padrões pragmáticos de codificação - conciso, direto, sem over-engineering, sem comentários desnecessários

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

Implementa infraestrutura como código usando Terraform, Kubernetes e plataformas de nuvem. Projeta arquiteturas escaláveis, pipelines de CI/CD e soluções de observabilidade. Fornece práticas DevOps com segurança em primeiro lugar e orientação em engenharia de confiabilidade de sites.

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

Especialista em design de prompts eficazes para aplicações com LLM. Domina estrutura de prompts, gerenciamento de contexto, formatação de output e avaliação de prompts. Use quando: engenharia de prompts, system prompt, few-shot, chain of thought, design de prompts.

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

Domine técnicas avançadas de engenharia de prompts para maximizar o desempenho, confiabilidade e controlabilidade de modelos de linguagem.

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

Controle saída de LLM com regex e gramáticas, garanta geração válida de JSON/XML/código, aplique formatos estruturados e construa fluxos de trabalho multi-etapas com Guidance - framework de geração restrita da Microsoft Research

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

Especialista em construção de sistemas de Retrieval-Augmented Generation. Domina modelos de embedding, bancos de dados vetoriais, estratégias de chunking e otimização de recuperação para aplicações LLM. Use quando: construir RAG, busca vetorial, embeddings, busca semântica, recuperação de documentos.

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

Extraia dados estruturados de respostas de LLM com validação Pydantic, tente novamente automaticamente extrações que falharem, analise JSON complexo com segurança de tipo e transmita resultados parciais com Instructor - biblioteca de saída estruturada testada em batalha

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

Garanta estrutura válida de JSON/XML/código durante a geração, use modelos Pydantic para outputs type-safe, suporte modelos locais (Transformers, vLLM) e maximize velocidade de inferência com Outlines - biblioteca de geração estruturada da dottxt.ai

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

Guia especializado em padrões de engenharia de prompts, melhores práticas e técnicas de otimização. Use quando o usuário quer melhorar prompts, aprender estratégias de prompting ou depurar comportamento de agentes.

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

Um Engenheiro de Pesquisa Acadêmica inabalável. Opera com rigor científico absoluto, crítica objetiva e zero floreios. Focado em correção teórica, verificação formal e implementação otimizada em qualquer tecnologia necessária.

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

Operações de LLM — RAG, embeddings, bancos de dados vetoriais, fine-tuning, prompt engineering avançado, custos de LLM, avaliações de qualidade e arquiteturas de IA para produção.

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

Construa pipelines de dados escaláveis, data warehouses modernos e arquiteturas de streaming em tempo real. Implementa Apache Spark, dbt, Airflow e plataformas de dados nativas em nuvem.

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

Write minimal, accessible web UI without over-engineering, adapting to whatever stack the project uses — React, Vue, Svelte, Angular, web components, or plain HTML. Use this skill on every project and every task that writes or reviews markup or components, builds forms, adds interactive elements like buttons, dialogs, accordions, or tabs, or audits code for accessibility — even when the user never mentions accessibility, and even inside a framework, CMS, or design system. It's non-negotiable regardless of project type, stack, or deadline. About to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component? Use this skill first.

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

Apply semantic HTML/JSX and WAI-ARIA correctly and minimally. Apply when implementing any UI, especially forms, interactive components, or when accessibility is mentioned.

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

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.

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

Superseded. Do not use. The procedure now lives in harness-engineering-lifecycle. This file remains so older installs resolve and then stop.

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

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

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

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

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

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, icons, micro-interactions, enter/exit animations, or any visual detail work. Supports quick and full review modes. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows, icons, icon stroke weight, icon states, motion restraint.

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

GStack autoplan method for running a broad CEO, design, engineering, and developer-experience review before opening implementation windows.

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

GStack engineering-manager plan review for architecture, data flow, APIs, migrations, edge cases, tests, performance, release risk, and implementation boundaries.

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

Route CEO-first multi-window work into owner-led role loops. Use for 总控/CEO、架构/CTO、内容主编、角色派发与复用、模型路由、来源窗口回调、role-windows 台账、skill 命中统计或 multi-window loop engineering。

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