claude-terminal-conventions

# Claude Terminal Conventions > Generated from [talayash/claude-terminal](https://github.com/talayash/claude-terminal) on 2026-03-24 ## Overview This skill teaches Claude the development patterns and conventions used in claude-terminal. ## Tech Stack - **Primary Language**: TypeScript - **Framework**: Vite - **Architecture**: type-based module organization - **Test Location**: separate ## When to Use This Skill Activate this skill when: - Making changes to this repository - Adding new features following established patterns - Writing tests that match project conventions - Creating commits with proper message format ## Commit Conventions Follow these commit message conventions based on 83 analyzed commits. ### Commit Style: Free-form Messages ### Prefixes Used - `feat` ### Message Guidelines - Average message length: ~49 characters - Keep first line concise and descriptive - Use imperative mood ("Add feature" not "Added feature") *Commit message example* ```text feat: add claude-terminal ECC bundle (.claude/commands/add-or-enhance-feature.md) ``` *Commit message example* ```text docs: Update README for v1.2.0 ``` *Commit message example* ```text Fix: Use correct Rust toolchain action in release workflow ``` *Commit message example* ```text Release v1.17.1 ``` *Commit message example* ```text Merge remote-tracking branch 'origin/feature/advanced-claude-features' ``` *Commit message example* ```text Merge pull request #8 from talayash/ecc-tools/claude-...