Standards Graph¶
This graph shows how VibeCode QA turns upstream framework and platform guidance into judgeable standards. Stack items are leaves. Authored stack rubrics are deployable composition nodes. Authored cross-cutting rubrics are first-class standards that apply across many stack shapes. Reference templates are runnable fixtures that prove the standard in CI. Some stack items are optional composition leaves: they are judged when present, but they do not define the minimum shape of the standard.
The machine-readable source for this map is
/standards/compositions.json.
Authored cross-cutting rubric
First-class rubric applied across stack shapes.
First-class rubric applied across stack shapes.
Planned standard
Cataloged rule surface; full rubric is not published yet.
Cataloged rule surface; full rubric is not published yet.
Stack item leaf
Framework, runtime, tool, protocol, quality, or supply-chain layer.
Framework, runtime, tool, protocol, quality, or supply-chain layer.
Reference template
Runnable repo with CI and a tracked VCQA report.
Runnable repo with CI and a tracked VCQA report.
Generated graph data: graph.json.
Reference Templates
ref-react-spapublished
ref-cloudflare-worker-mcppublished
ref-cloudflare-saaspublished
ref-node-cli-internal-toolpublished
ref-cloudflare-pages-fullstackpublished
ref-cloudflare-d1-apppublished
ref-firebase-react-fullstackexperimental
ref-typescript-sdkpublished
ref-github-action-packagepublished
ref-zensical-kb-siteexperimental
ref-vscode-extension-packageexperimental
ref-tauri-react-desktopexperimental
ref-flutter-firebase-appexperimental
Authored Stack Rubrics
Authored Cross-Cutting Rubrics
securityauthored v1
Secrets handling, input validation, XSS/injection, dependency supply chain.
testingauthored v1
Behavior-focused test strategy, required test layers, coverage risk, CI evidence, and fake/flaky test controls.
typescriptauthored v1
Strict flags, project references, no-any, typed-and-validated boundaries.
Published Aliases
Planned Standards
node-cli-internal-toolplanned
A Node command-line tool used by developers or CI, with stable exit codes, credential resolution, structured output, and noninteractive safety.
typescript-sdkplanned
A TypeScript package or SDK consumed by other code, with export maps, declarations, runtime validation, typed errors, and consumer compatibility checks.
github-action-packageplanned
A packaged GitHub Action with action metadata, minimum permissions, validated inputs, pinned runtime/dependencies, and release tag policy.
vscode-extension-packageplanned
A VS Code extension package with activation scope, workspace trust behavior, command/webview boundaries, marketplace metadata, and extension tests.
tauri-react-desktopplanned
A Tauri desktop application with a React frontend, command/capability boundaries, secure storage posture, packaging, and typed frontend/backend contracts.
zensical-kb-siteplanned
A docs-only knowledge base site published from Markdown with generated site output separated from source, stable URLs, references, and docs smoke checks.
accessibilityplanned
Semantics, keyboard, focus, ARIA, contrast. Applies to any UI-rendering slice.
dependenciesplanned
Lockfile pinning, audit, vetting, no unexpected install scripts.
Stack Item Leaves
Routing
Build Tool
Language
Quality
Security
Testing
Database
State
Protocol
Validation
API Contract
Extension
Automation
Desktop
Documentation
Supply Chain
Backend Platform
Workspace Tool
Reading The Map
- A stack item can feed several standards.
typescript,web-security, andgithub-actionsare intentionally shared across many stack shapes. react-spais both an authored stack rubric and an input tocloudflare-pages-fullstack.security,testing, andtypescriptare authored cross-cutting rubrics, so they are shown separately from deployable stack standards.- Dashed chips are optional/example leaves: they appear in reference templates but only apply to repositories that use that component.
- Reference templates are examples, not vendor-starter replacements. They point to the relevant standard and to a committed VCQA report.
- Planned stack charters are included so the graph shows the pathway, not only what is already published.