custom-statusline
Set up custom Claude Code status line with Nerd Font icons, colors, git status, usage tracking, system info, and project context. NO EMOJIS - only Nerd Font icons and symbols. Use when configuring statusline, setting up status bar, or customizing Claude UI. Triggers with statusline, status bar, custom theme.
What this skill does
# Custom Status Line Setup
Sets up a comprehensive Claude Code status line with **Nerd Font icons only** (no emojis), ANSI colors, real-time usage tracking, git integration, and system monitoring.
## Quick Start: Interactive Configuration
Run the `/custom-statusline` command to interactively configure your status line. It will ask which elements you want:
- **Current directory** - Working directory path
- **Nerd Font icons** - All icons (os, git, clock, usage) - all or nothing
- **Git branch & status** - Branch, dirty/clean, ahead/behind, stash
- **Model name** - Current Claude model
- **Session duration** - Time elapsed in session
- **API usage (5h/7d)** - Claude API usage percentages
- **Context % till compact** - Context window usage
The command will save your preferences to `~/.claude/statusline-config.json` and configure settings to use the plugin's script.
## Features
### Git Integration
- Clean/dirty status indicator
- Modified file count
- Ahead/behind tracking
- Stash count display
- Branch name with color coding
### Usage Tracking
- **5-hour and 7-day usage percentages** from Anthropic API
- Color-coded thresholds (green <50%, yellow 50-80%, red >80%)
- Cached for 60 seconds to avoid API spam
### Context Display
- Session context window percentage with **visual progress bar**
- Uses Claude Code's pre-calculated `used_percentage` for accuracy
- Color-coded thresholds matching community best practices:
- **Green** (<50%): Safe zone
- **Yellow** (50-80%): Approaching limit
- **Red** (>80%): Near auto-compact trigger
- Example: `ctx:45% ▓▓▓▓░░░░░░`
### Cost & Duration
- Total duration in minutes
## How It Works
- **Script**: Stays in the plugin folder at `${CLAUDE_PLUGIN_ROOT}/scripts/statusline.sh`
- **Config**: Saved to `~/.claude/statusline-config.json` (persists across plugin updates)
- **Settings**: Points to the plugin's script via dynamic lookup
## Manual Setup
If you prefer manual setup instead of the command:
### Step 1: Create Config File
Create `~/.claude/statusline-config.json`:
```json
{
"show_cwd": true,
"show_icons": true,
"show_git": true,
"show_model": true,
"show_duration": true,
"show_usage": true,
"show_context": true
}
```
### Step 2: Update Claude Settings
Update `~/.claude/settings.json`:
```json
{
"statusLine": {
"type": "command",
"command": "bash -c \"$(find ~/.claude/plugins/cache/zeul-claude-plugins/custom-statusline -name statusline.sh 2>/dev/null | head -1)\""
}
}
```
### Step 3: Test Status Line
```bash
echo '{}' | bash -c "$(find ~/.claude/plugins/cache/zeul-claude-plugins/custom-statusline -name statusline.sh | head -1)"
```
## Best Practices
This plugin follows community-recommended best practices for Claude Code statuslines:
### Why Context Tracking Matters
Claude Code has a 200K token context window and automatically runs `/compact` at ~80% usage. Without visibility, you won't know you're approaching the limit until context is lost.
### Design Principles
- **Keep it scannable** - Glance and get info in under a second
- **Use pre-calculated values** - `used_percentage` from Claude Code is more accurate than manual token math
- **Color-code thresholds** - 50%/80% boundaries match when to pay attention vs take action
- **Cache API calls** - 60-second cache prevents rate limiting and improves performance
### References
- [Creating The Perfect Claude Code Status Line](https://www.aihero.dev/creating-the-perfect-claude-code-status-line)
- [Custom Claude Code Statusline: Track Context](https://1ar.io/p/custom-claude-code-statusline-track-context-and-current-directory/)
- [How to Customize Your Claude Code Status Line](https://alexop.dev/posts/customize_claude_code_status_line/)
## Requirements
### Essential
- **Nerd Font installed** - For icons (JetBrains Mono, Hack, FiraCode, etc.)
- **jq installed** - For JSON parsing (`brew install jq`)
- **Git installed** - For git features
- **curl** - For API usage fetching
### Platform-Specific (macOS)
- **security** - Keychain access for API token
## Troubleshooting
**Icons not showing**: Install a Nerd Font and configure your terminal to use it
**No git branch**: Script shows nothing when not in a git repository
**Usage shows 0%**: API call failed. Check:
- Keychain has "Claude Code-credentials"
- Internet connection active
- API endpoint accessible
**Slow status line**: Increase `cache_max_age` in the script to reduce API calls
**Reconfigure**: Run `/custom-statusline` again to change your preferences
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.