{ "archive_path": "archive/1790330699.595977", "base_url": "github.com/Moeeryani/Vibe-Coding-Production-Kit", "basename": "Vibe-Coding-Production-Kit", "bookmarked_date": "2026-09-25 10:04", "canonical": { "archive_org_path": "https://web.archive.org/web/github.com/Moeeryani/Vibe-Coding-Production-Kit", "dom_path": "output.html", "favicon_path": "favicon.ico", "git_path": "git/", "google_favicon_path": "https://www.google.com/s2/favicons?domain=github.com", "headers_path": "headers.json", "htmltotext_path": "htmltotext.txt", "index_path": "index.html", "media_path": "media/", "mercury_path": "mercury/content.html", "pdf_path": "output.pdf", "readability_path": "readability/content.html", "screenshot_path": "screenshot.png", "singlefile_path": "singlefile.html", "warc_path": "warc/", "wget_path": "github.com/Moeeryani/Vibe-Coding-Production-Kit.html" }, "domain": "github.com", "extension": "", "hash": "16248R9MWAQKG7N46XK9", "history": { "archive_org": [], "dom": [], "favicon": [ { "cmd": [ "curl", "--silent", "--location", "--compressed", "--max-time", "120", "--output", "favicon.ico", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 ArchiveBox/0.7.4 (+https://github.com/ArchiveBox/ArchiveBox/) curl/curl 8.14.1 (x86_64-pc-linux-gnu)", "https://www.google.com/s2/favicons?domain=github.com" ], "cmd_version": "curl 8.14.1 (x86_64-pc-linux-gnu)", "end_ts": "2026-09-25T10:07:29.156584+00:00", "index_texts": null, "output": "favicon.ico", "pwd": "/data/archive/1790330699.595977", "schema": "ArchiveResult", "start_ts": "2026-09-25T10:07:28.744131+00:00", "status": "succeeded" } ], "git": [], "headers": [ { "cmd": [ "curl", "--silent", "--location", "--compressed", "--head", "--max-time", "120", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 ArchiveBox/0.7.4 (+https://github.com/ArchiveBox/ArchiveBox/) curl/curl 8.14.1 (x86_64-pc-linux-gnu)", "https://github.com/Moeeryani/Vibe-Coding-Production-Kit" ], "cmd_version": "curl 8.14.1 (x86_64-pc-linux-gnu)", "end_ts": "2026-09-25T10:07:29.827695+00:00", "index_texts": null, "output": "headers.json", "pwd": "/data/archive/1790330699.595977", "schema": "ArchiveResult", "start_ts": "2026-09-25T10:07:29.162282+00:00", "status": "succeeded" } ], "htmltotext": [], "media": [], "mercury": [ { "cmd": [ "/app/node_modules/@postlight/parser/cli.js", "https://github.com/Moeeryani/Vibe-Coding-Production-Kit" ], "cmd_version": "1.0.0", "end_ts": "2026-09-25T10:07:44.337279+00:00", "index_texts": null, "output": "mercury", "pwd": "/data/archive/1790330699.595977", "schema": "ArchiveResult", "start_ts": "2026-09-25T10:07:39.218774+00:00", "status": "succeeded" } ], "pdf": [], "readability": [ { "cmd": [ "/app/node_modules/readability-extractor/readability-extractor", "/tmp/tmpugciy5m_", "https://github.com/Moeeryani/Vibe-Coding-Production-Kit" ], "cmd_version": "0.0.11", "end_ts": "2026-09-25T10:07:39.212416+00:00", "index_texts": [ "Vibe Coding Production Kit\n\nBuild with AI like an engineering team \u2014 not like a chat session.\n\n\n\n\nVibe Coding Production Kit (VCP) is a production-minded operating system and zero-runtime-dependency CLI for AI-assisted software development. It turns vague \u201cvibe coding\u201d into a repeatable engineering lifecycle built around specifications, architecture, bounded tasks, repository-native agent rules, readiness gates, security, verification evidence, independent review, safe updates, and recovery.\nIt is model-agnostic and works with tools such as Codex, Claude Code, Cursor, GitHub Copilot, and other coding agents.\n\nArabic documentation: README.ar.md\n\nStart in 60 seconds\nRun the published npm package directly \u2014 no global install required:\nnpx vibe-coding-production init . --agent all --stack auto --yes\nOr target another repository:\nnpx vibe-coding-production init ./my-app --agent claude --stack auto --yes\nPreview without writing:\nnpx vibe-coding-production init . --agent all --stack auto --dry-run\nThe executable is also available as vcp when installed or invoked through npm package tooling.\nIf you intentionally want to run the repository version instead of the published npm package:\nnpx --yes github:Moeeryani/Vibe-Coding-Production-Kit init . --agent all --stack auto --yes\nThe CLI requires Node.js 22+, has no runtime dependencies, and auto-detects JavaScript/Node.js, TypeScript, Python, and Go only when repository evidence supports that decision.\nNew here? Follow the end-to-end 10-minute Quickstart.\nUse VCP through your coding agent\nVCP is intended to be driven primarily by the coding agent rather than by a developer manually filling every template or memorizing every command.\nAfter initialization, you can tell Claude Code, Codex, Cursor, or another compatible agent:\nSet up VCP for this repository. Inspect the existing code, package scripts, tests,\narchitecture, and documentation. Draft the VCP source-of-truth files from repository\nevidence. Distinguish discovered facts from proposed decisions, and ask me only for\ndecisions that require human product or engineering intent. Run VCP Doctor when done.\n\nFor feature work, state the intent normally:\nUse VCP and add verified email change. Draft the task, run the readiness gates,\nask me only for unresolved product decisions, plan before coding, verify the result,\nand perform an independent review.\n\nThe desired split is simple:\nAI does the inspection, drafting, bookkeeping, and VCP command execution.\nHuman makes product/engineering decisions and approves important trade-offs.\nVCP preserves the decisions, gates implementation, and records verification evidence.\n\nWhy this is different\nMost vibe-coding workflows optimize for getting the first demo working. VCP optimizes for the 100th feature, the second developer, production incidents, security reviews, migrations, refactors, upgrades, and years of maintenance.\n\n\n\nCasual vibe coding\nVibe Coding Production Kit\n\n\n\n\nPrompt is the source of truth\nRepository docs are the source of truth\n\n\nLarge \u201cbuild this app\u201d requests\nSmall bounded task contracts\n\n\nAgent starts coding immediately\nReadiness + plan-before-code gates\n\n\n\u201cTests should pass\u201d\nExecuted verification evidence\n\n\nSame agent builds and judges\nIndependent review workflow\n\n\nCopy templates once\nVersioned lifecycle state + safe updates\n\n\nOverwrite/reinstall to upgrade\nBaselines, merge, migrations, rollback\n\n\nHope production is okay\nSecurity, observability, release/recovery thinking\n\n\n\nThe daily workflow\nWhat the developer should experience:\nstate intent\n \u2193\nanswer only unresolved human decisions\n \u2193\nreview / approve plan\n \u2193\nreview final result + evidence\n\nWhat the coding agent executes behind that experience:\ninit / inspect\n \u2193\ntask\n \u2193\nready --stage plan\n \u2193\ncontext --mode plan\n \u2193\nplan\n \u2193\nready --stage implement\n \u2193\ncontext --mode implement\n \u2193\nimplement\n \u2193\nverify\n \u2193\nindependent review\n \u2193\ndoctor\n \u2193\nrelease / observe\n\nWhen a newer VCP version is available:\nupdate --check\n \u2193\nupdate --dry-run\n \u2193\nresolve conflicts if any\n \u2193\nupdate\n \u2193\ndoctor\n\nSafe lifecycle updates \u2014 v0.9\nvcp init now creates .vcp/manifest.json and persistent baseline snapshots. Once a repository is initialized, VCP refuses to replace that lifecycle state with init --force; upgrades go through the update engine.\nCheck version state:\nvcp update . --check\nvcp update . --check --json\nPreview the full migration plan without writing project files:\n\nApply after reviewing the plan:\n\nRecover the newest safe recovery point:\n\nDetach or re-track one VCP-managed file without deleting local content:\nvcp manage ignore AGENTS.md\nvcp manage track AGENTS.md\nThe update engine uses:\n\npersistent baseline hashes and snapshots;\nmanaged, generated, and preserve ownership policies;\nbounded three-way merge for independent edits;\nexplicit CONFLICT instead of guessing on overlaps;\nversioned migration declarations for renames/removals;\nlifecycle locking before planning and mutation;\npath traversal and symlink protections;\ntransaction state, backups, post-apply verification, and automatic rollback;\nconservative rollback semantics instead of pretending partial historical backups are complete snapshots.\n\nSee docs/UPDATES.md for the full contract and docs/CLI.md for commands/options.\nAudit an existing project\nThe read-only doctor checks whether the engineering system is actually configured\u2014not merely copied:\nnpx vibe-coding-production doctor .\nIt reports concrete PASS / WARN / FAIL findings for agent instructions, unresolved verification commands, source-of-truth documents, untouched templates, CI, plan/review workflow, manifest compatibility, baseline integrity, and interrupted update transactions.\nUse --json for automation or --strict to make warnings non-zero. See docs/DOCTOR.md.\nCreate a bounded task before coding\nnpx vibe-coding-production task accept-invite --title \"Accept invitation\"\nThe generator creates docs/tasks/accept-invite.md with source-of-truth links, acceptance criteria, scope boundaries, security/privacy questions, failure modes, observability, tests, rollout/recovery, implementation planning, review checks, and the verification commands actually configured in AGENTS.md.\nThe coding agent should draft and update this task from repository evidence instead of asking the developer to fill every field manually.\nSee docs/TASK-PACKS.md.\nGate readiness before planning and implementation\nvcp ready accept-invite --stage plan\nvcp ready accept-invite --stage implement\nThe planning gate requires a real outcome, resolvable Source of Truth, concrete acceptance criteria, explicit scope, and an unambiguous task structure. The implementation gate additionally requires resolved architecture/data/integration boundaries, domain invariants, security/privacy, failure modes, observability, testing, rollout/recovery, a concrete implementation plan, and an executable verification plan.\nReferenced Source of Truth files that still contain known starter-template signals are reported as warnings so the agent can draft project-specific decisions instead of treating an empty template as evidence.\nSee docs/TASK-READINESS.md.\nBuild the right context for each AI phase\nvcp context accept-invite --mode plan\nUse --mode implement, review, security, or release as the task progresses. Add only affected implementation files with repeatable --include flags. Context packs reject repository escapes and enforce a size budget by default.\nSee docs/CONTEXT-PACKS.md.\nTurn \u201cI ran the tests\u201d into evidence\nPreview exactly what would execute:\n\nExecution requires explicit consent and an implementation-ready task:\nvcp verify accept-invite --run \\\n --output .vcp/evidence/accept-invite.json\nCommands run sequentially and stop after the first failure. Evidence records command, status, exit code, signal, timeout state, and duration, while raw stdout/stderr is deliberately not persisted by default.\nSee docs/VERIFICATION-EVIDENCE.md.\nWorked reference project\nStart with examples/reference-saas-invite/ to see the workflow as concrete engineering artifacts instead of blank templates.\nIt models a security-sensitive multi-tenant invitation vertical slice with completed product/domain/architecture/data artifacts, ADR, threat model, test strategy, bounded task, layered code, and negative-path tests for authorization, tenant boundaries, token hashing, expiry, replay, and email binding.\ncd examples/reference-saas-invite\nnpm test\nnpm run check\nThe example explicitly documents what remains unproven for real production infrastructure instead of calling a demo \u201cproduction-ready.\u201d\nCore principle\nDo not ask AI to build your project. Build a system that makes it difficult for AI to build your project incorrectly.\nThe human owns intent, trade-offs, architecture, risk acceptance, and final decisions. AI helps inspect, draft, research, plan, implement, test, review, document, and automate \u2014 inside explicit constraints.\nThe lifecycle\nIdea\n -> Product brief\n -> PRD + acceptance criteria\n -> User flows\n -> Domain model\n -> Architecture + ADRs\n -> Data model\n -> Threat model\n -> Test strategy\n -> Epics / stories / bounded tasks\n -> Readiness gate\n -> Plan before code\n -> Bounded implementation\n -> Verification evidence\n -> Independent review\n -> CI gates\n -> Release + observability\n -> Safe VCP lifecycle updates\n -> Learn and update the source of truth\n\nWhat you get\n\nAGENTS.md \u2014 repository-wide rules and an AI-first VCP operating protocol for coding agents.\nProduct templates \u2014 product brief, PRD, user flows, acceptance criteria.\nArchitecture templates \u2014 domain model, system design, data model, ADRs.\nSecurity template \u2014 threat modeling before implementation.\nTest strategy \u2014 unit/integration/contract/E2E decision framework.\nDelivery system \u2014 Definition of Ready, Definition of Done, task/release checklists.\nvcp task \u2014 bounded repository-native task contracts.\nvcp ready \u2014 separate plan/implementation readiness gates.\nvcp context \u2014 bounded phase-specific AI context packs.\nvcp verify \u2014 explicit execution and verification evidence.\nvcp doctor \u2014 repository/system health audit without a misleading magic score.\nvcp update \u2014 lifecycle-aware safe updates with merge/migrations/recovery.\nAgent prompts \u2014 discovery, planning, implementation, review, security, refactoring, release review.\nGitHub hygiene \u2014 issue templates, PR template, contributing guide, security policy, validation workflow.\nEnglish README plus an Arabic guide.\n\nEstablish the source of truth\nThese are the main project documents VCP manages:\n\ndocs/product/PRODUCT-BRIEF.md\ndocs/product/PRD.md\ndocs/product/USER-FLOWS.md\ndocs/architecture/DOMAIN.md\ndocs/architecture/ARCHITECTURE.md\ndocs/architecture/DATA-MODEL.md\ndocs/security/THREAT-MODEL.md\ndocs/testing/TEST-STRATEGY.md\n\nDo not treat this as a manual form-filling checklist. Have the coding agent inspect repository evidence and draft these files. The developer should approve or correct decisions that require human intent. AGENTS.md should likewise be populated from proven repository commands where possible; unresolved commands stay explicit instead of being guessed.\nAgent execution loop\n\n \n flowchart LR\n A[Developer states intent] --> B[Agent inspects Source of Truth]\n B --> C[Agent drafts/updates bounded task]\n C --> D[Readiness: plan]\n D --> E[Build plan context]\n E --> F[Plan without editing]\n F --> G{Human decision needed?}\n G -- Yes --> H[Ask focused decision]\n H --> F\n G -- No --> I[Readiness: implement]\n I --> J[Implement bounded scope]\n J --> K[Verification evidence]\n K --> L[Independent review]\n L --> M{Quality gates pass?}\n M -- No --> J\n M -- Yes --> N[Merge / release / observe]\n\n \n \n \n Loading\n\n \n\n\nRepository map\n.\n\u251c\u2500\u2500 AGENTS.md\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 README.ar.md\n\u251c\u2500\u2500 CONTRIBUTING.md\n\u251c\u2500\u2500 SECURITY.md\n\u251c\u2500\u2500 bin/\n\u251c\u2500\u2500 lib/\n\u251c\u2500\u2500 docs/\n\u2502 \u251c\u2500\u2500 00-START-HERE.md\n\u2502 \u251c\u2500\u2500 QUICKSTART.md\n\u2502 \u251c\u2500\u2500 CLI.md\n\u2502 \u251c\u2500\u2500 UPDATES.md\n\u2502 \u251c\u2500\u2500 product/\n\u2502 \u251c\u2500\u2500 architecture/\n\u2502 \u251c\u2500\u2500 security/\n\u2502 \u251c\u2500\u2500 testing/\n\u2502 \u2514\u2500\u2500 delivery/\n\u251c\u2500\u2500 prompts/\n\u251c\u2500\u2500 examples/\n\u251c\u2500\u2500 scripts/\n\u2514\u2500\u2500 .github/\n\nNon-negotiables\n\nSpecs before implementation.\nArchitecture decisions are recorded, not buried in chat history.\nNo large unbounded agent tasks.\nExternal input is validated at trust boundaries.\nAuthorization is server-side and resource-specific.\nSchema changes use reviewed migrations and rollback thinking.\nTests are added with behavior, not postponed to the end.\nThe builder is not the only reviewer.\nCI is the mechanical source of truth when CI is available.\nProduction must be observable and recoverable.\nLifecycle upgrades are planned and reversible; templates are not blindly recopied.\nDo not make the developer write information the agent can reliably discover or draft.\n\nSuggested task size\nA good agent task normally has:\n\none primary outcome;\na narrow set of affected modules;\nexplicit acceptance criteria;\nknown tests;\nno unrelated refactor;\na diff small enough for a human to understand.\n\nIf a task requires a long explanation of \u201cand while you're there\u2026\u201d, split it.\nTool-specific notes\nThe kit intentionally avoids locking you into one AI vendor. Keep universal rules in AGENTS.md, and add tool-specific instruction files only when they provide real value.\nDo not duplicate conflicting rules across multiple agent configuration files. Prefer one source of truth and thin adapters.\nRoadmap\n\n CLI bootstrap with evidence-based JavaScript/TypeScript/Python/Go profiles\n Context-aware task pack generator\n Two-stage task readiness gate\n Phase-specific bounded context packs\n Safe verification evidence workflow\n Read-only doctor audit\n Worked reference vertical slice\n Versioned lifecycle state and safe vcp update\n Three-way merge, migrations, locking, backup, rollback, and manage ignore/track\n Mobile stack profiles\n Monorepo-aware stack/CI profiles\n Security profiles for common application classes\n Git-aware review/release automation\n Prompt evaluation suite for coding agents\n Architecture fitness-function examples\n Extensible community profile/plugin system\n\nSee CONTRIBUTING.md if you want to help.\nLicense\nMIT \u2014 use it in personal, commercial, and open-source projects." ], "output": "readability", "pwd": "/data/archive/1790330699.595977", "schema": "ArchiveResult", "start_ts": "2026-09-25T10:07:35.766317+00:00", "status": "succeeded" } ], "screenshot": [], "singlefile": [], "title": [ { "cmd": [ "curl", "--silent", "--location", "--compressed", "--max-time", "120", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 ArchiveBox/0.7.4 (+https://github.com/ArchiveBox/ArchiveBox/) curl/curl 8.14.1 (x86_64-pc-linux-gnu)", "https://github.com/Moeeryani/Vibe-Coding-Production-Kit" ], "cmd_version": "curl 8.14.1 (x86_64-pc-linux-gnu)", "end_ts": "2026-09-25T10:07:35.761829+00:00", "index_texts": null, "output": "GitHub - Moeeryani/Vibe-Coding-Production-Kit: Production-grade vibe coding framework with specs, architecture, AI agents, testing, security, code review, CI/CD, and battle-tested workflows \u2014 from idea to production. \u00b7 GitHub", "pwd": "/data/archive/1790330699.595977", "schema": "ArchiveResult", "start_ts": "2026-09-25T10:07:35.681831+00:00", "status": "succeeded" } ], "wget": [ { "cmd": [ "wget", "--no-verbose", "--adjust-extension", "--convert-links", "--force-directories", "--span-hosts", "--no-parent", "-e", "robots=off", "--reject=js,mjs,woff,woff2,ttf,otf,eot,mp4,m4v,mov,webm,ogv,mkv,avi,flv", "--timeout=120", "--restrict-file-names=windows", "--page-requisites", "--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 ArchiveBox/0.7.4 (+https://github.com/ArchiveBox/ArchiveBox/) wget/GNU Wget 1.21.3", "--compression=auto", "--timestamping", "https://github.com/Moeeryani/Vibe-Coding-Production-Kit" ], "cmd_version": "GNU Wget 1.21.3", "end_ts": "2026-09-25T10:07:35.676170+00:00", "index_texts": null, "output": "github.com/Moeeryani/Vibe-Coding-Production-Kit.html", "pwd": "/data/archive/1790330699.595977", "schema": "ArchiveResult", "start_ts": "2026-09-25T10:07:29.834494+00:00", "status": "succeeded" } ] }, "icons": null, "is_archived": true, "is_static": false, "latest": { "archive_org": null, "dom": null, "favicon": "favicon.ico", "git": null, "media": null, "pdf": null, "screenshot": null, "singlefile": null, "title": "GitHub - Moeeryani/Vibe-Coding-Production-Kit: Production-grade vibe coding framework with specs, architecture, AI agents, testing, security, code review, CI/CD, and battle-tested workflows \u2014 from idea to production. \u00b7 GitHub", "warc": null, "wget": "github.com/Moeeryani/Vibe-Coding-Production-Kit.html" }, "link_dir": "/data/archive/1790330699.595977", "newest_archive_date": "2026-09-25T10:07:39.218774+00:00", "num_failures": 0, "num_outputs": 6, "oldest_archive_date": "2026-09-25T10:07:28.744131+00:00", "path": "/Moeeryani/Vibe-Coding-Production-Kit", "schema": "Link", "scheme": "https", "snapshot_id": "5976e621-18b7-4899-97a1-d917ebc62f18", "sources": [ "/data/sources/1790330699-import.txt" ], "tags": null, "tags_str": "", "timestamp": "1790330699.595977", "title": "GitHub - Moeeryani/Vibe-Coding-Production-Kit: Production-grade vibe coding framework with specs, architecture, AI agents, testing, security, code review, CI/CD, and battle-tested workflows \u2014 from idea to production. \u00b7 GitHub", "updated": "2026-09-25T10:07:28.743830+00:00", "updated_date": "2026-09-25 10:07", "url": "https://github.com/Moeeryani/Vibe-Coding-Production-Kit" }