just-cli 0.2.1__tar.gz → 0.3.1__tar.gz

just_cli-0.3.1/.claude/plans/2026-04-18-edit-installer-macos-micro.md

@@ -0,0 +1,237 @@
+# Edit Installer: macOS Support with micro Implementation Plan
+
+> **For agentic workers:** REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** Add macOS support to `just install edit` by installing the `micro` text editor
+
+**Architecture:** Platform-specific branching in installer function - Windows/Linux continue using Microsoft Edit, macOS uses micro with symlink from `edit` to `micro`.
+
+**Tech Stack:** Python 3.10+, typer, just installer framework
+
+---
+
+## File Structure
+
+**Files to modify:**
+- `src/just/installers/edit/installer.py` - Main installer implementation
+
+**No new files needed.**
+
+---
+
+## Chunk 1: Update installer.py with macOS micro support
+
+### Task 1: Modify version parameter and add platform detection
+
+**Files:**
+- Modify: `src/just/installers/edit/installer.py`
+
+- [ ] **Step 1: Update the version parameter default**
+
+Change the `version` parameter default from `"1.2.0"` to `None`:
+
+```python
+def install_edit(
+    version: just.Annotated[
+        str, just.Option("-v", "--version", help="The version of Edit to install.")
+    ] = None,  # Changed from "1.2.0"
+):
+```
+
+- [ ] **Step 2: Add version resolution logic**
+
+Add platform-specific default version after the function definition:
+
+```python
+    # Resolve default version based on platform
+    if version is None:
+        if just.system.platform == "darwin":
+            version = "2.0.15"  # micro latest stable
+        else:
+            version = "1.2.0"  # Microsoft Edit
+```
+
+- [ ] **Step 3: Update docstring**
+
+Update the docstring to reflect macOS support:
+
+```python
+    """
+    Install a terminal text editor.
+
+    - Windows/Linux: Microsoft Edit
+    - macOS: micro (with 'edit' symlink)
+    """
+```
+
+- [ ] **Step 4: Commit**
+
+```bash
+git add src/just/installers/edit/installer.py
+git commit -m "feat(edit): add version parameter resolution for platform defaults"
+```
+
+---
+
+### Task 2: Add macOS branch with micro installation
+
+**Files:**
+- Modify: `src/just/installers/edit/installer.py`
+
+- [ ] **Step 1: Add macOS platform branch**
+
+Add the `elif just.system.platform == "darwin":` branch before the `else` clause:
+
+```python
+    elif just.system.platform == "darwin":
+        # Install micro text editor for macOS
+        editor_name = "micro"
+        url = f"https://github.com/zyedidia/micro/releases/download/v{version}/micro-{version}-{just.system.arch}-darwin.tar.gz"
+
+        just.echo.info(f"Installing {editor_name} v{version} as the default editor...")
+
+        just.ArchiveInstaller(
+            url=url,
+            executables=["micro"],
+            name="micro",
+        ).run()
+```
+
+- [ ] **Step 2: Add edit -> micro symlink creation**
+
+After the `ArchiveInstaller().run()` call in the macOS branch, add symlink creation:
+
+```python
+        # Create edit -> micro symlink for consistency
+        from just.core.installer.utils import create_symlink_or_wrapper
+        from just.core.config.utils import get_bin_dir
+
+        micro_path = get_bin_dir() / "micro"
+        create_symlink_or_wrapper(
+            target=micro_path,
+            link_dir=get_bin_dir(),
+            link_name="edit"
+        )
+```
+
+- [ ] **Step 3: Add info log for Windows/Linux branches**
+
+Add `just.echo.info()` calls before `ArchiveInstaller().run()` in Windows and Linux branches:
+
+```python
+        just.echo.info(f"Installing Microsoft Edit v{version} as the default editor...")
+```
+
+- [ ] **Step 4: Commit**
+
+```bash
+git add src/just/installers/edit/installer.py
+git commit -m "feat(edit): add macOS support with micro editor"
+```
+
+---
+
+### Task 3: Update installer decorator check command
+
+**Files:**
+- Modify: `src/just/installers/edit/installer.py`
+
+- [ ] **Step 1: Update check command for platform detection**
+
+The current `@just.installer(check="edit -v")` won't work for macOS since we install micro first.
+Update to use a dynamic check or remove the check parameter for now:
+
+```python
+@just.installer(check="edit --version")  # Works for both after symlink is created
+```
+
+Note: `micro --version` works, and after symlink `edit --version` will invoke micro.
+
+- [ ] **Step 2: Commit**
+
+```bash
+git add src/just/installers/edit/installer.py
+git commit -m "fix(edit): update check command to work with micro"
+```
+
+---
+
+## Chunk 2: Testing
+
+### Task 4: Manual testing on macOS
+
+**Files:**
+- None (manual testing)
+
+- [ ] **Step 1: Test macOS installation**
+
+Run on macOS:
+```bash
+just install edit
+```
+
+Expected output:
+```
+Installing micro v2.0.15 as the default editor...
+...
+Installing micro v2.0.15 as the default editor...
+```
+
+- [ ] **Step 2: Verify edit command works**
+
+```bash
+edit --version
+```
+
+Expected: micro version output
+
+- [ ] **Step 3: Verify symlink exists**
+
+```bash
+ls -la ~/.just/bin/edit
+```
+
+Expected: symlink pointing to micro
+
+- [ ] **Step 4: Test version override**
+
+```bash
+just install edit -v 2.0.14
+```
+
+Expected: installs specified micro version
+
+---
+
+### Task 5: Verify existing platforms unchanged
+
+**Files:**
+- None (manual testing on Windows/Linux)
+
+- [ ] **Step 1: Test default behavior**
+
+```bash
+just install edit
+```
+
+Expected: installs Microsoft Edit v1.2.0
+
+- [ ] **Step 2: Test version override**
+
+```bash
+just install edit -v 1.1.0
+```
+
+Expected: installs specified Microsoft Edit version
+
+---
+
+## Final State
+
+After implementation, `just install edit` will:
+
+| Platform | Editor | Default Version | Command Available |
+|----------|--------|-----------------|-------------------|
+| macOS | micro | 2.0.15 | `edit` (-> micro) |
+| Windows | Microsoft Edit | 1.2.0 | `edit` |
+| Linux | Microsoft Edit | 1.2.0 | `edit` |

just_cli-0.3.1/.claude/settings.local.json

@@ -0,0 +1,9 @@
+{
+  "permissions": {
+    "allow": [
+      "mcp__web-search-prime__web_search_prime",
+      "mcp__web-reader__webReader",
+      "mcp__context7__query-docs"
+    ]
+  }
+}

just_cli-0.3.1/.claude/skills/textual/README.md

@@ -0,0 +1,139 @@
+# Textual Skill
+
+Expert guidance for building TUI (Text User Interface) applications with the Textual framework.
+
+## Overview
+
+This skill provides comprehensive knowledge about building terminal user interfaces with Textual, a modern Python framework by Textualize.io. It covers:
+
+- **Core Concepts**: App architecture, screens, widgets, reactive programming, CSS styling
+- **Best Practices**: Design patterns, code organization, performance optimization
+- **Testing**: Testing strategies with pytest and Pilot
+- **Debugging**: Development console, logging, visual debugging
+- **Common Patterns**: Ready-to-use code templates and examples
+- **Error Prevention**: Common pitfalls and how to avoid them
+
+## Files
+
+- **SKILL.md**: Main skill definition with invocation triggers and high-level guidance
+- **quick-reference.md**: Concise cheat sheets, templates, and quick lookups
+- **guide.md**: Comprehensive architectural guide with detailed explanations
+- **README.md**: This file - skill documentation
+
+## When This Skill is Invoked
+
+Claude will automatically use this skill when you:
+
+- Ask about building TUI applications
+- Mention the Textual framework
+- Need help with widgets, screens, or layouts
+- Have questions about CSS styling (TCSS)
+- Want to implement reactive programming
+- Need testing guidance for Textual apps
+- Encounter errors with Textual code
+- Ask about TUI design patterns
+
+## Usage Examples
+
+**Basic Questions:**
+- "How do I create a Textual app?"
+- "What's the best way to organize a Textual project?"
+- "How do I test Textual applications?"
+
+**Specific Features:**
+- "How do I create a modal dialog in Textual?"
+- "What's the difference between reactive and var?"
+- "How do I make a widget focusable?"
+
+**Debugging:**
+- "Why isn't my reactive attribute updating the UI?"
+- "My test is failing - what am I doing wrong?"
+- "How do I debug a Textual app?"
+
+**Design & Architecture:**
+- "What's the best state management approach for my Textual app?"
+- "Should I use composition or inheritance for my widgets?"
+- "How do I implement the 'attributes down, messages up' pattern?"
+
+## Key Concepts Covered
+
+### Architecture
+- Event-driven message queue system
+- DOM-like widget hierarchy
+- Screen navigation and modes
+- Widget lifecycle methods
+
+### Reactive Programming
+- Reactive attributes with auto-refresh
+- Validation and watch methods
+- Computed properties
+- Data binding between widgets
+- Recompose for dynamic layouts
+
+### CSS Styling (TCSS)
+- Selector types and specificity
+- Layout with docking and FR units
+- Theme system with semantic colors
+- Pseudo-classes and nesting
+- Live reload during development
+
+### Testing
+- pytest with async support
+- Pilot for simulating interactions
+- Snapshot testing (optional)
+- Common testing patterns
+- Best practices and pitfalls
+
+### Best Practices
+- "Attributes down, messages up" pattern
+- Composition over inheritance
+- Single responsibility principle
+- Separation of UI and business logic
+- Performance optimization
+- Accessibility considerations
+
+## Quick Start
+
+To build a minimal Textual app:
+
+```python
+from textual.app import App, ComposeResult
+from textual.widgets import Header, Footer, Static
+
+class MyApp(App):
+    def compose(self) -> ComposeResult:
+        yield Header()
+        yield Static("Hello, Textual!")
+        yield Footer()
+
+if __name__ == "__main__":
+    MyApp().run()
+```
+
+Run with:
+```bash
+python my_app.py
+```
+
+Or use development mode for live reload:
+```bash
+textual run --dev my_app.py
+```
+
+## Resources
+
+- **Official Documentation**: https://textual.textualize.io
+- **GitHub**: https://github.com/Textualize/textual
+- **Discord**: Join the Textual Discord for community support
+
+## Skill Maintenance
+
+This skill is based on the Textual documentation and best practices as of January 2025. The framework is actively developed, so refer to the official documentation for the latest features and changes.
+
+### Original Source Files
+
+This skill was created from:
+- `textual-quick-reference.md` - Quick reference templates
+- `textual-guide.md` - Comprehensive framework guide
+
+These files can be updated and the skill regenerated if needed.