'impact' 검색 결과

Inject juice and game feel into gameplay code using the project's chosen middleware. Use when adding screen shake, tweens, particles, audio feedback, haptics, hitstop, or any form of "juice" to gameplay events. Triggers on requests like "add juice", "make this feel better", "add screen shake", "polish this feature", "add feedback to this action", "make the hit feel impactful", "add particles when", "screen shake on damage", "tween this", "add camera shake", "make this snappy", or any game feel, polish, or feedback work. Always reads ProjectConfig.yaml -> feel_tools and docs/GFD.md Feedback Matrix before generating code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates sustainability-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify environmental impact requirements, and provide actionable recommendations to build, deploy, and manage the workload sustainably in Google Cloud.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a vulnerability report. Use when the user says "vulnerability report", "vuln report", "security finding", "write up this finding", "pentest finding", "bug bounty report", "security disclosure", "CVE writeup", "document this vulnerability", "how to report a security issue", or needs to formally document a security vulnerability with evidence, impact, and remediation guidance - even if they don't explicitly say "report".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for annotating ENCODE regulatory variants with ClinVar clinical significance. Use when users need to check if variants in ENCODE peaks have clinical associations, find pathogenic variants in regulatory regions, or assess variant clinical impact. Trigger on: ClinVar, clinical significance, pathogenic variant, variant classification, clinical variant, disease variant, VUS, benign, likely pathogenic.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Annotate genetic variants (GWAS hits, eQTLs, rare variants) with ENCODE functional data to interpret non-coding variation. Use when the user has variants of interest and wants to understand their regulatory context, identify causal variants from GWAS loci, assess variant impact on regulatory elements, perform enrichment testing of variant sets in tissue-specific annotations, or link variants to target genes through enhancer-gene maps. Handles the full post-GWAS workflow from variant set → tissue mapping → functional annotation → fine-mapping awareness → enrichment → variant-to-gene → prioritization. Use this skill for ANY variant interpretation task involving ENCODE chromatin, accessibility, TF binding, or 3D genome data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze features from user perspective and write user stories with acceptance criteria. Use when defining requirements, writing user stories, validating scope against project state, prioritizing features by impact, comparing approaches, analyzing user needs, or planning next work. Triggers: "user story", "acceptance criteria", "scope", "prioritize", "compare requirements", "user needs", "what to build next".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the codebase, scores findings by impact and effort, and generates a prioritized TECH_DEBT.md remediation plan. Delegates to specialized skills for code quality (scout) and linting (lint-fix). Use when assessing overall project health, planning cleanup sprints, or onboarding to an unfamiliar codebase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit a codebase against well-known software design principles: SOLID, DRY, YAGNI, KISS, Law of Demeter, Separation of Concerns, Composition over Inheritance, and the code-relevant 12-Factor subset. Scores findings by impact and effort, runs adversarial debate on contested violations, and generates a prioritized DESIGN_AUDIT.md. Use when reviewing code quality beyond what linters catch, assessing design health before a refactor, or onboarding to an unfamiliar codebase. Can be invoked standalone or delegated from tech-debt.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scout Rule — identify the top 3 highest-impact improvement opportunities in files you're already touching. Analyzes entire file content, not just changed lines. Focuses on pre-existing code quality, not PR bugs. Use when preparing a PR, during code review, or after completing a feature.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

วิเคราะห์หุ้น technical, risk management, position sizing, news impact — SET + US stocks (ไม่ใช่คำแนะนำลงทุน)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Packaging Designer — บรรจุภัณฑ์ box/bottle/label, dieline, material selection, print spec, shelf impact, CMYK/RGB color management

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Climate science expert explaining climate systems, climate change, models, and environmental impacts

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluate edtech tools for their real impact on teacher time and administrative burden.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze debt payoff software — avalanche vs snowball strategy engines, interest calculation accuracy, amortization schedules, payment scheduling automation, credit score impact modeling, hardship accommodation workflows, and progress visualization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze project dependencies for health, security, and bloat — audit outdated, deprecated, vulnerable, duplicate, heavy, and unused packages across npm, pip, cargo, go mod, and more. Produce a dependency health score, CVE inventory, license compatibility matrix, bundle size impact assessment, and a prioritized update plan with migration paths.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Four-phase skill for planning and executing large-scale codebase migrations using full-context AI analysis. Produces an impact map, ordered batch plan, subagent execution protocol, and cross-codebase validation pass. Optimized for Fable 5's 1M-token context window.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze agricultural climate risk systems for weather impact modeling, crop insurance, drought/flood prediction, soil moisture, and carbon tracking. Triggers: 'assess crop climate risk', 'evaluate weather yield models', 'review crop insurance integration'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit credit risk modeling software for scoring algorithm accuracy, regulatory compliance (ECOA, FCRA, SR 11-7), bias and disparate impact testing, model governance lifecycle, and explainability..

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when Agentforce run costs are climbing, you need to forecast scale, or you want to reduce tokens per conversation without hurting quality. Covers topic (now subagent) design impact on cost, prompt/template reuse, grounding size discipline, caching, and model-tier selection. Triggers: 'agentforce cost', 'tokens per conversation too high', 'reduce agentforce runs spend', 'forecast agentforce scale cost', 'einstein trust layer tokens'. NOT for capping spend per user with a budget gate and fallback — use agentforce/agent-rate-limit-strategy. NOT for org-wide model-tier and BYOLLM platform strategy — use architect/ai-platform-architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

RecordType ID differences across orgs: dynamic lookup via Schema.SObjectType methods, DeveloperName for stable refs, hard-coded ID anti-patterns, record-type caching, deployment impact. NOT for deciding whether to use record types at all — use admin/record-types-and-page-layouts. NOT for layout/profile explosion at scale — use admin/record-type-strategy-at-scale. NOT for hard-coded Profile, Queue or User IDs in Apex — use apex/apex-hardcoded-id-elimination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating scientific magazine cover style images or prompts, research hero visuals, journal-cover-inspired concepts, academic poster covers, PPT covers, and high-impact scientific visual concepts. If the user asks to generate the image, use ChatGPT image generation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

案件预算和持续的 WIP/偏差监控。在案件设立时构建分阶段费用估算，按法域或工作流运行自下而上预算，计算应急准备金，并构建 AFA 安排（固定费用、上限费用、分阶段固定费用）。持续监控：对照预算的 WIP 跟踪、比例性评估（支出与进度）、带根本原因分析的偏差评述、完成预测、变现率监控、核销分析。触发词：'build a budget'、'fee estimate'、'what will this cost'、'WIP review'、'budget vs actual'、'how are we tracking against budget'、'we're over budget'、'realisation is poor'、'what's our ETC'、'budget for the German workstream'、'model the financial impact of this scope change'、'draft a fee adjustment'、'write-off analysis'、'how much contingency'、'AFA structure'、'fixed fee estimate'、'budget update'、'forecast to complete'。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.