1,903 件 ・ 関連度順
概要と使いどころ
Write and revise rigorous research narratives, literature reviews, manuscript sections, citations, and figure discussions. Use for technical introductions, methods, results, discussions, review articles, abstracts, or related-work sections.
日本語の概要は準備中です。原文の説明を表示しています。
Iterative manuscript improvement workflow where a reviewer agent critiques, an author agent revises, a verifier checks the revision, and the loop repeats until acceptance or a human-pause condition is reached. Use for virtual peer review, reviewer-author revision loops, rebuttal preparation, resubmission polishing, journal paper improvement, response-to-reviewers drafting, and deciding when additional data, experiments, theory, modeling, or author judgment is required before further revision.
日本語の概要は準備中です。原文の説明を表示しています。
Provide constructive, evidence-based research mentoring feedback on student manuscripts, proposals, analyses, code, figures, and presentations. Use for advisor-style review that teaches the next improvement without impersonating an advisor or making unsupported scientific judgments.
日本語の概要は準備中です。原文の説明を表示しています。
Design clean, graphics-first technical presentations and posters with logical slide progression, visual hierarchy, purposeful motion, and complementary speaker notes. Use for research talks, conference slides, seminars, defenses, posters, or figure-focused presentations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Dragline and Excavating/Loading Machine Operator in surface mining — converting a rated bucket capacity into bank cubic yards moved per shift, deciding whether a swing angle or spoil-placement plan needs to be flagged to pit engineering, matching loading pass count and payload to a haul truck's rated capacity, checking ground bearing conditions before walking or tracking a machine onto fill or spoil, or reading a berm/highwall condition against MSHA thresholds.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Computer and Information Systems Manager (IT Manager/Director/CIO-adjacent) — planning IT infrastructure and systems strategy, evaluating a technology vendor or platform decision, allocating an IT budget, or managing IT risk (security, uptime, technical debt) at an organizational level. Broader than the devops-sre or software-engineer roles — this one owns IT as a business function, not a specific engineering discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Costume Designer — deciding build vs. rent vs. buy for a specific garment, budgeting a production's costume-shop spend across principals and ensemble, engineering a quick-change to hit a scripted time window, building or reading a costume plot to track pieces across a run, or diagnosing why a build is behind schedule going into tech week.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Civil Engineer — sizing stormwater detention/drainage systems, checking foundation bearing capacity against a geotechnical report, verifying IBC/ASCE 7 code compliance for site civil work, reviewing construction RFIs against stamped drawings, or evaluating value-engineering changes for safety-margin impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Chef or Head Cook — costing and re-engineering a menu, diagnosing a food-cost or prime-cost overrun, building a kitchen labor schedule against sales volume, vetting or renegotiating a vendor, or resolving a health-code/HACCP compliance gap.
日本語の概要は準備中です。原文の説明を表示しています。
Transform vague inputs into precision-optimized AI prompts for Claude, ChatGPT, Gemini, or other LLMs. Use when user mentions "optimize prompt", "improve prompt", "lyra", "prompt engineering", or needs help crafting effective AI prompts.
日本語の概要は準備中です。原文の説明を表示しています。
工程/执行原则录入器。当用户发现系统应遵守某条原则（工程约束/AI行为规范），自动分类原则类型、写入正确执行层、审计当前违规点、生成修复追踪。区别于 cognitive-extract-principle（后者处理郑总的思维方式原则）。触发词：「立一个原则」「记下这个原则」「这是条工程原则」「以后所有X都要Y」「把这条原则记在相关文档里」「这应该是工程原则」。
日本語の概要は準備中です。原文の説明を表示しています。
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Electrical and electronic engineering reference — circuit analysis, component selection, power supply design, signal integrity, RF, thermal, EMC, and test & measurement. Use for design questions, calculations, component vetting, and first-principles analysis. Do not orchestrate a complete new board from requirements; use circuit-weaver for that end-to-end workflow.
日本語の概要は準備中です。原文の説明を表示しています。
General electrical engineering support for hardware design and review. Load the canonical Circuit Weaver skill from `skills/ee/SKILL.md`.
日本語の概要は準備中です。原文の説明を表示しています。
Run the data science workflow end to end — framing, exploration, feature engineering, modeling, validation, and communicating results. Use when turning raw data into decisions or predictions.
日本語の概要は準備中です。原文の説明を表示しています。
Analytics engineering with dbt — models, tests, and modular SQL pipelines — use when building or maintaining dbt projects.
日本語の概要は準備中です。原文の説明を表示しています。
Engineer the full context a model sees — system prompts, retrieved knowledge, tool definitions, state, and history as one designed artifact. Use when moving beyond prompt tweaks to systematic context design.
日本語の概要は準備中です。原文の説明を表示しています。
Chaos engineering — designing safe failure-injection experiments to build resilience — use when proactively testing system robustness.
日本語の概要は準備中です。原文の説明を表示しています。
Strengthen defensive security operations — detection engineering, hardening, monitoring, and continuous defense improvement.
日本語の概要は準備中です。原文の説明を表示しています。
Installs and configures reverse engineering tools including radare2, Ghidra, GDB, QEMU, Frida, and cross-compilation toolchains for ARM64, ARMv7, x86_64, and MIPS. Use when a tool command fails, a required tool is missing, or you need to set up a fresh analysis environment.
日本語の概要は準備中です。原文の説明を表示しています。
Review then build — chains architecture review into implementation. Accepts any spec format (ticket, PRD, engineering spec, feature description, screenshot) and autonomously reviews the design, resolves gaps, then implements with tests and a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Generates backend or frontend engineering specs in structured Jira format with description, categorized acceptance criteria, routes, dev notes, and table schemas.
日本語の概要は準備中です。原文の説明を表示しています。