vibemafiaclub

Analyze a Claude Code session transcript (.jsonl under ~/.claude/projects) where vspec was used in another repo, then surface prioritized, direction-aligned improvements for this vooster repo's API, CLI, contracts, web, and local sync surfaces. Use when given a session .jsonl path or asked to find vspec dogfood friction from a recorded agent run.

Commit protocol for vspec — when and how to make commits during TDD cycles, the pre-commit regression boundary, Conventional Commits format, push cadence, and open-source hygiene (secrets, .gitignore). Use whenever about to run `git commit`, install the pre-commit hook, push, or stage files in this repo.

Commit protocol for vspec — when and how to make commits during TDD cycles, staged-impact pre-commit checks, full regression before push/merge, Conventional Commits format, push cadence, and open-source hygiene (secrets, .gitignore). Use whenever about to run `git commit`, install the pre-commit hook, push, or stage files in this repo.

Tally API를 사용하여 폼 생성, 폼 목록 조회, 폼 상세 조회, 제출(응답) 데이터 조회, 질문 목록 조회 등을 수행하는 skill. "tally 폼 만들어줘", "폼 목록 보여줘", "설문 응답 조회", "tally form create", "tally submissions", "폼 제출 데이터", "설문 결과" 등 Tally 폼 관련 모든 요청에 이 skill을 사용한다.

코드베이스 전반을 감사해 기술 부채·아키텍처 비직관성·품질 게이트 이슈·코드 퀄리티 이슈·버그를 파악하고, 결과를 docs/findings/ 에 FCG 규약대로 문서화한 뒤 commit & push까지 완수한다. 주기 실행을 전제로 기존 findings와 중복되지 않게 증분 감사한다. 트리거 — "부채 파악", "findings 작성", "코드베이스 감사", "감사 돌려줘", "/findings-audit" 및 유사 의도.

A portable orchestrator that completes a high-level task through 5 stages — clarify → context-gather → plan → implement → verify. Each stage hands off via file artifacts, and a stage is skipped when its artifact already exists. The plan is decomposed into a task graph (DAG); independent nodes run in parallel, dependent nodes run in order.

Prisma 마이그레이션 파일이 포함된 커밋 완료 후 배포 체크리스트를 자동으로 출력한다

Analyze a Claude Code session transcript (a .jsonl under ~/.claude/projects) in which vspec was used in some other repo, and surface prioritized, direction-aligned improvements to THIS project (the vspec CLI). Use when given a session .jsonl path (or asked to find vspec friction / dogfood feedback / "어디를 개선해야 할지" from a recorded agent run).