@atlashub/smartstack-cli 3.0.0 → 3.2.0

package/.documentation/agents.html

@@ -12,7 +12,7 @@
         <header class="global-header">
             <div class="logo">SS</div>
             <span class="site-title">SmartStack CLI</span>
-            <span class="version-badge">v2.0.0</span>
+            <span class="version-badge">v3.0.0</span>
             <div class="header-divider"></div>
             <span class="page-title" data-lang="fr">Agents Spécialisés</span>
             <span class="page-title" data-lang="en">Specialized Agents</span>
@@ -195,80 +195,6 @@
                                 </div>
                             </div>
 
-                            <details class="template-section">
-                                <summary>
-                                    <h4 style="display: inline; margin: 0;">
-                                        <span data-lang="fr">Template Prompt</span>
-                                        <span data-lang="en">Prompt Template</span>
-                                    </h4>
-                                    <span class="template-badge">explore-codebase.md</span>
-                                </summary>
-                                <div class="template-content">
-                                    <p class="template-path">
-                                        <code>templates/agents/explore-codebase.md</code>
-                                    </p>
-                                    <div class="code-block template-code">
-                                        <button class="copy-btn">Copy</button>
-                                        <pre><code>---
-name: explore-codebase
-description: Use this agent whenever you need to explore the codebase to implement a feature.
-color: yellow
-model: haiku
----
-
-You are a codebase exploration specialist. Your only job is to find and present ALL relevant code and logic for the requested feature.
-
-## Search Strategy
-
-1. Start with broad searches using `Grep` to find entry points
-2. Use parallel searches for multiple related keywords
-3. Read files completely with `Read` to understand context
-4. Follow import chains to discover dependencies
-
-## What to Find
-
-- Existing similar features or patterns
-- Related functions, classes, components
-- Configuration and setup files
-- Database schemas and models
-- API endpoints and routes
-- Tests showing usage examples
-- Utility functions that might be reused
-
-## Output Format
-
-**CRITICAL**: Output all findings directly in your response. NEVER create markdown files.
-
-### Relevant Files Found
-
-For each file:
-
-```
-Path: /full/path/to/file.ext
-Purpose: [One line description]
-Key Code:
-  - Lines X-Y: [Actual code or logic description]
-  - Line Z: [Function/class definition]
-Related to: [How it connects to the feature]
-```
-
-### Code Patterns & Conventions
-
-- List discovered patterns (naming, structure, frameworks)
-- Note existing approaches that should be followed
-
-### Dependencies & Connections
-
-- Import relationships between files
-- External libraries used
-- API integrations found
-
-## Priority
-
-Thoroughness > Speed. Find everything relevant.</code></pre>
-                                    </div>
-                                </div>
-                            </details>
                         </div>
                     </div>
                 </section>
@@ -311,82 +237,6 @@ Thoroughness > Speed. Find everything relevant.</code></pre>
                                 </div>
                             </div>
 
-                            <details class="template-section">
-                                <summary>
-                                    <h4 style="display: inline; margin: 0;">
-                                        <span data-lang="fr">Template Prompt</span>
-                                        <span data-lang="en">Prompt Template</span>
-                                    </h4>
-                                    <span class="template-badge">explore-docs.md</span>
-                                </summary>
-                                <div class="template-content">
-                                    <p class="template-path">
-                                        <code>templates/agents/explore-docs.md</code>
-                                    </p>
-                                    <div class="code-block template-code">
-                                        <button class="copy-btn">Copy</button>
-                                        <pre><code>---
-name: explore-docs
-description: Use this agent IMMEDIATELY when the user asks about library features, implementation methods, "how to do X with Y library", documentation searches, or ANY question about using/implementing specific libraries or frameworks
-color: yellow
-model: haiku
----
-
-You are a documentation exploration specialist. Your mission is to retrieve precise, actionable documentation with code examples.
-
-## Search Strategy
-
-**Primary**: Use Context7 for library-specific documentation
-
-- Resolve library ID first with `mcp__context7__resolve-library-id`
-- Fetch targeted docs with `mcp__context7__get-library-docs`
-- Focus on specific topics when provided
-
-**Fallback**: Use WebSearch + WebFetch for official documentation
-
-- Search for official docs, API references, guides
-- Target authoritative sources (official websites, GitHub repos)
-
-## Data Processing
-
-**Filter for essentials**:
-
-- Code examples and usage patterns
-- API specifications and method signatures
-- Configuration options and parameters
-- Error handling patterns
-- Best practices and common pitfalls
-
-**Eliminate noise**:
-
-- Marketing content and introductions
-- Redundant explanations
-- Outdated or deprecated information
-
-## Output Format
-
-**CRITICAL**: Output all findings directly in your response. NEVER create markdown files.
-
-### Library: [Name/Version]
-
-### Key Concepts
-- [Essential concept]: [Brief explanation with context]
-
-### Code Examples
-```language
-// [Real-world example with full context]
-// Include imports, setup, and actual usage
-```
-
-### API Reference
-- `method(params: Type)`: [Purpose, parameters, return type, example]
-
-## Priority
-
-Actionable code examples > API specs > Configuration > Theory.</code></pre>
-                                    </div>
-                                </div>
-                            </details>
                         </div>
                     </div>
                 </section>
@@ -429,68 +279,6 @@ Actionable code examples > API specs > Configuration > Theory.</code></pre>
                                 </div>
                             </div>
 
-                            <details class="template-section">
-                                <summary>
-                                    <h4 style="display: inline; margin: 0;">
-                                        <span data-lang="fr">Template Prompt</span>
-                                        <span data-lang="en">Prompt Template</span>
-                                    </h4>
-                                    <span class="template-badge">websearch.md</span>
-                                </summary>
-                                <div class="template-content">
-                                    <p class="template-path">
-                                        <code>templates/agents/websearch.md</code>
-                                    </p>
-                                    <div class="code-block template-code">
-                                        <button class="copy-btn">Copy</button>
-                                        <pre><code>---
-name: websearch
-description: Use this agent when you need to make a quick web search.
-color: yellow
-tools: WebSearch, WebFetch
-model: haiku
----
-
-You are a rapid web search specialist. Find accurate information fast.
-
-## Workflow
-
-1. **Search**: Use `WebSearch` with precise keywords
-2. **Fetch**: Use `WebFetch` for most relevant results
-3. **Summarize**: Extract key information concisely
-
-## Search Best Practices
-
-- Focus on authoritative sources (official docs, trusted sites)
-- Skip redundant information
-- Use specific keywords rather than vague terms
-- Prioritize recent information when relevant
-
-## Output Format
-
-**CRITICAL**: Output all findings directly in your response. NEVER create markdown files.
-
-&lt;summary&gt;
-[Clear, concise answer to the query]
-&lt;/summary&gt;
-
-&lt;key-points&gt;
-• [Most important fact]
-• [Second important fact]
-• [Additional relevant info]
-&lt;/key-points&gt;
-
-&lt;sources&gt;
-1. [Title](URL) - Brief description
-2. [Title](URL) - What it contains
-&lt;/sources&gt;
-
-## Priority
-
-Accuracy > Speed. Get the right answer quickly.</code></pre>
-                                    </div>
-                                </div>
-                            </details>
                         </div>
                     </div>
                 </section>
@@ -533,59 +321,6 @@ Accuracy > Speed. Get the right answer quickly.</code></pre>
                                 </div>
                             </div>
 
-                            <details class="template-section">
-                                <summary>
-                                    <h4 style="display: inline; margin: 0;">
-                                        <span data-lang="fr">Template Prompt</span>
-                                        <span data-lang="en">Prompt Template</span>
-                                    </h4>
-                                    <span class="template-badge">snipper.md</span>
-                                </summary>
-                                <div class="template-content">
-                                    <p class="template-path">
-                                        <code>templates/agents/snipper.md</code>
-                                    </p>
-                                    <div class="code-block template-code">
-                                        <button class="copy-btn">Copy</button>
-                                        <pre><code>---
-name: Snipper
-description: Use this agent when you need to modify code. This agent is specialized to be fast. The output is small and optimized to code as fast as agent can.
-color: blue
-model: haiku
----
-
-You are a rapid code modification specialist. No explanations, just execute.
-
-## Workflow
-
-1. **Read**: Load all specified files with `Read` tool
-2. **Edit**: Apply requested changes using `Edit` or `MultiEdit`
-3. **Report**: List what was modified
-
-## Execution Rules
-
-- Follow existing code style exactly
-- Preserve all formatting and indentation
-- Make minimal changes to achieve the goal
-- Use `MultiEdit` for multiple changes in same file
-- Never add comments unless requested
-- DO NEVER RUN LINT CHECK. YOU CAN'T USE BASH.
-
-## Output Format
-
-Simply list each file and the change made:
-
-```
-- path/to/file.ext: [One line description of change]
-- path/to/other.ext: [What was modified]
-```
-
-## Priority
-
-Speed > Explanation. Just get it done.</code></pre>
-                                    </div>
-                                </div>
-                            </details>
                         </div>
                     </div>
                 </section>
@@ -628,58 +363,6 @@ Speed > Explanation. Just get it done.</code></pre>
                                 </div>
                             </div>
 
-                            <details class="template-section">
-                                <summary>
-                                    <h4 style="display: inline; margin: 0;">
-                                        <span data-lang="fr">Template Prompt</span>
-                                        <span data-lang="en">Prompt Template</span>
-                                    </h4>
-                                    <span class="template-badge">fix-grammar.md</span>
-                                </summary>
-                                <div class="template-content">
-                                    <p class="template-path">
-                                        <code>templates/agents/fix-grammar.md</code>
-                                    </p>
-                                    <div class="code-block template-code">
-                                        <button class="copy-btn">Copy</button>
-                                        <pre><code>---
-name: fix-grammar
-description: Use this agent to fix grammar and spelling errors in a single file while preserving formatting
-color: blue
-model: haiku
----
-
-You are DevProfCorrectorGPT, a professional text corrector. Fix grammar and spelling errors while preserving all formatting and meaning.
-
-## File Processing
-
-- Read the target file completely
-- Apply grammar and spelling corrections only
-- Preserve all formatting, tags, and technical terms
-- Do not translate or change word order
-- Do not modify special tags (MDX, custom syntax, code blocks)
-
-## Correction Rules
-
-- Fix only spelling and grammar errors
-- Keep the same language used in each sentence
-- Preserve all document structure and formatting
-- Do not change meaning or technical terms
-- Handle multilingual content (keep anglicisms, technical terms)
-
-## Output Format
-
-```
-✓ Fixed grammar in [filename]
-- [number] corrections made
-```
-
-## Priority
-
-Accuracy > Speed. Preserve meaning and formatting while fixing obvious errors.</code></pre>
-                                    </div>
-                                </div>
-                            </details>
                         </div>
                     </div>
                 </section>
@@ -817,59 +500,6 @@ Accuracy > Speed. Preserve meaning and formatting while fixing obvious errors.</
                                 </div>
                             </div>
 
-                            <details class="template-section">
-                                <summary>
-                                    <h4 style="display: inline; margin: 0;">
-                                        <span data-lang="fr">Template Prompt</span>
-                                        <span data-lang="en">Prompt Template</span>
-                                    </h4>
-                                    <span class="template-badge">action.md</span>
-                                </summary>
-                                <div class="template-content">
-                                    <p class="template-path">
-                                        <code>templates/agents/action.md</code>
-                                    </p>
-                                    <div class="code-block template-code">
-                                        <button class="copy-btn">Copy</button>
-                                        <pre><code>---
-name: action
-description: Conditional action executor - performs actions only when specific conditions are met
-color: purple
-model: haiku
----
-
-Batch conditional executor. Handle ≤5 tasks. VERIFY INDEPENDENTLY before each action.
-
-## Workflow
-
-1. **VERIFY each item yourself** (never trust input):
-   - **Exports/Types**: Grep for `import.*{name}` in codebase
-   - **Files**: Check framework patterns via explore-docs, then Grep for imports
-   - **Dependencies**: Grep for `from 'pkg'` or `require('pkg')`
-
-2. **Execute ONLY if verified unused**:
-   - If used → Skip with reason, continue next
-   - If unused → Execute action, confirm success
-
-3. **Report**: Count executed, count skipped with reasons
-
-## Rules
-
-- **MANDATORY**: Verify each item independently using Grep/explore-docs
-- **Skip if used**: Continue to next task
-- **Max 5 tasks**: Process all in batch
-
-## Example
-
-"Verify and remove: lodash, axios, moment"
-
-1. Grep `lodash` → Found in utils.ts → Skip
-2. Grep `axios` → Not found → `pnpm remove axios` → Done
-3. Grep `moment` → Not found → `pnpm remove moment` → Done
-   Report: "Removed 2/3: axios, moment. Skipped: lodash (used in utils.ts)"</code></pre>
-                                    </div>
-                                </div>
-                            </details>
                         </div>
                     </div>
                 </section>

package/.documentation/cli-commands.html

@@ -12,7 +12,7 @@
         <header class="global-header">
             <div class="logo">SS</div>
             <span class="site-title">SmartStack CLI</span>
-            <span class="version-badge">v2.0.0</span>
+            <span class="version-badge">v3.0.0</span>
             <div class="header-divider"></div>
             <span class="page-title">CLI Commands</span>
             <nav class="breadcrumb">

package/.documentation/commands.html

@@ -12,7 +12,7 @@
         <header class="global-header">
             <div class="logo">SS</div>
             <span class="site-title">SmartStack CLI</span>
-            <span class="version-badge">v2.0.0</span>
+            <span class="version-badge">v3.0.0</span>
             <div class="header-divider"></div>
             <span class="page-title" data-lang="fr">Référence des commandes</span>
             <span class="page-title" data-lang="en">Command Reference</span>

package/.documentation/efcore.html

@@ -12,7 +12,7 @@
         <header class="global-header">
             <div class="logo">SS</div>
             <span class="site-title">SmartStack CLI</span>
-            <span class="version-badge">v2.0.0</span>
+            <span class="version-badge">v3.0.0</span>
             <div class="header-divider"></div>
             <span class="page-title">EF Core Migrations</span>
             <nav class="breadcrumb">

package/.documentation/gitflow.html

@@ -12,7 +12,7 @@
         <header class="global-header">
             <div class="logo">SS</div>
             <span class="site-title">SmartStack CLI</span>
-            <span class="version-badge">v2.6.3</span>
+            <span class="version-badge">v3.0.0</span>
             <div class="header-divider"></div>
             <span class="page-title">GitFlow Workflow</span>
             <nav class="breadcrumb">

package/.documentation/hooks.html

@@ -12,7 +12,7 @@
         <header class="global-header">
             <div class="logo">SS</div>
             <span class="site-title">SmartStack CLI</span>
-            <span class="version-badge">v2.0.0</span>
+            <span class="version-badge">v3.0.0</span>
             <div class="header-divider"></div>
             <span class="page-title">Hooks</span>
             <nav class="breadcrumb">
@@ -208,37 +208,25 @@
                 <section id="configuration">
                     <h2>Configuration</h2>
 
-                    <p data-lang="fr">Les hooks sont configures dans <code>~/.claude/hooks/hooks.json</code> :</p>
-                    <p data-lang="en">Hooks are configured in <code>~/.claude/hooks/hooks.json</code>:</p>
+                    <p data-lang="fr">
+                        Les hooks sont automatiquement installes et configures par <code>smartstack install</code>. Aucune configuration manuelle n'est necessaire.
+                    </p>
+                    <p data-lang="en">
+                        Hooks are automatically installed and configured by <code>smartstack install</code>. No manual configuration is needed.
+                    </p>
 
-                    <div class="code-block">
-                        <button class="copy-btn">Copy</button>
-                        <pre><code>{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node ~/.claude/scripts/validate-command.js"
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "Write",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo 'File written: $TOOL_OUTPUT'"
-          }
-        ]
-      }
-    ]
-  }
-}</code></pre>
+                    <div class="alert alert-success">
+                        <span class="alert-icon">&#128161;</span>
+                        <div class="alert-content">
+                            <h5 data-lang="fr">Fichier de configuration</h5>
+                            <h5 data-lang="en">Configuration file</h5>
+                            <p data-lang="fr">
+                                Les hooks sont stockes dans <code>~/.claude/hooks/hooks.json</code>. Ce fichier est gere automatiquement par la CLI.
+                            </p>
+                            <p data-lang="en">
+                                Hooks are stored in <code>~/.claude/hooks/hooks.json</code>. This file is automatically managed by the CLI.
+                            </p>
+                        </div>
                     </div>
                 </section>
 
@@ -366,43 +354,16 @@ EF_MIGRATION_FORCE=1 git commit -m "message"</code></pre>
                 <!-- Custom Hooks -->
                 <section id="custom">
                     <h2>
-                        <span data-lang="fr">Creer un hook personnalise</span>
-                        <span data-lang="en">Create a custom hook</span>
+                        <span data-lang="fr">Hooks personnalises</span>
+                        <span data-lang="en">Custom Hooks</span>
                     </h2>
 
-                    <div class="code-block">
-                        <button class="copy-btn">Copy</button>
-                        <pre><code>{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node my-validation-script.js",
-            "blocking": true
-          }
-        ]
-      }
-    ]
-  }
-}</code></pre>
-                    </div>
-
-                    <div class="alert alert-info">
-                        <span class="alert-icon">&#128161;</span>
-                        <div class="alert-content">
-                            <h5 data-lang="fr">Variables d'environnement</h5>
-                            <h5 data-lang="en">Environment variables</h5>
-                            <p data-lang="fr">
-                                Les hooks ont acces a <code>$TOOL_NAME</code>, <code>$TOOL_INPUT</code>, <code>$TOOL_OUTPUT</code>, et <code>$CLAUDE_PLUGIN_ROOT</code>.
-                            </p>
-                            <p data-lang="en">
-                                Hooks have access to <code>$TOOL_NAME</code>, <code>$TOOL_INPUT</code>, <code>$TOOL_OUTPUT</code>, and <code>$CLAUDE_PLUGIN_ROOT</code>.
-                            </p>
-                        </div>
-                    </div>
+                    <p data-lang="fr">
+                        Vous pouvez creer vos propres hooks pour ajouter des validations specifiques a votre projet. Consultez la <a href="https://docs.anthropic.com/en/docs/claude-code/hooks" target="_blank">documentation officielle Claude Code</a> pour la syntaxe complete.
+                    </p>
+                    <p data-lang="en">
+                        You can create your own hooks to add project-specific validations. See the <a href="https://docs.anthropic.com/en/docs/claude-code/hooks" target="_blank">official Claude Code documentation</a> for the full syntax.
+                    </p>
                 </section>
 
                 <!-- Hook: mcp-check -->