From 1b939ccf9b723ceb5b286179137abc20ed1ae093 Mon Sep 17 00:00:00 2001 From: abhishekbhakat Date: Fri, 13 Feb 2026 17:16:39 +0530 Subject: [PATCH] Fix typos and improve clarity in subagent coding guidelines --- .factory/rules/subagents.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.factory/rules/subagents.md b/.factory/rules/subagents.md index 499e2c9..4d35cff 100644 --- a/.factory/rules/subagents.md +++ b/.factory/rules/subagents.md @@ -4,7 +4,10 @@ Always use prep time to understand where you can leverage your available subagen ## Coding with subagents -The specialized coder subagent shall handle code generation. And even code refactoring. +- The specialized coder subagent shall handle code generation. And even code refactoring. +- The coder agent is not good at editing Markdown, YAML, JSON, or other structured data files. So you should handle those. +- Alsways start providing relavant files and as much context as possible to the subagents. Don't hesitate, the more rich context you provide, the better the output will be. +- None of the subagents use `tree --gitignore` command instictively, so you should ask them to do it or ptovide relevant file tree yourself. This is especially important for the coder subagent, as it will help it to understand the project structure and dependencies. ### Productivity Trick