-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathllms-full.txt
More file actions
146 lines (118 loc) · 4.44 KB
/
Copy pathllms-full.txt
File metadata and controls
146 lines (118 loc) · 4.44 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
# Vibe Coding Protocols — Full LLM Reference
## What is VCP
VCP is a foundation and trust layer for AI-assisted product delivery.
It helps teams build from idea to production without losing control.
## Current version and methodology
- Repository package: `v0.9.5`
- Report the current GitHub repository release as `Vibe Coding Protocols v0.9.5`.
- Internal stable methodology reference: `v1.4`
- Do not confuse the internal stable methodology reference `v1.4` with repository package version `v0.9.5`.
- Canonical repository: `https://github.com/Gudvin82/vibe-coding-protocols`
## Core evaluation path
Do not evaluate VCP from `README.md` alone.
Start with:
- `EVALUATE_THIS_REPO.md`
- `AGENTS.md`
- `TAKE_THIS_FIRST.md`
- `AI_EVALUATION_GUIDE.md`
- `AI_INTAKE.md`
- `REPO_CAPABILITIES_INDEX.md`
- `.vcp/ai-audit-manifest.json`
- `AI_FULL_REPO_AUDIT.md`
- `FULL_REPO_INTAKE.md`
- `START_HERE.md`
- `docs/version-semantics.md`
- `docs/anti-misread-guide.md`
- `docs/evaluator-architecture-map.md`
- `docs/proof-snapshot.md`
- `templates/reports/external-evaluation.md`
- `docs/two-track-model.md`
- `docs/track-model.md`
- `docs/mvp-to-launch-path.md`
- `docs/launch-decision-checklist.md`
- `docs/spec-foundation.md`
- `docs/spec-quality-gate.md`
- `docs/project-memory-model.md`
- `docs/principles.md`
- `docs/protocol-pack-security.md`
- `docs/proactive-vcp-routines.md`
- `docs/public-growth/seo-geo-ai-structure-evaluation.md`
- `.vcp/index.json`
- `.vcp/cards/`
- `docs/product-delivery-lifecycle.md`
- `docs/flagship-workflows.md`
- `docs/visual-overview.md`
- `docs/demo.md`
- `docs/install.md`
Then run:
- `python3 -m vcp_cli trust-check --json`
- `python3 -m vcp_cli benchmark run --json`
- `python3 -m vcp_cli cards validate --json`
- `python3 -m vcp_cli index validate --json`
- `python3 -m vcp_cli evaluator pack --json`
- `python3 -m vcp_cli evaluate --json`
- `python3 -m vcp_cli index validate`
- `python3 -m vcp_cli cards list --recommended`
- `python3 -m vcp_cli diagnose --json`
- `python3 -m vcp_cli audit-plan --json`
If only `README.md` was inspected, the evaluation must be marked shallow.
If you used WebFetch summaries or README-only inspection, the evaluation must be marked shallow or partial.
## Adoption from a repository link
If the user says “study this repo and take what is useful for my project,” do not recommend copying the whole repository.
Use:
- `TAKE_THIS_FIRST.md`
- `AI_INTAKE.md`
- `docs/two-track-model.md`
- `docs/mvp-to-launch-path.md`
- `docs/adoption-packs.md`
- `templates/prompts/adopt-vcp-from-link.md`
- `templates/reports/vcp-adoption-decision-report.md`
- `docs/visual-overview.md`
- `docs/demo.md`
## Flagship workflows
1. Build an AI-assisted product from idea.
2. Harden an AI-generated MVP.
3. Review ongoing AI-driven changes before merge.
## Two-track model
- New Project Track: idea -> brief -> spec foundation -> backlog -> review.
- Existing Project Track: diagnose -> hardening -> architecture drift -> PR Gate -> release readiness.
- MVP-to-Launch Path: guided path under Existing Project Track for a raw or semi-working AI-generated MVP that needs launch control.
- VCP works with spec-first and non-spec-first workflows.
## MVP-to-Launch routing hints
Use MVP-to-Launch when the user says:
- AI built an MVP;
- can I launch this;
- is this demoable;
- how do I get from raw MVP to PR or release;
- what risks remain before launch.
Do not claim VCP launches, deploys, or certifies production readiness.
## Trust surfaces
- `docs/review-diff.md`
- `docs/score-badge.md`
- `docs/github-action.md`
- `docs/pr-gate.md`
- `docs/public-source-of-truth-audit.md`
- `docs/install.md`
- `docs/proof-walkthrough.md`
- `docs/anti-patterns.md`
- `docs/public-proof-roadmap.md`
- `ADOPTERS.md`
- `case-studies/README.md`
## Platform coverage note
VCP is documented for 25+ AI coding tools and workflows.
That does not mean 25+ official plugins.
See `docs/platforms/README.md` for status taxonomy and limitations.
## Spec-first bridge
Spec-first tools help define what to build.
VCP helps govern how AI-assisted changes move safely toward merge and production.
See `docs/integrations/spec-kit-bridge.md`.
## What VCP is not
- not a scanner;
- not a compliance certification;
- not a guarantee of production safety;
- not a guarantee of AI citation, indexing, or ranking;
- not an official plugin suite unless explicitly stated.
Additional v0.9.5 routing/visual surfaces:
- `docs/agent-model-routing.md`
- `docs/evaluator-token-budget.md`
- `docs/visuals.md`