본문으로 건너뛰기
cccskills
무료GitHub에 공개

help

Think before typing. Root cause first, two candidate fixes, pick one, ask if still unclear, then change only the files the request needs. Edit the confidence bar and scope rules to fit the project. Use when a bug report comes in, when a previous fix did not work, or when the request is vague.

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

연동 도구Vercel
설치 방법 보기

포함된 파일(1)

  • SKILL.md2.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Help

Slow down for thirty seconds before the first edit. It saves an hour later.

Reflect before acting

  1. Why does the current code not do what the user wants? Read it. Do not guess.
  2. What is missing, wrong, or incomplete relative to the request?
  3. List two or three candidate causes.
  4. Pick the most likely one and say why.
  5. If the answer to "what is unclear" is not empty, ask one question and stop.

Never assume. A wrong assumption costs more than a question.

Confidence bar

Do not write code below [98]% confidence in what needs to change. Below that: read more, ask, or propose a plan instead of a diff.

Convex rules

  • Mutations map form fields to document fields one to one. Field names match.
  • Patch without reading when possible. Indexed queries for ownership. Idempotent with early returns. Promise.all for independent writes.
  • Load the matching convex-* skill for anything deeper.

Scope

Change:

  • Files the request needs.
  • The schema, if the request needs it.
  • changelog.md, files.md, task.md after the change lands. Dates from git log --date=short, never invented.

Do not change:

  • UI, layout, colors, or copy that the request did not mention.
  • Existing sections, features, or components. Nothing gets removed without being asked.
  • [Add project specific protected areas: admin dashboard, billing flow, etc.]

UI

Docs policy

Do not create README, CONTRIBUTING, SUMMARY, or USAGE files unless asked. A short summary in the reply is enough.

Git

Load git-safety before any git command that could discard work. Short version: git status first, git diff before discarding, edit files by hand to undo, never reset --hard / checkout -- . / clean -fd / stash drop without the user saying yes to that exact command.

Checklist

Before the first edit:

  • I can name the root cause
  • I considered at least two fixes and picked one for a reason
  • I am at or above the confidence bar
  • I know which files change and which do not
  • Anything unclear has been asked

Before saying done:

  • The fix was verified, not just written
  • Nothing outside the request changed
  • Docs synced if the change was non trivial

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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'.

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

waynesutton/builder-skills4062026년 9월 28일 업데이트

convex

무료

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.

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

waynesutton/builder-skills4062026년 9월 28일 업데이트

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.

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

waynesutton/builder-skills4062026년 9월 28일 업데이트

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.

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

waynesutton/builder-skills4062026년 9월 28일 업데이트

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.

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

waynesutton/builder-skills4062026년 9월 28일 업데이트

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.

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

waynesutton/builder-skills4062026년 9월 28일 업데이트

waynesutton의 스킬 모두 보기

이 스킬의 문제 신고