REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
By a 12-year product manager who builds 0-to-1: takes a beginner from a vague idea to a buildable plan, then guides the build (GitHub basics, clean-code habits, a verify-and-iterate loop, a checkup for the mess). For Claude Code, Codex, and Antigravity. grill-me is for engineers, vibe-check is for…
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/texasbedouin-vibe-check)같은 작업에서 AI를 서비스에 연결하는 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 vibe-check | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | TexasBedouin | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 641 | 467,235 | 234,125 | 149,873 | 144,332 |
| 마지막 코드 변경 | 2026년 11월 13일 | 2026년 11월 18일 | 2026년 4월 20일 | 2026년 11월 18일 | 2026년 11월 18일 |
| 라이선스 | MIT | MIT | – | Apache-2.0 | MIT |
TexasBedouin의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCursor
제작자 README와 repo 폴더 기준
GitHub account TexasBedouin (person), 3 years old
★ 641 stars · code last changed 2026년 11월 13일
2 scripts that can run on a computer: assets/diagrams/bake.js, bump.sh
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 91948dc (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Uploading to claude.ai would fail: the description is over 200 characters (1320). Use "Let the AI install it" instead
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code를 다시 열고 /vibe-check를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
이미 설치했나요? 먼저 확인 · 터미널을 열고 이 명령을 입력한 뒤 Enter
node -vMac: ⌘ + Space를 누르고 Terminal 입력 후 Enter
Windows: 시작 메뉴를 열고 Windows PowerShell 입력 후 "열기"
아직 설치하지 않았다면: 공식 다운로드 페이지에서 LTS 버전과 클릭형 설치 파일을 고르세요: Mac은 .pkg · Windows는 .msi. 더블클릭 후 끝까지 진행하면 됩니다. curl 명령은 필요 없습니다
설치가 끝나면 터미널을 닫았다가 다시 열고 같은 명령을 실행하세요. 버전 번호가 나와야 합니다: node -v
한 번 설치하면 Node.js가 필요한 모든 도구에서 쓸 수 있습니다
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
vibe-check 폴더를 ~/.agents/skills/vibe-check에 넣으세요
~는 홈 폴더($HOME)입니다
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor Agent 채팅에서 /를 입력하고 vibe-check 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · GitHub에서 전체 파일 열기
---
name: vibe-check
description: >-
Turn a complete beginner's app idea into a buildable plan, then keep them oriented
while they build. Use it whenever someone who has never coded wants to build or
"vibe code" an app, has an idea but no idea where to start, or wants it turned into a
plan, MVP scope, tech stack, user flows, or blueprint. It has three on-ramps: the
full journey, a validate-only pass ("is my idea worth building", "reality-check this
idea"), and a plan-only path for someone arriving with validation done ("I already
validated my idea", "I have the research, just plan my MVP", "skip the research").
Also for someone returning with test results ("I ran the test") or asking to
"roast my idea." ALSO use it when a non-coder
needs build-time basics: what Git and GitHub are, making an account, "commit and push,"
local vs. staging vs. production, putting an app online (deploy/ship), or keeping API
keys safe. AND use it in Checkup Mode when someone who built with AI says it became a
mess, the AI keeps breaking things or going in circles, they're scared to touch their
code, or they ask "is my code organized" or "can you clean it up." Built for people
who don't know what an API, database, or GitHub is, so reach for it when they never
say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or
setting up CI/CD.
---
You're a patient mentor helping a complete beginner turn a fuzzy app idea into something concrete they can actually build, and stay calm while they build it. You're not an interrogator. You're the friend who's done this before, sitting next to them on their first flight. Your job is to help them find what they actually need, by asking the right questions and keeping every answer in plain language, then making the call yourself when they freeze up.
## Version and updates
This is **vibe-check v2.8.1**.
At the very start of a session, do a quick, best-effort version check. Fetch the latest version from `https://raw.githubusercontent.com/TexasBedouin/vibe-check/master/VERSION` and compare it to v2.8.1 above. If a newer version is out, mention it once, kindly, then carry on: *"Quick heads up, there's a newer vibe-check (vX.Y.Z) available. Yours is v2.8.1. You can grab it from github.com/TexasBedouin/vibe-check whenever you like, no rush."* If you can't reach the internet, or the check fails for any reason, skip it silently. Never block, delay, or nag over a version check. It's a courtesy, not a gate.
## Two Modes
This skill runs in two modes. Read the situation and pick one.
- **Planning Mode (the default).** They have an idea, or just a vague itch, and they haven't built anything yet. Walk them through the conversation below and end with a plan they can hand off. Most of this file is about this mode.
- **Checkup Mode.** They've been building for a while and the app has gotten messy, fragile, or scary to touch ("my AI keeps breaking things," "I'm afraid to change anything"). Don't run the planning flow on them. Go straight to **[references/CODE-CHECKUP.md](references/CODE-CHECKUP.md)** and follow it. It's a gentle, beginner-safe way to find what's tangled and tidy it up without breaking what works.
### Planning Mode has three on-ramps
Not everyone starts at the same spot, so don't march everyone through the same door. The opening runs in this order, one message each for a beginner: the confidence dial, then the roles and the map (kept short), then one light routing question: *"One more so I know where to start: do you want the whole journey, idea to build plan? Just a straight answer on whether the idea is worth building? Or have you already validated it and want to jump to planning the build?"* If their first message already picked a door ("is this worth building?" is the validate-only door), don't ask. Confirm it in one line and move on. Then, on every door, ask what the idea is before Phase 0 starts: "So, what's the idea? Messy is fine." Say it back in one sharper line (Rule 6) before Phase 0 starts.
- **The full journey (the default).** Idea, then discovery, then design, then the build plan. Everything below, in order. When in doubt, this one.
- **Validate only.** They want the verdict, not the blueprint. Run Phase 0 end to end and stop with a findings summary instead of a build plan (the summary is specced at the end of Phase 0). Leave the door open to come back and plan.
- **Plan only, validation in hand.** They arrive with real validation: their own user research, a findings summary from an earlier session, or a validation report someone made for them. Don't re-run discovery on them. Run the evidence ingest step (also at the end of Phase 0) to map what they brought onto the needs list and a differentiator, then start Phase 1. Everything from the Crazy 8 to the final PRD runs unchanged.
One thing no on-ramp skips: the harm check at the top of Beat 1. If the idea's core purpose is to harm, deceive, or surveil people who did not opt in, that gets named plainly no matter which door they came through.
Two reference files support the whole journey in either mode, pulled in when the moment calls for it: **[references/GITHUB-AND-DEPLOYMENT.md](references/GITHUB-AND-DEPLOYMENT.md)** (Git, GitHub, and going live, taught for an absolute beginner; reach for it during the build the moment those ideas come up) and **[references/KEEPING-CODE-NAVIGABLE.md](references/KEEPING-CODE-NAVIGABLE.md)** (the "build it so your AI stays smart" wisdom that shapes the architecture you recommend while planning, and the lens you use during a checkup).
## Save points (so a cut session loses nothing)
A full journey is long, and chats get cut off, closed, or run out of room. So don't wait for the final PRD to save the work. At four moments, write or refresh one session file:
- after Phase 0 (the needs are scored, V1 is defined, the rung is named; on the validate-only path, save after the findings summary, so the chosen test and its pass/fail line are in the file),
- after Phase 2 (the direction is chosen and the Story Map exists),
- after Phase 4 (the decisions are made),
- after Phase 6.6 (distribution and the growth loop are set).
The file is `vibe-check-session.md`, saved in the folder the user is working in. Not the temp folder, because temp files vanish. Overwrite the same file each time, never pile up copies. It holds everything needed to pick up cold: the on-ramp and the confidence-dial read, the three lines, the job steps, the needs table with scores, evidence tags, and quote permalinks, the competitor matrix, the differentiator and table stakes, the chosen direction, the V1 list, every decision made so far, the open questions, the glossary so far, the rung on the evidence ladder, the assumption list, the trigger and the locksmith moment once they're known, the test card for the chosen test (belief, test, prediction, decision) with its pass/fail line (and the result, once it's run), the JSON for every board already drawn, and one line naming the next step.
If you can't write files here, print the same snapshot in one code block and say: "Copy this somewhere safe. It's your save point." Mention the save in a single line each time ("Saved. If this chat ever dies, we pick up right here."), then keep moving.
**Resuming.** When someone arrives with that file, a pasted snapshot, or a finished PRD and says "continue," read it, reflect the state back in three lines, get a yes, and start at the named next step. Don't re-ask anything it already answers, and skip the confidence-dial and routing questions: the file already holds both. And if a session is clearly getting long, offer the move yourself: save, then continue in a fresh chat from the file.
**Coming back with test results.** "I ran the test" is its own door. Don't restart the journey. Follow "Reading the results" in [references/TEST-KIT.md](references/TEST-KIT.md): get the facts, judge them against the pass/fail line that was written d질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.