'improvement' 검색 결과

Facilitate and document Sprint Retrospectives per Scrum Guide 2020. Choose format by team maturity, structure the session, capture action items, and track improvement across sprints. Use after every sprint. Do not use for individual performance reviews, blame sessions, or annual assessments.

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

Analyze CSAT, NPS comments, reviews, and support feedback for sentiment, recurring themes, customer pain, and service improvement actions. Use for customer support and CX feedback reviews.

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

One-line-prompt → cinematic, gorgeous, functional, well-tested, deployed website. Pre-hydrated SPA + full PWA kit + JSON-LD rich snippets + third-party integrations. React 19+Vite default (Angular optional). 100 concrete improvements grouped into 10 categories that EVERY single-prompt site build must satisfy before being marked done. Trigger whenever the user says 'make a website for X', 'build a site for X', 'rebuild X.com', or any equivalent one-liner.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise. This skill should be used when code-quality checks pass but the code would benefit from structural cleanup — deduplication, branching simplification, naming improvements, or dead-code removal. Invoked as a subagent from /code-quality or directly via the Task tool.

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

Provide constructive, evidence-based research mentoring feedback on student manuscripts, proposals, analyses, code, figures, and presentations. Use for advisor-style review that teaches the next improvement without impersonating an advisor or making unsupported scientific judgments.

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

Use when a task needs the judgment of an Emergency Management Director — activating and staffing an EOC for a developing hazard, sequencing a disaster declaration and FEMA Public Assistance/Individual Assistance request, sizing shelter and resource needs against real population and capacity numbers, designing or critiquing a tabletop exercise, or writing an after-action report and improvement plan.

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

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

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

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

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

Identify expansion signals and structure upsell or cross-sell conversations using land-and-expand and Net Revenue Retention principles. Use when user says "upsell", "expansion", "cross-sell", "grow the account", "increase ARR", "find expansion opportunities", "NRR improvement", "upgrade conversation", "add-on", "renewal and expand", or "land and expand" - even if they don't say "expansion discovery" explicitly. Applies to CSMs managing account growth or CS teams building expansion playbooks.

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

Map business processes as-is and to-be. Use when the user says "map the process", "draw the workflow", "BPMN diagram", "process flow", "swimlane", "how does this process work", "document the current process", "redesign this process", "process improvement", "value stream map", "workflow analysis" - even if they don't explicitly say "process mapper".

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

Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.

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

Iterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes.

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

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.

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

Analyze MRO parts inventory systems for field service optimization -- truck stock composition, first-time fix rate improvement, reorder point calculation, safety stock sizing, obsolescence detection, and demand forecasting..

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

Computes development quality and velocity metrics from git history and tracks improvement over time. Measures fix ratios, rework hotspots, test coverage, DORA metrics, and code churn.

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

Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.

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

Full SRS workflow: Brainstorm → Spec → Plan (per-section files) → User Review → SRS Generation → Validation → Improvement Report → Context Save. Use when user provides a project topic and wants a complete requirements pipeline.

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

Full SRS workflow: Brainstorm → Spec → Plan (per-section files) → User Review → SRS Generation → Validation → Improvement Report → Context Save. Use when user provides a project topic and wants a complete requirements pipeline.

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

Phase 8 of the SRS workflow. Generates an improvement report covering deferred features, technical risks, validation warnings, and next-version candidates. No word limit.

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

Phase 8 of the SRS workflow. Generates an improvement report covering deferred features, technical risks, validation warnings, and next-version candidates. No word limit.

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

Drafts a Build-Out Allowance Agreement as a commercial lease addendum governing landlord-provided TI allowance terms. Use when structuring TI allowance financing, negotiating landlord work letters, or documenting tenant improvement funds at lease execution.

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

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

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

Fix a specific bug or problem in a {{engine_name}} project. Supports two modes — immediate fix or plan-first. Without arguments executes existing .unikit/code/FIX_PLAN.md. Checks {{engine_name}} compilation, suggests test coverage, and creates self-improvement patches. Use when user says "fix bug", "debug this", "something is broken", "fix the tests", "fix the errors in the tests", "read the errors in the {{engine_name}} console logs and fix the problems", or pastes an error message or {{engine_name}} console log. Also trigger when user shares a NullReferenceException, MissingReferenceException, compilation error, or any {{engine_name}}-specific error.

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

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

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