azclaude-copilot 0.4.39 → 0.5.0

package/templates/scripts/statusline.sh

@@ -0,0 +1,105 @@
+#!/bin/bash
+# AZCLAUDE statusline — auto-installed by setup
+# Shows: model | context % (color-coded) | rate limit | session time | lines changed
+# Updates automatically after every turn — no manual action needed.
+#
+# Data arrives as JSON on stdin from Claude Code.
+# Requires: jq (falls back to basic output if missing)
+
+input=$(cat)
+
+# ── Fallback if jq is not available ──────────────────────────────────────────
+if ! command -v jq &>/dev/null; then
+  echo "[AZCLAUDE] install jq for statusline metrics"
+  exit 0
+fi
+
+# ── Extract metrics ──────────────────────────────────────────────────────────
+MODEL=$(echo "$input" | jq -r '.model.display_name // "Claude"')
+CTX_PCT=$(echo "$input" | jq -r '.context_window.used_percentage // 0' | cut -d. -f1)
+CTX_SIZE=$(echo "$input" | jq -r '.context_window.context_window_size // 0')
+COST=$(echo "$input" | jq -r '.cost.total_cost_usd // 0')
+DURATION_MS=$(echo "$input" | jq -r '.cost.total_duration_ms // 0')
+LINES_ADD=$(echo "$input" | jq -r '.cost.total_lines_added // 0')
+LINES_DEL=$(echo "$input" | jq -r '.cost.total_lines_removed // 0')
+RATE_5H=$(echo "$input" | jq -r '.rate_limits.five_hour.used_percentage // -1' | cut -d. -f1)
+
+# ── Format duration ──────────────────────────────────────────────────────────
+DURATION_SEC=$((DURATION_MS / 1000))
+MINS=$((DURATION_SEC / 60))
+SECS=$((DURATION_SEC % 60))
+
+# ── Format context size (200k / 1M) ─────────────────────────────────────────
+if [ "$CTX_SIZE" -ge 1000000 ] 2>/dev/null; then
+  CTX_LABEL="1M"
+elif [ "$CTX_SIZE" -ge 100000 ] 2>/dev/null; then
+  CTX_LABEL="200k"
+else
+  CTX_LABEL="${CTX_SIZE}"
+fi
+
+# ── Color codes ──────────────────────────────────────────────────────────────
+GREEN="\033[32m"
+YELLOW="\033[33m"
+RED="\033[31m"
+DIM="\033[2m"
+BOLD="\033[1m"
+RESET="\033[0m"
+
+# ── Context bar (10 segments) ────────────────────────────────────────────────
+FILLED=$((CTX_PCT * 10 / 100))
+EMPTY=$((10 - FILLED))
+BAR=""
+[ "$FILLED" -gt 0 ] && printf -v FILL "%${FILLED}s" && BAR="${FILL// /\u2593}"
+[ "$EMPTY" -gt 0 ] && printf -v PAD "%${EMPTY}s" && BAR="${BAR}${PAD// /\u2591}"
+
+# ── Color thresholds ─────────────────────────────────────────────────────────
+if [ "$CTX_PCT" -ge 80 ]; then
+  CTX_COLOR="$RED"
+  CTX_WARN=" COMPACT SOON"
+elif [ "$CTX_PCT" -ge 60 ]; then
+  CTX_COLOR="$YELLOW"
+  CTX_WARN=""
+else
+  CTX_COLOR="$GREEN"
+  CTX_WARN=""
+fi
+
+# ── Build line 1: model + context bar ────────────────────────────────────────
+LINE1="${DIM}[${RESET}${BOLD}${MODEL}${RESET}${DIM}]${RESET} "
+LINE1+="${CTX_COLOR}${BAR} ${CTX_PCT}%${RESET}"
+LINE1+="${DIM}/${CTX_LABEL}${RESET}"
+LINE1+="${RED}${CTX_WARN}${RESET}"
+
+# ── Build line 2: rate limit + time + lines + cost ───────────────────────────
+LINE2=""
+
+# Rate limit (only show if available, i.e. Pro/Max subscription)
+if [ "$RATE_5H" -ge 0 ] 2>/dev/null; then
+  if [ "$RATE_5H" -ge 80 ]; then
+    LINE2+="${RED}Rate: ${RATE_5H}%${RESET} "
+  elif [ "$RATE_5H" -ge 50 ]; then
+    LINE2+="${YELLOW}Rate: ${RATE_5H}%${RESET} "
+  else
+    LINE2+="${DIM}Rate: ${RATE_5H}%${RESET} "
+  fi
+  LINE2+="${DIM}|${RESET} "
+fi
+
+# Duration
+LINE2+="${DIM}${MINS}m${SECS}s${RESET}"
+
+# Lines changed
+if [ "$LINES_ADD" -gt 0 ] || [ "$LINES_DEL" -gt 0 ]; then
+  LINE2+=" ${DIM}|${RESET} ${GREEN}+${LINES_ADD}${RESET}${DIM}/${RESET}${RED}-${LINES_DEL}${RESET}"
+fi
+
+# Cost (only show if > 0, i.e. API billing)
+if [ "$(echo "$COST > 0" | bc 2>/dev/null)" = "1" ]; then
+  COST_FMT=$(printf '$%.2f' "$COST")
+  LINE2+=" ${DIM}|${RESET} ${COST_FMT}"
+fi
+
+# ── Output ───────────────────────────────────────────────────────────────────
+echo -e "$LINE1"
+echo -e "$LINE2"

package/templates/skills/agent-creator/SKILL.md

@@ -11,10 +11,13 @@ description: >
   checking agent overlap, or pairing agents with skills. Even if the user
   doesn't say "agent", use this when they describe a workstream that needs
   isolation, parallelism, or specialized context.
+tags: [agent, create, subagent, specialized, 5-layer]
 ---
 
 # Agent Creator
 
+<instructions>
+
 Creates production-quality Claude Code agents following the 5-layer structure.
 An agent is an OWNERSHIP BOUNDARY — not a persona. If two agents can do the
 same task, one shouldn't exist.
@@ -36,6 +39,12 @@ Before diving into the full workflow, verify these 5 essentials:
 
 ## Workflow
 
+0. **Web research (MANDATORY for domain-specific agents).** Before writing any agent content:
+   - WebSearch for "{domain} best practices {current year}" — the agent's Layer 5 (Domain) must reflect current reality
+   - WebSearch for "{technology} API changes" — catch breaking changes, deprecations, new patterns
+   - WebFetch official docs for any technology the agent will work with
+   - **Why:** Claude hallucinates outdated APIs. An agent with stale domain knowledge makes confident wrong decisions.
+
 1. **Determine boundaries.** Run co-change analysis to find what changes together:
    ```bash
    bash .claude/skills/agent-creator/scripts/scaffold.sh --analyze
@@ -89,3 +98,5 @@ Before diving into the full workflow, verify these 5 essentials:
 For the complete agent engineering guide: `references/agent-engineering-guide.md`
 For the quality checklist: `references/quality-checklist.md`
 For a sample agent output: `examples/sample-agent.md`
+
+</instructions>

package/templates/skills/architecture-advisor/SKILL.md

@@ -13,10 +13,12 @@ description: >
   architecture milestone, or /debate needs evidence for a technical decision.
   Even if the user doesn't say "architecture", use this when the task involves
   choosing between competing approaches for a project of a specific size or domain.
+tags: [architecture, pattern, scale, database, rendering, framework]
 ---
 
 # Architecture Advisor
 
+<instructions>
 Claude already knows every framework, pattern, and language. This skill doesn't teach
 HOW to code — it guides WHEN to use WHICH approach based on project context and evidence.
 
@@ -65,22 +67,6 @@ Classify:
 
 For the detected scale, apply the matching evidence from `references/decision-matrices.md`.
 
-**Output format:**
-```
-## Decision: {question}
-
-Context: {SMALL|MEDIUM|LARGE} project, {domain}, {N} files, {N} contributors
-
-### Recommendation: {choice}
-Evidence: {why this is right for THIS context}
-
-### When to reconsider
-{thresholds that would change the answer}
-
-### Anti-pattern warning
-{what NOT to do at this scale}
-```
-
 ## Step 3: Record Decision
 
 Append to `.claude/memory/decisions.md`:
@@ -105,3 +91,22 @@ Append to `.claude/memory/decisions.md`:
 For complete decision matrices: `references/decision-matrices.md`
 For rendering strategy guide: `references/rendering-decisions.md`
 For database selection guide: `references/database-decisions.md`
+</instructions>
+
+<output_format>
+**Output format:**
+```
+## Decision: {question}
+
+Context: {SMALL|MEDIUM|LARGE} project, {domain}, {N} files, {N} contributors
+
+### Recommendation: {choice}
+Evidence: {why this is right for THIS context}
+
+### When to reconsider
+{thresholds that would change the answer}
+
+### Anti-pattern warning
+{what NOT to do at this scale}
+```
+</output_format>

package/templates/skills/debate/SKILL.md

@@ -10,10 +10,13 @@ description: >
   when the user presents two options and seems uncertain which to pick,
   even if they don't explicitly ask for a debate.
 disable-model-invocation: true
+tags: [decision, tradeoff, comparison, architecture, acemad]
 ---
 
 # Structured Debate [AceMAD]
 
+<instructions>
+
 Use when a decision is genuinely uncertain, multi-criteria, and wrong choice costs real time.
 Do NOT use for routine decisions — Claude's direct answer is faster and equally good.
 
@@ -34,3 +37,5 @@ Do NOT use for routine decisions — Claude's direct answer is faster and equall
 - If margin < 10 points: run synthesis reversed to check position bias
 
 For the full 7-phase protocol with examples, read `references/acemad-protocol.md`.
+
+</instructions>

package/templates/skills/env-scanner/SKILL.md

@@ -8,10 +8,13 @@ description: >
   environment discovery. Also use when entering a project for the first time,
   when /setup runs, when debugging dependency issues, or when you need to
   understand the project structure before making changes.
+tags: [environment, stack, framework, detection, setup]
 ---
 
 # Environment Scanner
 
+<instructions>
+
 ## How
 
 Run the env scanner script for structured JSON output:
@@ -39,3 +42,5 @@ If `.claude/scripts/env-scan.sh` doesn't exist, scan manually:
 2. Check for package.json, pyproject.toml, Cargo.toml, go.mod
 3. `git log --oneline -5`
 4. Read README.md first 20 lines
+
+</instructions>

package/templates/skills/frontend-design/SKILL.md

@@ -12,10 +12,12 @@ description: >
   Do NOT trigger when: user asks to review existing UI (use code-reviewer),
   request is code-only with no visual deliverable, or a strict brand guide
   already defines all visual decisions.
+tags: [frontend, ui, design, react, landing, dashboard, visual]
 ---
 
 # Frontend Design Skill
 
+<instructions>
 Produces interfaces that are visually distinctive and production-ready.
 The core constraint: every design choice must be intentional, not default.
 
@@ -143,6 +145,7 @@ If a request conflicts with constitution.md visual constraints:
 - Mobile-responsive: no horizontal scroll on 375px viewport, tap targets >= 44px
 - No broken links, placeholder `#` hrefs without intent, or `TODO` comments in shipped code
 - Images: use aspect-ratio, width/height attributes, or explicit dimensions to prevent layout shift
+</instructions>
 
 ---
 
@@ -150,6 +153,7 @@ If a request conflicts with constitution.md visual constraints:
 
 When done, output:
 
+<output_format>
 ```
 Direction: {chosen direction}
 Entry file: {absolute path to index.html}
@@ -163,6 +167,7 @@ wc -l index.html
 ```
 
 Show the actual line count. Do not estimate.
+</output_format>
 
 ## References
 

package/templates/skills/mcp/SKILL.md

@@ -11,10 +11,12 @@ description: >
   Claude Code, or asks which MCP works best for their stack.
   Do NOT trigger when: user is asking about AZCLAUDE's own security scanner for
   MCP configs (use security skill). Do NOT trigger for generic npm package questions.
+tags: [mcp, server, tool, integration, context7, playwright]
 ---
 
 # MCP Integration
 
+<instructions>
 MCP servers extend Claude Code with live capabilities: real-time docs, web search,
 browser control, database access. AZCLAUDE recommends MCPs based on your stack —
 it never bundles them (zero-dep rule).
@@ -110,3 +112,4 @@ claude mcp get context7            # shows context7 config
 Then test in Claude Code: ask Claude "use context7 to get the latest React docs" — if it returns live docs, it's working.
 
 For full MCP catalog: `references/mcp-catalog.md`
+</instructions>

package/templates/skills/security/SKILL.md

@@ -9,10 +9,12 @@ description: >
   or any work involving sensitive data. Also use before any /ship operation,
   when editing ~/.claude/settings.json, or when importing skills from
   external sources.
+tags: [security, credentials, secrets, hooks, deploy, audit]
 ---
 
 # Security Model
 
+<instructions>
 AZCLAUDE runs code and modifies files. A 4-hook pipeline provides layered runtime protection.
 
 ## 4-Hook Runtime Pipeline
@@ -91,3 +93,4 @@ Fires on **every** prompt (before session gate). Filters from goals.md + checkpo
 - Run `/sentinel --supply-chain` for full dependency scan
 
 For full details: `references/security-details.md`
+</instructions>

package/templates/skills/session-guard/SKILL.md

@@ -8,10 +8,12 @@ description: >
   resuming a session, when context feels incomplete, when you can't remember
   what was being worked on, or when the user asks "where were we". Always
   consult this skill before ending any session, even short ones.
+tags: [session, persist, goals, checkpoint, continuity]
 ---
 
 # Session Guard
 
+<instructions>
 You are in an AZCLAUDE-managed project. Session state survives context compaction
 through goals.md and checkpoints — but only if they're written.
 
@@ -31,3 +33,4 @@ Keep it brief — one line, not a lecture:
 - "Context was compacted — re-reading goals.md for continuity."
 
 Do NOT block the user's work. This is a gentle nudge, not a gate.
+</instructions>

package/templates/skills/skill-creator/SKILL.md

@@ -9,10 +9,13 @@ description: >
   or when the user describes a repeated workflow that should be automated.
   Even if the user doesn't say "skill", use this when they describe a behavior
   Claude should learn for a specific domain or task pattern.
+tags: [skill, create, template, workflow, automation]
 ---
 
 # Skill Creator
 
+<instructions>
+
 Creates production-quality skills that follow the Anthropic skill spec.
 A skill is a RECIPE that changes Claude's behavior — not documentation, not a prompt.
 
@@ -34,6 +37,13 @@ Before diving into the full workflow, verify these 5 essentials:
 
 1. **Capture intent.** Ask: what task does this skill handle? What triggers it?
 
+1b. **Web research (MANDATORY for domain skills).** Before writing any skill content:
+   - WebSearch for "{domain} best practices {current year}" — get current patterns, not stale training data
+   - WebSearch for "{domain} common mistakes" — build the anti-patterns section from real failures
+   - WebFetch the official docs for any API/library the skill covers — get correct method names, parameters, versions
+   - Include findings in the skill body and references/ — the skill must reflect CURRENT reality, not training-data memory
+   - **Why:** Claude hallucinates outdated APIs. A skill built on stale knowledge is worse than no skill.
+
 2. **Generate the directory:**
    ```bash
    bash .claude/skills/skill-creator/scripts/scaffold.sh SKILL_NAME
@@ -80,3 +90,5 @@ Before diving into the full workflow, verify these 5 essentials:
 For the complete skill engineering guide: `references/skill-engineering-guide.md`
 For the quality checklist: `references/quality-checklist.md`
 For a sample skill output: `examples/sample-skill.md`
+
+</instructions>

package/templates/skills/test-first/SKILL.md

@@ -8,10 +8,13 @@ description: >
   or any variation of testing-related work. Checks if the project uses TDD
   before enforcing test-first. Detects the test framework automatically.
   Does not apply to non-code tasks like documentation or configuration.
+tags: [tdd, testing, tests, coverage, red-green-refactor]
 ---
 
 # Test-First
 
+<instructions>
+
 ## Check before enforcing
 
 TDD is opt-in. Check BOTH signals:
@@ -39,3 +42,5 @@ Check the project's existing framework before writing any test:
 - `go.mod` → go test
 
 Use what's already there. Never introduce a new framework without asking.
+
+</instructions>