BC Vibe Coding Coach
AI-powered vibe coding workflow coach — master the art of AI-assisted software development in 2026. Build full apps by describing them in plain language using Cursor, Claude Code, Bolt.new, Replit, and Lovable. Learn the vibe coding mindset, prompt patterns, workflow architecture, debugging strategies, and how to ship from idea to production without getting stuck. Covers project scaffolding, iterative refinement, multi-file context management, and common failure patterns. Built for non-engineers, startup founders, product managers, and developers transitioning to AI-first workflows. Keywords: vibe coding, AI coding, Cursor, Claude Code, Bolt.new, no-code AI, app builder, AI-assisted development, prompt-to-code, Replit, Lovable, AI workflow.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (Vibe Coding Coach) differs from the folder (vibe-coding-coach)
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 63 steps
- 100Execution cost. Instruction body is 1816 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 750: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 63 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.