- 1 feature branch, 1 working tree: merge all loose branches/stashes/uncommitted files into it & push. Delete branches already merged into it
- ❌ ask user questions. Decide, act, report. Act autonomously
- Duplication = bug. Use deslop
- Important lints → error. Run static analysis routinely
- 🧹 After work: delete safe system caches & unneeded build files, kill your owned processes that eat CPU or memory and check disk space
- Refactors: violent, immediate, no back-compat. Legacy code banned → delete now
- Minimize code; decide toward less. Delete dead code now
- 📦 Minimize 3rd-party deps: routinely delete unused packages/crates, add none without need, consolidate overlapping deps into one, avoid those with a vulnerability history
- Reply ≤2 sentences, emojis for emphasis. Don't stream responses
- ✅ Tick mandatory plan checklist items as you work
Discover gists
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| // Quick try at doing a "print value" node for Unity ShaderGraph. | |
| // Tested on Unity 2019.2.17 with ShaderGraph 6.9.2. | |
| // | |
| // Use with CustomFunction node, with two inputs: | |
| // - Vector1 Value, the value to display, | |
| // - Vector2 UV, the UVs of area to display at. | |
| // And one output: | |
| // - Vector4 Color, the color. | |
| // Function name is DoDebug. |
公开版说明:文中的
DEV_PASSWORD已替换为占位符CHANGE_ME_LOCALLY。请在本地替换为自己的救援口令,并确保profile.env不进入 Git。
最后更新:2026-09-11
本文用于在 Apple Silicon Mac 上创建一台独立的 Ubuntu VM,专门运行 Claude Code。VM 使用目标地区的时区与 Locale,所有公网流量与 DNS 都经 Mac 上的 sing-box 走目标地区节点出口,代理不可用时阻止回落直连。
本文与地区无关:所有地区差异集中在 §1 的 profile,正文命令一律使用 $VM_NAME、$SOCKS_PORT、$TZ_REGION 等变量。§1.3 给出日本与美国两份现成 profile,新增地区照附录 A 填一份即可。
This document tries to give a description of the .mxtsession files used in the proprietary software MobaXterm. Sadly this format, as efficient as it is, is too obscure to encourage legitimate use cases of this format as there is no public documentation available.
The software licence of MobaXterm, for both Home and Pro editions, allows to "observe, study or test the functioning of the Software in order to determine the ideas and principles which are the basis of the Software, when performing the loading, display, execution, transmission or storage of the Software" and this study has been done in full under those terms.
The studied format is the one of version 26.3: sessions last modified (but not necessarily exported) before this version will have fewer fields.
Discord has decided to make the default page when you open the app to be the Quest home page, and we're not going to let them. Only a few users are experiencing this, so you may not be affected. (yet)
desktop-file-edit --set-key Exec --set-value "/usr/bin/discord discord://-/channels/@me" /usr/share/applications/discord.desktop
| 日時: | 2025-08-25 |
|---|---|
| 作: | 時雨堂 |
| バージョン: | 2025.1 |
| URL: | https://ayame-labo.shiguredo.app/ |
このサービスに興味がある人はこの資料に Star をつけてもらえると嬉しいです。
Solid 2.0 made async first-class. What that means is, you can create signals, memos, and stores that load their initial values asynchronously. This is a huge update over most other frameworks that — at the time of writing this (September 2026) — do not support anything of the sort.
So I decided to port my app, QuickPad, (which I had originally written in Vue and later migrated to Solid) to Solid 2.0 to try it out.
These are the differences that stood out to me during the porting process. I will go through each one in detail:
- No
asyncallowed in effect/setter/hook callbacks (major impact) - Updates are batched (medium impact)