status-line-customization

# Status Line Meta Skill

> ## 🚨 MANDATORY: Invoke docs-management First
>
> **STOP - Before providing ANY response about status line configuration:**
>
> 1. **INVOKE** `docs-management` skill
> 2. **QUERY** for the user's specific topic
> 3. **BASE** all responses EXCLUSIVELY on official documentation loaded
>
> **Skipping this step results in outdated or incorrect information.**
>
> ### Verification Checkpoint
>
> Before responding, verify:
>
> - [ ] Did I invoke docs-management skill?
> - [ ] Did official documentation load?
> - [ ] Is my response based EXCLUSIVELY on official docs?
>
> If ANY checkbox is unchecked, STOP and invoke docs-management first.

## Overview

Central authority for Claude Code status line configuration. This skill uses **100% delegation to docs-management** - it contains NO duplicated official documentation.

**Architecture:** Pure delegation with keyword registry. All official documentation is accessed via docs-management skill queries.

## When to Use This Skill

**Keywords:** status line, statusline, /statusline command, custom status line, status line configuration, statusLine setting, status line script, status line JSON input, model display, workspace info, cost tracking display, session info display, ANSI colors status line, git-aware status line, PS1-style prompt

**Use this skill when:**

- Creating custom status lines
- Configuring status line settings
- Understanding status line JSON input structure
- Writing status line scripts (Bash, Python, Node.js)
- Adding git information to status line
- Styling status lines with ANSI colors
- Troubleshooting status line issues
- Displaying model, cost, or workspace information

## Keyword Registry for docs-management Queries

Use these keywords when querying docs-management skill for official documentation:

### Status Line Fundamentals

| Topic | Keywords |
| --- | --- |
| Overview | "status line", "statusline", "custom status line" |
| Purpose | "status line purpose", "contextual info