2천건 · 관련도순
Create or improve AI prompts through a guided conversation about goals, roles, examples, and output formats. Receive a complete, reusable prompt with an explanation of its design, including behavioral boundaries for public-facing AI roles when needed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create roadmap updates, release notes, and feature announcements tailored to executives, engineering teams, or customers. Choose a suitable roadmap format and generate changelogs from Git history, making progress, user value, dependencies, and next actions clear.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan controlled failure experiments to uncover system weaknesses. Define normal operating metrics, estimate affected users and reliability risk, set abort and recovery conditions, and turn experiment results into a structured review with follow-up actions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review engineering delivery plans, hiring proposals, and team changes through six operational questions. Assess delivery metrics, recruitment stages, management structure, and production practices, then produce a verdict and three concrete actions to address the findings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evaluate whether Google SecOps rules detect threats described in articles or supplied text. Generate simulated attack logs, identify coverage gaps, summarize matching rules, and create rules for uncovered threats, with user approval before adding them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code changes for unnecessary complexity, including unused flexibility, avoidable dependencies, and abstractions with little purpose. Receive concise findings that name what to remove, what can replace it, and how many lines could be cut.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review unresolved Plain support tickets for missed response or resolution deadlines, VIP accounts, and serious problems. Route qualifying tickets to the responsible team, create linked Linear issues for engineering work, and post internal Slack alerts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use a structured starting point to write new context engineering skills. Organize activation conditions, responsibilities, practical steps, examples, and common mistakes, while keeping detailed references separate and clarifying boundaries with related skills.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create slides for internal engineering talks or conference presentations using a dark color scheme and a monospaced font. Organize the deck around an agenda, code examples, key points, terminal screenshots, and a closing Q&A.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a development-ready feature's specifications, customer context, demand evidence, and mockups into a concise executive summary. Give sales, leadership, and engineering one shared document covering the problem, solution, key decisions, scope, dependencies, metrics, and audience-specific questions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose why an AI workflow becomes inconsistent despite receiving extensive information. Through guided questions, define what to retain, retrieve when needed, or exclude, and develop a memory structure and a research-to-implementation process with focused context.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.