| name | cognitive-rhythm-writing |
|---|---|
| description | 説明的な文章に緩急を設計するための規範。緩急を装飾ではなく認知モードの切替（観察→逡巡→断定→再観察）と未回収の緊張の管理として扱い、文の拍、段落の密度波形、節の入り方、緩みと駄文の判別、執筆後の機械的な点検手順を定める。読み物として読ませたい章・記事・解説文を生成するとき、または「密度はあるが平坦でおもしろくない」文章を診断・修正するときに使用する。 |
密度の高い文章が退屈になるのは、情報が多いからではなく、全文が同じ認知モードで書かれているからである。 この規範は、読者の認知モード（観察する、迷う、確信する、確かめ直す）を意図的に切り替え、常に「続きを読む理由」を維持することで、読み進める推進力を作る。
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
| #!/usr/bin/env sh | |
| while true; do | |
| temp=$(sudo ec_probe read 0x70 | awk '{print $1}') | |
| high_byte=$(sudo ec_probe read 0x35 | awk '{print $1}') | |
| low_byte=$(sudo ec_probe read 0x36 | awk '{print $1}') | |
| fan1=$((high_byte * 256 + low_byte)) | |
| high_byte=$(sudo ec_probe read 0x37 | awk '{print $1}') | |
| low_byte=$(sudo ec_probe read 0x38 | awk '{print $1}') |
| // HOW TO INSTRUCTIONS | |
| // 1. Open Claude Desktop | |
| // 2. Go to Help -> Enable Developer Mode | |
| // 3. Navigate Developer Tools window named "Developer Tools - https://claude.ai" | |
| // 4. Go to "Console" tab | |
| // 5. Type "allow pasting" and hit Enter | |
| // 6. Paste this snippet and hit Enter | |
| // From now on, all MCP calls will be auto-approved |
| # frozen_string_literal: true | |
| # For now, run like this: `ruby --rjit --rjit-disable fjit.rb` | |
| # | |
| # Once RJIT is removed, the extra flags will not be necessary | |
| require "fiddle" | |
| require "ffi" | |
| require "jit_buffer" | |
| require "hacks" |
| # Reference #1: https://note.com/npaka/n/nc55e44e407ff | |
| # Reference #2: https://huggingface.co/blog/gemma-peft | |
| # Licence: MIT | |
| from peft import LoraConfig | |
| lora_config = LoraConfig( | |
| r=8, | |
| target_modules=["q_proj", "o_proj", "k_proj", "v_proj", "gate_proj", "up_proj", "down_proj"], | |
| task_type="CAUSAL_LM", |
| @echo off | |
| :: ============================================================================ | |
| :: ASUS Software Clean Up Tool — HAS MOVED | |
| :: ============================================================================ | |
| :: | |
| :: This Gist is no longer maintained. | |
| :: The tool has moved to a full repository with new features: | |
| :: | |
| :: https://github.com/allenk/ASUS-Software-Clean-Up-Tool | |
| :: |
| Copyright (c) 2022 Steven Silvester | |
| All rights reserved. | |
| Redistribution and use in source and binary forms, with or without | |
| modification, are permitted provided that the following conditions are met: | |
| 1. Redistributions of source code must retain the above copyright notice, this | |
| list of conditions and the following disclaimer. | |
| 2. Redistributions in binary form must reproduce the above copyright notice, |
