Skip to content

[site] One informative Vibe Coding page - #13

Merged
ctr26 merged 1 commit into
masterfrom
claude/anthropic-life-science-roles-5psay3
Oct 5, 2026
Merged

ctr26 merged 1 commit into
masterfrom
claude/anthropic-life-science-roles-5psay3

Conversation

@ctr26

@ctr26 ctr26 commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Summary

Craig's call after #12: the vibe page is a subpage that should inform, not read as a CV supplement. The two pages become one guide.

vibe.md ("Vibe Coding", /vibe/)

  • The scientists' guide is the spine: why it matters, getting started with Claude Code, CLAUDE.md, four workflows, tips and pitfalls, the point
  • The former working-style sheet folds in as Practices that keep it sane (commits, worktrees, typed configs, small diffs, files, standards, privacy) and Anti-patterns, rewritten as guidance to the reader with a reason per rule, and pointed at CLAUDE.md as the place to record them
  • Gone: "Working with me", "What I value", "Expectations", the bio line, the cross-links; nothing on the page is about Craig
  • Copilot's two accuracy points from [site] Review pass on the two vibe pages, and a tidy header nav #12 are carried over (worktrees don't prevent merge conflicts; Claude reads the files it needs)
  • House style: no colons or em dashes in prose (code fences excepted); checked by script

Removed

  • vibe-coding.md; /vibe-coding/ stops resolving. header_pages lists the one page, so the nav is "Vibe Coding" only

Testing

  • Preview build on this PR; nav and anchors checked from the artifact once it runs

🤖 Generated with Claude Code

https://claude.ai/code/session_01JFVYogXC9MgS2EuFBvrZog


Generated by Claude Code

The two subpages become one guide at /vibe/. The scientists' guide is
the spine (why, getting started, CLAUDE.md, workflows, pitfalls) and
the working-style sheet folds in as "Practices that keep it sane" and
"Anti-patterns", written as guidance to the reader rather than a
profile. The "working with me" sections, the bio line, and the
cross-links go; vibe-coding.md is removed and header_pages lists the
one page.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JFVYogXC9MgS2EuFBvrZog
@ctr26
ctr26 marked this pull request as ready for review October 5, 2026 16:37
Copilot AI balanced review requested due to automatic review settings October 5, 2026 16:37
@ctr26
ctr26 merged commit 5693449 into master Oct 5, 2026
2 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Two technical guidance statements about Git recovery and Pydantic validation are inaccurate.

Review effort: Balanced
Findings: 1 Medium severity · 1 Low severity

Open (2)
What changed in this PR

Consolidates two Vibe Coding pages into one practical guide for scientists.

Changes:

  • Expands vibe.md with setup, workflows, practices, and pitfalls.
  • Removes the duplicate guide and navigation entry.
File Description
vibe.md Becomes the unified Vibe Coding guide.
vibe-coding.md Removes the superseded page.
_config.yml Removes the deleted page from navigation.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread vibe.md
- One workspace means one concern, which also keeps the AI's context focused.

### Typed configs
- Pydantic schemas for configs, validated at runtime, so a typo in a YAML key fails at startup rather than three hours into training.
Comment thread vibe.md
- One commit does one thing. Ask for the change, review it, commit it, then ask for the next.
- The first line says what changed and the body says why. The why is what the AI can't recover for you later.
- Never bundle unrelated changes; "fix tests, update docs, add feature" in one commit is the classic failure.
- Commit working states often, so an iteration that goes sideways is a `git checkout` away from undone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants