signalcraftweb

외부 API, 스키마, 모델명, 컬럼명을 코드에 직접 박기 전에 계약과 런타임을 검증하는 스킬

Use when a route, schema, env var, worker path, or UI surface change can ripple across code, docs, and verification, and you need an explicit impact map before editing.

화면 설계에서 route/API/구조 문서까지 연결하는 범용 스킬

코드 변경 후 어떤 문서를 같이 고쳐야 하는지 change class 기준으로 좁혀주는 점검 스킬

Use before saying work is done, especially after code or document changes, to confirm executed verify commands, changed docs, assumptions, residual risks, and a clear release verdict.

Use when wiring page data fetch/mutation, loading timing, and stale/refresh behavior.

Use when hardening error boundaries, retry paths, and user-visible recovery messages.

Use when implementing field validation, submission states, and post-submit feedback.

E2E QA 시나리오를 그룹으로 나눠 빠르게 검증하는 스킬

새 프로젝트 시작 시 최소 골격과 진입 문서를 빠르게 잠그는 스킬

Use when ending a session or pausing a large task and you need a compact capsule for the next agent or the next day: entrypoint, blockers, unfinished decisions, and first verify command.

Use when a project may have drifted away from its original stack profile and you need a stable, drifting, or reprofile-needed verdict based on boundaries, verification commands, file map, and contract names.

Use when a new request first lands and you need to classify it into planning, implementation, doc-sync, review, impact-map, or subagent-needed, then choose the next skill and whether parallel sub-agents are worth it.

변경 사항을 분석하여 적절한 커밋 메시지를 생성하고, 원격 저장소에 안전하게 푸시합니다.