aiblueprint-cli 1.4.59 → 1.4.60

package/agents-config/scripts/statusline/statusline.config.json

@@ -0,0 +1,79 @@
+{
+	"features": {
+		"usageLimits": false,
+		"spendTracking": false
+	},
+	"oneLine": true,
+	"showSonnetModel": false,
+	"pathDisplayMode": "truncated",
+	"git": {
+		"enabled": true,
+		"showBranch": true,
+		"showDirtyIndicator": true,
+		"showChanges": false,
+		"showStaged": true,
+		"showUnstaged": true
+	},
+	"separator": "•",
+	"session": {
+		"infoSeparator": null,
+		"cost": { "enabled": false, "format": "decimal1" },
+		"duration": { "enabled": true },
+		"tokens": { "enabled": true, "showMax": false, "showDecimals": false },
+		"percentage": {
+			"enabled": true,
+			"showValue": true,
+			"progressBar": {
+				"enabled": true,
+				"length": 10,
+				"style": "braille",
+				"color": "progressive",
+				"background": "none"
+			}
+		}
+	},
+	"context": {
+		"usePayloadContextWindow": true,
+		"maxContextTokens": 200000,
+		"autocompactBufferTokens": 45000,
+		"useUsableContextOnly": true,
+		"overheadTokens": 0
+	},
+	"limits": {
+		"enabled": false,
+		"showTimeLeft": false,
+		"showPacingDelta": false,
+		"cost": { "enabled": false, "format": "decimal1" },
+		"percentage": {
+			"enabled": false,
+			"showValue": false,
+			"progressBar": {
+				"enabled": false,
+				"length": 10,
+				"style": "braille",
+				"color": "progressive",
+				"background": "none"
+			}
+		}
+	},
+	"weeklyUsage": {
+		"enabled": false,
+		"showTimeLeft": false,
+		"showPacingDelta": false,
+		"cost": { "enabled": false, "format": "decimal1" },
+		"percentage": {
+			"enabled": false,
+			"showValue": false,
+			"progressBar": {
+				"enabled": false,
+				"length": 10,
+				"style": "braille",
+				"color": "progressive",
+				"background": "none"
+			}
+		}
+	},
+	"dailySpend": {
+		"cost": { "enabled": false, "format": "decimal1" }
+	}
+}

package/agents-config/scripts/statusline/test-with-fixtures.ts

@@ -0,0 +1,37 @@
+#!/usr/bin/env bun
+
+import { readFile } from "node:fs/promises";
+import { join } from "node:path";
+import { $ } from "bun";
+
+const fixtureArg = process.argv[2] || "test-input.json";
+const fixturePath = join(
+	import.meta.dir,
+	"fixtures",
+	fixtureArg.endsWith(".json") ? fixtureArg : `${fixtureArg}.json`,
+);
+
+try {
+	const fixture = await readFile(fixturePath, "utf-8");
+
+	console.log("📊 Testing statusline with fixture:", fixtureArg);
+	console.log("─".repeat(60));
+
+	const result =
+		await $`echo ${fixture} | bun ${join(import.meta.dir, "src/index.ts")}`.quiet();
+
+	console.log(result.stdout.toString());
+	console.log("─".repeat(60));
+	console.log("✅ Test complete!");
+} catch (error) {
+	if ((error as any).code === "ENOENT") {
+		console.error(`❌ Fixture not found: ${fixturePath}`);
+		console.log("\nAvailable fixtures:");
+		const files =
+			await $`ls ${join(import.meta.dir, "fixtures")}/*.json`.quiet();
+		console.log(files.stdout.toString());
+	} else {
+		console.error("❌ Error:", error);
+	}
+	process.exit(1);
+}

package/agents-config/scripts/statusline/test.ts

@@ -0,0 +1,20 @@
+#!/usr/bin/env bun
+
+import { join } from "node:path";
+import { $ } from "bun";
+
+const fixtureFile = process.argv[2] || "fixtures/test-input.json";
+const fixtureFullPath = join(import.meta.dir, fixtureFile);
+
+console.log(`\n📝 Testing with fixture: ${fixtureFile}\n`);
+
+try {
+	const content = await Bun.file(fixtureFullPath).text();
+	const result = await $`echo ${content} | bun run src/index.ts`.text();
+
+	console.log(result);
+	console.log("\n✅ Test completed successfully!\n");
+} catch (error) {
+	console.error("❌ Test failed:", error);
+	process.exit(1);
+}

package/agents-config/scripts/statusline/tsconfig.json

@@ -0,0 +1,27 @@
+{
+	"compilerOptions": {
+		// Enable latest features
+		"lib": ["ESNext", "DOM"],
+		"target": "ESNext",
+		"module": "ESNext",
+		"moduleDetection": "force",
+		"jsx": "react-jsx",
+		"allowJs": true,
+
+		// Bundler mode
+		"moduleResolution": "bundler",
+		"allowImportingTsExtensions": true,
+		"verbatimModuleSyntax": true,
+		"noEmit": true,
+
+		// Best practices
+		"strict": true,
+		"skipLibCheck": true,
+		"noFallthroughCasesInSwitch": true,
+
+		// Some stricter flags (disabled by default)
+		"noUnusedLocals": false,
+		"noUnusedParameters": false,
+		"noPropertyAccessFromIndexSignature": false
+	}
+}

package/agents-config/scripts/tsconfig.json

@@ -0,0 +1,27 @@
+{
+	"compilerOptions": {
+		// Enable latest features
+		"lib": ["ESNext", "DOM"],
+		"target": "ESNext",
+		"module": "ESNext",
+		"moduleDetection": "force",
+		"jsx": "react-jsx",
+		"allowJs": true,
+
+		// Bundler mode
+		"moduleResolution": "bundler",
+		"allowImportingTsExtensions": true,
+		"verbatimModuleSyntax": true,
+		"noEmit": true,
+
+		// Best practices
+		"strict": true,
+		"skipLibCheck": true,
+		"noFallthroughCasesInSwitch": true,
+
+		// Some stricter flags (disabled by default)
+		"noUnusedLocals": false,
+		"noUnusedParameters": false,
+		"noPropertyAccessFromIndexSignature": false
+	}
+}

package/agents-config/skills/{subagent-creator → agents-managers}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: subagent-creator
-description: Expert guidance for creating, building, and using Claude Code subagents and the Task tool. Use when working with subagents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.
+name: agents-managers
+description: Expert guidance for creating, building, and using Claude Code agents and the Task tool. Use when working with agents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.
 ---
 
 <objective>
-Subagents are specialized Claude instances that run in isolated contexts with focused roles and limited tool access. This skill teaches you how to create effective subagents, write strong system prompts, configure tool access, and orchestrate multi-agent workflows using the Task tool.
+Agents are specialized Claude instances that run in isolated contexts with focused roles and limited tool access. This skill teaches you how to create effective agents, write strong system prompts, configure tool access, and orchestrate multi-agent workflows using the Task tool.
 
-Subagents enable delegation of complex tasks to specialized agents that operate autonomously without user interaction, returning their final output to the main conversation.
+Agents enable delegation of complex tasks to specialized agents that operate autonomously without user interaction, returning their final output to the main conversation.
 </objective>
 
 <quick_start>
@@ -15,12 +15,12 @@ Subagents enable delegation of complex tasks to specialized agents that operate
 1. Run `/agents` command
 2. Select "Create New Agent"
 3. Choose project-level (`.claude/agents/`) or user-level (`~/.claude/agents/`)
-4. Define the subagent:
+4. Define the agent:
    - **name**: lowercase-with-hyphens
-   - **description**: When should this subagent be used?
+   - **description**: When should this agent be used?
    - **tools**: Optional comma-separated list (inherits all if omitted)
    - **model**: Optional (`sonnet`, `opus`, `haiku`, or `inherit`)
-5. Write the system prompt (the subagent's instructions)
+5. Write the system prompt (the agent's instructions)
    </workflow>
 
 <example>
@@ -59,7 +59,7 @@ Provide specific, actionable feedback with file:line references.
 | **User** | `~/.claude/agents/` | All projects | Lower |
 | **Plugin** | Plugin's `agents/` dir | All projects | Lowest |
 
-Project-level subagents override user-level when names conflict.
+Project-level agents override user-level when names conflict.
 </file_structure>
 
 <configuration>
@@ -70,8 +70,8 @@ Project-level subagents override user-level when names conflict.
 
 <field name="description">
 - Natural language description of purpose
-- Include when Claude should invoke this subagent
-- Used for automatic subagent selection
+- Include when Claude should invoke this agent
+- Used for automatic agent selection
 </field>
 
 <field name="tools">
@@ -83,26 +83,26 @@ Project-level subagents override user-level when names conflict.
 <field name="model">
 - `sonnet`, `opus`, `haiku`, or `inherit`
 - `inherit`: uses same model as main conversation
-- If omitted: defaults to configured subagent model (usually sonnet)
+- If omitted: defaults to configured agent model (usually sonnet)
 </field>
 </configuration>
 
 <execution_model>
 <critical_constraint>
-**Subagents are black boxes that cannot interact with users.**
+**Agents are black boxes that cannot interact with users.**
 
-Subagents run in isolated contexts and return their final output to the main conversation. They:
+Agents run in isolated contexts and return their final output to the main conversation. They:
 - ✅ Can use tools like Read, Write, Edit, Bash, Grep, Glob
 - ✅ Can access MCP servers and other non-interactive tools
 - ❌ **Cannot use AskUserQuestion** or any tool requiring user interaction
 - ❌ **Cannot present options or wait for user input**
-- ❌ **User never sees subagent's intermediate steps**
+- ❌ **User never sees agent's intermediate steps**
 
-The main conversation sees only the subagent's final report/output.
+The main conversation sees only the agent's final report/output.
 </critical_constraint>
 
 <workflow_design>
-**Designing workflows with subagents:**
+**Designing workflows with agents:**
 
 Use **main chat** for:
 - Gathering requirements from user (AskUserQuestion)
@@ -110,7 +110,7 @@ Use **main chat** for:
 - Any task requiring user confirmation/input
 - Work where user needs visibility into progress
 
-Use **subagents** for:
+Use **agents** for:
 - Research tasks (API documentation lookup, code analysis)
 - Code generation based on pre-defined requirements
 - Analysis and reporting (security review, test coverage)
@@ -121,11 +121,11 @@ Use **subagents** for:
 
 Main Chat: Ask user for requirements (AskUserQuestion)
 ↓
-Subagent: Research API and create documentation (no user interaction)
+Agent: Research API and create documentation (no user interaction)
 ↓
 Main Chat: Review research with user, confirm approach
 ↓
-Subagent: Generate code based on confirmed plan
+Agent: Generate code based on confirmed plan
 ↓
 Main Chat: Present results, handle testing/deployment
 
@@ -135,7 +135,7 @@ Main Chat: Present results, handle testing/deployment
 
 <system_prompt_guidelines>
 <principle name="be_specific">
-Clearly define the subagent's role, capabilities, and constraints.
+Clearly define the agent's role, capabilities, and constraints.
 </principle>
 
 <principle name="use_pure_xml_structure">
@@ -171,20 +171,20 @@ You are a senior code reviewer specializing in security.
 </principle>
 
 <principle name="task_specific">
-Tailor instructions to the specific task domain. Don't create generic "helper" subagents.
+Tailor instructions to the specific task domain. Don't create generic "helper" agents.
 
 ❌ Bad: "You are a helpful assistant that helps with code"
 ✅ Good: "You are a React component refactoring specialist. Analyze components for hooks best practices, performance anti-patterns, and accessibility issues."
 </principle>
 </system_prompt_guidelines>
 
-<subagent_xml_structure>
-Subagent.md files are system prompts consumed only by Claude. Like skills and slash commands, they should use pure XML structure for optimal parsing and token efficiency.
+<agent_xml_structure>
+Agent.md files are system prompts consumed only by Claude. Like skills and slash commands, they should use pure XML structure for optimal parsing and token efficiency.
 
 <recommended_tags>
-Common tags for subagent structure:
+Common tags for agent structure:
 
-- `<role>` - Who the subagent is and what it does
+- `<role>` - Who the agent is and what it does
 - `<constraints>` - Hard rules (NEVER/MUST/ALWAYS)
 - `<focus_areas>` - What to prioritize
 - `<workflow>` - Step-by-step process
@@ -194,55 +194,55 @@ Common tags for subagent structure:
   </recommended_tags>
 
 <intelligence_rules>
-**Simple subagents** (single focused task):
+**Simple agents** (single focused task):
 
 - Use role + constraints + workflow minimum
 - Example: code-reviewer, test-runner
 
-**Medium subagents** (multi-step process):
+**Medium agents** (multi-step process):
 
 - Add workflow steps, output_format, success_criteria
 - Example: api-researcher, documentation-generator
 
-**Complex subagents** (research + generation + validation):
+**Complex agents** (research + generation + validation):
 
 - Add all tags as appropriate including validation, examples
 - Example: mcp-api-researcher, comprehensive-auditor
   </intelligence_rules>
 
 <critical_rule>
-**Remove ALL markdown headings (##, ###) from subagent body.** Use semantic XML tags instead.
+**Remove ALL markdown headings (##, ###) from agent body.** Use semantic XML tags instead.
 
 Keep markdown formatting WITHIN content (bold, italic, lists, code blocks, links).
 
-For XML structure principles and token efficiency details, see @skills/create-agent-skills/references/use-xml-tags.md - the same principles apply to subagents.
+For XML structure principles and token efficiency details, see @skills/create-agent-skills/references/use-xml-tags.md - the same principles apply to agents.
 </critical_rule>
-</subagent_xml_structure>
+</agent_xml_structure>
 
 <invocation>
 <automatic>
-Claude automatically selects subagents based on the `description` field when it matches the current task.
+Claude automatically selects agents based on the `description` field when it matches the current task.
 </automatic>
 
 <explicit>
-You can explicitly invoke a subagent:
+You can explicitly invoke a agent:
 
 ```
-> Use the code-reviewer subagent to check my recent changes
+> Use the code-reviewer agent to check my recent changes
 ```
 
 ```
-> Have the test-writer subagent create tests for the new API endpoints
+> Have the test-writer agent create tests for the new API endpoints
 ```
 
 </explicit>
 </invocation>
 
 <background_execution>
-Subagents can run in the background using the `run_in_background` parameter, allowing parallel execution while the main conversation continues.
+Agents can run in the background using the `run_in_background` parameter, allowing parallel execution while the main conversation continues.
 
 <how_it_works>
-**Starting a background subagent:**
+**Starting a background agent:**
 The Task tool accepts `run_in_background: true` to launch agents asynchronously:
 
 ```
@@ -366,24 +366,24 @@ The agent continues with its full previous context preserved.
 <management>
 <using_agents_command>
 Run `/agents` for an interactive interface to:
-- View all available subagents
-- Create new subagents
-- Edit existing subagents
-- Delete custom subagents
+- View all available agents
+- Create new agents
+- Edit existing agents
+- Delete custom agents
 </using_agents_command>
 
 <manual_editing>
-You can also edit subagent files directly:
+You can also edit agent files directly:
 
-- Project: `.claude/agents/subagent-name.md`
-- User: `~/.claude/agents/subagent-name.md`
+- Project: `.claude/agents/agent-name.md`
+- User: `~/.claude/agents/agent-name.md`
   </manual_editing>
   </management>
 
 <reference>
 **Core references**:
 
-**Subagent usage and configuration**: [references/subagents.md](references/subagents.md)
+**Agent usage and configuration**: [references/agents.md](references/agents.md)
 
 - File format and configuration
 - Model selection (Sonnet 4.5 + Haiku 4.5 orchestration)
@@ -392,7 +392,7 @@ You can also edit subagent files directly:
 - **Background execution** (run_in_background, TaskOutput, parallel agents)
 - Complete examples
 
-**Writing effective prompts**: [references/writing-subagent-prompts.md](references/writing-subagent-prompts.md)
+**Writing effective prompts**: [references/writing-agent-prompts.md](references/writing-agent-prompts.md)
 
 - Core principles and XML structure
 - Description field optimization for routing
@@ -439,7 +439,7 @@ You can also edit subagent files directly:
   </reference>
 
 <success_criteria>
-A well-configured subagent has:
+A well-configured agent has:
 
 - Valid YAML frontmatter (name matches file, description includes triggers)
 - Clear role definition in system prompt

package/agents-config/skills/{subagent-creator/references/subagents.md → agents-managers/references/agents.md}

@@ -1,16 +1,16 @@
 <file_format>
-Subagent file structure:
+Agent file structure:
 
 ```markdown
 ---
-name: your-subagent-name
-description: Description of when this subagent should be invoked
+name: your-agent-name
+description: Description of when this agent should be invoked
 tools: tool1, tool2, tool3 # Optional - inherits all tools if omitted
 model: sonnet # Optional - specify model alias or 'inherit'
 ---
 
 <role>
-Your subagent's system prompt using pure XML structure. This defines the subagent's role, capabilities, and approach.
+Your agent's system prompt using pure XML structure. This defines the agent's role, capabilities, and approach.
 </role>
 
 <constraints>
@@ -30,7 +30,7 @@ Step-by-step process for consistency.
 | `name` | Yes | Unique identifier using lowercase letters and hyphens |
 | `description` | Yes | Natural language description of purpose. Include when Claude should invoke this. |
 | `tools` | No | Comma-separated list. If omitted, inherits all tools from main thread |
-| `model` | No | `sonnet`, `opus`, `haiku`, or `inherit`. If omitted, uses default subagent model |
+| `model` | No | `sonnet`, `opus`, `haiku`, or `inherit`. If omitted, uses default agent model |
 </configuration_fields>
 </file_format>
 
@@ -42,35 +42,35 @@ Step-by-step process for consistency.
 | **CLI** | `--agents` flag | Current session | Medium |
 | **Plugin** | Plugin's `agents/` dir | All projects | Lowest |
 
-When subagent names conflict, higher priority takes precedence.
+When agent names conflict, higher priority takes precedence.
 </storage_locations>
 
 <execution_model>
 <black_box_model>
-Subagents execute in isolated contexts without user interaction.
+Agents execute in isolated contexts without user interaction.
 
 **Key characteristics:**
-- Subagent receives input parameters from main chat
-- Subagent runs autonomously using available tools
-- Subagent returns final output/report to main chat
+- Agent receives input parameters from main chat
+- Agent runs autonomously using available tools
+- Agent returns final output/report to main chat
 - User only sees final result, not intermediate steps
 
 **This means:**
-- ✅ Subagents can use Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch
-- ✅ Subagents can access MCP servers (non-interactive tools)
-- ✅ Subagents can make decisions based on their prompt and available data
-- ❌ **Subagents CANNOT use AskUserQuestion**
-- ❌ **Subagents CANNOT present options and wait for user selection**
-- ❌ **Subagents CANNOT request confirmations or clarifications from user**
-- ❌ **User does not see subagent's tool calls or intermediate reasoning**
+- ✅ Agents can use Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch
+- ✅ Agents can access MCP servers (non-interactive tools)
+- ✅ Agents can make decisions based on their prompt and available data
+- ❌ **Agents CANNOT use AskUserQuestion**
+- ❌ **Agents CANNOT present options and wait for user selection**
+- ❌ **Agents CANNOT request confirmations or clarifications from user**
+- ❌ **User does not see agent's tool calls or intermediate reasoning**
 </black_box_model>
 
 <workflow_implications>
-**When designing subagent workflows:**
+**When designing agent workflows:**
 
 Keep user interaction in main chat:
 ```markdown
-# ❌ WRONG - Subagent cannot do this
+# ❌ WRONG - Agent cannot do this
 ---
 name: requirement-gatherer
 description: Gathers requirements from user
@@ -84,9 +84,9 @@ You ask the user questions to gather requirements...
 # ✅ CORRECT - Main chat handles interaction
 Main chat: Uses AskUserQuestion to gather requirements
   ↓
-Launch subagent: Uses requirements to research/build (no interaction)
+Launch agent: Uses requirements to research/build (no interaction)
   ↓
-Main chat: Present subagent results to user
+Main chat: Present agent results to user
 ```
 </workflow_implications>
 </execution_model>
@@ -102,7 +102,7 @@ description: Reviews code for quality and security
 ---
 ```
 
-Subagent has access to all tools, including MCP tools.
+Agent has access to all tools, including MCP tools.
 </inherit_all_tools>
 
 <specific_tools>
@@ -185,18 +185,18 @@ Use `/agents` command to see full list of available tools.
 
 <invocation>
 <automatic>
-Claude automatically selects subagents based on:
+Claude automatically selects agents based on:
 - Task description in user's request
-- `description` field in subagent configuration
+- `description` field in agent configuration
 - Current context
 </automatic>
 
 <explicit>
-Users can explicitly request a subagent:
+Users can explicitly request a agent:
 
 ```
-> Use the code-reviewer subagent to check my recent changes
-> Have the test-runner subagent fix the failing tests
+> Use the code-reviewer agent to check my recent changes
+> Have the test-runner agent fix the failing tests
 ```
 </explicit>
 </invocation>
@@ -204,23 +204,23 @@ Users can explicitly request a subagent:
 <management>
 <using_agents_command>
 **Recommended**: Use `/agents` command for interactive management:
-- View all available subagents (built-in, user, project, plugin)
-- Create new subagents with guided setup
-- Edit existing subagents and their tool access
-- Delete custom subagents
-- See which subagents take priority when names conflict
+- View all available agents (built-in, user, project, plugin)
+- Create new agents with guided setup
+- Edit existing agents and their tool access
+- Delete custom agents
+- See which agents take priority when names conflict
 </using_agents_command>
 
 <direct_file_management>
-**Alternative**: Edit subagent files directly:
-- Project: `.claude/agents/subagent-name.md`
-- User: `~/.claude/agents/subagent-name.md`
+**Alternative**: Edit agent files directly:
+- Project: `.claude/agents/agent-name.md`
+- User: `~/.claude/agents/agent-name.md`
 
 Follow the file format specified above (YAML frontmatter + system prompt).
 </direct_file_management>
 
 <cli_based_configuration>
-**Temporary**: Define subagents via CLI for session-specific use:
+**Temporary**: Define agents via CLI for session-specific use:
 
 ```bash
 claude --agents '{
@@ -237,7 +237,7 @@ Useful for testing configurations before saving them.
 </cli_based_configuration>
 </management>
 
-<example_subagents>
+<example_agents>
 <test_writer>
 ```markdown
 ---
@@ -299,7 +299,7 @@ You are a debugging specialist skilled at root cause analysis and systematic pro
 </debugging_techniques>
 ```
 </debugger>
-</example_subagents>
+</example_agents>
 
 <tool_security>
 <core_principle>
@@ -342,7 +342,7 @@ Scope: Can draft email, cannot access sensitive financial data
 
 <audit_checklist>
 **Tool access audit**:
-- [ ] Does this subagent need Write/Edit, or is Read sufficient?
+- [ ] Does this agent need Write/Edit, or is Read sufficient?
 - [ ] Should it execute code (Bash), or just analyze?
 - [ ] Are all granted tools necessary for the task?
 - [ ] What's the worst-case misuse scenario?
@@ -354,7 +354,7 @@ Scope: Can draft email, cannot access sensitive financial data
 
 <prompt_caching>
 <benefits>
-Prompt caching for frequently-invoked subagents:
+Prompt caching for frequently-invoked agents:
 - **90% cost reduction** on cached tokens
 - **85% latency reduction** for cache hits
 - Cached content: ~10% cost of uncached tokens
@@ -405,13 +405,13 @@ Recent changes: {varies per invocation}
 
 <when_to_use>
 **Best candidates for caching**:
-- Frequently-invoked subagents (multiple times per session)
+- Frequently-invoked agents (multiple times per session)
 - Large, stable prompts (extensive guidelines, examples)
 - Consistent tool definitions across invocations
-- Long-running sessions with repeated subagent use
+- Long-running sessions with repeated agent use
 
 **Not beneficial**:
-- Rarely-used subagents (once per session)
+- Rarely-used agents (once per session)
 - Prompts that change frequently
 - Very short prompts (caching overhead > benefit)
 </when_to_use>
@@ -424,7 +424,7 @@ Recent changes: {varies per invocation}
 - Expires after 5 minutes of non-use (or 1 hour for extended TTL)
 
 **Invalidation triggers**:
-- Subagent prompt modified
+- Agent prompt modified
 - Tool definitions changed
 - Cache TTL expires
 </cache_management>
@@ -550,7 +550,7 @@ Task tool:
 
 <best_practices>
 <be_specific>
-Create task-specific subagents, not generic helpers.
+Create task-specific agents, not generic helpers.
 
 ❌ Bad: "You are a helpful assistant"
 ✅ Good: "You are a React performance optimizer specializing in hooks and memoization"