Skip to content

[pull] main from PaulDuvall:main #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pull merged 1 commit into from
Dec 5, 2025
Merged

[pull] main from PaulDuvall:main #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
88 changes: 88 additions & 0 deletions experiments/NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
# Experimental Pattern Notes

This file tracks patterns under exploration that may eventually be formalized into full patterns.

## Pattern Exploration Queue

### Voice-to-Code Interface

**Status**: Early exploration
**Date Added**: 2025-12-04

**Description**: Using voice input tools (e.g., WisprFlow, Talon Voice, Voice Control for VSCode) to dictate code, commands, and AI prompts for hands-free development.

**Potential Use Cases**:
- Accessibility for developers with mobility limitations
- Reducing repetitive strain injuries (RSI)
- Faster prompt composition for AI interactions
- Multi-modal input (voice + keyboard/mouse hybrid)
- Hands-free code review and exploration

**Tools to Evaluate**:
- [WisprFlow](https://whisperflow.com/) - Voice-to-text for coding
- [Talon Voice](https://talonvoice.com/) - Voice control for development
- [Voice Control for VSCode](https://marketplace.visualstudio.com/items?itemName=pokey.cursorless) - VSCode voice extensions
- Native OS voice control (macOS Voice Control, Windows Speech Recognition)

**Research Questions**:
1. How accurate is voice-to-code for technical terminology (function names, variable names)?
2. Can voice dictation handle AI prompt composition effectively?
3. What's the learning curve for voice commands vs. keyboard shortcuts?
4. Does voice input improve or hinder AI-assisted development workflows?
5. How does voice integrate with existing AI coding tools (Claude Code, Cursor, Copilot)?

**Next Steps**:
- [ ] Test WisprFlow with Claude Code for prompt dictation
- [ ] Evaluate voice accuracy for Python/JavaScript/TypeScript
- [ ] Measure WPM (words per minute) voice vs. keyboard for prompts
- [ ] Document voice command vocabulary for common AI interactions
- [ ] Assess impact on [Context Persistence](../README.md#context-persistence) pattern

**Related Patterns**:
- [Tool Integration](../README.md#tool-integration) - Voice as input tool for AI
- [Custom Commands](#custom-commands) - Voice-triggered slash commands
- [Event Automation](#event-automation) - Voice input as lifecycle event

**Anti-patterns to Avoid**:
- Over-reliance on voice for precise code editing (better for high-level commands)
- Using voice in noisy environments (poor transcription accuracy)
- Voice-only workflow without keyboard fallback (voice fatigue)

---

## Notes Template

When adding new pattern explorations, copy this template:

```markdown
### [Pattern Name]

**Status**: [Early exploration | Active testing | Ready for formalization]
**Date Added**: YYYY-MM-DD

**Description**: Brief 1-2 sentence description

**Potential Use Cases**:
- Use case 1
- Use case 2

**Tools to Evaluate**:
- Tool 1 with link
- Tool 2 with link

**Research Questions**:
1. Question 1
2. Question 2

**Next Steps**:
- [ ] Step 1
- [ ] Step 2

**Related Patterns**:
- Link to pattern 1
- Link to pattern 2

**Anti-patterns to Avoid**:
- Anti-pattern 1
- Anti-pattern 2
```
Loading