Keeps a change scoped to what was asked. Flags extra features, refactors, and 'while we are here' edits, and moves them to a suggestions list instead of the diff. Use when a request is small and the agent is about to expand it, when a PRD grows beyond its problem statement, or when the user says 'just do what I asked'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
The request sets the scope. Everything the diff contains should trace back to a sentence in the ask. Anything else is a suggestion, not a change.
Build what was asked. Not what would be nice, not what a senior engineer would also do, not what the codebase "should" have. If a line of the diff cannot be justified by the request, it does not belong in the diff.
This applies to product scope and to code scope. A PRD that grows past its problem statement has the same disease as a bug fix that ships with a refactor.
Stop when you notice any of these:
Each of these might be a good idea. None of them are in scope unless the user says so.
Suggestions heading, one line eachOut of scope with a one line reasonprds/ folder, append to the relevant PRD's Out of scope sectionSuggestions are cheap to write and free to ignore. Unrequested code costs review time, adds bugs, and blurs what the change was for.
Every feature request has a source: a PM, an exec, a user, a developer scratching an itch, or an AI coding agent. Treat them all the same way. Log the request, weigh it against the current scope, and defer it unless it solves the problem the work was started for.
AI agents are stakeholders now. They have opinions and they push. Common agent driven creep:
If you are the agent, catch yourself doing this and move it to the suggestions list. If you are working with an agent, state the scope at the start of the session and treat its extras like any other stakeholder ask.
Before adding anything, ask:
If the first answer is no, it goes in suggestions.
Request: "Add a deletedAt field to tasks and hide deleted tasks from the list query."
Before, the creeping version:
deletedAt to the schemaby_user_and_deleted indexlist to use the indexsoftDelete, restore, and purgeDeleted mutationslist to listActive and updated three call sitesshowDeleted argument "for the admin view later"After, the scoped version:
deletedAt: v.optional(v.number()) to the schemalist at it so deleted rows never loadSummary sent with the change:
Done: deletedAt field and list query now skips deleted tasks.
Suggestions
- A softDelete mutation to set deletedAt (nothing sets it yet)
- A restore mutation
- A cron to purge rows older than 30 days
- An admin flag on list to include deleted rows
Two lines of diff answered the request. Four lines of suggestions preserved every idea. The user decides what happens next.
A PRD earns each section by pointing back to its problem statement. When a PRD grows:
Out of scope with one reason each.Suggestions in the summary or Out of scope in the PRD아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Routes Convex work to the right builder skill and covers the handful of rules that apply everywhere: validators on every function, withIndex over filter, idempotent mutations, internal functions for scheduling. Use when a task mentions Convex and no more specific skill matches, or as the first stop before picking one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds AI agents on the Convex agent component: threads, messages, tools that call queries and mutations, streaming, RAG with vector search, and workflows for multi step jobs. Use when adding a chat assistant, tool calling agent, or retrieval feature to a Convex app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Production patterns for Convex apps and the rules the @convex-dev/eslint-plugin enforces: validators, indexes, idempotent mutations, avoiding OCC conflicts, thin function wrappers, error handling. Use when reviewing Convex code, asking whether a pattern is right, setting up ESLint, or fixing write conflicts and slow queries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates reusable Convex components with defineComponent, a clean client wrapper, their own schema, and an npm publish setup. Use when extracting a feature into a package, building something for the Convex component directory, or when a component's functions are not showing up in the parent app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Schedules work in Convex: cron jobs in convex/crons.ts, one off scheduled functions with runAfter and runAt, batching large jobs, and cancelling or inspecting the queue. Use when something needs to run on a timer, later, or in the background, or when a cron is not firing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Handles files in Convex: upload URLs, storing blobs from actions, serving with getUrl or an HTTP action, metadata from the _storage table, and deletion. Use when users upload images or documents, when an action fetches a file from a third party, or when a file URL expires unexpectedly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.