193건 · 관련도순
Use when using the Popochiu addon — point-and-click adventure framework with rooms, characters, props/hotspots, inventory, dialog trees, and a command-based GUI
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert patterns for Godot 3D physics (Jolt/PhysX), including Ragdolls, PhysicalBones, Joint3D constraints, RayCasting optimizations, and collision layers. Use for rigid body simulations, character physics, or complex interactions. Trigger keywords: RigidBody3D, PhysicalBone3D, Jolt, Ragdoll, Skeleton3D, Joint3D, PinJoint3D, HingeJoint3D, Generic6DOFJoint3D, RayCast3D, PhysicsDirectSpaceState3D.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert blueprint for physics queries using RayCast, ShapeCast, and DirectSpaceState. Covers hit detection, volume overlap, mouse picking, and high-performance server-side intersection queries. Use when implementing projectiles, LOS, terrain grounding, or AI sensors. Keywords raycast, shapecast, direct_space_state, intersect_ray, intersect_shape, PhysicsRayQueryParameters, collision mask, mouse picking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert patterns for Godot 2D physics including collision layers/masks, Area2D triggers, raycasting, and PhysicsDirectSpaceState2D queries. Use when implementing collision detection, trigger zones, line-of-sight systems, or manual physics queries. Trigger keywords: CollisionShape2D, CollisionPolygon2D, collision_layer, collision_mask, set_collision_layer_value, set_collision_mask_value, Area2D, body_entered, body_exited, RayCast2D, force_raycast_update, PhysicsPointQueryParameters2D, PhysicsShapeQueryParameters2D, direct_space_state, move_and_collide, move_and_slide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Converges an underspecified request into an IntentSpec: looks up what sources answer, asks only what they cannot, halts instead of guessing, checks delivery against the spec. Use when a request to implement, add, change, fix or configure leaves a decision open — scope, approach, failure behaviour, what done means — contradicts itself, reads two ways, or rests on a premise sources rule out. Silent on a fully stated request its sources do not contradict; not for explaining existing state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use dotnet-diagnostics-mcp for MCP-driven .NET CPU, allocation, GC, and test-host profiling. USE FOR: profiling unit tests or investigating runtime bottlenecks. DO NOT USE FOR: writing test assertions, coverage collection, or precise microbenchmark timing. INVOKES: connect the MCP server, select target processes, collect bounded profiles, and attribute hotspots to source.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. This should trigger for requests such as Analyze JFR profile; Analyze the profile; Analyze the performance; Analyze the memory; Analyze the threading; Analyze GC logs from profiling; Prioritize Java profiling bottlenecks by impact. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects time and space complexity hotspots via AST scan. Use when code feels slow, before performance-sensitive merges, or to find O(n²) regressions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Native macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces. Use when asked to profile, attach, record, or analyze Instruments .trace files, find hotspots, or optimize native app performance without opening Instruments UI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework patterns, root causes, hotspots, and auto-improves prompts/health.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect and analyze areas with high maintenance cost, poor design, or accumulated technical debt. Use this skill when reviewing codebases for quality issues, planning refactoring efforts, conducting code audits, assessing project health, identifying maintenance hotspots, or prioritizing technical improvements. Analyzes code smells, architectural issues, dependency problems, test quality, documentation gaps, and provides actionable recommendations with priority rankings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Profile programs at the function/method level to identify performance hotspots, bottlenecks, and optimization opportunities. Records execution time, memory usage, and call frequency for each interval. Generates actionable recommendations and visualizations. Use when users need to (1) analyze program performance, (2) identify slow functions or bottlenecks, (3) optimize execution time or memory usage, (4) profile Python, Java, or C/C++ programs with test cases or workload scenarios, or (5) generate performance reports with flame graphs and recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Life-Cycle Assessment Analyst. Use when a task calls for Life-Cycle Assessment Analyst judgment. Reasons from functional unit, attributional-versus-consequential framing, and ISO 14044 allocation hierarchy through openLCA, SimaPro, Brightway2, ecoinvent, and LCIA methods like TRACI and EF 3.0 while treating allocation-driven ranking flips, biogenic-versus-fossil carbon mistagging, cut-off-masked hotspots, and PCR mismatch as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Electronics Engineer. Use when a task calls for Electronics Engineer judgment. Reasons from datasheet-corner device physics, signal-chain error budgets, and analog-digital return-path coupling through LTspice/IBIS-AMI simulation, ICT/boundary-scan coverage, golden-board signature comparison, and IPC/AEC-Q standards while treating ESD versus EOS overstress, MLCC DC-bias derating, reference and clock-jitter ENOB loss, and NFF field returns as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Agricultural Engineer. Use when a task calls for Agricultural Engineer judgment. Reasons from mass, energy, and momentum balances on variable biological media through ET-based scheduling, psychrometric grain-drying balances, ASABE D497 draft estimates, EPANET pipe networks, and RTK-GNSS/ISOBUS precision-ag validation while treating soil compaction, clogged drip emitters, grain-bin hotspots, GPS drift, and uncalibrated yield monitors as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate protein backbones using RFdiffusion, a diffusion-based generative model for de novo protein structure generation. Use this skill when: (1) Designing binder scaffolds for a target protein, (2) Generating novel protein backbones from scratch, (3) Scaffolding functional motifs into new proteins, (4) Specifying hotspot residues for interface design, (5) Creating symmetric oligomers. For sequence design after backbone generation, use proteinmpnn. For structure validation, use alphafold or chai. For QC thresholds, use protein-qc.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explain a repository's architecture (modules, routes, storage, services), find risky hotspots, draw a Mermaid diagram of the code graph, or review how far a change reaches, from Cognee's code graph.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maps an unfamiliar or large codebase before implementation by locating entry points, ownership, execution paths, conventions, tests, dependencies, change hotspots, and unresolved questions. Use when onboarding to a repository, scoping a cross-cutting change, preparing a handoff or reusable CodeTour, explaining a subsystem, or when the agent is guessing where behavior lives. Not for diagnosing one reproduced failure or designing a new architecture before the current system is understood.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full codebase health assessment. Use when diagnosing project health or starting a rescue workflow on legacy code — OR when evaluating an external GitHub repo for dependency / fork / contribution decisions (--external mode). Analyzes complexity, dependencies, dead code, tech debt, and git hotspots. Produces a health score and rescue plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews App Intents code for intent structure, entities, shortcuts, and parameters. Use when reviewing code with import AppIntents, @AppIntent, AppEntity, AppShortcutsProvider, or @Parameter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Belastbaren Produktmarketing-Kontext für Positionierung, Zielgruppen, Botschaften, Einwände und Nachweise erstellen, prüfen und aktualisieren. Nutze diesen Skill, wenn die gemeinsame Grundlage fehlt, auf die sich Texte, Content, Vergleiche und Kampagnen stützen sollen: ICP, Jobs-to-be-Done, Nutzenversprechen, Differenzierung, Preislogik, Einwandbehandlung und Belegklassen. Legt das Ergebnis als `.agents/product-marketing.md` im Projekt ab und kennzeichnet, was belegt, was Anbieterangabe und was Annahme ist. Ersetzt weder Kundenforschung noch Rechtsprüfung.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.