gp_scratch

.claude/settings.local.json

@@ -1,5 +1,4 @@
 {
-  "model": "haiku",
   "permissions": {
     "allow": [
       "Bash(find:*)",
@@ -16,6 +15,7 @@
       "Bash(git push:*)"
     ]
   },
+  "model": "haiku",
   "hooks": {
     "Notification": [
       {

.claude/skills/blog.add_figures/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Add figures to a blog post
+model: haiku
 ---
 
 Given the blog post written in markdown, you are an expert illustrator who can

.claude/skills/blog.create_tldr/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Create 3 catchy and controversial TLDR summaries for a blog post
+model: opus
 ---
 
 Create 3 catchy and controversial TLDR of less than 20 words without emdash

.claude/skills/blog.write_tutorial2/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Write a blog post about a machine learning library or technique for a technical audience
+model: opus
 ---
 
 You are a technical writer specializing in writing blog posts about machine

.claude/skills/blog.write_tutorial_tool_in_30_mins/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Write a practical technical tutorial for engineers, covering one tool or concept in 10-15 mins of reading time
+model: opus
 ---
 
 # Purpose
@@ -64,13 +65,11 @@ description: Write a practical technical tutorial for engineers, covering one to
 ## Code Examples
 - Use copy-paste ready code blocks with `bash` or language-specific syntax highlighting
 - Include expected output so readers know it worked
-- For shell commands, show the prompt style:
-  ```markdown
+- For shell commands, show the prompt style, e.g.,
   - On macOS and Linux using the official installer:
     ```bash
     > curl -LsSf https://astral.sh/uv/install.sh | sh
     ```
-  ```
 
 ## Platform Coverage
 - Focus on macOS and Linux instructions
@@ -95,10 +94,14 @@ description: Write a practical technical tutorial for engineers, covering one to
 - Use code blocks for all commands, config files, and output
 
 # Examples to Reference
-- Located in `website/docs/blog/posts/`:
-  - `uv_in_30_mins.md` — Tool intro with installation, core concepts, examples
-  - `ripgrep_in_30_mins.md` — Search tool with practical use cases
-  - `python_packaging_in_30_mins.md` — Concept-based tutorial with workflow
-  - `mdm_unified_markdown_manager.md` — Multi-tool tutorial
+- Located in `website/docs/blog/posts/`
+  - `website/docs/blog/posts/uv_in_30_mins.md`: Tool intro with installation,
+    core concepts, examples
+  - `website/docs/blog/posts/ripgrep_in_30_mins.md`: Search tool with practical
+    use cases
+  - `website/docs/blog/posts/python_packaging_in_30_mins.md`: Concept-based
+    tutorial with workflow
+  - `website/docs/blog/posts/mdm_unified_markdown_manager.md`: Multi-tool
+    tutorial
 
 - Study these for structure, tone, depth, and length.

.claude/skills/book.gather_info/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Gather information about books
+model: haiku
 ---
 
 - Given information about books (either a partially complete table or a list of

.claude/skills/book.rename/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Rename a file storing a book or paper into a standard format
+model: haiku
 ---
 
 Given the name of a file storing a book or a paper, rename it to match the

.claude/skills/coding.add_comments/SKILL.md

@@ -1,22 +1,52 @@
 ---
 description: Add comments to make the code more readable
+model: haiku
 ---
 
 - I will pass you one of more files `<FILES>`
 
 # Goal
+
+## Add Comments
 - Improve its readability by adding concise comments with these rules
 
 - Add comments for every cohesive code block that is at least 5 lines long
   explaining what the code block does
 - Add comments describing important invariants, assumptions, or guarantees
   maintained by the code
-- Keep all comments as short and precise as possible
-- Avoid obvious line-by-line comments
-  - Do not restate the code in English
 - Add comments that explain _why_ rather than _what_
+  - Keep all comments as short and precise as possible
+  - Avoid obvious line-by-line comments
+  - Do not restate the code in English
+- Do not remove any comment, only add new ones when needed
+- Follow the rules in `.claude/skills/coding.rules.md` `# Comments`
+
+## Add Functions to Track Entering in a Function
+- For each function add at the beginning either
+  - `_LOG.debug(hprint.func_signature_to_str())` or
+  - `_LOG.debug(hprint.to_str("a b c")`
+     with the variables that are most important and not too big to print (e.g.,
+     large text, dictionary and so on)
+
+## Add `_LOG.debug` to Track the Execution in a Function
+- Use `_LOG.debug` to add debugging info in functions that can help a programmer
+  to track the issues and execution
+
+
+## Add `_LOG.debug` to Track the Resulting Values of a Function
+- Refactor code to avoid more than one `return` statement when possible
+- Instrument the code to print the exit value of a function
+  ```python
+  _LOG.debug("return=%s", ...)
+  ```
+
+## Conventions
+- Use `_LOG.debug(hprint.to_str("a b c")` when possible
+
+- Do not print large object, e.g.,
+  - If there is an array of objects print only the first element
+  - If there is a dictionary print only the first key
 
 - Do not change the behavior of the code in any way
 
-- Follow the rules in `.claude/skills/coding.rules.md`, especially in
-  `# Comments`
+- Follow the rules in `.claude/skills/coding.rules.md`

.claude/skills/coding.find_doc/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Find documentation files for a given dir, file, class, or function and summarize in 3 bullet points
+model: haiku
 ---
 
 - Given the passed object (e.g., dir, file, class, function)

.claude/skills/coding.fix_bloated_imports/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Fix Python imports of large packages needed only for few functions in a module
+model: haiku
 ---
 
 - I will pass you one of more files `<FILES>` and one or more packages `<PACKAGES>` that

.claude/skills/coding.fix_comments/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Update docstrings and comments in a Python file without changing logic
+model: haiku
 ---
 
 - Given the passed Python file

.claude/skills/coding.fix_dasserts/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Fix dassert in Python code
+model: haiku
 ---
 
 - I will pass you one of more files `<FILES>`

.claude/skills/coding.fix_docstring/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Fix Python Docstrings
+model: haiku
 ---
 
 - I will pass you one of more files `<FILES>`

.claude/skills/coding.fix_from_imports/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Replace "from X import Y" style imports with "import X" and update usages throughout a file
+model: haiku
 ---
 
 - Replace any Python statement like `from X import Y` with the form `import X`

.claude/skills/coding.fix_inline/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Find and remove the functions that are too thin
+model: haiku
 ---
 
 - I will pass you one of more files `<FILES>`

.claude/skills/coding.fix_param_use/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Fix function call sites to pass positional args by position and assign constants to intermediate variables
+model: haiku
 ---
 
 - I will pass you a file

.claude/skills/coding.fix_pyright/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Run pyright on Python files and fix the reported lints
+model: haiku
 ---
 
 Given a list of files `<FILES>`

.claude/skills/coding.fix_type_hints/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Fix type hints
+model: haiku
 ---
 
 - Use all the type hints related rules from `.claude/skills/coding.rules.md`

.claude/skills/coding.fix_use_helpers/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Identify and replace Python code with code in the `helpers` package
+model: haiku
 ---
 
 - I will provide references to one or more Python source files

.claude/skills/coding.make_function_private/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Identify functions not called externally and rename them with a leading underscore to make them private
+model: haiku
 ---
 
 For each function and class in the passed Python file, check if it's a function

.claude/skills/coding.rename/SKILL.md

@@ -1,5 +1,6 @@
 ---
 description: Rename files, functions, and variables across a codebase and update all references
+model: haiku
 ---
 
 I will give a list of files, functions, variable to rename in a codebase

.claude/skills/coding.reorg_functions/SKILL.md

@@ -1,15 +1,17 @@
 ---
 description: Reorganize the Python functions in a file
+model: haiku
 ---
 
 # Reorganize Python Functions Within a File
 
-Reorganize the Python functions in the user-provided file according to the
-following rules.
+- Reorganize the Python functions in the user-provided file according to the
+  following rules
 
 ## Organize Functions Into Logical Layers
 
-- Group related functions into sections separated by headers in the following format:
+- Group related functions into sections separated by headers in the following
+  format:
   ```python
   # #############################################################################
   # <Layer Description>
@@ -75,14 +77,15 @@ following rules.
 
 ## Preserve Behavior Exactly
 
-- Do not modify functionality, logic, signatures, control flow, side effects, or semantics
+- Do not modify functionality, logic, signatures, control flow, side effects, or
+  semantics
 - The resulting code must behave identically to the original.
 
 ## Move Code Only
 
-- The refactor must be structural only.
-  Allowed changes:
+- The refactor must be structural only
 
+- Allowed changes:
   - Reordering functions
   - Adding section headers
   - Renaming internal/private functions consistently