1,887 件 ・ 関連度順
概要と使いどころ
Topic router for the AI Engineering from Scratch curriculum. Give it a topic, a question, or a bug you are fighting, and it points at the exact lessons that teach it, plus the right next command. Trigger phrases: "where do I learn", "which lesson covers", "course guide", "I'm stuck on", "what should I do next", "teach me MCP", "teach me Agent Skills", "where do I prepare for a Claude certification"
日本語の概要は準備中です。原文の説明を表示しています。
Interactive lesson tutor for the AI Engineering from Scratch curriculum. Reads LEARNING.md, fetches the next lesson, teaches it section by section in the terminal, quizzes at the end, and records progress. Works cloned or entirely over raw.githubusercontent.com — no setup required. Trigger phrases: "next lesson", "teach me", "continue the course", "let's learn", "resume learning"
日本語の概要は準備中です。原文の説明を表示しています。
Design and execute a social engineering penetration test combining OSINT-driven target profiling with phishing, vishing, smishing, and physical pretexting campaigns using tools like GoPhish, the Social Engineer Toolkit (SET), and Evilginx to measure human security resilience. Use when scoping or running an authorized human-attack-surface test and reporting results to identify security awareness training gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute authorized vishing (voice phishing) pretext calls to assess employee susceptibility to social engineering and evaluate security awareness controls.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning, running, or learning from chaos engineering experiments. Triggers on "chaos experiment", "fault injection", "gameday", "resilience test", "blast radius", "steady state", "abort criteria", "Chaos Toolkit", "Chaos Mesh", "Litmus", "Gremlin", "AWS FIS", or any deliberate failure-injection question. Ships experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references on chaos principles + experiment design + attack taxonomy + tooling landscape, and a /chaos-experiment slash command. Composes with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (common chaos targets).
日本語の概要は準備中です。原文の説明を表示しています。
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.
日本語の概要は準備中です。原文の説明を表示しています。
Automates the end-to-end detection engineering workflow in Google SecOps using MCP tools. Use when fetching threat intelligence from blogs, generating Threat Detection Opportunities (TDOs), simulating attacker behavior with synthetic UDM events, evaluating rule coverage, and deploying gap-closing rules. Don't use for standalone YARA-L 2.0 rule authoring/tuning (use secops-detection-engineering), threat hunting, or SOC investigation.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used to explain or reason about the foundational concepts of context engineering: what context is, the anatomy of a context window, how attention mechanics work, the U-shaped attention curve, why context quality matters more than quantity, and the mental models needed to interpret every other context-engineering decision. Use this for conceptual explanation, onboarding, and background reading. Route operational work to the specialized skills: debugging attention failures goes to context-degradation, token-efficiency work goes to context-optimization, conversation summarization goes to context-compression, and project-shape decisions go to project-development.
日本語の概要は準備中です。原文の説明を表示しています。
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Chaos engineering: hypothesis-driven fault injection to surface weakness before users do. Use when designing a chaos experiment, planning a gameday, choosing what to inject, computing blast radius, or building a chaos maturity model.
日本語の概要は準備中です。原文の説明を表示しています。
VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning. Use when scoring engineering org health, designing the eng org, planning capacity, or building the productivity dashboard.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a Harness Engineering framework in the current project. Use when user says 'harness', 'init harness', 'initialize framework', 'setup harness engineering', '/harness', or wants to set up a Plan-Build-Verify development workflow with specialized agents (planner, generator, evaluator). Creates CLAUDE.md, agent definitions, command templates, hooks, and documentation structure for autonomous AI-driven development.
日本語の概要は準備中です。原文の説明を表示しています。
VP Engineering perspective - org design (team topologies), process improvement, cross-team dependencies, engineering culture, OKRs, incident management maturity, platform strategy, DX optimization, release management at scale
日本語の概要は準備中です。原文の説明を表示しています。
Binary analysis, assembly interpretation, disassembly, decompilation, firmware RE, and protocol reverse engineering
日本語の概要は準備中です。原文の説明を表示しています。
Design engineering principles and patterns for building polished, accessible web interfaces. Use this skill when building UI components, reviewing frontend code, implementing forms, handling touch interactions, optimizing performance, or creating marketing pages. Triggers on: design engineering, UI polish, input fields, form validation, button states, touch devices, mobile UX, accessibility, a11y, keyboard navigation, aria labels, font rendering, typography, layout shift, z-index, animations, transitions, easing, hover effects, tap targets, iOS Safari, prefers-reduced-motion, marketing pages, landing pages, dark mode, theme switching, scrollbars, gradients, shadows, virtualization, preloading.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs engineering or research-paper figures: system architecture diagrams, algorithm workflows, hardware schematics, benchmark charts, ablation plots, figure briefs, redraws, image edits, or exact publication-style plots from numeric data. Covers Gemini, Nano Banana, OpenAI image models, and local plotting workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the bioengineering, mechanobiology, and lymphatic transport reasoning of J. Brandon Dixon, professor of mechanical and biomedical engineering at Georgia Institute of Technology. Reach for this skill whenever analyzing lymphatic biomechanics, active vessel contractility versus passive drainage, peristaltic fluid transport, microfluidic organ-on-a-chip design, preclinical lymphedema models, non-invasive functional imaging, targeted nanomedicine delivery, or automated disease staging. Use this skill to critique bioengineering assumptions, guide quantitative protocol design, evaluate biomechanical pump failure, and formulate interdisciplinary biomedical solutions.
日本語の概要は準備中です。原文の説明を表示しています。
ROS 2 engineering: rclcpp/rclpy, colcon/ament, launch, QoS/DDS, tf2/URDF, ros2_control, Nav2, MoveIt 2, sensors, runtime/artifact provenance, and hardware safety. Use for development, review, debugging, and ROS 1 migration to ROS 2. Not for general C++/Python, unrelated middleware, or web/mobile tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Genome Engineering (CRISPR) Scientist. Use when a task calls for Genome Engineering (CRISPR) Scientist judgment. Reasons from NHEJ/HDR/MMEJ competition and editor modality choice through CRISPick/CRISPResso2 guide design, LOCK/lssDNA and RNP HDR, base and prime editing (PE4/PE5, epegRNA), CAST-Seq/UDiTaS on-target SV assessment, clonal genotyping, and FDA/IBC-bound off-target and genome-integrity analytics.
日本語の概要は準備中です。原文の説明を表示しています。
Audits and reorganises what an AI coding agent carries in its context window: instruction files, path-scoped rules, skills, subagents, hooks and the running conversation. Use when someone says "the agent ignores our CLAUDE.md", "set this repo up for Claude Code / Codex / Cursor", "my AGENTS.md is too long", "quality drops in long sessions", "it keeps inventing APIs", "what should go in a skill versus the rules file", or asks how to hand work to a subagent. Grounded in the documented loading behaviour of Claude Code, with the equivalents for Codex, Gemini CLI and Cursor.
日本語の概要は準備中です。原文の説明を表示しています。
Routes to the right vibe-engineering skill for the current task and lists the full catalog. Use when the user asks which skill to use, asks what vibe-engineering can do, or is unsure how to approach a task.
日本語の概要は準備中です。原文の説明を表示しています。
UBNT/UniFi 企业 Wi-Fi 工程 (UniFi/UBNT Enterprise Wi-Fi Engineering) Master OS — automated mastery of UniFi/UBNT Enterprise Wi-Fi Engineering: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on UniFi/UBNT Enterprise Wi-Fi Engineering problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「造大师 UBNT Wi-Fi」「UBNT WiFi 工程」「UniFi 高密度部署」「我做企业 Wi-Fi」「80 人办公网慢」
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate evidence-first engineering for WeChat and other mini programs from a vague idea or existing repository through project discovery, product specification, architecture, implementation, debugging, device adaptation, verification, and release readiness. Use when users ask to build a mini program from zero to one, take over an existing mini-program project, deliver a cross-stage feature, diagnose project status, coordinate development and testing, or judge whether a mini program is ready to upload or release. Enforces fact discovery, change boundaries, stage gates, evidence-calibrated status, sensitive-information redaction, and continuity after side questions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".
日本語の概要は準備中です。原文の説明を表示しています。