vosk work

Author: teknopaul

.claude/skills/c-bash/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: c-bash
+description: make .sh files follow common C code conventions for readability and maintainability
+allowed-tools: bash
+---
+
+All `.sh` files should follow `.claude/skills/bash-coding-standards.md`
+
+You MUST work on one file at a time, don't do bulk updates since these tend to break scripts subtly.
+
+When replacing `"${var}"` it is _not_ always safe to use `$var`, especially if the variable might contain spaces or unknown input.
+
+It is only safe to use the shortened `$var` syntax when the variable is known to be a simple string value, usually that means its set earlier in the script.
+
+It is also only safe to remove the `{}` if the use of this variable does not cause ambiguity, or if the text following it does not cause bash to interpret it as a different variable.
+
+After making changes to each file one at a time you must `bash -n` the changed script and then run the script to make sure it still works.
+
+## converting non-compliant code
+
+When asked to convert bash to to these conventions...
+
+Never do mass sed/perl replacements across many files at once.
+
+Each change must be read in context first. A variable that looks like a path may hold multi-line output, quoted strings, or JSON. The fix that is correct for one variable may silently corrupt another.
+
+Quotes are load-bearing — check usage before removing them
+"$var" is NOT just style. It is required when:
+- the variable may contain spaces (file names, URLs with query strings, response bodies)
+- the variable may contain newlines (curl response bodies, grep output)
+- the variable may contain glob characters (*, ?, [)
+- the variable is on the right-hand side of [[ ]] and could contain * or ?
+
+- Only remove quotes when you can see, from reading the script, that none of these apply.
+echo "$var" must stay quoted when var is a response body
+echo $var word-splits and glob-expands. echo "$var" preserves newlines. Any variable holding HTTP response bodies, JSON, or log output must keep quotes.
+
+Work iteratively — one file at a time
+
+1. Read the full file
+1. Identify violations
+1. Understand each variable's content and all its usages
+1. Make targeted changes
+1. Run bash -n and the test before moving to the next file
+
+Never use automated tools (sed/perl/python) to rename variables across files
+
+Variable names are not unique tokens — $body in one script is a response body requiring quotes; in another it is a simple path. Mass rename without reading context will introduce bugs.
+The rule is: remove ${braces} only, not quotes
+
+"${foo}" → "$foo" is usually safe (keeps quotes, removes unnecessary braces).
+If any code uses "${foo}_baa" changing to  "$foo_bar" is not safe.
+
+"${foo}" → $foo is only safe after reading the specific usage.

.claude/skills/c-bash/bash-coding-standards.md

@@ -0,0 +1,43 @@
+# Bash coding standards
+
+All test `.sh` scripts should follow these guidelines.
+
+follow [bash code style](bash-code-style.md).
+
+
+Presume no spaces in paths, this is Linux, no need to quote them.
+Presume URLs do not have spaces, they never do, no need to quote them.
+Don't quote `$port` variables
+Don't use colors `${RED}` outside of the test utilities.
+Avoid env vars for nodejs server parameters, use CLI args.
+
+Make use of test utilities `test-functions.sh` and `integration-test-fucntion.sh`, do not write script specific
+
+- assertions
+- kill functions
+
+Finish scripts with `test_summary` this will exit in a way that integrates with Makefile test targets.
+For nginx integration tests just before `test_summary` run `crash_check`
+
+## exit handlers
+
+Handle cleanup in an exit handler, that runs in success or failure scenario.
+```
+cleanup() {
+  cleanup_nginx
+  cleanup_pid $backend_pid
+  cleanup_temp_dir
+}
+trap cleanup EXIT
+```
+
+# Prefer standard ports
+
+mxsrv           53880
+legacy          8080
+winchecker-next 9090
+cache_manager   9999
+
+# preferred vars
+
+base_url

.claude/skills/opus-exec/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: opus-exec
+description: executing a plan written by opus-plan
+allowed-tools: java, bash
+---
+
+Claude Opus will write phased delivery plans in `./ai-context`.
+
+Claude Sonnet should execute, if the agent asked to execute is Opus it should stop and report this as an error.
+
+Arguments to this skill should be the plan name and phase.
+Plan may be provided as an attached document to the chat.
+
+For this skill, executed by Claude Sonnet, each phase should be executed in sequence.
+Agent should execute phases autonomously, one after the other. until the context window is 80% full.
+
+If the context window is 80% full it should report progress, and wait for human user to clear the
+context for the subsequent phases. 
+
+During execution
+
+Never submit code.
+Never change .perf.targets - humans must review performance regressions
+
+After each phase is complete update the _PLAM.md, so that we can recover from crashes and full context windows.

.claude/skills/opus-plan/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: opus-plan
+description: use Claude Opus to plan development for Claude Sonnet
+allowed-tools: java, bash
+---
+
+Rather than implementing any code, output should be a markdown file in `./ai-context`
+that contains a phased implementation plan where each phase fits in the Claude Sonnet 4.6 context window.
+
+No changes should be made, other than writing one new plan document.
+
+After each phase Claude Sonnet should write to ./ai-context/PROGRESS.md so we can /clear and continue with a fresh context.

Makefile.am

@@ -111,6 +111,10 @@ if ENABLE_GEANYCONTROL
 SUBDIRS += geanycontrol
 endif
 
+if ENABLE_GEANYVOSK
+SUBDIRS += geanyvosk
+endif
+
 if ENABLE_GEANYSERVERS
 SUBDIRS += geanyservers
 endif

ai-context/PROGRESS.md

@@ -0,0 +1,21 @@
+# geanyvosk — Implementation Progress
+
+## Status
+
+| Phase | Description                          | Status   |
+|-------|--------------------------------------|----------|
+| 1     | Project scaffold & build system      | complete |
+| 2     | ALSA microphone capture thread       | complete |
+| 3     | Vosk ASR + wake word detection       | complete |
+| 4     | UI command dispatch via geanycontrol | complete |
+| 5     | Skill & AI-prompt creation by voice  | complete |
+| 6     | Agent skill execution by voice       | complete |
+
+## Notes
+
+- Plan document: `ai-context/geanyvosk-plan.md`
+- Vosk is NOT installed on the system; must be installed before Phase 3.
+  - Install libvosk: download from https://alphacephei.com/vosk/models (C library + header)
+  - Install ALSA dev: `sudo apt install libasound2-dev`
+- To resume after `/clear`, start a new session and say:
+  "Continue geanyvosk Phase N per ai-context/geanyvosk-plan.md"