feat: update all opencode configurations to support newest opencode features

.config/opencode/command/context.md

@@ -2,75 +2,25 @@
 description: Analyze and understand the complete project context and structure
 ---
 
-# Project Context Analysis
+# Context
 
-You are a project analysis specialist. When invoked, you will systematically analyze the project to understand its structure, purpose, technology stack, and current state. Use $ARGUMENTS to focus on specific aspects if provided.
+When the user runs this command, systematically analyze the project to understand its structure, purpose, stack, and current state. Use $ARGUMENTS to focus on specific aspects if provided.
 
-## Your Analysis Process:
+## Analysis Process
 
-**Step 1: Project Discovery**
-- Read the README.md file to understand project purpose and setup
-- Examine package.json/requirements.txt/Cargo.toml for dependencies and scripts
-- Check for documentation files (CONTRIBUTING.md, CHANGELOG.md, etc.)
+1. **Project discovery** — Read README, examine build configs (package.json, Cargo.toml, pyproject.toml, Gemfile, Makefile, CMakeLists.txt, etc.), and check for documentation files.
 
-**Step 2: Codebase Structure Analysis**
-- Run `git ls-files | head -50` to get an overview of file structure
-- Identify main directories and their purposes
-- Examine configuration files (.gitignore, .env.example, config files)
-- Look for framework-specific patterns
+2. **Codebase structure** — Run `git ls-files | head -60` to see the file layout. Identify main directories and their purposes. Examine key config files.
 
-**Step 3: Technology Stack Detection**
-- Identify primary programming languages
-- Detect frameworks and libraries in use
-- Find build tools and development workflow
-- Check for containerization (Dockerfile, docker-compose.yml)
+3. **Tech stack detection** — Identify languages, frameworks, build tools, package manager, containerization (Dockerfile, compose.yml), and CI/CD setup.
 
-**Step 4: Current Project State**
-- Check git status and recent commit history with `git log --oneline -10`
-- Identify any immediate issues or TODO items
-- Look for test coverage and CI/CD setup
+4. **Current state** — Check `git status`, `git log --oneline -10`, and scan for TODO items, test coverage patterns.
 
-**Step 5: Present Comprehensive Analysis**
+## Report
 
-## 📋 Project Context Report
-
-### 🎯 Project Overview
-- **Name**: [Project name from README/package.json]
-- **Purpose**: [What this project does]
-- **Status**: [Development stage, active/maintenance]
-
-### 🛠️ Technology Stack
-- **Primary Language**: [Main programming language]
-- **Framework**: [React, Django, Express, etc.]
-- **Database**: [If applicable]
-- **Build Tools**: [Webpack, Vite, etc.]
-- **Package Manager**: [npm, yarn, pip, cargo, etc.]
-
-### 📁 Project Structure
-```
-[Key directories and their purposes]
-src/ - source code
-tests/ - test files
-docs/ - documentation
-etc.
-```
-
-### 🔧 Development Workflow
-- **Setup Commands**: [How to get started]
-- **Build Process**: [How to build the project]
-- **Testing**: [How to run tests]
-- **Deployment**: [How to deploy]
-
-### 📊 Current State
-- **Recent Activity**: [Summary of recent commits]
-- **Open Issues**: [Any obvious problems or TODOs]
-- **Configuration**: [Environment setup needed]
-
-### 🎯 Key Files to Know
-- [List of important files developers should be aware of]
-
-## Analysis Guidelines:
-- **Be thorough**: Don't just read README, examine actual code structure
-- **Focus on developer needs**: What would a new team member need to know?
-- **Identify gaps**: Missing documentation, setup issues, etc.
-- **Practical insights**: Actual workflow vs documented workflow
+Provide a concise summary covering:
+- Project name and purpose
+- Technology stack (language, framework, build tools, package manager)
+- Directory structure overview
+- Development workflow (setup, build, test, deploy)
+- Recent activity and any obvious issues