milktea 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 2ed418298f9856106a16ea4b8547cddbdde2841e270faa7e7c5750e45498055c
+  data.tar.gz: ebbc971d234ee535db7d4cda1d57a94c57fbe6a6cade430d3a715a13340fae24
+SHA512:
+  metadata.gz: 4733b94d3d650b662671a3d14fee70d7a4aec3b8dd7bbb64f69f4f5e4bd8744a2993791bcc02690b349fa95b4dfdf0d4f01eb26261a733ce800ad0fa8823137a
+  data.tar.gz: 0f871c49c46ec816401b93cf7f16e856ccb2103e8bc256665d2a3fffcb0a8f669ba241f0d6279d37a0716acbe6e6ca1152d3f2a4283fdbedf925011a0f910eea

data/.claude/commands/devlog.md

@@ -0,0 +1,103 @@
+# Milktea Development Log Generator
+
+Create a comprehensive development log for today in English, following this standardized format and guidelines. The document should be readable in 5 minutes (1200-1500 words maximum) and serve as a historical record for future development decisions.
+
+## Output Requirements
+
+**File Location**: `docs/devlog/[YYYYMMDD].md` where `[YYYYMMDD]` is today's date (e.g., `20250702.md`)
+
+**Structure**: Use exactly this template structure:
+
+```markdown
+# Development Log - [Date in YYYY-MM-DD format]
+
+## What's New
+[New features, capabilities, and enhancements that provide value to users or developers]
+
+## What's Fixed
+[Bug fixes, issues resolved, and improvements to existing functionality]
+
+## Design Decisions
+[Architectural choices, alternatives considered, and reasoning for future reference]
+
+## Impact
+[Brief summary of how these changes affect users, developers, or the project direction]
+
+## Files Modified
+[Bulleted list of key files changed for quick reference]
+```
+
+## Content Guidelines
+
+### What's New Section
+- **Focus on**: New features, enhancements, added capabilities
+- **Format**: Use descriptive headers (####) for major features
+- **Include**: User impact, developer benefits, new possibilities enabled
+- **Exclude**: Implementation details, code snippets (unless essential for understanding)
+
+### What's Fixed Section
+- **Structure**: Problem description → Root cause (if relevant) → Solution implemented
+- **Focus on**: User-visible improvements, stability enhancements, developer experience
+- **Include**: Impact of the fix, scenarios that now work correctly
+- **Highlight**: Critical bugs, performance improvements, reliability enhancements
+
+### Design Decisions Section
+- **Document**: Architectural choices, pattern selections, technology decisions
+- **Include**:
+  - Problem context and alternatives considered
+  - Reasoning and trade-offs made
+  - Future implications and guidance for similar decisions
+- **Format**: Decision title → Context → Choice → Rationale
+- **Critical**: Any decisions that change development patterns or conflict with existing approaches
+
+### Quality Standards
+- **Reading Time**: 5 minutes maximum (1200-1500 words)
+- **Audience**: Ruby developers building TUI applications and contributors to the Milktea framework
+- **Tone**: Professional, clear, technically accurate but accessible
+- **Depth**: Enough detail to understand decisions, not implementation specifics
+
+## Research Instructions
+
+1. **Check recent commits**: Use `git log --oneline -10` to identify changes since last devlog
+2. **Analyze changes**: Look at modified files, commit messages, and change patterns
+3. **Categorize changes**: Group related commits and changes by the three main sections
+4. **Extract decisions**: Identify any architectural, design, or technical choices made
+5. **Check conflicts**: Review if any decisions contradict current CLAUDE.md guidance
+
+## CLAUDE.md and ARCHITECTURE.md Integration
+
+**Critical**: If any design decisions documented in the devlog contradict or change the development approach described in CLAUDE.md or ARCHITECTURE.md:
+
+1. **Update CLAUDE.md** to reflect new development practices and commands
+2. **Update ARCHITECTURE.md** to document architectural changes and design patterns
+3. **Document the change** in the devlog's Design Decisions section
+4. **Explain reasoning** for why the previous approach was modified
+5. **Ensure consistency** between devlog, CLAUDE.md, and ARCHITECTURE.md for future development
+
+### When to Update Each File:
+- **CLAUDE.md**: Development commands, testing approaches, coding conventions, repository management
+- **ARCHITECTURE.md**: System design, component relationships, architectural patterns, technical decisions
+
+## File Analysis Guidelines
+
+When analyzing git changes:
+- **Focus on intent**: What problem was being solved?
+- **Identify patterns**: Are there recurring themes in the changes?
+- **Note architecture changes**: Any new patterns, refactoring, or structural improvements?
+- **Capture rationale**: Why were specific approaches chosen?
+- **TUI-specific considerations**: How do changes affect terminal rendering, user interaction, or event handling?
+- **Framework impact**: How do modifications influence the developer experience for TUI application builders?
+
+## Final Checklist
+
+Before saving the devlog, verify:
+- [ ] All three main sections are present and populated
+- [ ] Word count is under 1500 words (5-minute read)
+- [ ] Design decisions include reasoning and context
+- [ ] File list captures major changes
+- [ ] CLAUDE.md is updated if needed for development practices
+- [ ] ARCHITECTURE.md is updated if needed for design changes
+- [ ] Date format is correct (YYYY-MM-DD)
+- [ ] Content provides value for future developers reviewing project history
+
+This devlog will serve as a crucial historical record for understanding project evolution and making informed decisions in future development.

data/.claude/settings.json

@@ -0,0 +1,29 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(bundle exec rspec:*)",
+      "Bash(bundle exec rubocop:*)",
+      "Bash(diff:*)",
+      "Bash(find:*)",
+      "Bash(git add:*)",
+      "Bash(git rm:*)"
+    ]
+  },
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "jq -r '.tool_input.file_path | select(endswith(\".rb\"))' | xargs -r bundle exec rubocop -A"
+          },
+          {
+            "type": "command",
+            "command": "jq -r '.tool_input.file_path | select(endswith(\"_spec.rb\"))' | xargs -r bundle exec rspec"
+          }
+        ]
+      }
+    ]
+  }
+}

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,17 @@
+AllCops:
+  NewCops: enable
+  SuggestExtensions: false
+  TargetRubyVersion: 3.1
+  Exclude:
+    - 'examples/**/*'
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  EnforcedStyle: double_quotes
+
+Metrics/BlockLength:
+  Exclude:
+    - '*.gemspec'
+    - 'spec/**/*_spec.rb'