scitex 2.13.0__py3-none-any.whl → 2.15.1__py3-none-any.whl

scitex/scholar/docs/to_claude/guidelines/USER_PHILOSOPHY/07_DEBUGGING_TECHNIQUES.md

@@ -1,153 +0,0 @@
-<!-- ---
-!-- Timestamp: 2025-09-01 08:32:51
-!-- Author: ywatanabe
-!-- File: /home/ywatanabe/.dotfiles/.claude/to_claude/guidelines/USER_PHILOSOPHY/07_DEBUGGING_TECHNIQUES.md
-!-- --- -->
-
-# Debugging Techniques
-
-1.  Basic Tools
-    -   Screen sessions for isolation
-        -   See `./docs/to_claude/guidelines/python/programming_common/screen.md` (MCP server support)
-    -   CIPDB for conditional debugging
-        -   See `./docs/to_claude/guidelines/python/official/cipdb.md`
-    -   IceCream for variable inspection
-        -   See `./docs/to_claude/guidelines/python/icrecream.md`
-
-2.  Quick Debug Setup
-
-```bash
-screen -dmS debug_session
-screen -S debug_session -X stuff "python script.py\n"
-sleep 2
-screen -S debug_session -X hardcopy -h /tmp/output.txt
-```
-
-1.  Code Integration
-
-```python
-import cipdb
-from icecream import ic
-
-def debug_function(data):
-    ic(data)
-    cipdb.set_trace(id="function_debug")
-    result = ic(process_data(data))
-    return result
-```
-
-1.  Targeted Debugging
-
-```bash
-export CIPDB_IDS=function_debug
-python script.py
-```
-
-1.  Best Practices
-    -   Name sessions: debug_${ISSUE_ID}
-    -   Add sleep 1-2s before screen capture
-    -   Use ic.disable() in production
-    -   Run screen -wipe periodically
-
-2.  Benefits
-    -   Multiple agents debug independently
-    -   Selective breakpoints by agent ID
-    -   Complete session capture
-
-```
-
-1.  Screen Session Handling
-
-1.  CIPDB (Conditional ipdb) for selective debugging independently from other agents
-
-1.  IceCream Integration
-
-1.  Multi-Agent Workflow
-    -   Issue Identification
-        ```bash
-        screen -dmS error_scan
-        screen -S error_scan -X stuff "python failing_script.py\n"
-        sleep 2
-        screen -S error_scan -X hardcopy -h /tmp/initial_error.txt
-        grep "Traceback\\|Error" /tmp/initial_error.txt
-        ```
-    
-    -   Enhanced Debugging with IceCream
-        
-        File: problematic_script.py
-        ```python
-        import cipdb
-        from icecream import ic
-        
-        def validate_input(data):
-            ic(data)
-            cipdb.set_trace(id="input_validation")
-            result = ic(validation_logic(data))
-            return result
-        
-        def database_query(sql):
-            ic(sql)
-            cipdb.set_trace(id="db_query")
-            connection = ic(get_connection())
-            return execute_query(connection, sql)
-        ```
-    
-    -   Targeted Debugging
-        ```bash
-        export CIPDB_IDS=input_validation
-        export AGENT_ID=DebuggerAgent
-        screen -dmS debug_input
-        screen -S debug_input -X stuff "python problematic_script.py\n"
-        sleep 1
-        screen -S debug_input -X hardcopy -h /tmp/debug_state.txt
-        ```
-    
-    -   State Analysis with IceCream Output
-        ```bash
-        grep "ic|" /tmp/debug_state.txt
-        grep "^> " /tmp/debug_state.txt | tail -1
-        screen -S debug_input -X stuff "pp vars()\n"
-        ```
-
-2.  Best Practices
-    -   Session Naming
-        -   Use: debug_${ISSUE_ID}_${TIMESTAMP}
-        -   Avoid conflicts between concurrent debugging
-    
-    -   Timing
-        -   Add sleep 0.5-2s after commands before capture
-        -   Screen needs time to process
-    
-    -   IceCream Configuration
-        -   Disable ic in production: ic.disable()
-        -   Use agent-specific prefixes
-        -   Include context for complex debugging
-    
-    -   Cleanup
-        -   Run screen -wipe periodically
-        -   Set CIPDB_ID=false in production
-    
-    -   Integration Pattern
-        ```python
-        
-        from icecream import ic
-        import cipdb
-        import os
-        
-        def debug_function(data):
-            ic(data)
-            cipdb.set_trace(id="function_debug") # You need to insert this line to inspect with ID
-            result = ic(process_data(data))
-            return result
-        ```
-        
-        `CIPDB_ID=function_debug python /path/to/filename.py`
-
-3.  Integration Benefits
-    -   IceCream provides lightweight variable inspection
-    -   CIPDB enables selective debugging by boolean, `$CLAUD_AGENT_ID`, `$CIPD_ID`, or `CIPD_IDS`
-        -   Multiple agents can debug same codebase simultaneously
-    -   Screen captures show everything human developers can see
-        Keep in mind the line number limitation in `~/.screenrc`
-
-<!-- EOF -->

scitex/scholar/docs/to_claude/guidelines/command/IMPORTANT-rm.md

@@ -1,69 +0,0 @@
-<!-- ---
-!-- Timestamp: 2025-05-25 23:21:15
-!-- Author: ywatanabe
-!-- File: /ssh:sp:/home/ywatanabe/.claude/to_claude/guidelines/command/rm.md
-!-- --- -->
-
-# Safe File Removal Guidelines
-
-## Policy
-- ALWAYS KEEP REPOSITORY CLEAN
-- For this, use `./docs/to_claude/bin/safe_rm.sh` to hide old/unrelated files with timestamp
-- `rm` command is not allowed
-
-## Table of Contents
-- [Usage](#usage)
-- [Examples](#examples)
-- [Comparison of Approaches](#comparison-of-approaches)
-- [Understanding Check](#your-understanding-check)
-
-## Usage
-`safe_rm.sh [-h|--help] file_or_directory [file_or_directory...]`
-
-## Examples
-- Remove a single file: `safe_rm.sh file1.txt`
-- Remove a directory: `safe_rm.sh dir1`
-- Remove multiple items: `safe_rm.sh file1.txt dir1 file2.py`
-- Remove all text files: `safe_rm.sh *.txt`
-
-## Comparison of Approaches
-
-| ❌ DO NOT | ✅ DO |
-|-----------|------|
-| ```bash
-# Permanently delete files
-rm file.txt
-``` | ```bash
-# Safely move files to .old directory
-./docs/to_claude/bin/safe_rm.sh file.txt
-``` |
-| ```bash
-# Recursively remove directories
-rm -rf directory/
-``` | ```bash
-# Safely preserve directory structure
-./docs/to_claude/bin/safe_rm.sh directory/
-``` |
-| ```bash
-# Mass deletion with glob patterns
-rm *.bak
-rm *_old*
-``` | ```bash
-# Safe removal with glob patterns
-./docs/to_claude/bin/safe_rm.sh *.bak
-./docs/to_claude/bin/safe_rm.sh *_old*
-``` |
-| ```bash
-# Force deletion without confirmation
-rm -f important_file.txt
-``` | ```bash
-# Files are preserved in .old directory
-./docs/to_claude/bin/safe_rm.sh important_file.txt
-# Can recover the file if needed
-``` |
-
-## Your Understanding Check
-Did you understand the guideline? If yes, please say:
-`CLAUDE UNDERSTOOD: /home/ywatanabe/.dotfiles/.claude/to_claude/guidelines/guidelines-command-rm.md`
-
-<!-- EOF -->

scitex/scholar/docs/to_claude/guidelines/command/IMPORTANT-tree.md

@@ -1,162 +0,0 @@
-<!-- ---
-!-- Timestamp: 2025-05-25 23:21:15
-!-- Author: ywatanabe
-!-- File: /ssh:sp:/home/ywatanabe/.claude/to_claude/guidelines/command/tree.md
-!-- --- -->
-
-# Tree Command Guidelines
-
-## Table of Contents
-- [Overview](#overview)
-- [Common Usage Patterns](#common-usage-patterns)
-- [Examples](#examples)
-- [Full Command Reference](#full-command-reference)
-
-## Overview
-The `tree` command displays the directory structure in a visual tree format, making it easier to understand project organization. Use this command regularly to maintain awareness of the codebase structure.
-
-## Common Usage Patterns
-
-| Option | Description | Example |
-|--------|-------------|---------|
-| `-a` | Show all files, including hidden files | `tree -a` |
-| `-d` | Show only directories | `tree -d` |
-| `-L n` | Limit depth to n levels | `tree -L 2` |
-| `-I pattern` | Exclude files/directories matching pattern | `tree -I "node_modules\|.git"` |
-| `--gitignore` | Honor gitignore patterns | `tree -a --gitignore` |
-| `-h` | Print sizes in human-readable format | `tree -h` |
-| `-C` | Enable colorization | `tree -C` |
-
-## Examples
-
-| Use Case | Command | Description |
-|----------|---------|-------------|
-| Project Overview | `tree -L 2` | View top-level directories and immediate subdirectories |
-| Code Navigation | `tree -L 3 src` | View source code structure to 3 levels deep |
-| Full Directory Analysis | `tree -a -h --du` | Show all files with human-readable sizes and calculate directory sizes |
-| Exclude Build Artifacts | `tree -I "node_modules\|build\|dist\|__pycache__"` | Show only relevant source files |
-| Find Large Directories | `tree -d -h --du \| grep -B 3 -A 1 "[GM]"` | Identify directories with large content |
-| JSON Output | `tree -J > structure.json` | Output structure in JSON format for parsing |
-
-## Example Outputs
-
-### Basic Project Structure
-```
-.
-├── docs
-│   ├── api
-│   └── user-guide
-├── src
-│   ├── components
-│   ├── services
-│   └── utils
-├── tests
-│   ├── integration
-│   └── unit
-├── README.md
-└── package.json
-```
-
-### Detailed Source Analysis
-```
-src
-├── components
-│   ├── Button
-│   │   ├── Button.jsx
-│   │   ├── Button.test.js
-│   │   └── index.js
-│   └── Header
-│       ├── Header.jsx
-│       ├── Header.test.js
-│       └── index.js
-├── services
-│   ├── api.js
-│   └── auth.js
-└── utils
-    ├── formatters.js
-    └── validators.js
-```
-
-## Full Command Reference
-
-``` plaintext
-usage: tree [-acdfghilnpqrstuvxACDFJQNSUX] [-L level [-R]] [-H  baseHREF]
-    [-T title] [-o filename] [-P pattern] [-I pattern] [--gitignore]
-    [--gitfile[=]file] [--matchdirs] [--metafirst] [--ignore-case]
-    [--nolinks] [--hintro[=]file] [--houtro[=]file] [--inodes] [--device]
-    [--sort[=]<n>] [--dirsfirst] [--filesfirst] [--filelimit #] [--si]
-    [--du] [--prune] [--charset[=]X] [--timefmt[=]format] [--fromfile]
-    [--fromtabfile] [--fflinks] [--info] [--infofile[=]file] [--noreport]
-    [--version] [--help] [--] [directory ...]
-  ------- Listing options -------
-  -a            All files are listed.
-  -d            List directories only.
-  -l            Follow symbolic links like directories.
-  -f            Print the full path prefix for each file.
-  -x            Stay on current filesystem only.
-  -L level      Descend only level directories deep.
-  -R            Rerun tree when max dir level reached.
-  -P pattern    List only those files that match the pattern given.
-  -I pattern    Do not list files that match the given pattern.
-  --gitignore   Filter by using .gitignore files.
-  --gitfile X   Explicitly read gitignore file.
-  --ignore-case Ignore case when pattern matching.
-  --matchdirs   Include directory names in -P pattern matching.
-  --metafirst   Print meta-data at the beginning of each line.
-  --prune       Prune empty directories from the output.
-  --info        Print information about files found in .info files.
-  --infofile X  Explicitly read info file.
-  --noreport    Turn off file/directory count at end of tree listing.
-  --charset X   Use charset X for terminal/HTML and indentation line output.
-  --filelimit # Do not descend dirs with more than # files in them.
-  -o filename   Output to file instead of stdout.
-  ------- File options -------
-  -q            Print non-printable characters as '?'.
-  -N            Print non-printable characters as is.
-  -Q            Quote filenames with double quotes.
-  -p            Print the protections for each file.
-  -u            Displays file owner or UID number.
-  -g            Displays file group owner or GID number.
-  -s            Print the size in bytes of each file.
-  -h            Print the size in a more human readable way.
-  --si          Like -h, but use in SI units (powers of 1000).
-  --du          Compute size of directories by their contents.
-  -D            Print the date of last modification or (-c) status change.
-  --timefmt <f> Print and format time according to the format <f>.
-  -F            Appends '/', '=', '*', '@', '|' or '>' as per ls -F.
-  --inodes      Print inode number of each file.
-  --device      Print device ID number to which each file belongs.
-  ------- Sorting options -------
-  -v            Sort files alphanumerically by version.
-  -t            Sort files by last modification time.
-  -c            Sort files by last status change time.
-  -U            Leave files unsorted.
-  -r            Reverse the order of the sort.
-  --dirsfirst   List directories before files (-U disables).
-  --filesfirst  List files before directories (-U disables).
-  --sort X      Select sort: name,version,size,mtime,ctime.
-  ------- Graphics options -------
-  -i            Don't print indentation lines.
-  -A            Print ANSI lines graphic indentation lines.
-  -S            Print with CP437 (console) graphics indentation lines.
-  -n            Turn colorization off always (-C overrides).
-  -C            Turn colorization on always.
-  ------- XML/HTML/JSON options -------
-  -X            Prints out an XML representation of the tree.
-  -J            Prints out an JSON representation of the tree.
-  -H baseHREF   Prints out HTML format with baseHREF as top directory.
-  -T string     Replace the default HTML title and H1 header with string.
-  --nolinks     Turn off hyperlinks in HTML output.
-  --hintro X    Use file X as the HTML intro.
-  --houtro X    Use file X as the HTML outro.
-  ------- Input options -------
-  --fromfile    Reads paths from files (.=stdin)
-  --fromtabfile Reads trees from tab indented files (.=stdin)
-  --fflinks     Process link information when using --fromfile.
-  ------- Miscellaneous options -------
-  --version     Print version and exit.
-  --help        Print usage and this help message and exit.
-  --            Options processing terminator.
-```
-
-<!-- EOF -->

scitex/scholar/docs/to_claude/guidelines/elisp/IMPORTANT-ELISP-01-basic.md

@@ -1,65 +0,0 @@
-<!-- ---
-!-- Timestamp: 2025-05-30 08:19:08
-!-- Author: ywatanabe
-!-- File: /home/ywatanabe/.dotfiles/.claude/to_claude/guidelines/elisp/IMPORTANT-ELISP-01-basic.md
-!-- --- -->
-
-# Elisp Troubleshooting Guidelines
-
-## Parentheses Mismatch
-Use the following scripts for debugging:
-  - `.claude/to_claude/bin/elisp_check_parens.sh`
-  - `.claude/to_claude/bin/elisp-check-parens-lib.el`
-
-## Require and Provide
-- DO NEVER INCLUDE SLASH (`/`) in `require` and `provide` statements.
-  The arguments to require and provide are called features. These are symbols, not file paths.
-  When you want to use code from `./xxx/yyy.el`:
-  In `./xxx/yyy.el`, use `(provide 'yyy)`. 
-  The provided feature should EXACTLY MATCH THE FILENAME WITHOUT DIRECTORY OR EXTENSION.
-  In other files, use `(require 'yyy)` to load it.
-  If `./xxx` is not already in your `load-path`, add it:
-  `(add-to-list 'load-path "./xxx")`
-  Again, DO NOT USE `(require 'xxx/yyy)`—symbols with slashes will raise problems.
-  ```elisp
-  ;; ~/.emacs.d/lisp/xxx/yyy.el
-  (provide 'yyy)
-  
-  ;; elsewhere
-  (add-to-list 'load-path "~/.emacs.d/lisp/xxx")
-  (require 'yyy)
-  ```
-
-## load-path
-- Place the following block to the top of entry file
-- This adds subdirectories recursively except for hidden files
-- To add paths for source/test files, placing and calling this function in root will be useful.
-
-```elisp
-(defun --elisp-add-subdirs-to-loadpath-recursive (parent-dir)
-  "Recursively add all visible subdirectories of PARENT-DIR to `load-path'.
-Recursively adds all non-hidden subdirectories at all levels to the load path.
-Hidden directories (starting with '.') are ignored.
-Example:
-(--elisp-add-subdirs-to-loadpath-recursive \"~/.emacs.d/lisp/\")"
-  (let ((default-directory parent-dir))
-    (add-to-list 'load-path parent-dir)
-    (dolist (dir (directory-files parent-dir t))
-      (when (and (file-directory-p dir)
-                 (not (string-match-p "/\\.\\.?$" dir))
-                 (not (string-match-p "/\\." dir)))
-        (add-to-list 'load-path dir)
-        (--elisp-add-subdirs-to-loadpath-recursive dir)))))
-
-;; Usage: add ./src and ./tests directories to load-path
-(let ((current-dir (file-name-directory (or load-file-name buffer-file-name))))
-  (--elisp-add-subdirs-to-loadpath-recursive (concat current-dir "src"))
-  (--elisp-add-subdirs-to-loadpath-recursive (concat current-dir "tests")))
-```
-
-## Your Understanding Check
-========================================
-Did you understand the guideline? If yes, please say:
-`CLAUDE UNDERSTOOD: <THIS FILE PATH HERE>`
-
-<!-- EOF -->

scitex/scholar/docs/to_claude/guidelines/elisp/IMPORTANT-ELISP-02-project-structure.md

@@ -1,97 +0,0 @@
-<!-- ---
-!-- Timestamp: 2025-05-30 08:21:58
-!-- Author: ywatanabe
-!-- File: /home/ywatanabe/.dotfiles/.claude/to_claude/guidelines/elisp/IMPORTANT-ELISP-02-project-structure.md
-!-- --- -->
-
-# Elisp Project Structure Guidelines
-
-## Umbrella Structure
-- Use umbrella structure with up to 1 depth
-- Each umbrella must have at least:
-  - Entry point: e.g., `./src/<package-prefix>-<umbrella>/<package-prefix>-<umbrella>.el`
-  - A dedicated variable file under the scope of the umbrella: 
-    - e.g., `./src/<package-prefix>-<umbrella>/<package-prefix>-<umbrella>-variables.el`
-  - Variables and functions in an umbrella should be named as:
-    - `<package-prefix>-<umbrella>-...`
-- Entry script should add load-path to child directories
-- Entry file should be `project-name.el`
-- <project-name> is the same as the directory name of the repository root
-
-## Directory Layout
-1. Place entry point: `./<package-name>.el`
-   This allows to `(require 'package-name)` outside of the pacakge as long as path is added.
-2. Adopt umbrella design as follows:
-
-```plaintext
-./package-name/
-├── package-name.el                 # Entry point, allows (require 'package-name)
-│   # Contents:
-│   # Add loadpath to umbrella entry points
-│   # (require 'umbrella-xxx)
-│   # (require 'umbrella-yyy)
-│   # (provide 'package-name)
-├── src
-|   ├── umbrella-xxx/                   # First functional grouping
-|   │   ├── umbrella-xxx.el             # Submodule integrator 
-|   │   │   # Contents:
-|   │   │   # (require 'umbrella-xxx-aab)
-|   │   │   # (require 'umbrella-xxx-bbb) 
-|   │   │   # (provide 'umbrella-xxx)
-|   │   ├── umbrella-xxx-aab.el         # Component A functionality
-|   │   └── umbrella-xxx-bbb.el         # Component B functionality
-|   └── umbrella-yyy/                   # Second functional grouping
-|       ├── umbrella-yyy.el             # Submodule integrator
-|       │   # Contents:
-|       │   # (require 'umbrella-yyy-ccc)
-|       │   # (require 'umbrella-yyy-ddd)
-|       │   # (provide 'umbrella-yyy)
-|       ├── umbrella-yyy-ccc.el         # Component C functionality
-|       └── umbrella-yyy-ddd.el         # Component D functionality
-└── tests/                          # Test suite directory
-    ├── test-package-name.el        # Tests for main package
-    │   # Contents:
-    │   # Loadability check
-    ├── test-umbrella-xxx/          # Tests for xxx component
-    │   ├── test-umbrella-xxx.el    # Tests for xxx integration
-    │   │   # Loadability check
-    │   ├── test-umbrella-xxx-aab.el # Tests for aab functionality
-    │   │   # Contents:
-    │   │   # (ert-deftest test-umbrella-xxx-aab-descriptive-test-name-1 ...)
-    │   │   # (ert-deftest test-umbrella-xxx-aab-descriptive-test-name-2 ...)
-    │   └── test-umbrella-xxx-bbb.el # Tests for bbb functionality
-    │       # Contents:
-    │       # (ert-deftest test-umbrella-xxx-bbb-descriptive-test-name-1 ...)
-    │       # (ert-deftest test-umbrella-xxx-bbb-descriptive-test-name-2 ...)
-    └── test-umbrella-yyy/          # Tests for yyy component
-        ├── test-umbrella-yyy.el    # Tests for yyy integration
-        │   # Contents:
-        │   # Loadability check
-        ├── test-umbrella-yyy-ccc.el # Tests for ccc functionality
-        │   # (ert-deftest test-umbrella-yyy-ccc-descriptive-test-name-1 ...)
-        │   # (ert-deftest test-umbrella-yyy-ccc-descriptive-test-name-2 ...)
-        └──test-umbrella-yyy-ddd.el # Tests for ddd functionality
-            # (ert-deftest test-umbrella-yyy-ddd-descriptive-test-name-1 ...)
-            # (ert-deftest test-umbrella-yyy-ddd-descriptive-test-name-2 ...)
-└.playground
-```
-
-**IMPORTANT**: 
-- DO NOT CREATE DIRECTORIES IN PROJECT ROOT  
-- Create child directories under predefined directories instead
-
-## Temporal Working Space: `./.playground`
-- For your temporally work, use `./.playground`
-  - Organize playground with categoris: 
-    `./.playground/category-name-1/...`
-    `./.playground/category-name-2/...`
-
-## Test Run Script
-Use `./run_tests_elisp.sh` in the project root
-- It creates detailed `LATEST-ELISP-REPORT.org` with metrics
-
-## Your Understanding Check
-Did you understand the guideline? If yes, please say:
-`CLAUDE UNDERSTOOD: <THIS FILE PATH HERE>`
-
-<!-- EOF -->

scitex/scholar/docs/to_claude/guidelines/elisp/IMPORTANT-ELISP-03-file-template.md

@@ -1,70 +0,0 @@
-<!-- ---
-!-- Timestamp: 2025-05-30 08:20:03
-!-- Author: ywatanabe
-!-- File: /home/ywatanabe/.dotfiles/.claude/to_claude/guidelines/elisp/IMPORTANT-ELISP-03-file-template.md
-!-- --- -->
-
-# Elisp File Template Guidelines
-
-## Elisp Header Rules
-
-#### Required Header Format
-DO INCLUDE headers like:
-``` elisp
-;;; -*- coding: utf-8; lexical-binding: t -*-
-;;; Author: ywatanabe
-;;; Timestamp: <2025-05-12 21:39:05>
-;;; File: /home/ywatanabe/.emacs.d/lisp/sample-package/hw-utils/hw-utils.el
-
-;;; Copyright (C) 2025 Yusuke Watanabe (ywatanabe@alumni.u-tokyo.ac.jp)
-```
-
-#### Headers We Do Not Use
-On the other hand, we DO NOT FOLLOW THIS KINDS OF HEADERS THOUGH THEY ARE ELISP CONVENTIONS:
-``` elisp
-;;; hw-utils.el --- Utility functions for emacs-hello-world  -*- lexical-binding: t; -*-
-
-;;; Commentary:
-;; This file provides utility functions for the emacs-hello-world package.
-
-;;; Code:
-```
-
-## Elisp Footer Rules
-
-Do not remove this kind of footer. This is useful when evaluate the buffer to confirm no problem found in the file.
-In general, they are handled by an automatic script by the `ehf-update-header-and-footer` function from `emacs-header-footer-manager package. So they will not have syntax errors.
-``` elisp
-(when
-    (not load-file-name)
-  (message "ecc-vterm-yank-as-file.el loaded."
-           (file-name-nondirectory
-            (or load-file-name buffer-file-name))))
-```
-
-## Elisp In-File Hierarchy and Sorting Rules
-
-- Functions must be sorted considering their hierarchy.
-- Upstream functions should be placed in upper positions
-  - from top (upstream functions) to down (utility functions)
-- Do not change any code contents during sorting
-- Includes comments to show hierarchy
-
-```elisp
-;; 1. Main entry point
-;; ---------------------------------------- 
-
-
-;; 2. Core functions
-;; ---------------------------------------- 
-
-
-;; 3. Helper functions
-;; ---------------------------------------- 
-```
-
-## Your Understanding Check
-Did you understand the guideline? If yes, please say:
-`CLAUDE UNDERSTOOD: <THIS FILE PATH HERE>`
-
-<!-- EOF -->

scitex/scholar/docs/to_claude/guidelines/elisp/IMPORTANT-ELISP-04-coding-style.md

@@ -1,42 +0,0 @@
-<!-- ---
-!-- Timestamp: 2025-05-30 08:20:22
-!-- Author: ywatanabe
-!-- File: /home/ywatanabe/.dotfiles/.claude/to_claude/guidelines/elisp/IMPORTANT-ELISP-04-coding-style.md
-!-- --- -->
-
-# Elisp Coding Style Guidelines
-
-## Naming Conventions
-
-#### General Naming Rules
-- Use kebab-case for filenames, function names, and variable names
-- Use acronym as prefix for non-entry files (e.g., `ecc-*.el`)
-- Do not use acronym for exposed functions, variables, and package name
-- Use `--` prefix for internal functions and variables (e.g., `--ecc-internal-function`, `ecc-internal-variable`)
-- Function naming: `<package-prefix>-<category>-<verb>-<noun>` pattern
-- Include comprehensive docstrings
-
-## Elisp Docstring Example
-
-```elisp
-(defun elmo-load-json-file (json-path)
-  "Load JSON file at JSON-PATH by converting to markdown first.
-
-Example:
-  (elmo-load-json-file \"~/.emacs.d/elmo/prompts/example.json\")
-  ;; => Returns markdown content from converted JSON"
-  (let ((md-path (concat (file-name-sans-extension json-path) ".md")))
-    (when (elmo-json-to-markdown json-path)
-      (elmo-load-markdown-file md-path))))
-```
-
-## Elisp Commenting Rules
-- Keep comments minimal but meaningful
-- Use comments for section separation and clarification
-- Avoid redundant comments that just restate code
-
-## Your Understanding Check
-Did you understand the guideline? If yes, please say:
-`CLAUDE UNDERSTOOD: <THIS FILE PATH HERE>`
-
-<!-- EOF -->