Skip to content
FSS Knowledge Base

Upgrades

Section titled “Upgrades”

CC (Claude Code)

Section titled “CC (Claude Code)”

Windows Startup

Section titled “Windows Startup”
  • Fix LilySpeech startup timing

Idea Capture

Section titled “Idea Capture”
  • Obsidian web clipper CAN be used on mobile devices without a pro subscription
    • Best Cross-Platform Free Option
      • Syncthing + Mobius Sync is recommended for reliable, private, and free (for a single folder/vault) bidirectional sync between Android, iOS, and desktop.[youtube +2]
      • Share with Sean, after working
    • Try Obsidian mobile 1 mn, if needed
      • if sync alternative not good enough
    • For all saved articles/clippings …
      • Rate on a 0 to 10 scale.
      • Summarize key ideas and how they can benefit.

Cheatsheets

Section titled “Cheatsheets”
  • for WSL aliases, tmux, AHK
    • always current with SSOT

Date formating

Section titled “Date formating”
  • define my unambiguous date format; per the AHK script
    • { Months := [“JA”, “FE”, “MR”, “AP”, “MY”, “JN”, “JL”, “AU”, “SE”, “OC”, “NO”, “DE”] CurrentYear := FormatTime(, “yyyy”) CurrentMonth := Integer(FormatTime(, “MM”)) ; Convert “01” to 1 CurrentDay := FormatTime(, “dd”) MonthAbbreviation := Months[CurrentMonth] FormattedDate := CurrentYear . MonthAbbreviation . CurrentDay . ”: ” SendText(FormattedDate) }

Obsidian Wep Clipper

Section titled “Obsidian Wep Clipper”
  • Template: create better one, apply to all existing clips
    • template should also add to top of article a 2-4 bullet summary of key points, and (ideally) how it benefits my smart debt mission
  • organize/save into General Notes, instead??

SDC Mission PDA

Section titled “SDC Mission PDA”

Monorepo

Section titled “Monorepo”
  • SD Logo Animation - Dot “Bloom”
  • SD favicon
    • Stroke Weight: The “S” and “D” characters are quite thin at this scale. On standard-resolution (non-Retina) monitors, these thin lines may appear “blurry” or “grayed out” due to anti-aliasing.
      • Recommendation: For the 16px export specifically, try manually thickening the “SD” letters by about 0.5–1px. Aligning the vertical strokes of the “D” and “S” strictly to the pixel grid will make them look much sharper.
    • The Gold Dot: The accent dot is very small (looks like 1.5–2px). It risks looking like a random “stray pixel” or a glitch rather than a deliberate design choice.
      • Recommendation: Increase the diameter of the gold dot for the 16px version. Making it 3px or 4px wide ensures it remains a distinct “accent” rather than a speck.
  • Components
    • Heading animation, property, similar to global and mail
      • Very light primary brand colour from theme, add some animation similar to or better than the border being animated and disappearing. Ask AI for other alternatives so it is not a perfect copy of their approach.
      • Half second of no styling. Then part second of fading in the background of the text. Add additional animation similar or better than border animation.
  • Tailwind v4

notify.py

Section titled “notify.py”
  • WORKS WELL - simply turning all WAIT flags OFF; notifications simply stream to terminal, with optional TTS on some
  • WAIT notifications are blocking subsequent notifications
    • what is a practical solution here? Less critical notifications that do not have a wait status, could and should proceed as scheduled. Then, upgrade the UX as follows …
  • UX: clear indicate status after showing/saying a notification
    • show notification text in a box, but show continuation prompt on terminal line that also indicates if in Waiting status:
      • WAITING for input … (in green)
        • AckCan you spare for the leaf next Monday at 9:00 pm?nowledge: Enter; Exit: Ctrl+C
        • Snooze: ‘s’ for 5 min, ‘s20’ for 20 min
        • Next: ‘n’ to show next 5 notifications, ‘n10’ for next 10
    • also speak that “Waiting for acknowledgement or Snooze”
    • Needs to have more of a dashboard like UI, where status is very clear, especially if waiting for acknowledgment, and all subsequent notifications are listed, in ascending order
      • Any other suggestions to make this app more effective?

KB Structure

Section titled “KB Structure”
  • AI Rules
    • better organize the rules and context resources used for actively used AI tools, currently warp and cursor. The master sources probably should exist in the knowledge base, with symbolic links accessed by these tools.
    • also clean up and reorganize the warp subfolder, moving session logs to the logs main folder.

Globe and Mail article capture

Section titled “Globe and Mail article capture”
  • automate for future
  • transform all existing to make it easy to search, and perhaps cross-link in KB
  • could use MarkItDown
    • Microsoft MarkItDown is an open‑source tool from Microsoft that converts many file types (Office docs, PDFs, images, audio, web pages) into clean, structured Markdown optimized for use with LLMs and search. a simple Python API (MarkItDown().convert(path)), batch processing of folders, and a plugin system to add custom format handlers, making it suitable for building chatbots, wikis, or backend services that need large‑scale document ingestion

Web Dev

Section titled “Web Dev”
  • use Bun/Deno hybrid: Bun instead of Deno where possible
    • Try Bun for local dev and CI to shave minutes off builds, validate native module compatibility before switching full time.

Email Names

Section titled “Email Names”
  • ‘nextsteps@’ is good for a general entry point, but it is not great as a lead magnet that clear suggests a tangible benefit
  • roadmap@ is better … better alternatives?

AutoHotKey

Section titled “AutoHotKey”
  • SSoT issue
    • My current process requires that I manually synchronize the KB cheatsheet with the AHK hotstrings and hotkeys actually used, in d:\FSS\Software\Utils\AutoHotkey\AllScripts.ahk (which itself “includes” several other .ahk files).
    • Is there a better process that is not vulnerable to human oversight and copy/paste errors?

Cleanups

Section titled “Cleanups”
  • purge node_modules, except created by pnpm
  • consolidate Python installs (3.10.4, 3.11.5, 3.13.1)

System Utils

Section titled “System Utils”
  • create a dashboard to easily execute all utils, see Cheatsheets, etc.
  • Use uv to run python utils
    • uvx replaces uv run or uv tool run

Obsidian

Section titled “Obsidian”
  • Purge to be minimal idea-capture tool
    • Inbox!!!
    • move fron Dynalist to KB
      • Software: all
      • Personal: Sean

  • Obsidian Skills

    Section titled “Obsidian Skills”
  • upgrade kb-online to a PWA
    • a PWA could upgrade your Obsidian-to-Astro static site setup, making it more seamless across devices with offline access, faster loading, and potentially automated updates for content changes. Here’s how it could work:
      • Core enhancements with PWA basics: Add a manifest.json and service worker to your Astro site. This lets users “install” it as an app on any device (mobile/desktop), with full-screen mode, home screen icons, and offline caching of your static pages/assets. Since your site is already static, this is straightforward—Astro has good PWA integration via plugins like @astrojs/pwa or vite-pwa. Your knowledge base becomes accessible offline, which is a big win over a plain website.
      • Automated hot loading of content changes: “Hot loading” (real-time or near-real-time updates without manual rebuilds) isn’t inherent to static sites, but a PWA can bridge this with some tweaks:
          • Service worker for dynamic updates: Configure the service worker to periodically check for new builds or content hashes when online (e.g., via fetch() on a version endpoint). If changes are detected (say, from a rebuilt Astro site deployed to Vercel/Netlify), it can prompt the user to refresh or auto-update the cache in the background. This isn’t true “hot” reloading like in dev mode, but it enables seamless pulls of new content without full page reloads.
        • Syncing from Obsidian: To automate the pipeline, hook your Obsidian vault (assuming it’s in a Git repo) to a CI/CD workflow (e.g., GitHub Actions). On file changes/pushes, auto-rebuild the Astro site and deploy. Then, in the PWA, use background sync (via service worker’s sync event) or periodic polling to fetch updated pages or data. If you want bidirectional edits (editing notes from the PWA), you’d need to store notes in IndexedDB (or Dexie.js) and sync back to your Obsidian vault via an API (e.g., GitHub API or a simple backend like Supabase).
        • Implementation outline: Start with Astro’s PWA plugin, add a service worker script (e.g., using Workbox) to handle caching strategies like network-first for dynamic parts. For hot updates, expose a /updates endpoint in your Astro site that returns a manifest of changed files. The SW can compare and fetch diffs. This could be built in a weekend if your static site is simple.

KB/Task/Project Management

Section titled “KB/Task/Project Management”
  1. Run claude from terminal to initialize Claude Code in your project
  2. Run init to create the CLAUDE.md file where you can:
  • Add crucial information about yourself
  • Link to important files that define who you are
  • Explain your tag system and what each tag means
  • Describe your folder structure
  • Note that you use Zettelkasten methodology
  • Provide any context that helps Claude Code navigate and search effectively

The CLAUDE.md file becomes your AI’s instruction manual. You can write whatever you want — this is where you teach Claude Code how to understand your specific system.