「engineer」の検索結果

Use when a user requests an engineering retrospective for a period. Not for agent-environment retrospectives: use agent-environment-retrospective. For learning milestones: use learning-retrospective.

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

Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.

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

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".

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

Menu engineering analysis — item placement, description quality, pricing psychology, upsell opportunities, photo presence, Kasavana matrix (Stars/Plowhorses/Puzzles/Dogs)

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

Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through utility rather than content. Also use when someone asks 'how do I get more signups', 'what should I build for marketing', or 'content marketing alternative' — a free tool is often the best answer. Includes search volume validation, UX flow templates, and conversion hook design.

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

Design and review autonomous or semi-autonomous agent loops — systems where an agent prompts itself, runs on a schedule or event, and iterates toward a goal without a human at the keyboard. Use this whenever the user wants to build, design, harden, or audit any kind of self-running agent, agentic workflow, control loop, background worker, cron/heartbeat/webhook-driven agent, "Ralph loop", auto-PR-fixer, monitoring agent, or any long-running task that should keep going on its own until done. Trigger this even when the user says "agentic workflow", "automation that runs itself", "an agent that keeps trying until X", or "make my agent stop running away / burning tokens" without using the word "loop". Also use it to review an existing loop's stopping conditions, guardrails, verification, and escalation paths.

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

Turn an electronic product idea, behavior description, reverse-engineering note, or incomplete circuit concept into a decision-ready engineering brief and architecture. Use before schematic design or audit when functions, operating states, power, interfaces, mechanics, production quantity, cost, or measurable requirements are missing or ambiguous.

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

Use when writing Swift code for Apple platforms - iOS, macOS, visionOS. Covers Swift 6 concurrency, actors, Sendable, async/await, SwiftUI, MVVM architecture, Metal GPU programming, RealityKit ECS, visionOS scenes, interpolation/animation, advanced collection types, property wrappers, Combine bridging, error handling, testing, and API design patterns.

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

Use when the user asks about phishing campaigns, social-engineering techniques, BEC (business email compromise), pretexting, AiTM (adversary-in-the-middle) kits, or specific phishing-kit families. Self-updating knowledge cell.

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

Use when designing, optimizing, testing, or deploying robust prompt systems for AI agents. This skill provides frameworks for structured prompt engineering, meta-prompting, and automated optimization workflows.

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

Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.

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

Expert prompt engineer specializing in designing, optimizing, and managing prompts for large language models. Masters prompt architecture, evaluation frameworks, and production prompt systems with focus on reliability, efficiency, and measurable outcomes.

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

Expert fintech engineer specializing in financial systems, regulatory compliance, and secure transaction processing. Masters banking integrations, payment systems, and building scalable financial technology that meets stringent regulatory requirements.

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

Expert IoT engineer specializing in connected device architectures, edge computing, and IoT platform development. Masters IoT protocols, device management, and data pipelines with focus on building scalable, secure, and reliable IoT solutions.

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

Use when legacy prompts or older framework flows reference `remotion-engineer` and you need the modern runtime to resolve that capability cleanly.

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

Use when legacy prompts or older framework flows reference `qa-automation-engineer` and you need the modern runtime to resolve that capability cleanly.

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

Use when legacy prompts or older framework flows reference `growth-engineer` and you need the modern runtime to resolve that capability cleanly.

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

Use when legacy prompts or older framework flows reference `devops-engineer` and you need the modern runtime to resolve that capability cleanly.

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

Use when legacy prompts or older framework flows reference `conversion-engineer` and you need the modern runtime to resolve that capability cleanly.

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

Consolidated Galyarder Framework Engineering intelligence bundle.

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

"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.".

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

Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.

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

Use for hands-on repository work when a quiet, risk-scaled engineering method can improve design, implementation, debugging, review, delegation, workspace lifecycle, or verification. Keep clear local changes direct, preserve the complete requested outcome, and add method only where risk or uncertainty justifies it. Do not use for general technical explanations, simple file lookup, casual discussion, or non-engineering writing.

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

Malware reverse engineering and suspicious artifact analysis skill for defensive triage, static analysis, dynamic analysis planning, unpacking strategy, indicators of compromise, behavior summaries, YARA/Sigma ideas, and remediation guidance. Use for suspicious binaries, scripts, documents, logs, memory artifacts, sandbox reports, and malware family analysis in isolated environments.

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