'feedback' 검색 결과

Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest "ACTIONABLE_FEEDBACK". Optionally add either or both: --category "CATEGORY" and --subject "SUBJECT". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; when an AI agent repeatedly failed, got stuck, or needed the user to take over an Expo task (report it as an eval candidate); or when the user explicitly asks to enable or disable telemetry (tracking), check its status, or understand what it collects.

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

Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions "microinteraction", "button feedback", "loading state", "toggle design", "animation detail", "state transitions", "input feedback", "the interface feels dead", "make the UI feel responsive", or "add polish to interactions". Also trigger when designing form-validation responses, progress indicators, confirmation dialogs, or any element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

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

Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional feedback loops, clear graduation criteria). Triggers on beta program, alpha test, beta cohort, beta participant, beta feedback, beta to GA decision, design partner, early access program, closed beta, open beta, RC release. Also triggers when a feature is approaching launch and the team needs structured pre-GA validation, when prior betas produced noise rather than signal, or when the team has soft-launched before but wants more structured feedback this time.

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

Analyse existing written feedback for quality, specificity, actionability, and impact on student learning. Use when reviewing teacher or peer feedback to improve feedback practices.

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

Performance scorecard design, post-matter feedback collection, QBR preparation, and firm comparison for in-house legal ops teams evaluating outside counsel. Design a scorecard framework calibrated to your team's maturity level. Produce post-matter feedback forms for supervising attorneys to complete at matter close. Prepare a QBR pack with agenda, data summary, and talking points for structured business reviews. Produce a side-by-side firm comparison for panel decision-making. Trigger on: 'design a performance scorecard', 'how do we evaluate our firms', 'build us a scorecard', 'post-matter feedback form', 'feedback at matter close', 'collect feedback on the firm', 'QBR', 'quarterly business review', 'prep for the firm review', 'what should I raise with the partner', 'compare the firms', 'which firm is performing better', 'rank our panel', 'firm performance data', 'scorecard framework', 'evaluate outside counsel', 'annual firm review', 'how are our firms performing'.

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

Synthesize user feedback from multiple channels and identify patterns to inform product decisions. Use when analyzing feedback, prioritizing feature requests, conducting NPS surveys, or understanding user sentiment. Covers feedback collection, categorization, prioritization frameworks, and closing the feedback loop.

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

Use when the user wants to add an in-site feedback loop to a website repo — a floating "提个建议" button where allowlisted visitors submit suggestions that become a GitHub Issue, which GitHub Actions turns into an automatic code change via Claude Code, auto-merges and deploys, and records on a /_feedback dashboard with one-click revert. Triggers — "给网站加个反馈对话框", "提一句话就自动改网站", "装上反馈闭环", "feedback loop", "/wjs-looping-feedback".

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

Analyse existing written feedback for quality, specificity, actionability, and impact on student learning. Use when reviewing teacher or peer feedback to improve feedback practices.

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

Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.

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

Handle pull request feedback and merge conflicts with focused fixes and validation. Before committing or pushing, run a read-only cross-review, assess its findings against the actual changes, and report checks, decisions, and remaining risks.

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

• Addressing pull request review comments
• Resolving merge conflicts while preserving upstream changes
• Reviewing fixes before committing or pushing

Analyze reviews, surveys, and other user feedback by user group. Summarize satisfaction scores, recurring complaints, positive themes, and the goals users want to achieve, then recommend product improvements based on frequency, severity, and business impact.

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

• Finding recurring themes across large volumes of user feedback
• Comparing satisfaction across user groups
• Prioritizing product improvements from customer complaints

Analyze user feedback and usage data to identify at least three customer groups based on behavior, goals, and unmet needs. Build profiles covering pain points, product fit, and priorities for serving each group.

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

• Finding customer groups within diverse user feedback
• Comparing needs across user groups
• Prioritizing product improvements by customer group

Turn recorded product feedback from screens, voice, or notes into evidence for bug reports and requirements. Handle a single issue quickly or organize a broader evidence set, and guide Riffrec installation, capture, and sharing when no recording exists.

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

• Turning a short recording into a bug report
• Extracting multiple issues and requirements from a walkthrough
• Interpreting product feedback in voice recordings or notes

Switch PUA to offline mode from Codex CLI. This alias updates the offline setting and sets feedback frequency to zero while preserving other configuration fields, then reports the mode change.

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

• Switching PUA to offline mode
• Setting feedback frequency to zero
• Calling the offline command from Codex CLI

Analyze rejected plans and reviewer feedback to identify recurring concerns, changing expectations, and concrete prompt improvements. Produce an HTML dashboard from Plannotator archives, or use Claude Code plan rejection reasons when those archives are unavailable.

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

• Finding recurring reasons for plan rejection
• Understanding how review expectations changed
• Deriving planning instructions from past feedback

Collect Google Maps reviews through BrowserAct using search keywords, language, and country settings. Retrieve reviewer names, ratings, review text, dates, and likes as structured data for reputation research, competitor comparisons, and customer feedback analysis.

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

• Collect reviews for nearby shops and facilities
• Track feedback for a brand location
• Gather competitor reviews for comparison

Collect customer reviews from e-commerce product and review pages, including review text, ratings, dates, verified purchase status, and helpful votes. Gather multiple pages of feedback to prepare data for customer opinion research and sentiment analysis.

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

• Gathering customer feedback for product research
• Preparing review text for sentiment analysis
• Collecting recent or helpful Amazon reviews

Extract details from an open eBay listing into JSON, a structured data format. Collect prices, availability, sales counts, seller feedback, specifications, and image links for product comparisons and catalog checks across regional eBay sites.

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

• Comparing prices and availability across eBay listings
• Checking seller feedback and item locations
• Collecting product identifiers and specifications

Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.

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

Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.

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

Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".

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

Interpret third-party feedback by running parallel internal and peer interpretations to surface intent, correctness concerns, and ambiguities. Use when the user asks to "interpret feedback", "interpret comments", "what does this feedback mean", "clarify reviewer intent", "understand this review", or "interpret these suggestions".

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

Prepare a user-reviewed Arch Studio bug report or feature request for GitHub. Use when the user runs /as:studio-feedback, says "report a bug", "this skill broke", "send feedback", or requests a feature. Do not use for Claude Code's native /feedback command.

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

Design of active analog circuits built around operational amplifiers and discrete gain stages — inverting, non-inverting, difference, and instrumentation topologies, negative feedback and loop stability (gain-bandwidth product, phase margin, compensation), active filters (Sallen-Key, multiple-feedback biquad), sinusoidal and relaxation oscillators, comparators and Schmitt triggers, voltage references (bandgap, shunt, series), and linear versus switching voltage regulators. Covers how to pick a topology, close a feedback loop that stays stable, set gain and bandwidth, and choose a power-conversion approach. Use when designing an amplifier, filter, oscillator, reference, comparator, or regulator, or when reasoning about feedback stability, loop gain, phase margin, or op-amp non-idealities.

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