appiq-solution 1.4.8 → 1.4.9

package/#Tools/SuperClaude/.claude/commands/task.md

@@ -1,110 +0,0 @@
-# /task: - Task Management & Session Recovery
-
-@see shared/task-system.yml
-
-## Purpose
-Manage complex features & requirements across sessions with automatic breakdown, context preservation & recovery.
-
-## Syntax
-```bash
-/task:create <title> [--type feature|bugfix|refactor|docs|test] [--priority high|medium|low]
-/task:list [--status pending|in-progress|completed] [--priority high|medium|low]
-/task:start <id>
-/task:pause <id>
-/task:complete <id>
-/task:resume <id>
-/task:cancel <id>
-/task:show <id>
-/task:update <id> --status <status> --priority <priority>
-```
-
-## Workflow
-```yaml
-Creation:
-  1. Analyze requirement complexity
-  2. Generate unique task ID (YYYYMMDD-HHMMSS)
-  3. Break down into phases & steps
-  4. Create task file from template
-  5. Create git branch
-  6. Move to pending folder
-
-Execution:
-  1. Move to in-progress folder
-  2. Create git checkpoint
-  3. Execute steps sequentially
-  4. Update progress & context
-  5. Handle session breaks gracefully
-
-Completion:
-  1. Verify all steps completed
-  2. Run final tests
-  3. Create completion checkpoint
-  4. Move to completed folder
-  5. Merge git branch
-```
-
-## Auto-Detection
-```yaml
-Triggers:
-  - "build feature X"
-  - "implement functionality Y"
-  - "add component Z"
-  - Requirements >3 files
-  - Complex multi-step work
-
-Response:
-  "This looks like a multi-step task. Should I create a task breakdown?"
-  Options: [Yes - create task] [No - proceed directly]
-```
-
-## Session Recovery
-```yaml
-Startup:
-  1. Scan .tasks/in-progress/
-  2. Identify active tasks
-  3. Restore context from task files
-  4. Suggest resumption steps
-
-Context:
-  - Key architectural decisions
-  - Current implementation state
-  - Known blockers & solutions
-  - File modification history
-```
-
-## Examples
-```bash
-# Create new feature task
-/task:create "User authentication system" --type feature --priority high
-
-# List all pending tasks
-/task:list --status pending
-
-# Start working on a task
-/task:start 20250623-143052
-
-# Pause current work (auto-saves context)
-/task:pause 20250623-143052
-
-# Resume after session break
-/task:resume 20250623-143052
-
-# Mark task complete
-/task:complete 20250623-143052
-```
-
-## Integration
-- **Git**: Automatic branching & checkpoints
-- **TodoWrite**: Sync with current todo system
-- **Personas**: Task-specific persona activation
-- **MCP**: Context preservation across tools
-- **Commands**: Chain with other /user: commands
-
-## File Structure
-```
-./claudedocs/tasks/
-├── pending/feature-20250623-143052-user-auth.md
-├── in-progress/bugfix-20250623-144022-login-error.md
-├── completed/refactor-20250623-142033-api-cleanup.md
-└── templates/feature-template.md
-```

package/#Tools/SuperClaude/.claude/commands/test.md

@@ -1,67 +0,0 @@
-@include shared/constants.yml#Process_Symbols
-
-@include shared/command-templates.yml#Universal_Flags
-
-Create or run comprehensive tests for code in $ARGUMENTS.
-
-Thinking flags (optional):
-- --think→multi-component test planning
-- --think-hard→complex test arch & strategy
-- --ultrathink→comprehensive test system design
-
-MCP flags (optional):
-- --pup→browser-based E2E testing w/ Puppeteer | --c7→testing framework docs
-- --seq→complex test scenario planning | --no-mcp→native test runners only
-
-Examples:
-- `/user:test --e2e --pup --think` - E2E tests w/ Puppeteer & context analysis
-- `/user:test --coverage --c7` - Test w/ framework docs support
-- `/user:test --integration --seq --think-hard` - Complex test scenarios w/ deep planning
-
-Pre-test cleanup:
-- Clean test output dirs (coverage/, test-results/) | Remove test artifacts from previous runs
-- Reset test DB/state→clean baseline | Clear test cache & temp files
-
-When --coverage flag is present:
-- Generate comprehensive coverage reports
-- Identify untested code paths
-- Aim for >80% code coverage
-- Focus on critical business logic
-
-When --watch flag is present:
-- Set up automatic test execution on file changes
-- Provide fast feedback during development
-- Only run affected tests for efficiency
-- Continuous integration during development
-
-When --interactive flag is present:
-- Interactive test runner with real-time feedback
-- Allow test selection and filtering
-- Step-through debugging for failing tests
-- Live code coverage visualization
-
-When --e2e flag is present:
-- Create end-to-end tests for user flows
-- Test critical paths through the application
-- Include both happy paths and error scenarios
-- Use appropriate E2E testing frameworks
-
-Test types to implement:
-- Unit tests: Test individual functions, logic, and utilities in isolation
-- Integration tests: Test APIs, services, and database interactions
-- E2E tests: Test complete user workflows and critical paths
-
-## Testing Best Practices
-
-Follow testing standards:
-- Use descriptive test names that explain what is being tested
-- Follow AAA pattern: Arrange, Act, Assert
-- Use appropriate mocking for external dependencies
-- Create fixtures for consistent test data
-- Ensure tests are independent and can run in any order
-
-@include shared/command-templates.yml#Research_Requirements
-
-@include shared/command-templates.yml#Report_Output
-
-@include shared/constants.yml#Success_Messages

package/#Tools/SuperClaude/.claude/commands/troubleshoot.md

@@ -1,93 +0,0 @@
-@include shared/constants.yml#Process_Symbols
-
-@include shared/command-templates.yml#Universal_Flags
-
-Troubleshoot & resolve issues in code or system in $ARGUMENTS.
-
-Thinking flags (optional):
-- --think→multi-component debugging w/ context
-- --think-hard→complex system issues & race conditions
-- --ultrathink→critical prod issues or elusive bugs
-
-Examples:
-- `/user:troubleshoot --investigate --think` - Debug w/ full context
-- `/user:troubleshoot --five-whys --think-hard` - Deep root cause analysis
-- `/user:troubleshoot --prod --ultrathink` - Critical prod debugging
-
-Mode selection:
-
---investigate flag:
-- Focus→understanding & analyzing issue | Use debugging tools & techniques→gather info
-- Document findings w/o necessarily impl fixes | Useful→complex problems requiring deep analysis
-
---fix flag:
-- Complete full bug-fixing workflow | Create tests, impl solution & verify resolution
-- Document the fix and prevention measures
-- Default mode if no flag specified
-
-When --five-whys flag is present:
-- Apply root cause analysis methodology
-- Ask "why" iteratively to uncover underlying causes
-- Document each level of analysis
-- Propose systemic improvements to prevent recurrence
-
-When --prod flag is present:
-- Focus on production-specific issues
-- Analyze logs, monitoring data, and metrics
-- Consider performance and scaling factors
-- Ensure minimal disruption to live services
-- Implement safe rollout strategies
-
-Comprehensive troubleshooting workflow:
-
-1. **Reproduce & Understand**
-   - Create minimal reproduction steps
-   - Document expected vs actual behavior
-   - Identify affected components and users
-   - Determine severity and business impact
-
-2. **Investigate & Isolate**
-   - Use debugging tools and strategic logging
-   - Apply binary search to narrow problem scope
-   - Check recent changes (git blame/history)
-   - Analyze logs, stack traces, and monitoring data
-   - Rule out environmental factors
-
-3. **Root Cause Analysis**
-   - Identify the underlying cause, not just symptoms
-   - Use five-whys technique if needed
-   - Consider systemic issues
-   - Document contributing factors
-
-4. **Solution Development** (if --fix flag)
-   - Create failing test that reproduces the issue
-   - Implement minimal fix addressing root cause
-   - Ensure backward compatibility
-   - Consider edge cases and side effects
-
-5. **Verification & Prevention**
-   - Verify fix resolves the issue completely
-   - Run full test suite for regressions
-   - Test in realistic conditions
-   - Add monitoring for early detection
-   - Document lessons learned
-
-Investigation techniques:
-- Strategic logging and breakpoints
-- Performance profiling for bottlenecks
-- Memory analysis for leaks
-- Network inspection for API issues
-- Database query analysis
-
-For production issues:
-- Correlate with deployment timeline
-- Check for traffic patterns
-- Review configuration changes
-- Analyze resource utilization
-- Consider rollback if critical
-
-@include shared/command-templates.yml#Research_Requirements
-
-@include shared/command-templates.yml#Report_Output
-
-@include shared/constants.yml#Success_Messages

package/#Tools/SuperClaude/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,114 +0,0 @@
-name: 🐛 Bug Report
-description: Report a bug or issue with SuperClaude
-title: "[Bug] "
-labels: ["bug", "needs-triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for reporting a bug! Please provide the following information to help us fix it.
-
-  - type: input
-    id: superclaude-version
-    attributes:
-      label: SuperClaude Version
-      description: What version of SuperClaude are you using?
-      placeholder: v4.0.0
-    validations:
-      required: true
-
-  - type: input
-    id: claude-code-version
-    attributes:
-      label: Claude Code Version
-      description: What version of Claude Code are you using?
-      placeholder: Latest
-    validations:
-      required: true
-
-  - type: dropdown
-    id: operating-system
-    attributes:
-      label: Operating System
-      description: What operating system are you using?
-      options:
-        - macOS
-        - Windows
-        - Linux (Ubuntu)
-        - Linux (Other)
-        - Other
-    validations:
-      required: true
-
-  - type: textarea
-    id: bug-description
-    attributes:
-      label: Bug Description
-      description: A clear and concise description of what the bug is.
-      placeholder: Describe what happened...
-    validations:
-      required: true
-
-  - type: textarea
-    id: reproduction-steps
-    attributes:
-      label: Steps to Reproduce
-      description: Steps to reproduce the behavior
-      placeholder: |
-        1. Run command: /user:analyze --code
-        2. Open file X
-        3. See error...
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected-behavior
-    attributes:
-      label: Expected Behavior
-      description: What did you expect to happen?
-      placeholder: Command should analyze code successfully...
-    validations:
-      required: true
-
-  - type: textarea
-    id: actual-behavior
-    attributes:
-      label: Actual Behavior
-      description: What actually happened?
-      placeholder: Command failed with error...
-    validations:
-      required: true
-
-  - type: textarea
-    id: error-messages
-    attributes:
-      label: Error Messages
-      description: Include any error messages or logs
-      placeholder: |
-        ```
-        Error: Cannot find file...
-        ```
-    validations:
-      required: false
-
-  - type: textarea
-    id: additional-context
-    attributes:
-      label: Additional Context
-      description: Add any other context about the problem here
-      placeholder: Screenshots, configuration files, etc.
-    validations:
-      required: false
-
-  - type: checkboxes
-    id: terms
-    attributes:
-      label: Checklist
-      description: Please confirm the following
-      options:
-        - label: I have searched for existing issues
-          required: true
-        - label: I have provided all required information
-          required: true
-        - label: I can reproduce this issue consistently
-          required: false

package/#Tools/SuperClaude/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,119 +0,0 @@
-name: ✨ Feature Request
-description: Suggest a new feature or enhancement for SuperClaude
-title: "[Feature] "
-labels: ["enhancement", "needs-discussion"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for suggesting a feature! Please provide details to help us understand your request.
-
-  - type: dropdown
-    id: feature-type
-    attributes:
-      label: Feature Type
-      description: What type of feature are you requesting?
-      options:
-        - New Slash Command
-        - New Persona
-        - MCP Integration
-        - Configuration Enhancement
-        - Documentation Improvement
-        - Installation/Setup
-        - Other
-    validations:
-      required: true
-
-  - type: textarea
-    id: problem-description
-    attributes:
-      label: Problem Description
-      description: What problem does this feature solve?
-      placeholder: I'm frustrated when I try to... because...
-    validations:
-      required: true
-
-  - type: textarea
-    id: proposed-solution
-    attributes:
-      label: Proposed Solution
-      description: Describe the solution you'd like to see
-      placeholder: |
-        I would like to see...
-        
-        Example usage:
-        /user:newcommand --flag
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternative-solutions
-    attributes:
-      label: Alternative Solutions
-      description: Describe alternatives you've considered
-      placeholder: I also considered... but it doesn't work because...
-    validations:
-      required: false
-
-  - type: textarea
-    id: use-cases
-    attributes:
-      label: Use Cases
-      description: Describe specific scenarios where this would be useful
-      placeholder: |
-        1. When working on React projects...
-        2. During code reviews...
-        3. For debugging performance issues...
-    validations:
-      required: true
-
-  - type: textarea
-    id: examples
-    attributes:
-      label: Examples
-      description: Provide concrete examples of how this feature would work
-      placeholder: |
-        Command: /user:example --new-flag
-        Output: Expected behavior...
-        
-        Persona usage:
-        /persona:newtype → specialized behavior
-    validations:
-      required: false
-
-  - type: dropdown
-    id: priority
-    attributes:
-      label: Priority
-      description: How important is this feature to you?
-      options:
-        - Nice to have
-        - Would be helpful
-        - Important for my workflow
-        - Critical/Blocking
-    validations:
-      required: true
-
-  - type: textarea
-    id: additional-context
-    attributes:
-      label: Additional Context
-      description: Add any other context, screenshots, or examples
-      placeholder: Links to similar features, mockups, related issues...
-    validations:
-      required: false
-
-  - type: checkboxes
-    id: terms
-    attributes:
-      label: Checklist
-      description: Please confirm the following
-      options:
-        - label: I have searched for existing feature requests
-          required: true
-        - label: I have provided a clear use case
-          required: true
-        - label: I'm willing to help test this feature
-          required: false
-        - label: I'm willing to help implement this feature
-          required: false

package/#Tools/SuperClaude/.github/ISSUE_TEMPLATE/question.yml

@@ -1,87 +0,0 @@
-name: ❓ Question
-description: Ask a question about SuperClaude usage or configuration
-title: "[Question] "
-labels: ["question", "help-wanted"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Have a question about SuperClaude? We're here to help!
-        
-        **Tip:** Consider using [Discussions](../../discussions) for general questions and community help.
-
-  - type: dropdown
-    id: question-type
-    attributes:
-      label: Question Type
-      description: What type of question is this?
-      options:
-        - Installation/Setup
-        - Command Usage
-        - Persona Configuration
-        - MCP Integration
-        - Troubleshooting
-        - Best Practices
-        - Other
-    validations:
-      required: true
-
-  - type: textarea
-    id: question
-    attributes:
-      label: Your Question
-      description: What would you like to know?
-      placeholder: How do I... / Why does... / What's the best way to...
-    validations:
-      required: true
-
-  - type: textarea
-    id: context
-    attributes:
-      label: Context
-      description: Provide context about what you're trying to achieve
-      placeholder: |
-        I'm trying to...
-        My setup is...
-        I've already tried...
-    validations:
-      required: false
-
-  - type: textarea
-    id: current-config
-    attributes:
-      label: Current Configuration
-      description: Share relevant configuration or commands you're using
-      placeholder: |
-        ```
-        /user:command --flags
-        Persona: architect
-        Claude Code version: latest
-        ```
-    validations:
-      required: false
-
-  - type: textarea
-    id: attempted-solutions
-    attributes:
-      label: What Have You Tried?
-      description: What solutions have you already attempted?
-      placeholder: |
-        1. I tried reading the documentation...
-        2. I searched for similar issues...
-        3. I tested with different settings...
-    validations:
-      required: false
-
-  - type: checkboxes
-    id: terms
-    attributes:
-      label: Checklist
-      description: Please confirm the following
-      options:
-        - label: I have read the README.md
-          required: true
-        - label: I have searched existing issues and discussions
-          required: true
-        - label: This is not a bug report (use Bug Report template instead)
-          required: true

package/#Tools/SuperClaude/.github/pull_request_template.md

@@ -1,62 +0,0 @@
-# Pull Request
-
-## Legend
-| Symbol | Meaning | | Abbrev | Meaning |
-|--------|---------|---|--------|---------|
-| → | leads to | | cfg | configuration |
-| ✓ | completed | | PR | pull request |
-
-## Summary
-Brief description of changes
-
-## Type of Change
-- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
-- [ ] ✨ New feature (non-breaking change which adds functionality)
-- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] 📚 Documentation update
-- [ ] 🔧 Configuration change
-- [ ] 🎨 Code style/formatting change
-- [ ] ♻️ Refactoring (no functional changes)
-- [ ] ⚡ Performance improvement
-- [ ] 🔒 Security fix
-
-## Changes Made
-- Change 1
-- Change 2
-- Change 3
-
-## Testing
-- [ ] Tested install.sh on clean system
-- [ ] Verified slash commands work in Claude Code
-- [ ] Checked YAML syntax validity
-- [ ] Tested persona functionality
-- [ ] Tested MCP integration
-- [ ] Manual testing performed
-- [ ] All existing tests pass
-
-## Related Issues
-Fixes #(issue number)
-Closes #(issue number)
-Related to #(issue number)
-
-## Screenshots (if applicable)
-<!-- Add screenshots to demonstrate visual changes -->
-
-## Checklist
-- [ ] My code follows the project's style guidelines
-- [ ] I have performed a self-review of my code
-- [ ] I have commented my code, particularly in hard-to-understand areas
-- [ ] I have made corresponding changes to the documentation
-- [ ] My changes generate no new warnings
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] New and existing unit tests pass locally with my changes
-- [ ] Any dependent changes have been merged and published
-
-## Additional Notes
-<!-- Any additional information, concerns, or notes for reviewers -->
-
-## Breaking Changes
-<!-- If this is a breaking change, describe what users need to do to migrate -->
-
----
-**Ready for review!** 🚀