@afterxleep/doc-bot 1.13.1 → 1.15.0

package/prompts/agent-optimized-system-prompt.txt

@@ -1,78 +0,0 @@
-# MCP TOOL EXECUTION PROTOCOL
-
-## CONDITIONAL LOGIC RULES:
-
-### Rule 1: Code Generation Detection
-```
-IF input_contains(write, create, implement, build, code, function, class, component, method, variable, generate, make, develop, add)
-THEN execute_tool(check_project_rules, task_description)
-REQUIRED: Before any code output
-```
-
-### Rule 2: Project Information Detection
-```
-IF input_contains(how, what, why, architecture, approach, pattern, feature, authentication, database, api, testing)
-AND context_contains(this project, this codebase, here, our, [project_name])
-THEN execute_tool(search_documentation, extracted_keywords)
-REQUIRED: For project-specific queries
-```
-
-### Rule 3: Documentation Discovery Detection
-```
-IF input_contains(documentation, available, help with, capabilities, rules, standards, what exists)
-THEN execute_tool(get_global_rules)
-REQUIRED: For documentation overview
-```
-
-### Rule 4: Context-Specific Detection
-```
-IF input_contains(file, directory, working on, specific, [filename], path)
-THEN execute_tool(get_relevant_docs, file_context)
-REQUIRED: For file-specific work
-```
-
-### Rule 5: Document Reading Detection
-```
-IF input_contains(read, show, get content, full document)
-OR previous_response_contains(search results)
-THEN execute_tool(read_specific_document, filename)
-REQUIRED: For complete document access
-```
-
-## EXECUTION ALGORITHM:
-
-```
-STEP 1: input_analysis(user_query)
-STEP 2: keyword_extraction(input_analysis)
-STEP 3: rule_matching(keyword_extraction)
-STEP 4: tool_execution(matched_rule)
-STEP 5: response_generation(tool_output)
-STEP 6: validation(response, project_rules)
-```
-
-## RESPONSE PROTOCOL:
-
-### Tool-Based Response:
-1. **Execute Tool**: Call appropriate MCP tool first
-2. **Parse Output**: Extract relevant information from tool response
-3. **Generate Answer**: Base response on tool output only
-4. **Validate**: Ensure consistency with project documentation
-
-### Fallback Response:
-1. **Context Check**: Verify if response requires project knowledge
-2. **Tool Selection**: Use search_documentation if uncertain
-3. **Generic Response**: Only if certain no project context needed
-
-## VALIDATION REQUIREMENTS:
-
-- **Tool Precedence**: Tool responses override general knowledge
-- **Accuracy**: Do not add information beyond tool output
-- **Completeness**: Use tools for all project-related queries
-- **Consistency**: Ensure responses align with project standards
-
-## OPERATIONAL CONSTRAINTS:
-
-- **Custom Patterns**: Project implements non-standard practices
-- **Rule Compliance**: Generated code must follow project rules
-- **Documentation Authority**: Project docs are the authoritative source
-- **Context Awareness**: Always consider project-specific context

package/prompts/cognitive-triggers.txt

@@ -1,40 +0,0 @@
-# MCP TOOL USAGE DECISION TREE
-
-## KEYWORD-TO-TOOL MAPPINGS:
-
-### Code Generation Keywords → check_project_rules
-**Keywords**: write, create, implement, build, add, code, function, class, component, method, develop, generate, make
-**Logic**: Code generation requires project-specific rules validation
-**Action**: Execute check_project_rules before any code output
-
-### Project Information Keywords → search_documentation
-**Keywords**: how, what, why, architecture, approach, feature, authentication, database, API, testing, pattern
-**Context Indicators**: "this project", "this codebase", "here", "our", specific feature names
-**Logic**: Project-specific questions require documentation lookup
-**Action**: Execute search_documentation with relevant query
-
-### Documentation Discovery Keywords → get_global_rules
-**Keywords**: documentation, available, capabilities, help with, what exists, rules, standards
-**Logic**: Documentation queries need comprehensive rule listing
-**Action**: Execute get_global_rules for overview
-
-### Context-Specific Keywords → get_relevant_docs
-**Keywords**: file, directory, component, working on, specific, this [filename], path
-**Logic**: File-specific work requires targeted documentation
-**Action**: Execute get_relevant_docs with file context
-
-## DECISION ALGORITHM:
-
-1. **Parse Input**: Extract keywords from user query
-2. **Match Patterns**: Check keywords against tool mappings
-3. **Priority Order**: Code generation > Project questions > Documentation discovery > Context-specific
-4. **Tool Execution**: Call appropriate MCP tool first
-5. **Response Generation**: Base answer on tool output
-6. **Validation**: Ensure response aligns with retrieved documentation
-
-## EXECUTION REQUIREMENTS:
-
-- **Mandatory**: Use MCP tools for any project-related query
-- **Precedence**: Tool responses override general knowledge
-- **Accuracy**: Verify information against documentation
-- **Completeness**: Don't add assumptions beyond tool output

package/prompts/relevant-docs.txt

@@ -1,13 +0,0 @@
-# CONTEXTUAL DOCUMENTATION
-
-${globalRulesSection}
-${contextualDocsSection}
-${inferredDocsSection}
-${confidenceSection}
-
-## IMPLEMENTATION GUIDANCE:
-
-**Context**: The above documentation applies to your current working context
-**Usage**: Apply these patterns and rules to all generated code
-**Priority**: Context-specific rules take precedence over general guidelines
-**Validation**: Verify generated code complies with all listed requirements