القائمة
Set descriptive names for Aura HUD session display
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used when the user asks to "check consistency", "find conflicts", "consistency check", "conflict detection", "incremental check", "full check", "check my specs", "validate BDD specs", "check for contradictions", or wants to detect and resolve conflicts between BDD spec files (.feature files, BDRs, and glossary).
This skill should be used when the user asks to "discover a feature", "explore behaviour", "write a feature file", "BDD discovery", "formulate BDD specs", "example mapping", "start a discovery session", "resume a discovery session", "explore a user story", or wants to interactively explore and define system behaviour using BDD patterns.
Initialize agent documentation structure (docs/agents/) for a project. Use when the user asks to "initialize agent docs", "bootstrap docs/agents/", or "set up project knowledge files".
Capture learnings from current session into agent documentation. Use when the user asks to "update project knowledge", "capture session learnings", or "record improvements or postmortems".
Use this skill when the user explicitly asks for a handoff note, resume checkpoint, or transfer summary for ongoing work.
Engineering workflow — reasoning, plan/code modes, code quality, git conventions
| name | session-naming |
| description | Set descriptive names for Aura HUD session display |
| version | 2.0.0 |
Set descriptive session names in the Aura HUD to help users track what each session is working on.
aura set-name "<name>"
Aura does not read aura set-name ... from arbitrary terminals. The HUD name updates only when Aura observes this command inside an agent event stream.
Bash tool (hooks capture tool_input.command).exec_command tool (it appears in the rollout JSONL).If you run aura set-name ... in another terminal, you'll see local stdout but the HUD will not change.
The session name should describe what we're trying to accomplish. For larger tasks with distinct phases, use Task - Step format.
Use Task - Step format when:
| Rule | Good | Bad |
|---|---|---|
| 2-6 words | "Fix Login Auth Flow" | "Fix the authentication bug in the login system" |
| Start with verb | "Add Export" | "Export Feature" |
| No filler words | "Refactor API" | "Refactor the API Layer" |
| No paths/files | "Update Config" | "Update src/config.ts" |
| No jargon | "Speed Up Search" | "Optimize O(n^2)" |
| User Request | Session Name |
|---|---|
| "Fix the bug where login fails" | "Fix Login" |
| "Add a button to export data" | "Add Export" |
| "Refactor the authentication code" | "Refactor Auth" |
| "Add dark mode to the app" | "Add Dark Mode" |
| "Help me understand this code" | (don't set) |
| "Run the tests" | (don't set) |
| Large feature with phases | "Add Auth - Design" -> "Add Auth - Implement" -> "Add Auth - Test" |
Fix [Thing] -> "Fix Login", "Fix Cart"Add [Thing] -> "Add Export", "Add Dark Mode"Refactor [Area] -> "Refactor Auth", "Refactor API"Update [Thing] -> "Update Deps", "Update Config"[Task] - [Step] -> "Add Auth - Design", "Add Auth - Implement", "Add Auth - Test"