dotfiles

Create and update paper reading notes in the user's Logseq vault. Use when summarizing a paper, recording results from a paper reading session, or appending notes to an existing paper page. The vault is shared between Logseq (daily-use viewer) and Obsidian (CLI access). Writes use Logseq syntax (key:: value, tab-indented outline), reads can use Obsidian CLI for backlinks/search or rg for raw content.

Write and review Japanese prose (articles, long-form docs) free of LLM rhetoric-excess, with consistent register and disciplined terminology. Universal layer — delegates project-specific house style to the project's CLAUDE.md / GLOSSARY.md. Use when drafting or reviewing Japanese articles, blog posts, or documentation prose.

User's opinionated Julia preferences. Four real frictions: (1) ASCII-only identifiers — never use Unicode (π, ≤, χ, …) because editor / terminal glyphs collapse confusables (e.g. x vs χ) and the resulting bugs are silent; (2) Tooling — scaffold with `jtc create MyPackage.jl`, manage deps with `mise run add`, and use `TestItemRunner.jl` with tags for test selection (mise tasks filter by tag); never `Pkg.generate` / `Pkg.add` / `Pkg.test` by hand; (3) Union{T, Nothing} for optional / fallible values rather than throwing or sentinel returns; (4) parameter-pack factory pattern — @kwdef struct with parametric types fed by a factory constructor that takes a loose Dict{String, Any} from CLI / config parsing. Plus opinions on multiple dispatch, type stability, performance idioms (@view, @inbounds, @simd, StaticArrays), and Project.toml compat. TRIGGER when writing or editing any Julia (.jl) file, Project.toml, test/, or mise.toml. SKIP for non-Julia work.

User's opinionated Python preferences. The two non-negotiables are (1) ALWAYS use uv for package management — never pip/poetry/conda/venv directly — and (2) ALWAYS add type annotations to every function signature. Plus secondary preferences (ruff, pyright strict, pydantic v2, 3.10+ syntax) and known pitfalls. TRIGGER when writing or editing any Python (.py) file, pyproject.toml, requirements.txt, or any package-management or environment setup. SKIP for non-Python work.