mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-04-29 17:20:21 -05:00

Files

Vijay Janapa Reddi 79e73a530c fix: Correct biological neuron to artificial neuron mapping

Thanks to @formlsysbookissue for identifying this important clarification.

- Updated Table 3.1: Dendrites now map to inputs, synapses to weights
- Revised explanatory text throughout Chapter 3 to maintain distinction
- Updated quiz question to reflect corrected understanding
- Renumbered mapping list for clarity (1-5 instead of 1-4)

This correction helps students build accurate mental models of how biological
neural structures relate to artificial neural networks.

Part of #947

2025-08-23 22:24:52 +02:00

2.7 KiB

Raw Blame History

Claude Code Configuration for MLSysBook

How I Work

When you give me a command, I:

Check if it matches one of the patterns below
Read the methodology in .claude/private/ (if it exists)
Follow those instructions exactly

Command Patterns I Recognize

Issue Resolution

Pattern: resolve issue <number> or fix issue <number> Action: I will: <<<<<<< HEAD

Create a feature branch
Fetch the issue using gh issue view <number>
Apply methodology from .claude/private/ISSUE_RESOLVER.md
Make necessary changes
Show you the changes for review
Create a DRAFT PR for private review

Pattern: review changes Action: Show all changes in current branch with explanations

Pattern: create draft pr Action: Create a draft PR (not visible to issue author)

Pattern: `finalize pr <number>` Action: Convert draft PR to ready and tag the issue author with thanks

Fetch the issue using gh issue view <number>
Apply methodology from .claude/private/ISSUE_RESOLVER.md
Make necessary changes
Create a PR

origin/fix/issue-947-dendrite-synapse-correction

Pattern: analyze issue <number> Action: I will analyze but NOT make changes

Pattern: check issues Action: I will list all open improvement issues

Content Quality

check chapter <name> - Review chapter for quality issues
improve flow <section> - Enhance pedagogical progression
check terminology - Ensure consistent terminology

Quick Fixes

fix typo <description> - Quick typo fixes
update reference <old> <new> - Update citations
fix links - Check and fix broken links

Workflow

When resolving issues:

I fetch and analyze the issue from GitHub
I classify it (content, technical, structural)
I apply the appropriate methodology
I make changes maintaining quality standards
I create a PR with clear description

Quality Standards

Every change must:

Maintain technical accuracy
Preserve pedagogical flow
Keep consistent voice
Match chapter difficulty level
Include practical relevance

File Organization

Book content: quarto/contents/core/
Labs: quarto/contents/labs/
Build configs: quarto/config/
Scripts: tools/scripts/

Building & Testing

# Quick build test
cd quarto && quarto render --to html

# Full build
./binder build html

# Check specific chapter
./binder preview <chapter_name>

Git Workflow

Main branch: dev
PR branches: fix/issue-<number>-<description>
Commit style: Conventional commits

Notes

The .claude/private/ directory contains proprietary methodologies
Always verify builds before creating PRs
Tag PRs with appropriate labels

2.7 KiB Raw Blame History