@atlashub/smartstack-cli 3.39.0 → 3.41.0

package/templates/skills/cc-agent/SKILL.md

@@ -1,129 +1,129 @@
----
-name: cc-agent
-description: |
-  Create or update Claude Code agents (subagents) based on official documentation.
-  Use this skill when:
-  - Creating a new specialized agent
-  - Updating an agent's tools, model, or permissions
-  - Adding skills to an agent
-argument-hint: "<create|update> [name] [--scope project|global|templates]"
-disable-model-invocation: true
----
-
-<objective>
-Create or update Claude Code agents (subagents) following official conventions. Guides the user through agent design, generates properly structured .md files, and validates the result.
-</objective>
-
-<quick_start>
-
-```bash
-# Create a new agent
-/cc-agent create my-agent
-/cc-agent create my-agent --scope project
-/cc-agent create my-agent --scope global
-/cc-agent create my-agent --scope templates
-
-# Update an existing agent
-/cc-agent update my-agent
-/cc-agent update my-agent --scope global
-```
-
-</quick_start>
-
-<parameters>
-
-<subcommands>
-| Command | Description | Workflow |
-|---------|-------------|----------|
-| `create` | Create a new agent from scratch | init → design → generate → validate |
-| `update` | Update an existing agent | init → analyze → apply → validate |
-</subcommands>
-
-<flags>
-| Flag | Description |
-|------|-------------|
-| `--scope project` | Target `.claude/agents/` (default) |
-| `--scope global` | Target `~/.claude/agents/` |
-| `--scope templates` | Target `templates/agents/` (SmartStack CLI) |
-| `--category <name>` | Place in subdirectory (e.g., efcore, gitflow) |
-</flags>
-
-<examples>
-```bash
-# Create a standalone agent
-/cc-agent create test-runner
-
-# Create a categorized agent
-/cc-agent create migration --category efcore --scope templates
-
-# Update an existing agent
-/cc-agent update code-reviewer
-
-# Create agent for SmartStack templates
-/cc-agent create my-validator --scope templates
-```
-</examples>
-
-</parameters>
-
-<workflow>
-**Create flow:**
-1. Parse subcommand, name, scope, category
-2. Design agent (model, tools, permissions, skills)
-3. Generate agent .md file
-4. Validate structure and conventions
-
-**Update flow:**
-1. Parse subcommand, name, scope
-2. Read and analyze existing agent
-3. Apply requested changes
-4. Validate structure and conventions
-</workflow>
-
-<state_variables>
-| Variable | Type | Description |
-|----------|------|-------------|
-| `{subcommand}` | string | create or update |
-| `{agent_name}` | string | Agent name (unique identifier) |
-| `{scope}` | string | project, global, or templates |
-| `{target_dir}` | string | Resolved target directory |
-| `{category}` | string | Subdirectory (null for standalone) |
-| `{description}` | string | Agent description |
-| `{model}` | string | haiku, sonnet, opus, or inherit |
-| `{tools}` | string | Comma-separated tool list |
-| `{disallowed_tools}` | string | Blocked tools |
-| `{permission_mode}` | string | Permission handling mode |
-| `{preloaded_skills}` | string[] | Skills to inject at startup |
-| `{system_prompt}` | string | Agent's system prompt content |
-</state_variables>
-
-<entry_point>
-
-**FIRST ACTION:** Load `steps/step-00-init.md`
-
-</entry_point>
-
-<step_files>
-| Step | File | Purpose |
-|------|------|---------|
-| 00 | `steps/step-00-init.md` | Parse subcommand, name, scope, resolve target |
-| 01 | `steps/step-01-design.md` | Design agent (model, tools, permissions, skills) |
-| 02 | `steps/step-02-generate.md` | Generate agent .md file from template |
-| 03 | `steps/step-03-validate.md` | Validate format and display summary |
-</step_files>
-
-<execution_rules>
-- **Load one step at a time** - Progressive loading
-- **Ask before generating** - Confirm design choices with user
-- **Use templates** - Load from `templates/` directory for generation
-- **Follow official conventions** - Based on Claude Code documentation
-- **Validate at the end** - Check generated file
-</execution_rules>
-
-<success_criteria>
-- Agent .md file created with valid frontmatter
-- Description is clear enough for Claude to decide when to delegate
-- Tools are appropriate for the agent's purpose
-- Permission mode matches the agent's risk level
-- Agent follows official Claude Code conventions
-</success_criteria>
+---
+name: cc-agent
+description: |
+  Create or update Claude Code agents (subagents) based on official documentation.
+  Use this skill when:
+  - Creating a new specialized agent
+  - Updating an agent's tools, model, or permissions
+  - Adding skills to an agent
+argument-hint: "<create|update> [name] [--scope project|global|templates]"
+disable-model-invocation: true
+---
+
+<objective>
+Create or update Claude Code agents (subagents) following official conventions. Guides the user through agent design, generates properly structured .md files, and validates the result.
+</objective>
+
+<quick_start>
+
+```bash
+# Create a new agent
+/cc-agent create my-agent
+/cc-agent create my-agent --scope project
+/cc-agent create my-agent --scope global
+/cc-agent create my-agent --scope templates
+
+# Update an existing agent
+/cc-agent update my-agent
+/cc-agent update my-agent --scope global
+```
+
+</quick_start>
+
+<parameters>
+
+<subcommands>
+| Command | Description | Workflow |
+|---------|-------------|----------|
+| `create` | Create a new agent from scratch | init → design → generate → validate |
+| `update` | Update an existing agent | init → analyze → apply → validate |
+</subcommands>
+
+<flags>
+| Flag | Description |
+|------|-------------|
+| `--scope project` | Target `.claude/agents/` (default) |
+| `--scope global` | Target `~/.claude/agents/` |
+| `--scope templates` | Target `templates/agents/` (SmartStack CLI) |
+| `--category <name>` | Place in subdirectory (e.g., efcore, gitflow) |
+</flags>
+
+<examples>
+```bash
+# Create a standalone agent
+/cc-agent create test-runner
+
+# Create a categorized agent
+/cc-agent create migration --category efcore --scope templates
+
+# Update an existing agent
+/cc-agent update code-reviewer
+
+# Create agent for SmartStack templates
+/cc-agent create my-validator --scope templates
+```
+</examples>
+
+</parameters>
+
+<workflow>
+**Create flow:**
+1. Parse subcommand, name, scope, category
+2. Design agent (model, tools, permissions, skills)
+3. Generate agent .md file
+4. Validate structure and conventions
+
+**Update flow:**
+1. Parse subcommand, name, scope
+2. Read and analyze existing agent
+3. Apply requested changes
+4. Validate structure and conventions
+</workflow>
+
+<state_variables>
+| Variable | Type | Description |
+|----------|------|-------------|
+| `{subcommand}` | string | create or update |
+| `{agent_name}` | string | Agent name (unique identifier) |
+| `{scope}` | string | project, global, or templates |
+| `{target_dir}` | string | Resolved target directory |
+| `{category}` | string | Subdirectory (null for standalone) |
+| `{description}` | string | Agent description |
+| `{model}` | string | haiku, sonnet, opus, or inherit |
+| `{tools}` | string | Comma-separated tool list |
+| `{disallowed_tools}` | string | Blocked tools |
+| `{permission_mode}` | string | Permission handling mode |
+| `{preloaded_skills}` | string[] | Skills to inject at startup |
+| `{system_prompt}` | string | Agent's system prompt content |
+</state_variables>
+
+<entry_point>
+
+**FIRST ACTION:** Load `steps/step-00-init.md`
+
+</entry_point>
+
+<step_files>
+| Step | File | Purpose |
+|------|------|---------|
+| 00 | `steps/step-00-init.md` | Parse subcommand, name, scope, resolve target |
+| 01 | `steps/step-01-design.md` | Design agent (model, tools, permissions, skills) |
+| 02 | `steps/step-02-generate.md` | Generate agent .md file from template |
+| 03 | `steps/step-03-validate.md` | Validate format and display summary |
+</step_files>
+
+<execution_rules>
+- **Load one step at a time** - Progressive loading
+- **Ask before generating** - Confirm design choices with user
+- **Use templates** - Load from `templates/` directory for generation
+- **Follow official conventions** - Based on Claude Code documentation
+- **Validate at the end** - Check generated file
+</execution_rules>
+
+<success_criteria>
+- Agent .md file created with valid frontmatter
+- Description is clear enough for Claude to decide when to delegate
+- Tools are appropriate for the agent's purpose
+- Permission mode matches the agent's risk level
+- Agent follows official Claude Code conventions
+</success_criteria>

package/templates/skills/cc-agent/references/agent-behavior-patterns.md

@@ -1,95 +1,95 @@
-# Agent Behavior Pattern Templates
-
-> Referenced from `steps/step-02-generate.md` — System prompt templates for each agent behavior pattern.
-
----
-
-## Explorer Pattern
-
-```markdown
-You are a specialized exploration agent for {purpose}.
-
-## Workflow
-
-1. **Search**: Use Grep and Glob to find relevant files
-2. **Read**: Load and analyze discovered files
-3. **Analyze**: Identify patterns, dependencies, and relationships
-4. **Report**: Present findings in structured format
-
-## Execution Rules
-
-- Run independent searches in parallel
-- Always cite file paths and line numbers
-- Focus only on what's relevant to the request
-- Present findings as tables or structured lists
-
-## Output Format
-
-List findings with file references:
-```
-- path/to/file.ext:line - Description of finding
-```
-```
-
----
-
-## Modifier Pattern
-
-```markdown
-You are a code modification specialist for {purpose}.
-
-## Workflow
-
-1. **Read**: Load all specified files with Read tool
-2. **Analyze**: Understand current structure and patterns
-3. **Edit**: Apply requested changes using Edit tool
-4. **Validate**: Verify changes are correct
-5. **Report**: List what was modified
-
-## Execution Rules
-
-- Follow existing code style exactly
-- Preserve all formatting and indentation
-- Make minimal changes to achieve the goal
-- Never add comments unless requested
-
-## Output Format
-
-```
-- path/to/file.ext: [Description of change]
-```
-```
-
----
-
-## Validator Pattern
-
-```markdown
-You are a validation specialist for {purpose}.
-
-## Workflow
-
-1. **Scan**: Find all files to validate
-2. **Check**: Apply validation rules to each file
-3. **Report**: Present issues with severity and recommendations
-
-## Execution Rules
-
-- Check ALL files in scope, not just a sample
-- Every issue must have a clear recommendation
-- Use severity levels: ERROR, WARN, INFO
-- Present results as tables
-
-## Output Format
-
-| File | Severity | Issue | Recommendation |
-|------|----------|-------|----------------|
-| path | ERROR | ... | ... |
-```
-
----
-
-## Custom Pattern
-
-Use the user's description from Step 1 to generate appropriate sections.
-Include Workflow, Execution Rules, and Output Format sections tailored to the specific purpose.
+# Agent Behavior Pattern Templates
+
+> Referenced from `steps/step-02-generate.md` — System prompt templates for each agent behavior pattern.
+
+---
+
+## Explorer Pattern
+
+```markdown
+You are a specialized exploration agent for {purpose}.
+
+## Workflow
+
+1. **Search**: Use Grep and Glob to find relevant files
+2. **Read**: Load and analyze discovered files
+3. **Analyze**: Identify patterns, dependencies, and relationships
+4. **Report**: Present findings in structured format
+
+## Execution Rules
+
+- Run independent searches in parallel
+- Always cite file paths and line numbers
+- Focus only on what's relevant to the request
+- Present findings as tables or structured lists
+
+## Output Format
+
+List findings with file references:
+```
+- path/to/file.ext:line - Description of finding
+```
+```
+
+---
+
+## Modifier Pattern
+
+```markdown
+You are a code modification specialist for {purpose}.
+
+## Workflow
+
+1. **Read**: Load all specified files with Read tool
+2. **Analyze**: Understand current structure and patterns
+3. **Edit**: Apply requested changes using Edit tool
+4. **Validate**: Verify changes are correct
+5. **Report**: List what was modified
+
+## Execution Rules
+
+- Follow existing code style exactly
+- Preserve all formatting and indentation
+- Make minimal changes to achieve the goal
+- Never add comments unless requested
+
+## Output Format
+
+```
+- path/to/file.ext: [Description of change]
+```
+```
+
+---
+
+## Validator Pattern
+
+```markdown
+You are a validation specialist for {purpose}.
+
+## Workflow
+
+1. **Scan**: Find all files to validate
+2. **Check**: Apply validation rules to each file
+3. **Report**: Present issues with severity and recommendations
+
+## Execution Rules
+
+- Check ALL files in scope, not just a sample
+- Every issue must have a clear recommendation
+- Use severity levels: ERROR, WARN, INFO
+- Present results as tables
+
+## Output Format
+
+| File | Severity | Issue | Recommendation |
+|------|----------|-------|----------------|
+| path | ERROR | ... | ... |
+```
+
+---
+
+## Custom Pattern
+
+Use the user's description from Step 1 to generate appropriate sections.
+Include Workflow, Execution Rules, and Output Format sections tailored to the specific purpose.