메뉴
Before non-trivial code — challenge approach, ask unknowns, propose alternatives, list edge cases, get explicit sign-off. Skip only for trivial fixes (typos, renames). Use when the user asks for a feature, refactor, schema change, or anything touching public surface.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | plan-before-code |
| description | Before non-trivial code — challenge approach, ask unknowns, propose alternatives, list edge cases, get explicit sign-off. Skip only for trivial fixes (typos, renames). Use when the user asks for a feature, refactor, schema change, or anything touching public surface. |
Source: CLAUDE.md "Before Writing Code" + multica-ai/andrej-karpathy-skills.
Read first: CLAUDE.md "Before Writing Code" section.
Trivial fixes — just do it:
cargo fix / replace_all).cargo fmt / bun run check produces.Anything else — and especially:
moderation_actions rows or append?" is a real question — pick wrong and you ship a bug.kind + an enum variant — same info, no migration."auth_date.Run through these for any non-trivial change:
i64 everywhere? Negative supergroup IDs (-100…) handled?moderation_actions ledger before acting.SELECT ... FOR UPDATE on the chat row?bot_token, initData, phone, full name, message body? Use RedactedToken.server/assets/captcha/ (forbidden) or adding a new versioned file?.down.sql present? BIGINT NOT NULL for TG IDs? Index on FK columns?auth_date < 24h check? HMAC algorithm matches the surface (WebApp vs Login Widget)?en?Plan. What I'm doing: ... What I'm assuming: ... Open questions: ... Edge cases: ... Alternatives considered: ... Sign off?
Keep it ≤ 15 lines. Long plans are skipped.
verifiable-goal — convert the agreed plan to a check that fails before, passes after.change-impact-assessment — list affected systems before coding.code-review-self — read your own diff before pushing.Bump the patch version in server/Cargo.toml or website/package.json after completing a major change. Use when the user asks to bump/release a version, or when CLAUDE.md's rule about version bumps after major changes applies.
Before a non-trivial change, list affected systems — DB schema, API contract, Telegram handlers, jobs, TS types, docs. Catch ripple effects upfront, not after CI fails. Use when planning a feature, migration, refactor, or any cross-module touch.
Self-review before push — read the diff as a reader, scan for vixen footguns (token leaks, PII, idempotency, captcha asset overwrites), run validation pipeline, no surprise files. Use before "git push", before opening a PR, or when the user says "ready to commit".
Write a git commit message for vixen-rs following the project's Conventional Commits convention. Use when the user asks to commit, create a commit, or write a commit message.
Reproduce → bisect → root cause → fix → verify. Don't speculate, don't "add more error handling" as a guess. Use when something is broken, when a test fails intermittently, when the user says "this isn't working" or "investigate why".
Write small, fast, reproducible Dockerfiles for the vixen-rs server (Rust) and website (bun) using multi-stage builds, cache mounts, distroless/alpine runtime images, and non-root users. Use when editing server/Dockerfile, website/Dockerfile, docker-compose.yml, or when the user asks to shrink an image or speed up a Docker build.