القائمة
Use when the developer is implementing, modifying, or fixing any AI feature in this project
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | working-with-ai-agent |
| description | Use when the developer is implementing, modifying, or fixing any AI feature in this project |
AiTaskGenerateChatHub.cs — entry point for both text messages and voice input (SendMessage, TranscribeAudio); manages session lifecycleAiTaskGenerateService.cs — init, run, error mappingTaskGenerationTools.cs — the tool methods the agent can invokeAiTaskGeneratorPrompts.cs — system promptProduct rationale and decision history for this feature live in the private repo — use the private-context skill to find and read it before making design decisions.
The AiTaskGenerateChatHub SignalR hub is the entry point — both text (SendMessage) and voice (TranscribeAudio → transcribe → SendMessage) funnel through the same path:
SignalR hub → DateTimeResolveService.Resolve (pre-process dates) → AiTaskGenerateService.GenerateAiResponse → context.Agent.RunAsync(...) → AI invokes tools that mutate context.Tasks / context.Notes.
State lives in AiChatContext (Agent + Session + Tools + Tasks + Notes + TimeZone), created once in OnConnectedAsync and stored per SignalR connection in Context.Items["ChatContext"].
TaskGenerationTools.cs with [Description] on the method and every parameter. These descriptions are the model's instructions; write them as if the AI is the only reader. Increment ToolCallCount at the top.[Description], not the prompt.Use when the user wants to open a pull request — e.g. "create me a PR", "open a PR", "raise a PR" — or wants to fix the description or release note on an existing PR.
Use when starting feature work, making design/product decisions, or needing the rationale or history behind a feature — checks the private companion repo for planning notes and decision records.
Use when the user wants to capture an idea, problem, or task as a PBI in the Blotz backlog — e.g. "create a PBI for this", "add this to the backlog".
Use when the developer is adding, modifying, or fixing backend API logic — endpoints, handlers, domain entities, events, or anything in `blotztask-api/`.
Use when the developer is adding, renaming, or changing a database field, entity, or relationship — anything that produces an EF Core migration.
Use before writing, adding, or modifying any test in blotztask-test/.