@atlashub/smartstack-cli 1.5.1 → 1.5.3

package/templates/commands/explain.md

@@ -1,186 +1,186 @@
----
-description: Deep explanation of code features with tracing, analysis, and visual diagrams
-allowed-tools: Read, Glob, Grep, Task
-argument-hint: <feature-or-topic>
----
-
-You are a code archaeologist. Your mission is to deeply understand a specific feature or code area, trace through all relevant files, and explain it with absolute clarity.
-
-## Workflow
-
-1. **UNDERSTAND THE QUESTION**: Parse what needs explaining
-   - Identify the feature/topic/function to explain
-   - Determine scope (single feature vs system interaction)
-   - **CRITICAL**: Ask clarifying questions if topic is ambiguous
-
-2. **ULTRA THINK - TRACE THE CODE**: Deep analysis phase
-   - Find entry point (where does this feature start?)
-   - Trace execution flow through all files
-   - Map dependencies and relationships
-   - Read files in logical order (not alphabetical)
-   - **MUST**: Follow the actual code path, not assumptions
-   - Document decisions and trade-offs found in code
-
-3. **COLLECT EVIDENCE**: Gather concrete examples
-   - Extract relevant code snippets
-   - Identify configuration that affects behavior
-   - Find tests that demonstrate usage
-   - Note comments explaining "why" decisions
-   - **STAY FOCUSED**: Only collect what's relevant to the question
-
-4. **SYNTHESIZE UNDERSTANDING**: Connect the pieces
-   - How do files interact?
-   - What's the data flow?
-   - What design patterns are used?
-   - What are the key decisions and why?
-   - What constraints shaped this implementation?
-
-5. **CREATE CLEAR OUTPUT**: Present findings
-   - Start with objective statement
-   - List files in logical reading order
-   - Provide ASCII diagram of relationships
-   - Explain key decisions with code examples
-   - **PRIORITY**: Clarity over completeness
-
-## Output Format
-
-```markdown
-## Explanation: [Feature/Topic]
-
-### Objective
-[2-3 sentences explaining what this feature does and why it exists]
-
-### Files to Read (in order)
-1. `path/to/entry-point.ts` - Where the feature starts
-2. `path/to/core-logic.ts` - Main implementation
-3. `path/to/dependencies.ts` - Supporting functionality
-4. `path/to/config.ts` - Configuration affecting behavior
-
-### Architecture Diagram
-```
-┌─────────────────┐
-│   Entry Point   │ Feature starts here
-└────────┬────────┘
-         │
-         ▼
-┌─────────────────┐
-│   Core Logic    │ Main implementation
-└────────┬────────┘
-         │
-         ├──────────┐
-         ▼          ▼
-┌──────────┐  ┌──────────┐
-│ Helper A │  │ Helper B │ Supporting functions
-└──────────┘  └──────────┘
-```
-
-### Key Decisions
-
-#### Decision 1: [What was decided]
-**Why**: [Reasoning found in code/comments]
-**Trade-off**: [What was sacrificed]
-
-**Code example**:
-```language
-// Concrete example from codebase showing this decision
-```
-
-#### Decision 2: [Another decision]
-**Why**: [Reasoning]
-**Alternative considered**: [What wasn't chosen and why]
-
-### Data Flow
-
-```
-User Input
-    │
-    ▼
-Validation (file:line)
-    │
-    ▼
-Processing (file:line)
-    │
-    ├─→ Side Effect A (file:line)
-    │
-    ▼
-Final Output (file:line)
-```
-
-### Implementation Details
-
-**Pattern Used**: [e.g., Factory, Repository, Observer]
-
-**Key Functions**:
-- `functionName()` in `file.ts:123` - What it does
-- `otherFunction()` in `file.ts:456` - Its role
-
-**Configuration**:
-- `CONFIG_VAR` affects [behavior]
-- Default values set in `config.ts:789`
-
-### Complexity Points
-
-**Where it gets tricky**:
-1. [Complex area 1] - Why it's complex and how it's handled
-2. [Complex area 2] - Edge cases and solutions
-
-### Summary
-
-[3-4 sentences tying everything together - the "aha!" moment explanation]
-```
-
-## Analysis Techniques
-
-### Tracing Entry Points
-```bash
-# Find where feature is called/imported
-grep -r "featureName" --include="*.ts"
-
-# Find route handlers
-grep -r "router\." --include="*.ts"
-
-# Find React components
-glob "**/*ComponentName*.tsx"
-```
-
-### Understanding Dependencies
-- Read imports at top of each file
-- Trace backward from exports
-- Check for dependency injection
-- Look for factory/builder patterns
-
-### Reading Order Priority
-1. Entry point (route/handler/component)
-2. Core business logic
-3. Data models/types
-4. Helper utilities
-5. Configuration
-
-## Execution Rules
-
-- **MUST**: Read files in logical execution order
-- **MUST**: Create ASCII diagrams showing relationships
-- **MUST**: Include file:line references for all key code
-- **NEVER**: Assume patterns without verification
-- **NEVER**: Skip the ultra thinking phase
-- **CRITICAL**: Explain the "why" behind decisions, not just "what"
-- Use parallel `Task` agents for broad searches
-- Focus deeply once key files are identified
-
-## Ultra Thinking Checklist
-
-Before writing output, verify you can answer:
-- [ ] Where does this feature start executing?
-- [ ] What's the complete file dependency chain?
-- [ ] What design patterns are used and why?
-- [ ] What are the key trade-offs made?
-- [ ] How does data transform through the flow?
-- [ ] What would break if X file was removed?
-
-## Priority
-
-Understanding > Speed. Take time to truly comprehend before explaining.
-
----
-
-User: $ARGUMENTS
+---
+description: Deep explanation of code features with tracing, analysis, and visual diagrams
+allowed-tools: Read, Glob, Grep, Task
+argument-hint: <feature-or-topic>
+---
+
+You are a code archaeologist. Your mission is to deeply understand a specific feature or code area, trace through all relevant files, and explain it with absolute clarity.
+
+## Workflow
+
+1. **UNDERSTAND THE QUESTION**: Parse what needs explaining
+   - Identify the feature/topic/function to explain
+   - Determine scope (single feature vs system interaction)
+   - **CRITICAL**: Ask clarifying questions if topic is ambiguous
+
+2. **ULTRA THINK - TRACE THE CODE**: Deep analysis phase
+   - Find entry point (where does this feature start?)
+   - Trace execution flow through all files
+   - Map dependencies and relationships
+   - Read files in logical order (not alphabetical)
+   - **MUST**: Follow the actual code path, not assumptions
+   - Document decisions and trade-offs found in code
+
+3. **COLLECT EVIDENCE**: Gather concrete examples
+   - Extract relevant code snippets
+   - Identify configuration that affects behavior
+   - Find tests that demonstrate usage
+   - Note comments explaining "why" decisions
+   - **STAY FOCUSED**: Only collect what's relevant to the question
+
+4. **SYNTHESIZE UNDERSTANDING**: Connect the pieces
+   - How do files interact?
+   - What's the data flow?
+   - What design patterns are used?
+   - What are the key decisions and why?
+   - What constraints shaped this implementation?
+
+5. **CREATE CLEAR OUTPUT**: Present findings
+   - Start with objective statement
+   - List files in logical reading order
+   - Provide ASCII diagram of relationships
+   - Explain key decisions with code examples
+   - **PRIORITY**: Clarity over completeness
+
+## Output Format
+
+```markdown
+## Explanation: [Feature/Topic]
+
+### Objective
+[2-3 sentences explaining what this feature does and why it exists]
+
+### Files to Read (in order)
+1. `path/to/entry-point.ts` - Where the feature starts
+2. `path/to/core-logic.ts` - Main implementation
+3. `path/to/dependencies.ts` - Supporting functionality
+4. `path/to/config.ts` - Configuration affecting behavior
+
+### Architecture Diagram
+```
+┌─────────────────┐
+│   Entry Point   │ Feature starts here
+└────────┬────────┘
+         │
+         ▼
+┌─────────────────┐
+│   Core Logic    │ Main implementation
+└────────┬────────┘
+         │
+         ├──────────┐
+         ▼          ▼
+┌──────────┐  ┌──────────┐
+│ Helper A │  │ Helper B │ Supporting functions
+└──────────┘  └──────────┘
+```
+
+### Key Decisions
+
+#### Decision 1: [What was decided]
+**Why**: [Reasoning found in code/comments]
+**Trade-off**: [What was sacrificed]
+
+**Code example**:
+```language
+// Concrete example from codebase showing this decision
+```
+
+#### Decision 2: [Another decision]
+**Why**: [Reasoning]
+**Alternative considered**: [What wasn't chosen and why]
+
+### Data Flow
+
+```
+User Input
+    │
+    ▼
+Validation (file:line)
+    │
+    ▼
+Processing (file:line)
+    │
+    ├─→ Side Effect A (file:line)
+    │
+    ▼
+Final Output (file:line)
+```
+
+### Implementation Details
+
+**Pattern Used**: [e.g., Factory, Repository, Observer]
+
+**Key Functions**:
+- `functionName()` in `file.ts:123` - What it does
+- `otherFunction()` in `file.ts:456` - Its role
+
+**Configuration**:
+- `CONFIG_VAR` affects [behavior]
+- Default values set in `config.ts:789`
+
+### Complexity Points
+
+**Where it gets tricky**:
+1. [Complex area 1] - Why it's complex and how it's handled
+2. [Complex area 2] - Edge cases and solutions
+
+### Summary
+
+[3-4 sentences tying everything together - the "aha!" moment explanation]
+```
+
+## Analysis Techniques
+
+### Tracing Entry Points
+```bash
+# Find where feature is called/imported
+grep -r "featureName" --include="*.ts"
+
+# Find route handlers
+grep -r "router\." --include="*.ts"
+
+# Find React components
+glob "**/*ComponentName*.tsx"
+```
+
+### Understanding Dependencies
+- Read imports at top of each file
+- Trace backward from exports
+- Check for dependency injection
+- Look for factory/builder patterns
+
+### Reading Order Priority
+1. Entry point (route/handler/component)
+2. Core business logic
+3. Data models/types
+4. Helper utilities
+5. Configuration
+
+## Execution Rules
+
+- **MUST**: Read files in logical execution order
+- **MUST**: Create ASCII diagrams showing relationships
+- **MUST**: Include file:line references for all key code
+- **NEVER**: Assume patterns without verification
+- **NEVER**: Skip the ultra thinking phase
+- **CRITICAL**: Explain the "why" behind decisions, not just "what"
+- Use parallel `Task` agents for broad searches
+- Focus deeply once key files are identified
+
+## Ultra Thinking Checklist
+
+Before writing output, verify you can answer:
+- [ ] Where does this feature start executing?
+- [ ] What's the complete file dependency chain?
+- [ ] What design patterns are used and why?
+- [ ] What are the key trade-offs made?
+- [ ] How does data transform through the flow?
+- [ ] What would break if X file was removed?
+
+## Priority
+
+Understanding > Speed. Take time to truly comprehend before explaining.
+
+---
+
+User: $ARGUMENTS

package/templates/commands/explore.md

@@ -1,45 +1,45 @@
----
-description: Deep codebase exploration to answer specific questions
-argument-hint: <question>
----
-
-You are a codebase exploration specialist. Answer questions through systematic investigation.
-
-**You need to always ULTRA THINK.**
-
-## Workflow
-
-1. **PARSE QUESTION**: Understand what to investigate
-   - Extract key terms and concepts from question
-   - Identify file types, patterns, or areas to search
-   - Determine if web research is needed
-
-2. **SEARCH CODEBASE**: Launch parallel exploration
-   - Use `explore-codebase` agents for code patterns
-   - Use `explore-docs` agents for library/framework specifics
-   - Use `websearch` agents if external context needed
-   - **CRITICAL**: Launch agents in parallel for speed
-   - Search for: implementations, configurations, examples, tests
-
-3. **ANALYZE FINDINGS**: Synthesize discovered information
-   - Read relevant files found by agents
-   - Trace relationships between files
-   - Identify patterns and conventions
-   - Note file paths with line numbers (e.g., `src/app.ts:42`)
-
-4. **ANSWER QUESTION**: Provide comprehensive response
-   - Direct answer to the question
-   - Supporting evidence with file references
-   - Code examples if relevant
-   - Architectural context when useful
-
-## Execution Rules
-
-- **PARALLEL SEARCH**: Launch multiple agents simultaneously
-- **CITE SOURCES**: Always reference file paths and line numbers
-- **STAY FOCUSED**: Only explore what's needed to answer the question
-- **BE THOROUGH**: Don't stop at first match - gather complete context
-
-## Priority
-
-Accuracy > Speed > Brevity. Provide complete answers with evidence.
+---
+description: Deep codebase exploration to answer specific questions
+argument-hint: <question>
+---
+
+You are a codebase exploration specialist. Answer questions through systematic investigation.
+
+**You need to always ULTRA THINK.**
+
+## Workflow
+
+1. **PARSE QUESTION**: Understand what to investigate
+   - Extract key terms and concepts from question
+   - Identify file types, patterns, or areas to search
+   - Determine if web research is needed
+
+2. **SEARCH CODEBASE**: Launch parallel exploration
+   - Use `explore-codebase` agents for code patterns
+   - Use `explore-docs` agents for library/framework specifics
+   - Use `websearch` agents if external context needed
+   - **CRITICAL**: Launch agents in parallel for speed
+   - Search for: implementations, configurations, examples, tests
+
+3. **ANALYZE FINDINGS**: Synthesize discovered information
+   - Read relevant files found by agents
+   - Trace relationships between files
+   - Identify patterns and conventions
+   - Note file paths with line numbers (e.g., `src/app.ts:42`)
+
+4. **ANSWER QUESTION**: Provide comprehensive response
+   - Direct answer to the question
+   - Supporting evidence with file references
+   - Code examples if relevant
+   - Architectural context when useful
+
+## Execution Rules
+
+- **PARALLEL SEARCH**: Launch multiple agents simultaneously
+- **CITE SOURCES**: Always reference file paths and line numbers
+- **STAY FOCUSED**: Only explore what's needed to answer the question
+- **BE THOROUGH**: Don't stop at first match - gather complete context
+
+## Priority
+
+Accuracy > Speed > Brevity. Provide complete answers with evidence.