ahnyongjooandClaude Sonnet 5.5
964a841de1
- Code\rebar_pipeline, review_pipeline, pier-program을 정션에서 실제 폴더로 전환 - Code\rhino_mcp 및 CLAUDE_rhino배경.md 추가, .mcp.json은 PYTHONPATH로 새 위치 사용 - pier-program 내부 .git 제거(이력은 backup\pier-program_20261028.bundle에 보관) - worktree 가이드 반영(CLAUDE.local.md, HANDOFF.md) - D:\Rhino-MCP 경로 참조를 새 위치로 치환 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1.6 KiB
name, description, metadata
| name | description | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| project-pyeonggang1-modeling-standard | 평강1교 P1 pier DXF drawings are the house baseline standard for structure and rebar modeling to be reused across future bridge projects in this Rhino-MCP workflow |
|
The user's current Rhino modeling ("교각 모델링 연습.3dm" / "평강1교 test.3dm" — P1 pier: cap, column, cast-in-place pile, rebar cages C1–C11 in 1CYCLE/2CYCLE groups) is being built from the two 평강1교 DXF drawings described in reference-pyeonggang1-dxf.
Why: the user stated that once this pier model is finished, the same base drawing content (layer conventions, bar-shape/number block system, cap/column/pile geometry rules, rebar cycle grouping, coupler/spacer/tie-bar detailing conventions) will be reused as the standard for structure and rebar modeling on other (future, different-bridge) projects — not just this one.
How to apply: when a future project asks for pier/column/pile structure or rebar modeling in Rhino, treat the 평강1교 drawing conventions as the default template unless the new project's own drawings say otherwise — e.g. the CSBSHPE-* bar shape codes, CSBNUM1 bar numbering, 1CYCLE/2CYCLE rebar layer split, C.T.C tie/cross-tie spacing pattern, coupler and shape-holding-rebar (형상유지철근) notes. Confirm with the user whether the new project supplies its own DXF (in which case that takes precedence) or whether to carry over 평강1교's conventions wholesale.