스킬 찾기

Audit saved project learnings against the current codebase to find outdated explanations, overlapping documents, and contradictions. Maintain the documentation with evidence-based updates, consolidation, replacement, or deletion, and deliver a per-document report with committed changes when applicable.

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

• Checking saved learnings against current code
• Consolidating overlapping knowledge documents
• Correcting outdated paths and links

Document a solved and verified problem when its reasoning is missing from code, tests, and existing documentation. Save one durable lesson in the repository so future agents can find it and avoid repeating substantial investigation.

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

• Recording reasoning behind a verified fix
• Preserving lessons to prevent recurring mistakes
• Updating a lesson that has become inaccurate

Create a handoff that captures work context and relevant references for another agent or session. Read an existing continuity document to explain the current situation and recommend next steps for the user to confirm.

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

• Handing ongoing work to another agent
• Saving context before starting a new session
• Resuming from a selected handoff document

Turn a vague feature idea into clear requirements through dialogue. Define what to build, its scope, and success criteria, then capture the result in a short chat summary or a requirements document ready for implementation planning.

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

• Clarifying a vague feature idea
• Narrowing the scope of an ambitious improvement
• Documenting requirements before implementation planning

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

Carry a request through the appropriate Compound Engineering skills with minimal intervention. For code changes, the workflow covers planning, implementation, review, browser testing, and an open pull request with automated check results assessed.

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

• Taking a feature request through to an open pull request
• Diagnosing a bug and preparing the fix for review
• Implementing an existing plan through delivery

Review and simplify code while preserving its behavior. Check readability, reuse, and efficiency, assess whether tests and comments add value, and verify applied changes with the project's configured checks before review.

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

• Cleaning up code after implementation
• Improving readability before code review
• Auditing tests for practical value

Develop independent solutions to a defined problem, compare them against shared requirements, and combine useful contributions into a coherent recommendation. An independent assessment and evidence checks support the selection, while unresolved tradeoffs and verification needs remain explicit.

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

• Comparing concrete solutions to a defined problem
• Developing rough options before choosing an approach
• Comparing architectural or product proposals

Retune a collection of skills for a new model using archived runs and controlled comparisons. Establish normal measurement variation, register success criteria before editing, and make targeted changes until measured behavior meets the criteria or a specific limitation is reported.

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

• Investigating skill regressions after switching models
• Measuring the effect of instruction changes
• Separating behavior improvements from normal run variation

Generate improvement ideas grounded in the project or topic, critique every candidate, and rank the survivors with explanations. Produce a document that helps users choose which ideas deserve further exploration before defining requirements.

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

• Finding improvement ideas based on the current project
• Exploring unexpected directions for a topic
• Comparing candidates and understanding rejection reasons

Monitor an open GitHub pull request over time, respond to review feedback, and address automated check failures. Apply and push fixes, then report whether it appears ready to merge or what still blocks progress.

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

• Monitoring a pull request until it appears ready to merge
• Addressing review feedback as it arrives
• Handling automated check failures during review

Review code changes or a pull request for bugs, effects on existing behavior, test gaps, and project standards. Receive findings supported by the code and a clear account of review coverage, with local fixes available when explicitly requested.

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

• Reviewing a pull request before release
• Checking changes for bugs and test gaps
• Applying review findings locally

Review an existing requirements document, plan, or specification from several role-based perspectives. Identify inconsistencies and obstacles to carrying out the work, verify their consequences, apply authorized corrections, and present improvements or decisions that still need attention.

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

• Checking a requirements document for inconsistencies
• Reviewing whether an implementation plan is feasible
• Organizing decisions left open in a specification

Draft announcements for a shipped feature, explaining what users can now do and why it matters. Produce copy-ready text tailored to channels such as X, LinkedIn, email, release notes, blogs, or demo scripts.

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

• Announcing a new feature on X
• Writing a concise release note
• Preparing LinkedIn posts and announcement emails

Set up a separate Git working directory for a new task or an existing branch, pull request, or commit. Detect and reuse existing isolation, prefer the agent environment's worktree tools, and report the working path and branch.

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

• Starting a feature in a separate working directory
• Isolating an existing branch or commit
• Preparing a separate workspace for pull request review

Share Markdown specs, plans, and drafts through Proof, a collaborative document editor. Read shared documents, add comments or tracked suggestions, edit text, and pull documents into local files, with confirmation of each requested operation.

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

• Sharing a Markdown plan through a Proof link
• Commenting on a shared specification
• Suggesting or applying changes to a draft

Refine a working feature through browser feedback from the user. Collect observations through typed comments or live speech and drawing, apply focused usability fixes, and save the changes in local commits.

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

• Refining usability before release
• Adjusting a page while checking the changes
• Giving feedback through speech and on-page drawing

Explain how something works, why it took its current form, or what happened during a period of work. Use supporting evidence, distinguish documented reasons from inference, and adapt the answer or document to its readers.

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

• Understand how an existing feature works
• Learn the reasons behind a design or change
• Recap work completed during a specific period

Gather usage, performance, and error data from configured sources for a chosen time window. Produce a compact, saved product report with followup actions, and show its headlines in chat to support regular reviews of product activity.

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

• Reviewing product usage and errors over the past 24 hours
• Checking product activity during a launch window
• Saving weekly reports to track changes over time

Test user journeys affected by a branch’s changes in a real browser. Check correctness and the experience for intended users, fix small defects with regression tests, and commit fixes alongside a report documenting results and unresolved decisions.

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

• Check user-facing changes before a PR is merged
• Test complete user journeys affected by a branch
• Fix small defects and add regression tests

Build a disposable prototype to test how a product should work, feel, or look before committing to an approach. Let the user experience it, record their choices, and carry those decisions into requirements or further planning.

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

• Trying a navigation flow before committing to it
• Judging layout density and color choices
• Resolving design questions that sketches cannot answer

Create or update STRATEGY.md through guided questions about a product’s purpose, users, success metrics, and investment areas. Capture a shared basis for product decisions, with draft review and focused updates to existing documents.

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

• Define product strategy at launch
• Review strategy after a change in direction
• Clarify target users and success metrics

Save working changes as local Git commits with messages that explain the outcome. Follow the project's commit style, select files explicitly, and split clearly separate changes into a few logical commits when appropriate.

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

• Saving completed work as a local commit
• Writing messages that explain the outcome
• Separating unrelated changes into commits

Improve a measurable target in a working system by tracing workload costs or scoring alternative implementations. Compare results against a baseline, keep confirmed improvements on a dedicated branch, and record experiments for review or resumption.

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

• Investigating the cost of a specific workload
• Comparing implementations against a measurable target
• Running improvement experiments within time and spending limits