Bruce1986/vibe-to-prod-lab

Teaching materials for the afternoon session of the NTU course “From Vibe Coding to Production Architecture”: testing strategies in the AI era, LLM quality validation, and production-quality workflows (template repo, no API key required)

This repository also configures its own agents. See what vibe-to-prod-lab tells them →

2Stars on the repository
8Mods indexed here, across every type
18d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

course-help

01

Bruce1986/vibe-to-prod-lab

Skill Claude Code

A Traditional Chinese guide to a course repository about testing and production architecture, using a bubble-tea ordering bot as its example. It explains the repository map, three labs, and common commands.

not rated 2 18d ago A 43 tokens original MIT

lab1

02

Bruce1986/vibe-to-prod-lab

Skill Claude Code

A Traditional Chinese teaching guide for a software testing lab covering unit, integration, contract, and regression tests. Contract tests check whether data follows an agreed structure.

not rated 2 18d ago A 51 tokens original MIT

lab2

03

Bruce1986/vibe-to-prod-lab

Skill Claude Code

A Traditional Chinese teaching guide for a software lab on golden datasets and prompt regression. A golden dataset is a set of expected examples used to check whether changes still produce acceptable results.

not rated 2 18d ago A 45 tokens original MIT

lab3

04

Bruce1986/vibe-to-prod-lab

Skill Claude Code

A Traditional Chinese teaching guide for a production-quality software lab covering automated delivery, system monitoring, and logs.

not rated 2 18d ago A 50 tokens original MIT

live-eval

05

Bruce1986/vibe-to-prod-lab

Skill Claude Code

A guide for running a real large language model evaluation through GitHub Models and a GitHub Actions workflow. It compares model responses with data-structure rules and expected test cases.

not rated 2 18d ago A 39 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: