CLICK ME
yes, even hidden code blocks!
print("hello world!")
yu fujioka fujiokayu
dictav
/ シェアハウスを解散するにあたってのエントリ.md
Last active
January 13, 2025 15:21
geek-koshiji.com/2018/02/21/post-332/ のバックアップ
このエントリは残しておかないといけないと思ったので残します。 copyright 2018 https://twitter.com/geek_niigata
2018/2/21 ブログ
2月末でギークハウス越路を解散することになりましたのでその経緯エントリ。
mizchi
/ tsmeetup-draft-wip2.md
Last active
July 14, 2022 11:50
technohippy
/ 2022-03-03-WAR.md
Last active
August 10, 2025 02:34
https://zverok.space/blog/2022-03-03-WAR.html 翻訳
2022年3月3日
やぁ、僕はVictor Shepelev。ウクライナのハリコフに住んでいて、TwitterやGitHubでは@zverokというIDで活動している。
僕がRubyを書き始めたのは2003年からで、いくつかのライブラリやRuby Changelogのメンテナだ。国際的なカンファレンスや/r/rubyなんかで君たちと会ったことがあるかも知れない。今年、僕はRubyコミッターに申請して、嬉しいことに承認された。僕が取り組んでいるのは（いくつかの小さな機能追加と共に）Rubyドキュメントの改善だ。僕のRubyに関する作業の一覧はここで確認できる。
ATTENTION, THIS GIST ISN'T FREQUENTLY UPDATED
MAIN SOURCE: https://github.com/isaqueprofeta/cybersec-path
- Jose Bravo - What is a SIEM? (5 Vídeos): https://www.youtube.com/watch?v=MtqFMe4zSpQ&list=PLHh9jhztlMyp8lyKXt9orVM57ygW_ihPS
- IPPSec - PowerSIEM Analyzing Sysmon Events with PowerShell: https://www.youtube.com/watch?v=MvfhIydxFmw
ruvnet
/ .roomodes.json
Last active
October 28, 2025 17:46
This guide introduces Roo Code and the innovative Boomerang task concept, now integrated into SPARC Orchestration. By following the SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) and leveraging advanced reasoning models such as o3, Sonnet 3.7 Thinking, and DeepSeek, you can efficiently break down complex proj…
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "customModes": [ | |
| { | |
| "slug": "sparc", | |
| "name": "⚡️ SPARC Orchestrator", | |
| "roleDefinition": "You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.", | |
| "customInstructions": "Follow SPARC:\n\n1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.\n2. Pseudocode: Request high-level logic with TDD anchors.\n3. Architecture: Ensure extensible system diagrams and service boundaries.\n4. Refinement: Use TDD, debugging, security, and optimization flows.\n5. Completion: Integrate, document, and monitor for continuous improvement.\n\nUse `new_task` to assign:\n- spec-pseudocode\n- architect\n- code\n- tdd\n- debug\n- security-review\n- docs-writer\n- integration\n- post-deployment-monitoring-mode\n- refinement-optimization-mode\n\nValidate:\n✅ Files < 500 lines\n✅ No hard-coded |