Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Vibe Coding Production (Demo → Real System)

A gated 5-step launch checklist — dev conventions, security baseline, deployment, manual acceptance, docs — for turning a working demo into a system other people can rely on.

Dev & CodingIntermediate★ 169⑂ 1AI score 9/10Last updated: Jun 30, 2026

What it does

  • Triggers on phrases like "I want to go live", "how do I deploy this", "turn this demo into a real product", "do I need to worry about security", or when you're about to open-source code.
  • Runs the launch stage as S3.1 dev conventions → S3.2 security baseline → S3.3 deployment → S3.4 acceptance testing → S3.5 docs (optional), each with an explicit exit gate written back to a progress ledger.
  • Gives copy-paste prompts for Git branching, structured logging ([time] [level] [module] message), explicit error handling, and comment style.
  • Walks an 8-item security table: auth on every endpoint, brute-force lockout, input validation/sanitization, HTTPS, secrets via env vars, log masking, least-privilege DB users, non-leaky error responses.
  • Warns about secrets in code and commit history before publishing publicly, and recommends .gitignore handling plus immediate key rotation if leaked.
  • Produces a checkbox acceptance list in "I do X, I should see Y" form so a non-coder can verify by hand instead of trusting the AI's word.

Who it's for

  • Non-developers or solo builders shipping an AI-built project to a server or the public internet
  • Anyone unsure what they've forgotten about security and deployment
  • Maintainers doing a final sweep before open-sourcing a repo

Examples

  1. "Deploy this chatbot so my team can use it" → confirm the 8 security items, then get a deployment runbook covering dependencies, config location, startup, autostart, logs, and version rollover.
  2. "I'm about to make this repo public" → guided audit of code, config, and commit history for keys/tokens, with rotate-now guidance.
  3. "How should I test my project?" → a verifiable checklist covering happy path, failure cases (bad input, timeouts), and edge cases (empty/extreme values).

Note: the skill text is written in Chinese and expects sibling skills (requirements, architecture, survival, harness) plus docs/ ledger files from the same kit.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/Junliu1066/vibe-coding-kit/HEAD/skills/vibe-coding-production/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/vibe-coding-production folder from the GitHub repo Junliu1066/vibe-coding-kit into my ~/.claude/skills/vibe-coding-production/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/Junliu1066/vibe-coding-kit.git /tmp/vibe-coding-kit && mkdir -p ~/.claude/skills && cp -r /tmp/vibe-coding-kit/skills/* ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repo: git clone https://github.com/Junliu1066/vibe-coding-kit.git
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the skills in: cp -r vibe-coding-kit/skills/* ~/.claude/skills/ (installing the whole kit is recommended, since this skill references the other stages).
  5. In your project, add docs/进度账本.md (progress ledger) and a project spec file based on the templates in the repo's examples/ folder so the gate bookkeeping works.
  6. Restart Claude Code and say "I want to take this demo to production" to confirm the skill loads.
  7. Optional: ask Claude to respond in English while following the Chinese instructions.
View source on GitHub ↗License: MIT