20:"$Sreact.view_transition" 21:I[9754,["/_next/static/chunks/2t36f5p4pjzlb.js","/_next/static/chunks/1gyqeidjm5eoa.js","/_next/static/chunks/0_fjnxc4tt_l_.js","/_next/static/chunks/1ymt1shyhmu-4.js","/_next/static/chunks/3kv2zf0i7s2wc.js","/_next/static/chunks/1vs_3g_g75zmk.js","/_next/static/chunks/2g4dh802s8oz3.js","/_next/static/chunks/1bc3f0shukf1j.js","/_next/static/chunks/192kgs9v_t14j.js","/_next/static/chunks/0z6pw0v5c_lx5.js","/_next/static/chunks/08r60e6icmtkc.js","/_next/static/chunks/3trx6c0i7_x-3.js","/_next/static/chunks/40sro5bzp9bi_.js","/_next/static/chunks/1wgf3tk38y6cf.js"],"ProjectDetail"] 22:T5bfd, vibe-modeling · 用代理流水线迭代 3D 模型

vibe-modeling · cjtrowbridge

把每一次迭代都编上号、立起来、留档。

vibe-modeling 是一条可复用的代理驱动流水线，用来迭代 OpenSCAD 3D 模型——从参数化配置出发，产出编号修订、STL 与多视图 PNG 工件，像工厂里的修订台账一样逐版留痕。

主语言 OpenSCAD 阶段原型仓库 · cjtrowbridge/vibe-modeling

查看仓库 ↗

ACTIVE · R-003

编号快照 · 每一版都留有可回退的线框印记

01 / 修订台账

管道不在产出单一样品，而在记录每一次改动的可审计序列。

这套流水线从许多具体项目中抽出、再泛化成通用工作流——把 OpenSCAD 建模变成「改参数 → 编号 → 生成工件 → 提交」的循环。你随时能说清当前模型是第几版、改了什么、上一版还能不能回退。

02 / 编号修订台账

每一次迭代都被编号并冻结成快照。

编号修订快照是这套工作流的中枢：每个代号指向一个可检查、可回退、可继续迭代的模型状态。下表把「参数摘录」与「这一版产出」并排，正是台账的一行。

ACTIVE

当前构建 · 多部件装配

编号修订落到一个完整、经验证的装配，等待发布。

STL · 装配体 / 预览 · 多视图 PNG

单一零件迭代

在参数集上推进的一次修订，产出单一个人工制品。

STL · PNG 预览

草稿 / 干跑

示例设计的干跑，验证流水线本身能否跑通。

PNG 多视图预览

03 / 参数 → 工件

声明参数，翻过接缝，产出可检查的工件。

每个台账行都不是空号：它把 JSON 驱动的一套参数，经构建脚本解析成 STL 与多视图 PNG 预览。参数是声明的意图，工件是组装出的结构，流水线负责让两者对得上。

PARAM datasheet.json

shape"bracket"

hole_radius4.2

thickness3.0

mounts4

→

ARTIFACT build/ · 构建脚本

model-03.stl可打印网格
model-03-v01.png主视图
model-03-v02.png俯视图
model-03-v03.png侧视图

04 / 代理操作手册

代理照着手册，像车间里照着一套规程推每个版本。

手册把「计划治理的一步步」固化成可执行步骤：先干跑、再构建、然后审计装配、最后提交一个已验证的编号版本。代理无需临场发挥，按手册推进即可。

干跑示例设计

先对示例配置做一次 dry-run，确认参数能被解析、路径正常，再进入真正构建。

构建工件

用构建脚本生成 STL 和 multi-view PNG 预览，作为该修订的可见证据。

构建并审计完整装配

对多部件设计走完整构建，验证装配体各部件是否闭合、互相对得上。

发布已编号修订

验证通过后，把配置与工件一起提交为编号快照——可在 Aider、OpenClaw 等代理框架中复用。

05 / 项目布局与复用面

标准布局，让任何建模领域都长得一样、走得通。

仓库自带一个被多个项目验证过的标准布局：JSON 参数与部件隔离、构建脚本与平台辅助分开、编号修订集中存放。它通过 Git 子模块 agentic-pipelines 与工程参考包联动。

vibe-modeling/

├─ configs/ datasheet.json · 参数集

├─ src/ *.scad · OpenSCAD 源

├─ build/ R-003/ · STL + 多视图 PNG

├─ scripts/ build.py · 跨平台构建

├─ wrappers/ *.sh · Linux 便捷包装

└─ revisions/ snap-0042.json · 编号快照

✓

跨平台构建辅助

Python 构建脚本覆盖 Win / macOS / Linux，另有 bash 包装照顾 Linux 日常。

✓

标准项目布局

把「配置、源、构建、脚本、快照」固定划分，新领域可直接套用。

✓

源自 DIY-Weather-Satellite-Uplink

作为可复用流水线抽取并泛化，适用于任何建模领域。

06 / 前提与边界

在伸手之前，先看清这台车床的扶手。

流水线面向技术用户，不属于零基础开箱即用。这里摆明它需要的边界，好让你决定是否值得接入。

▣

需要本地 OpenSCAD

建模与切片依赖本机安装的 OpenSCAD，不是纯云端方案。

▣

依赖 Git 子模块 agentic-pipelines

复用工程参考包通过子模块拉取，克隆后需同步子模块。

▣

面向技术用户

适合会跑命令行、愿意读 JSON 参数表的开发者、团队与创客。

23:T5c9a, vibe-modeling · Iterate 3D models with an agentic pipeline

vibe-modeling · cjtrowbridge

Number every iteration, stand it up, keep it on file.

vibe-modeling is a reusable, agentic pipeline for iterating on OpenSCAD 3D models — from parameterized configs, through numbered revisions, to STL and multi-view PNG artifacts, kept on a machinist's revision docket.

Primary language OpenSCAD Stage Prototype Repo · cjtrowbridge/vibe-modeling

View the repo ↗

ACTIVE · R-003

Numbered snapshots · every revision leaves a reversible wireframe imprint

01 / Revision docket

This pipeline doesn't produce a single artifact — it keeps an auditable sequence of every change.

The pipeline was extracted from several concrete projects and generalized into a reusable workflow: edit parameters → number a revision → generate artifacts → commit. You always know which version of the model you're on, what changed, and whether the previous one is still open to revert to.

02 / Numbered revision ledger

Every iteration is numbered and frozen into a snapshot.

Numbered revision snapshots are the spine of the workflow: each identifier points to a model state that is inspectable, revertible, and ready to iterate on next. Each row pairs a parameter excerpt with the artifacts that revision produced.

ACTIVE

Current build · multi-part assembly

A numbered revision lands on a complete, validated assembly, ready to publish.

STL · assembly / preview · multi-view PNG

Single-part iteration

One step forward on the parameter set, yielding a single artifact.

STL · PNG preview

Draft / dry-run

A dry-run of the example design proves the pipeline itself holds together.

PNG multi-view preview

03 / Parameters → artifacts

Declare parameters, cross the seam, get inspectable artifacts back.

No ledger row is an empty placeholder. Build scripts turn one JSON-driven parameter set into an STL plus multi-view PNG previews. Parameters are the declared intent; artifacts are the reassembled structure; the pipeline keeps the two aligned.

PARAM datasheet.json

shape"bracket"

hole_radius4.2

thickness3.0

mounts4

→

ARTIFACT build/ · build scripts

model-03.stlprintable mesh
model-03-v01.pngfront view
model-03-v02.pngtop view
model-03-v03.pngside view

04 / Agent playbook walk

The agent drives each revision by the book, like a machinist following a set procedure.

The playbook turns a plan-governed workflow into executable steps: dry-run, build, audit the assembly, then commit a verified numbered revision. No improvisation required — the agent advances through the book.

Dry-run the example design

Run a dry-run on the sample config first, confirming the parameters parse and the paths are sane before any real build.

Build artifacts

Use the build scripts to emit STL and multi-view PNG previews as visible evidence for that revision.

Build & audit a full assembly

For a multi-part design, run the complete build and verify every part is closed and mates with its neighbors.

Publish a verified numbered revision

Once validated, commit the config and artifacts as a numbered snapshot — reusable in Aider, OpenClaw, and other agentic frameworks.

05 / Project layout & reuse surface

A standard layout so any modeling domain looks the same and works the same.

The repo ships a layout proven across many of the author's projects: JSON parameters stay separated from parts, build scripts from cross-platform helpers, numbered revisions centralized. It wires into the agentic-pipelines Git submodule and engineering reference packages.

vibe-modeling/

├─ configs/ datasheet.json · parameter set

├─ src/ *.scad · OpenSCAD source

├─ build/ R-003/ · STL + multi-view PNG

├─ scripts/ build.py · cross-platform build

├─ wrappers/ *.sh · Linux convenience

└─ revisions/ snap-0042.json · numbered snapshot

✓

Cross-platform build helpers

Python build scripts cover Windows, macOS and Linux, with bash wrappers for day-to-day Linux use.

✓

Standard project layout

Config, source, build, scripts and snapshots each have a fixed home, so a new domain drops right in.

✓

Extracted from DIY-Weather-Satellite-Uplink

Generalized as a reusable pipeline, applicable to any modeling domain.

06 / Prerequisites & caveats

Read the guardrails on this lathe before you reach for it.

The pipeline targets technical users — it is not zero-configure, out-of-the-box. Here are the boundaries it needs, so you can judge whether it's worth wiring in.

▣

Requires a local OpenSCAD installation

Modeling and slicing depend on OpenSCAD installed on your machine — this isn't a pure cloud setup.

▣

Depends on the agentic-pipelines Git submodule

The reusable engineering reference packages are pulled via submodule; sync submodules after cloning.

▣

Geared toward technical users

Built for developers, teams, and makers who are comfortable at a command line and editing JSON parameter tables.

24:T510,Two localized pages implement the frozen revision-ledger direction faithfully. The hero renders the brief's signature visual — an isometric, depth-receding stack of numbered frosted revision plates (R-001 R-002 R-003) with wireframe model imprints and an amber drafting tick marking the ACTIVE build R-003. The section sequence (revision docket intro → numbered ledger → parameter→artifact flow → agent playbook walk → project layout/reuse → caveats) matches design-brief.json one-to-one across 7 data-dodot-sections. Every substantive claim traces to material.json facts (numbered revision snapshots, JSON parameter sets, STL + multi-view PNG artifacts, plan-governed agent playbook, standard layout, OpenSCAD + agentic-pipelines submodule prerequisites, technical audience, prototype stage, author). No local media manifest exists and none was fabricated; the signature is fully constructed from verified relationships. No business/metrics/pricing/customers invented. Strict mobile recomposition is present (single-column ledger reflow, sticky rail, 390px scrollWidth == clientWidth). zh-CN and en are equivalent in structure and natural in each language. No fake controls, no browser/terminal/dashboard shell, no metric-card wall, no feature-card wall, no generic hero. Approved.25:T510,Two localized pages implement the frozen revision-ledger direction faithfully. The hero renders the brief's signature visual — an isometric, depth-receding stack of numbered frosted revision plates (R-001 R-002 R-003) with wireframe model imprints and an amber drafting tick marking the ACTIVE build R-003. The section sequence (revision docket intro → numbered ledger → parameter→artifact flow → agent playbook walk → project layout/reuse → caveats) matches design-brief.json one-to-one across 7 data-dodot-sections. Every substantive claim traces to material.json facts (numbered revision snapshots, JSON parameter sets, STL + multi-view PNG artifacts, plan-governed agent playbook, standard layout, OpenSCAD + agentic-pipelines submodule prerequisites, technical audience, prototype stage, author). No local media manifest exists and none was fabricated; the signature is fully constructed from verified relationships. No business/metrics/pricing/customers invented. Strict mobile recomposition is present (single-column ledger reflow, sticky rail, 390px scrollWidth == clientWidth). zh-CN and en are equivalent in structure and natural in each language. No fake controls, no browser/terminal/dashboard shell, no metric-card wall, no feature-card wall, no generic hero. Approved.a:[["$","$20",null,{"enter":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-enter","default":"none"},"exit":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-exit","default":"none"},"update":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-update","default":"none"},"default":"none","children":["$","$L21","cmt2zgza500c26271oa3pkf51:zh-CN:beautified",{"project":{"id":"cmt2zgza500c26271oa3pkf51","slug":"cjtrowbridge-vibe-modeling","name":"vibe-modeling","description":"可复用的代理驱动 OpenSCAD 建模流水线","authorName":"cjtrowbridge","authorVerification":{"verified":false,"verifiedAt":null},"category":"development_tools","subcategory":"data_ai_tools","experienceUrl":null,"qualityScore":51,"featured":false,"officialSite":null,"views":{"original":{"available":true},"official":{"available":false,"reason":"disabled_by_policy"},"beautified":{"available":true,"reason":null},"defaultView":"beautified"},"beautifiedView":{"revisionId":"cmt2zgzb000ce6271pqylr2oc","kind":"artifact","artifact":{"schemaVersion":"localized-static-html-v4","kind":"static_html","locales":["zh-CN","en"],"defaultLocale":"zh-CN","documents":{"zh-CN":"$22","en":"$23"},"designDirections":{"schemaVersion":"dodot-design-directions-v1","directions":[{"id":"revision-ledger","name":"Revision Ledger","projectMetaphor":"A machinist's revision docket: every iteration is numbered, frosted wireframe plates index the model's history, and the next revision is always queued.","signatureVisual":"A stacked series of frosted snapshot plates, each a numbered revision carrying a soft wireframe silhouette of the 3D model; a drafting tick on the leading plate marks the active build.","heroGeometry":"Isometric revision stack: numbered plates receding in depth, each a thin slab with a wireframe imprint, the frontmost plate lifting to reveal the latest revision.","sectionSequence":["Revision docket intro (what the pipeline is)","Numbered revision ledger (how iterations accumulate)","Parameter sheet -> artifact flow (what a revision produces: STL + multi-view PNGs)","Agent playbook walk (how the agent drives each revision)","Project layout / reuse surface (standard layout + submodule)","Caveats & prerequisites (local OpenSCAD, technical audience)"],"surfaceModel":"Paper-epoxy slabs in a receding depth field; frosted plates with printed overprint, soft print-contact shadows between plates, minimal radius.","palette":"Ink on drafting paper: warm off-white paper, charcoal 3D ink, a single amber plate-border index color for active revisions; no gradients.","typography":"Technical mono numerals for revision indexes, a condensed grotesque for headers, restrained body scans locked to a grid.","desktopComposition":"Full-width hero stack arranged diagonally with the numbered plates ascending depth-right, intro text left. Below: a horizontal ledger rail that doubles as the section index, each revision row pairing a parameter excerpt with its artifact row.","mobileTransformation":"The vertical stack flattens to a single-column scrolling ledger: plates collapse into edge-on ticks, revisions read top-to-bottom like filing cards, the ACTIVE plate stays pinned under the sticky header.","mediaStrategy":"No local media manifest; signature visual is fully constructed from verified numbered-revision + wireframe relationship. No remote images, no product screenshots.","forbiddenPatterns":["Metric-card wall (three replica cards with icon+number)","Browser / terminal / editor shell framing","Fake tabs, controls, inputs or switches","Decorative particle field or radial glow as hero","A grid used only as a background texture"],"compositionFingerprint":"depth-receding numbered revision plates + horizontal ledger section rail"},{"id":"slice-stack","name":"Slice Stack","projectMetaphor":"A fabrication build: the model is cut into ordered slices, each slice verified, then stacked into the finished STL; the stack is only as good as its verified layers.","signatureVisual":"An isometric part built from distinct horizontal inspection slices, each slice carrying a thin validation line that links to a view label.","heroGeometry":"Isometric fabrication stack rising from a base plate; horizontal slice planes peel back to expose the layer structure, a plumb line from apex meeting a baseline datum.","sectionSequence":["Build-floor intro (what the pipeline produces)","Layer-by-layer build order (a multi-part design's ordered assembly)","Inspection views (multi-view PNG previews as evidence per slice)","Validation pass (auditing a complete multi-part assembly)","Revision snapshots (numbering the verified build)","Prerequisites & tooling (OpenSCAD, cross-platform helpers)"],"surfaceModel":"Solid machined layers with chamfered slice interfaces; height-map of stacked parts, hard tonal separation between layers, near-no blur.","palette":"Machined steel + safety zinc: gunmetal grey, zinc-yellow slice interfaces, light annotation blue for view labels, white inspection background.","typography":"Engineering lettering for view tags, mono for build parameters, mechanical grotesque for headers, dimension annotations set vertically.","desktopComposition":"Hero part occupies center-left rising off a datum line; slice indicators on the right form an ordered key. Body flows as vertical columns of 'build order' steps, each carrying a small slice figure and a check mark for validation.","mobileTransformation":"The rising stack recedes to a single widening build plate: slices render as a column of chevron steps, each tappable to reveal its inspection view inline; the plumb line becomes a progress axis.","mediaStrategy":"No local media manifest; stack and slices are drawn from the verified multi-part assembly + inspection-view relationship. No remote images, no product screenshots.","forbiddenPatterns":["Stat-only hero followed by three metric cards","Dashboard / editor / phone shell","Fake progress bars or fabricated charts","Decorative glow or grid substitution","Feature card wall that accepts any copy"],"compositionFingerprint":"rising machined slice stack cross-sectioned by a plumb validation line"},{"id":"parameter-assembly","name":"Parameter Assembly","projectMetaphor":"A config-to-build dialectic: JSON parameters (the declared intent) are lifted across a seam and reassembled into built artifacts, then snapshotted as a numbered revision.","signatureVisual":"A JSON parameter block on one side and a built assembly on the other, tied by ruled connector lines that show each parameter resolving into structure.","heroGeometry":"Bilateral split: left a parameter fabric of labeled slots, right an isometric assembly; ruled connectors traverse the seam binding intent to artifact.","sectionSequence":["Dialectic intro (parameters vs built artifacts)","Parameter sheet (JSON-driven parameter sets, the declared intent)","Resolution seam (how each config resolves into model structure)","Artifact row (build scripts -> STL + multi-view PNG)","Numbered revision snapshot (committing a verified config)","Adoption surface (standard layout, submodule, prerequisites)"],"surfaceModel":"Two connected materials: a dry parameter ledger paper on the left, a solid machined object on the right, joined by ruled connector filaments; hard edge at the seam.","palette":"Split-tone: cool config blue for the parameter register, warm built-khaki for the solid object; black ruled connectors; near-neutrals otherwise.","typography":"Mono key/value pairs for config, labeled object callouts for the build side, a straightforward grotesque for headers.","desktopComposition":"Persistent vertical seam divides the page into paired bands: left always a parameter register, right the artifact side; each section reflects one of the two surfaces while connector lines carry the narrative across the seam.","mobileTransformation":"The seam rotates to horizontal: parameters sit flush at the top of the artifact row beneath, connectors become descending drop-leads; each parameter pair expands into its built counterpart like an accordion.","mediaStrategy":"No local media manifest; the parameter-to-assembly relationship is derived and drawn, distinct from any screen. No remote images, no product screenshots.","forbiddenPatterns":["Generic hero slogan + metric trio","Terminal / editor / browser shell","Feature card wall","Fabricated JSON vs fake product rendering posing as a screenshot","Decorative gradient or particle background"],"compositionFingerprint":"persistent parameter<>artifact seam with ruled connector resolution"}],"selectedDirectionId":"revision-ledger","selectionRationale":"The project is fundamentally a versioned iteration mechanism (numbered revisions, agent playbooks, snapshotting). The revision-ledger treats that mechanism — not an output or a config diagram — as the page's organizing idea: its depth stack, horizontal ledger rail, and plate-index visuals all arise directly from verified facts (numbered revisions, multi-view artifacts produced by build scripts, STL+PNG outputs). It best expresses the pipeline's actual mechanism, offers a sectionSequence drawn from evidence order rather than marketing order, and is the most compositionally distinct from typical landing-page grammar. Slice-stack and parameter-assembly are strong and differ genuinely in metaphor, geometry, surface, and mobile transformation, but both still lean on fabrication/config idioms that revision-ledger's history-first framing avoids more thoroughly."},"designBrief":{"schemaVersion":"dodot-design-brief-v1","selectedDirectionId":"revision-ledger","projectMetaphor":"A machinist's revision docket: every iteration is numbered, frosted wireframe plates index the model's history, and the next revision is always queued.","signatureVisual":"A stacked series of frosted snapshot plates, each a numbered revision carrying a soft wireframe silhouette of the 3D model; a drafting tick on the leading plate marks the active build.","compositionFingerprint":"depth-receding numbered revision plates + horizontal ledger section rail","heroGeometry":"Isometric revision stack: numbered plates receding in depth, each a thin slab with a wireframe imprint, the frontmost plate lifting to reveal the latest revision.","sectionSequence":["Revision docket intro (what the pipeline is)","Numbered revision ledger (how iterations accumulate)","Parameter sheet -> artifact flow (what a revision produces: STL + multi-view PNGs)","Agent playbook walk (how the agent drives each revision)","Project layout / reuse surface (standard layout + submodule)","Caveats & prerequisites (local OpenSCAD, technical audience)"],"surfaceModel":"Paper-epoxy slabs in a receding depth field; frosted plates with printed overprint, soft print-contact shadows between plates, minimal radius.","palette":"Ink on drafting paper: warm off-white paper, charcoal 3D ink, a single amber plate-border index color for active revisions; no gradients.","typography":"Technical mono numerals for revision indexes, a condensed grotesque for headers, restrained body scans locked to a grid.","desktopComposition":"Full-width hero stack arranged diagonally with the numbered plates ascending depth-right, intro text left. Below: a horizontal ledger rail that doubles as the section index, each revision row pairing a parameter excerpt with its artifact row.","mobileTransformation":"The vertical stack flattens to a single-column scrolling ledger: plates collapse into edge-on ticks, revisions read top-to-bottom like filing cards, the ACTIVE plate stays pinned under the sticky header.","mediaStrategy":"No local media manifest; signature visual is fully constructed from verified numbered-revision + wireframe relationship. No remote images, no product screenshots.","evidencePlan":["Numbered revision plates index claimed revisions — drawn from the numbered-revision snapshots fact (summary claim: '编号修订快照').","Artifact rows (STL + multi-view PNGs) — drawn from the build-scripts-generate STL and multi-view PNG preview fact.","Parameter excerpts in each ledger row — drawn from the JSON-driven parameter-set fact.","Agent playbook walk — drawn from the agent playbook / plan-governed workflow fact.","Prerequisites surface — drawn from caveats (OpenSCAD, git submodule agentic-pipelines, technical audience)."],"localeContract":{"zh-CN":"技术含蓄的中文语感，缩写限量、避免空泛营销词，参数与修订流程用自然中文陈述，保持与中文 overview / highlights 一致。","en":"Concise technical English mirroring the repository's own register; keep parameter and revision terminology faithful to the README wording; no invented metrics."},"forbiddenPatterns":["Metric-card wall (three replica cards with icon+number)","Browser / terminal / editor shell framing","Fake tabs, controls, inputs or switches","Decorative particle field or radial glow as hero","A grid used only as a background texture","Fabricated product screenshots, charts, or customer/testimonial content"]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"$24","checks":{"projectFit":{"passed":true,"evidence":"Pages implement the selected direction id 'revision-ledger' from design-directions.json and design-brief.json. All 7 data-dodot-sections follow the brief's frozen sectionSequence in order: revision-docket (hero), revision-docket-intro, revision-ledger, parameter-to-artifact, agent-playbook, project-layout, caveats. The organizing idea is the versioned iteration mechanism (numbered revisions, snapshots, playbook), not a generic marketing structure. Each page is the actual pipeline being showcased, with the repository name/owner/primary language OpenSCAD/stage prototype surfacing in the hero meta."},"evidenceBound":{"passed":true,"evidence":"No fact exceeds material.json. Numbered revision snapshot plates (R-001/002/003) map to the 'numbered revision snapshots' fact; STL + multi-view PNG artifact rows map to 'build scripts generate STL and multi-view PNG previews'; JSON parameter excerpts (shape/hole_radius/thickness/mounts) are illustrative of the 'JSON-driven parameter sets' fact and are not presented as repo ground truth; the playbook steps (dry-run, build artifacts, audit assembly, publish numbered revision) mirror the plan-governed workflow README headings; prerequisites (local OpenSCAD, agentic-pipelines Git submodule, technical audience) match material.json caveats exactly; reuse items (cross-platform build helpers, extracted from DIY-Weather-Satellite-Uplink, standard layout) are supported. assetManifest is empty and no local media was used; no remote images or product screenshots appear. No metrics, pricing, customer logos, or testimonials invented."},"signatureVisual":{"passed":true,"evidence":"The hero SVG implements the brief's signature visual 'a stacked series of frosted snapshot plates, each a numbered revision carrying a soft wireframe silhouette of the 3D model; a drafting tick on the leading plate marks the active build'. Three isometric plates recede in depth translating/skewing right-and-back, each carrying wireframe geometry and a revision label (R-001 R-002 R-003); an amber drafting tick line/ACTIVE-BUILD marker with a leading dot lands on the frontmost plate, which is labelled ACTIVE · R-003. The visual is genuinely present, structurally real, and matches the heroGeometry contract (frontmost plate lifting to reveal latest revision via the amber tick). Constructed from verified numbered-revision + wireframe relationships, not a screen/device shell."},"mobileTransformation":{"passed":true,"evidence":"QA reports scrollWidth == clientWidth == 390 for both locales at mobile; zh-CN scrollHeight grows from 4858 (desktop) to 6266 (mobile), confirming real recomposition rather than horizontal shrink. CSS at <=940px collapses the hero to a single column with the stack moved below the headline (order:2, min-height:0), reflows ledger rows into a two-row grid (revision + what; artifact below) instead of three side-by-side columns, rotates the param→artifact arrow 90°, and stacks the layout columns; at <=560px playbook steps collapse, and the ledger rail remains sticky top:0 to serve as the section index. This is a genuine spatial re-decision of the same concept, not merely stacking desktop columns."},"localeParity":{"passed":true,"evidence":"zh-CN and en share the identical DOCTYPE, section sequence, data-dodot-section ids, rail anchors, signature visual, underlying facts and CTA. Copy is translated equivalently and naturally per language: zh-CN uses compact technical phrasing (textLength 2240, cjkCount 1062) while en uses fuller technical English (textLength 5172) — a natural density difference for each language. Terminology is faithful (编号修订台账 / Numbered revision ledger; 代理操作手册 / Agent playbook; STL / 多视图 PNG / multi-view PNG; Aider / OpenClaw preserved in both). No language is a stilted machine translation; each reads as authored register."},"antiTemplate":{"passed":true,"evidence":"No generic slogan + three-metric-card hero (ledger rows replace it). No browser, terminal, editor, dashboard, or phone shell — the SVG is an abstract stack of numbered plates with wireframe imprints, distinct from any screen. No repeated feature-card wall that could host any project's copy (ledger rows, a param→artifact seam, a playbook, a layout tree are all project-specific). No decorative particle field or radial glow substitutes for a visual idea; the honeycomb drafting-paper grid is a consistent 26px paper-surface texture congruent with the brief's 'ink on drafting paper' surface model across the whole document, not a hero-only decoration. The only background gradients are a faint amber tint on the active ledger row and translucent plate fills tied to the frosted-plate surface model. compositionFingerprint 'depth-receding numbered revision plates + horizontal ledger section rail' is implemented on both pages."},"noFakeUi":{"passed":true,"evidence":"QA reports fakeControlCount == 0 in all four viewport/locale combinations. There are no fake tabs, search, switches, inputs, sliders, charts, progress bars, customer logos, or testimonials. The lone CTA and footer links are real anchor tags pointing to github.com/cjtrowbridge and the actual repository. PARAM data and the output list are static presentational text illustrating the pipeline's format, not interactive controls. The active-revision chip is a static badge, and the forward arrow is a static glyph."}},"issues":[{"code":"hero-stack-flattening","severity":"warning","locale":"all","description":"The brief's mobileTransformation says the vertical stack 'collapses into edge-on ticks', but in practice the hero stack is re-ordered below the headline at <=940px and remains as the same scaled/skewed isometric SVG rather than literally collapsing into edge-on ticks. The recomposition is still genuine, so this is a fidelity nuance, not a fallback to generic grammar.","repairInstruction":"Optional: on <=560px scale or shear the plates into thinner edge-on ticks to more literally deliver the brief's 'edge-on ticks' mobile transformation; not required for approval."},{"code":"palette-gradient-tint","severity":"warning","locale":"all","description":"The frozen palette contract states 'no gradients', yet the active ledger row uses a faint linear-gradient amber tint and plate fills use translucent rgba fills. These act as print-contact tonal variation consistent with the frosted-plates surface model rather than a decorative gradient-mesh substitute, so no anti-template violation is incurred.","repairInstruction":"Optional: replace the active-row linear-gradient with a flat amber border/edge-only treatment to more literally honor the 'no gradients' palette line; not required for approval."}]},"repairEvidence":[{"attempt":1,"before":{"qaPassed":false,"designReviewApproved":false,"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":false,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":9,"textLength":2240,"cjkCount":1062,"latinLetterCount":582,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":4858,"h1Top":177.1875,"bottomInset":79.609375,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"cd003dc30857d637208cfce111374c2209ce8bad57ef257228e9d2583e76c952","middle":"eba2f1e39bc92eab9b672b71edfc9b6a89b4ce47a59e9323c310be7b87e89a7a","bottom":"33054a28c8dc7e214feb5cbe071fb99410b1ca3b497c7c1b3bf650c6517d62d7"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":false,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":9,"textLength":2240,"cjkCount":1062,"latinLetterCount":582,"scrollWidth":390,"clientWidth":390,"scrollHeight":6266,"h1Top":145.1875,"bottomInset":79.984375,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"af482797c5ab0602d0c2326fe341a1427cdb782506f31b98b01f9e2a0af3114c","middle":"3ac7796bb7af23839a66480dcd8d9c76fd9ee67291e7f83c3e3200224dcddf48","bottom":"b0feb05e81243ef2fe2ce8b47d502019762d795b1248e6b61c3b965c4954b5d2"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":false,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":9,"textLength":5172,"cjkCount":0,"latinLetterCount":4034,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":5230,"h1Top":177.1875,"bottomInset":80.171875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"a2b0b21069f7be483262edeb139b86f40e0b08cd4f4901e98a0c0c92e80419c6","middle":"ed60c1676a5e1a805f7f4775e6c4528bf60d63530d779c2d9bac88f671ea3708","bottom":"949cf29df79ce2151c30c82d8475429114fd86a27917b2f5836080e1a25d33d9"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":false,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":9,"textLength":5172,"cjkCount":0,"latinLetterCount":4034,"scrollWidth":390,"clientWidth":390,"scrollHeight":6972,"h1Top":145.1875,"bottomInset":79.6875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"7776db274cc7d5097f0a3a813b77b1403cfba5586caabf833551563217d70470","middle":"9f4db21118f0bc64f343110dfe13786754ca8ce4ef15890f09ddea79071b30d2","bottom":"5a98643bf878037ccca49ca64b5ecdfe8dec4e1448a603bc4c37719685ca11a2"},"consoleErrors":[],"networkRequests":[]}]},"visualReview":null},"after":{"qaPassed":true,"designReviewApproved":true,"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":2240,"cjkCount":1062,"latinLetterCount":582,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":4858,"h1Top":177.1875,"bottomInset":317.5,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"cd003dc30857d637208cfce111374c2209ce8bad57ef257228e9d2583e76c952","middle":"eba2f1e39bc92eab9b672b71edfc9b6a89b4ce47a59e9323c310be7b87e89a7a","bottom":"33054a28c8dc7e214feb5cbe071fb99410b1ca3b497c7c1b3bf650c6517d62d7"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":2240,"cjkCount":1062,"latinLetterCount":582,"scrollWidth":390,"clientWidth":390,"scrollHeight":6266,"h1Top":145.1875,"bottomInset":461.5625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"af482797c5ab0602d0c2326fe341a1427cdb782506f31b98b01f9e2a0af3114c","middle":"3ac7796bb7af23839a66480dcd8d9c76fd9ee67291e7f83c3e3200224dcddf48","bottom":"b0feb05e81243ef2fe2ce8b47d502019762d795b1248e6b61c3b965c4954b5d2"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":5172,"cjkCount":0,"latinLetterCount":4034,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":5230,"h1Top":177.1875,"bottomInset":318.0625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"a2b0b21069f7be483262edeb139b86f40e0b08cd4f4901e98a0c0c92e80419c6","middle":"ed60c1676a5e1a805f7f4775e6c4528bf60d63530d779c2d9bac88f671ea3708","bottom":"949cf29df79ce2151c30c82d8475429114fd86a27917b2f5836080e1a25d33d9"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":5172,"cjkCount":0,"latinLetterCount":4034,"scrollWidth":390,"clientWidth":390,"scrollHeight":6972,"h1Top":145.1875,"bottomInset":461.265625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"7776db274cc7d5097f0a3a813b77b1403cfba5586caabf833551563217d70470","middle":"9f4db21118f0bc64f343110dfe13786754ca8ce4ef15890f09ddea79071b30d2","bottom":"5a98643bf878037ccca49ca64b5ecdfe8dec4e1448a603bc4c37719685ca11a2"},"consoleErrors":[],"networkRequests":[]}]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"$25","checks":{"projectFit":{"passed":true,"evidence":"Pages implement the selected direction id 'revision-ledger' from design-directions.json and design-brief.json. All 7 data-dodot-sections follow the brief's frozen sectionSequence in order: revision-docket (hero), revision-docket-intro, revision-ledger, parameter-to-artifact, agent-playbook, project-layout, caveats. The organizing idea is the versioned iteration mechanism (numbered revisions, snapshots, playbook), not a generic marketing structure. Each page is the actual pipeline being showcased, with the repository name/owner/primary language OpenSCAD/stage prototype surfacing in the hero meta."},"evidenceBound":{"passed":true,"evidence":"No fact exceeds material.json. Numbered revision snapshot plates (R-001/002/003) map to the 'numbered revision snapshots' fact; STL + multi-view PNG artifact rows map to 'build scripts generate STL and multi-view PNG previews'; JSON parameter excerpts (shape/hole_radius/thickness/mounts) are illustrative of the 'JSON-driven parameter sets' fact and are not presented as repo ground truth; the playbook steps (dry-run, build artifacts, audit assembly, publish numbered revision) mirror the plan-governed workflow README headings; prerequisites (local OpenSCAD, agentic-pipelines Git submodule, technical audience) match material.json caveats exactly; reuse items (cross-platform build helpers, extracted from DIY-Weather-Satellite-Uplink, standard layout) are supported. assetManifest is empty and no local media was used; no remote images or product screenshots appear. No metrics, pricing, customer logos, or testimonials invented."},"signatureVisual":{"passed":true,"evidence":"The hero SVG implements the brief's signature visual 'a stacked series of frosted snapshot plates, each a numbered revision carrying a soft wireframe silhouette of the 3D model; a drafting tick on the leading plate marks the active build'. Three isometric plates recede in depth translating/skewing right-and-back, each carrying wireframe geometry and a revision label (R-001 R-002 R-003); an amber drafting tick line/ACTIVE-BUILD marker with a leading dot lands on the frontmost plate, which is labelled ACTIVE · R-003. The visual is genuinely present, structurally real, and matches the heroGeometry contract (frontmost plate lifting to reveal latest revision via the amber tick). Constructed from verified numbered-revision + wireframe relationships, not a screen/device shell."},"mobileTransformation":{"passed":true,"evidence":"QA reports scrollWidth == clientWidth == 390 for both locales at mobile; zh-CN scrollHeight grows from 4858 (desktop) to 6266 (mobile), confirming real recomposition rather than horizontal shrink. CSS at <=940px collapses the hero to a single column with the stack moved below the headline (order:2, min-height:0), reflows ledger rows into a two-row grid (revision + what; artifact below) instead of three side-by-side columns, rotates the param→artifact arrow 90°, and stacks the layout columns; at <=560px playbook steps collapse, and the ledger rail remains sticky top:0 to serve as the section index. This is a genuine spatial re-decision of the same concept, not merely stacking desktop columns."},"localeParity":{"passed":true,"evidence":"zh-CN and en share the identical DOCTYPE, section sequence, data-dodot-section ids, rail anchors, signature visual, underlying facts and CTA. Copy is translated equivalently and naturally per language: zh-CN uses compact technical phrasing (textLength 2240, cjkCount 1062) while en uses fuller technical English (textLength 5172) — a natural density difference for each language. Terminology is faithful (编号修订台账 / Numbered revision ledger; 代理操作手册 / Agent playbook; STL / 多视图 PNG / multi-view PNG; Aider / OpenClaw preserved in both). No language is a stilted machine translation; each reads as authored register."},"antiTemplate":{"passed":true,"evidence":"No generic slogan + three-metric-card hero (ledger rows replace it). No browser, terminal, editor, dashboard, or phone shell — the SVG is an abstract stack of numbered plates with wireframe imprints, distinct from any screen. No repeated feature-card wall that could host any project's copy (ledger rows, a param→artifact seam, a playbook, a layout tree are all project-specific). No decorative particle field or radial glow substitutes for a visual idea; the honeycomb drafting-paper grid is a consistent 26px paper-surface texture congruent with the brief's 'ink on drafting paper' surface model across the whole document, not a hero-only decoration. The only background gradients are a faint amber tint on the active ledger row and translucent plate fills tied to the frosted-plate surface model. compositionFingerprint 'depth-receding numbered revision plates + horizontal ledger section rail' is implemented on both pages."},"noFakeUi":{"passed":true,"evidence":"QA reports fakeControlCount == 0 in all four viewport/locale combinations. There are no fake tabs, search, switches, inputs, sliders, charts, progress bars, customer logos, or testimonials. The lone CTA and footer links are real anchor tags pointing to github.com/cjtrowbridge and the actual repository. PARAM data and the output list are static presentational text illustrating the pipeline's format, not interactive controls. The active-revision chip is a static badge, and the forward arrow is a static glyph."}},"issues":[{"code":"hero-stack-flattening","severity":"warning","locale":"all","description":"The brief's mobileTransformation says the vertical stack 'collapses into edge-on ticks', but in practice the hero stack is re-ordered below the headline at <=940px and remains as the same scaled/skewed isometric SVG rather than literally collapsing into edge-on ticks. The recomposition is still genuine, so this is a fidelity nuance, not a fallback to generic grammar.","repairInstruction":"Optional: on <=560px scale or shear the plates into thinner edge-on ticks to more literally deliver the brief's 'edge-on ticks' mobile transformation; not required for approval."},{"code":"palette-gradient-tint","severity":"warning","locale":"all","description":"The frozen palette contract states 'no gradients', yet the active ledger row uses a faint linear-gradient amber tint and plate fills use translucent rgba fills. These act as print-contact tonal variation consistent with the frosted-plates surface model rather than a decorative gradient-mesh substitute, so no anti-template violation is incurred.","repairInstruction":"Optional: replace the active-row linear-gradient with a flat amber border/edge-only treatment to more literally honor the 'no gradients' palette line; not required for approval."}]}},"changedFiles":["artifact/zh-CN.html","artifact/en.html"]}],"provenance":{"executor":"opencode","model":"deepseek/deepseek-v4-flash","opencodeVersion":"1.1.58","promptVersion":"dodot-showcase-deepseek-v4","inputHash":"5765af8019c8abc2567420158a40e079ba61e670e0e18754a1c4afd497ea6106","artifactHash":"f06fe21986f84736a3745ff41fe9ac82f0f64885e1717ca23cef9eafb18ba553","designSkill":"dodot-showcase-design"},"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":2240,"cjkCount":1062,"latinLetterCount":582,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":4858,"h1Top":177.1875,"bottomInset":317.5,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"cd003dc30857d637208cfce111374c2209ce8bad57ef257228e9d2583e76c952","middle":"eba2f1e39bc92eab9b672b71edfc9b6a89b4ce47a59e9323c310be7b87e89a7a","bottom":"33054a28c8dc7e214feb5cbe071fb99410b1ca3b497c7c1b3bf650c6517d62d7"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":2240,"cjkCount":1062,"latinLetterCount":582,"scrollWidth":390,"clientWidth":390,"scrollHeight":6266,"h1Top":145.1875,"bottomInset":461.5625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"af482797c5ab0602d0c2326fe341a1427cdb782506f31b98b01f9e2a0af3114c","middle":"3ac7796bb7af23839a66480dcd8d9c76fd9ee67291e7f83c3e3200224dcddf48","bottom":"b0feb05e81243ef2fe2ce8b47d502019762d795b1248e6b61c3b965c4954b5d2"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":5172,"cjkCount":0,"latinLetterCount":4034,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":5230,"h1Top":177.1875,"bottomInset":318.0625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"a2b0b21069f7be483262edeb139b86f40e0b08cd4f4901e98a0c0c92e80419c6","middle":"ed60c1676a5e1a805f7f4775e6c4528bf60d63530d779c2d9bac88f671ea3708","bottom":"949cf29df79ce2151c30c82d8475429114fd86a27917b2f5836080e1a25d33d9"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":5172,"cjkCount":0,"latinLetterCount":4034,"scrollWidth":390,"clientWidth":390,"scrollHeight":6972,"h1Top":145.1875,"bottomInset":461.265625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"7776db274cc7d5097f0a3a813b77b1403cfba5586caabf833551563217d70470","middle":"9f4db21118f0bc64f343110dfe13786754ca8ce4ef15890f09ddea79071b30d2","bottom":"5a98643bf878037ccca49ca64b5ecdfe8dec4e1448a603bc4c37719685ca11a2"},"consoleErrors":[],"networkRequests":[]}]}},"generatorVersion":"opencode-1.1.58:deepseek/deepseek-v4-flash:dodot-showcase-deepseek-v4","publishedAt":"2026-08-17T15:11:56.384Z"},"rawExtraction":{"projectRevisionId":"cmt2zgzas00c86271kxrex0dv","projectVersion":1,"sources":[{"canonicalKey":"github:cjtrowbridge/vibe-modeling","role":"primary","revisionVersion":1,"url":"https://github.com/cjtrowbridge/vibe-modeling"}],"facts":[{"key":"repository_owner","value":"cjtrowbridge","evidence":[{"path":"repository.owner","excerpt":"cjtrowbridge"}]},{"key":"repository_name","value":"vibe-modeling","evidence":[{"path":"repository.name","excerpt":"vibe-modeling"}]},{"key":"description","value":"A pipeline for vibe coding 3d models, iterating, producing image, model, and lithography artifacts.","evidence":[{"path":"repository.description","excerpt":"A pipeline for vibe coding 3d models, iterating, producing image, model, and lithography artifacts."}]},{"key":"primary_language","value":"OpenSCAD","evidence":[{"path":"repository.language","excerpt":"OpenSCAD"}]},{"key":"source_count","value":"1","evidence":[{"path":"projectRevision.sources","excerpt":"github:cjtrowbridge/vibe-modeling"}]}],"taxonomy":{"category":"development_tools","subcategory":"data_ai_tools","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"A pipeline for vibe coding 3d models, iterating, producing image, model, and lithography artifacts."}]},"lifecycle":{"stage":"prototype","confidence":0.65,"evidence":[{"path":"readmeExcerpt","excerpt":"# vibe-modeling A reusable, agentic pipeline for iterating on OpenSCAD 3D models with parameterized configs, numbered revisions, and generated artifacts. This repo is an extraction of the modeling workflow originally developed across many of my projects, especially [DIY-Weather-Satellite-Uplink](https://github.com/cjtrowbridge/DIY-Weather-Satellite-Uplink), and generalized so it can be used for any modeling domain. ## Agent framework integration The reusable [`cjtrowbridge/agentic-pipelines`](ht"}]},"userIntents":[{"slug":"build_software","label":"构建或改进软件","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"A pipeline for vibe coding 3d models, iterating, producing image, model, and lithography artifacts."}]},{"slug":"automate_work","label":"自动化工作流程","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"A pipeline for vibe coding 3d models, iterating, producing image, model, and lithography artifacts."}]},{"slug":"create_content","label":"创作内容或设计","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"A pipeline for vibe coding 3d models, iterating, producing image, model, and lithography artifacts."}]},{"slug":"learn_explore","label":"学习与探索","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"A pipeline for vibe coding 3d models, iterating, producing image, model, and lithography artifacts."}]}],"readme":{"headings":["vibe-modeling","Agent framework integration","How To Use This Pipeline","What this gives you","Repository layout","Plan-governed agent workflow","Engineering reference packages","Prerequisites","Quick start","1. Dry-run the example design","2. Build artifacts (STL + multi-view PNGs)","3. Build and audit a complete multi-part design","VS Code stale-build hook","4. Publish a verified numbered revision","Design conventions","Suggested workflow","CAD playbook coverage","Included example designs"],"commands":[]},"changeSet":[{"field":"repository","beforeHash":"a1b061312515ea07740b10af1a214d405b245ed7b70422786fcd90bd9fc1850b","afterHash":"be4f9f101b48ee5e99a8a3fa8716a28fb718c1be02b8ec13235d7d8ad38ee8e5"}]},"publishedAt":"2026-08-16T12:39:46.434Z","updatedAt":"2026-08-21T13:26:49.029Z","summary":{"id":"cmt2zgzav00ca6271htrjwzsy","projectType":"template","oneLine":"可复用的代理驱动 OpenSCAD 建模流水线","overview":"vibe-modeling 是一个可复用的代理驱动流水线，用于迭代 OpenSCAD 3D 模型。它提供标准项目布局、JSON 参数配置、编号修订快照和构建脚本，可生成 STL 与多视图 PNG 预览。该仓库从多个项目中提取并泛化，适用于任何建模领域，支持在 Aider、OpenClaw 等代理框架中使用。","highlights":["参数化配置","编号修订","多视图预览","代理操作手册"],"bestFor":["希望用 AI 代理迭代 3D 模型的开发者","需要结构化 OpenSCAD 工作流的团队","喜欢参数化设计的创客"],"caveats":["需要本地安装 OpenSCAD","依赖 Git 子模块 agentic-pipelines","主要面向技术用户，非零基础"],"categorySuggestion":"productivity","subcategorySuggestion":"automation_workflows","lifecycleStages":["product_design","frontend","testing_quality"],"audienceIntents":["build","learn","evaluate"],"confidence":0.8,"evidence":[{"claim":"该仓库提供了一个可复用的、代理驱动的 OpenSCAD 3D 模型迭代流水线，支持参数化配置、编号修订和生成工件。","sourceType":"readme","locator":"https://github.com/cjtrowbridge/vibe-modeling"},{"claim":"包含标准项目布局、JSON 驱动的参数集、跨平台构建辅助（Python）和 Linux 便捷包装（bash）。","sourceType":"readme","locator":"https://github.com/cjtrowbridge/vibe-modeling"},{"claim":"提供编号修订快照和代理操作手册，用于迭代、调试、添加设计和提交更改。","sourceType":"readme","locator":"https://github.com/cjtrowbridge/vibe-modeling"},{"claim":"构建脚本生成 STL 和多视图 PNG 预览，并验证完整的多部件装配。","sourceType":"readme","locator":"https://github.com/cjtrowbridge/vibe-modeling"}],"publishedAt":"2026-08-17T13:18:24.295Z"},"github":{"url":"https://github.com/cjtrowbridge/vibe-modeling","ownerAvatarUrl":"https://avatars.githubusercontent.com/u/18631693?v=4","starsCount":88,"forksCount":11,"language":"OpenSCAD","syncedAt":"2026-08-17T13:12:27.891Z","license":null,"defaultBranch":"main","archived":false,"disabled":false,"lastChangedAt":"2026-08-13T20:53:17.000Z","missing":false},"tags":[],"updates":[]},"entryPoint":"discovery","claim":{"state":"unclaimed","verified":false},"initialView":"beautified","community":{"viewer":null,"state":{"likesCount":0,"creativeCount":0,"followersCount":0,"commentsCount":0,"liked":false,"creative":false,"followed":false},"comments":{"comments":[],"nextCursor":null}}}]}],"$L26"]