appiq-solution 1.4.8 → 1.5.0

package/SuperClaude/CHANGELOG.md

@@ -1,109 +0,0 @@
-# Changelog
-
-## Legend
-| Symbol | Meaning | | Abbrev | Meaning |
-|--------|---------|---|--------|---------|
-| → | leads to | | cfg | configuration |
-| + | added | | MCP | Model Context Protocol |
-| - | removed | | UI | user interface |
-| ! | breaking | | deps | dependencies |
-
-All notable changes to SuperClaude will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [Unreleased]
-### Added
-- Community interaction files
-- GitHub issue & PR templates
-- Contributing guidelines
-
-## [4.0.0] - 2024-06-22
-### Added
-- **Core Configuration Framework**
-  - CLAUDE.md → Main cfg + ops rules
-  - RULES.md → Governance + severity system (C/H/M/L)
-  - PERSONAS.md → 9 cognitive archetypes
-  - MCP.md → Model Context Protocol integration patterns
-
-- **Slash Commands (18)**
-  - Dev: build, dev-setup, test
-  - Analysis: analyze, troubleshoot, improve, explain
-  - Ops: deploy, migrate, scan, estimate, cleanup, git
-  - Design: design
-  - Workflow: spawn, document
-  - System: load
-
-- **Shared Resources (26)**
-  - YAML configuration files
-  - Workflow patterns & templates
-  - Performance monitoring
-  - Error recovery strategies
-
-- **Cognitive Personas (9)**
-  - architect → System design & long-term thinking
-  - frontend → UX & interface optimization
-  - backend → Performance & reliability
-  - analyzer → Root cause analysis
-  - security → Threat modeling & secure design
-  - mentor → Teaching & guided discovery
-  - refactorer → Code quality & simplification
-  - performance → Speed optimization
-  - qa → Quality assurance & testing
-
-- **MCP Integration**
-  - Context7 → Documentation lookup
-  - Sequential → Complex analysis
-  - Magic → UI component generation
-  - Puppeteer → Browser automation
-
-- **Advanced Features**
-  - UltraCompressed mode (~70% token reduction)
-  - Token economy & smart model selection
-  - Research-first methodology
-  - Planning mode w/ --plan flag
-  - Thinking modes (basic→standard→deep→critical)
-  - Evidence-based decision making
-
-- **Installation & Setup**
-  - Global deployment to ~/.claude/
-  - Bash installation script
-  - Backup & migration support
-  - Verification & validation
-
-### Technical Details
-- **Languages**: Bash, YAML, Markdown
-- **Target**: Claude Code enhancement
-- **License**: MIT
-- **Compatibility**: Cross-platform (macOS, Windows, Linux)
-
-## Version History Notes
-
-### Versioning Strategy
-- **Major** (X.0.0): Breaking changes to core architecture
-- **Minor** (X.Y.0): New features, personas, or commands
-- **Patch** (X.Y.Z): Bug fixes, documentation, minor improvements
-
-### Breaking Changes Policy
-- Deprecated features → 1 version warning
-- Migration guides provided
-- Backward compatibility when possible
-
-### Release Process
-1. Feature development
-2. Testing & validation
-3. Documentation updates
-4. CHANGELOG.md update
-5. Version tag & release
-6. Community notification
-
----
-
-**Links:**
-- [Repository](https://github.com/NomenAK/SuperClaude)
-- [Issues](https://github.com/NomenAK/SuperClaude/issues)
-- [Contributing](CONTRIBUTING.md)
-- [License](LICENSE)
-
-*SuperClaude v4.0.0 | Configuration framework for Claude Code*

package/SuperClaude/CLAUDE.md

@@ -1,95 +0,0 @@
-# CLAUDE.md - SuperClaude Cfg
-
-## Legend
-| Symbol | Meaning | | Abbrev | Meaning |
-|--------|---------|---|--------|---------|
-| → | leads to | | cfg | configuration |
-| & | and/with | | docs | documentation |
-| > | greater than | | ops | operations |
-
-@RULES.md
-@MCP.md
-@PERSONAS.md
-
-## Core Cfg
-
-```yaml
-Philosophy: Code>docs | Simple→complex | Security first
-Communication: Concise format | Symbols: →|&:» | Bullets>prose
-Workflow: TodoRead()→TodoWrite(3+)→Execute | Update immediate
-Stack: React|TS|Vite + Node|Express|PostgreSQL + Git|ESLint|Jest
-Commands: /user:<command> [flags] | /task:<action> | Ex: /user:build --init
-```
-
-## Thinking Modes
-
-```yaml
-Activation: Natural language OR command flags
-Flags: --think | --think-hard | --ultrathink
-none: Single file|Basic | think: Multi-file|Standard
-think hard: Architecture|Complex | ultrathink: Redesign|Critical
-Examples: /user:analyze --code --think | /user:design --api --ultrathink
-```
-
-## Token Economy
-
-```yaml
-Targets: Minimal commands | Responses<4 lines | Concise docs
-Symbols: →(leads to) |(separator) &(combine) :(define) »(sequence)
-Remove: the|a|very|really|that|which | "in order to"→to | and→&
-```
-
-## UltraCompressed Mode
-
-```yaml
-Purpose: ~70% token reduction | Telegram-style docs | Symbols & abbrevs
-Activation: --uc flag | Natural language | Auto when context>70%
-Rules: shared/ultracompressed.yml | Remove filler | Use symbols
-Output: Direct info only | No intros/outros | Lists>prose
-Legend: Auto-generate | Used symbols/abbrevs only | Start of docs
-```
-
-## Code Economy
-
-```yaml
-Generation: No comments | Short names | No boilerplate
-Documentation: Only on request | Bullets>prose | Essential facts only
-Patterns: Destructure | Chain | Ternary | Arrow functions
-Output: Code only | No explanation unless asked
-```
-
-## Cost Optimization
-
-```yaml
-Models: Simple→sonnet | Complex→sonnet-4 | Critical→opus-4
-MCP: C7 progressive loading | Seq adaptive thinking | Batch similar
-Efficiency: Min tokens | Cache results | Batch ops
-```
-
-## Auto-Activation
-
-```yaml
-Files: *.tsx→frontend | *.sql→data | Docker→devops | *.test→qa
-Keywords: bug|error→debugger | optimize→performance | secure→security
-Context: TypeError→trace | Module error→deps | Permission→security
-Tasks: Auto-detect complexity→seamless task creation | ./claudedocs/tasks/in-progress→auto-resume
-```
-
-## Task Management
-
-```yaml
-Mode: Automatic | No user prompts | Seamless activation
-Detection: ≥8 complexity points→auto-create | 5-7→brief notify | <5→normal
-Triggers: "build|create|implement" + "system|feature" + complexity flags
-Flow: requirement→analyze→create→breakdown→implement | Background operation
-Recovery: Auto-resume active tasks | Context preservation | Git integration
-```
-
-## Performance
-
-```yaml
-Ops: Parallel>sequential | Batch similar | One in-progress
-```
-
----
-*SuperClaude v4.0.0 | Critical load order | Internal Claude cfg*

package/SuperClaude/CODE_OF_CONDUCT.md

@@ -1,45 +0,0 @@
-# Code of Conduct
-
-## Our Pledge
-
-We pledge to make participation in the SuperClaude community a welcoming experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-### Positive Behavior
-- Being respectful and inclusive
-- Providing constructive feedback
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-- Helping newcomers learn and contribute
-
-### Unacceptable Behavior
-- Harassment, trolling, or discriminatory language
-- Personal attacks or political arguments
-- Publishing private information without permission
-- Spam or off-topic content
-- Any conduct that could reasonably be considered inappropriate
-
-## Responsibilities
-
-Project maintainers are responsible for clarifying standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-## Scope
-
-This Code of Conduct applies within all project spaces, including:
-- GitHub repository (issues, PRs, discussions)
-- Project documentation
-- Community forums and chat
-- Project events and meetups
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team through GitHub issues. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.0.
-
----
-
-*SuperClaude v4.0.0 | Building a respectful community*

package/SuperClaude/CONTRIBUTING.md

@@ -1,225 +0,0 @@
-# Contributing to SuperClaude
-
-## Legend
-| Symbol | Meaning | | Abbrev | Meaning |
-|--------|---------|---|--------|---------|
-| → | leads to | | PR | pull request |
-| & | and/with | | cfg | configuration |
-
-Thanks for contributing to SuperClaude! This guide helps you get started.
-
-## Quick Start
-
-1. **Fork & Clone**
-   ```bash
-   git clone https://github.com/YOUR_USERNAME/SuperClaude.git
-   cd SuperClaude
-   ```
-
-2. **Create Branch**
-   ```bash
-   git checkout -b feature/your-feature-name
-   ```
-
-3. **Make Changes** → Test → Commit → Push → PR
-
-## Types of Contributions
-
-### 🐛 Bug Fixes
-- Use issue template
-- Include steps to reproduce
-- Test fix before submitting
-
-### ✨ New Features
-- Check existing issues first
-- Create feature request issue
-- Discuss approach before coding
-
-### 📚 Documentation
-- Fix typos, improve clarity
-- Add examples & use cases
-- Update README if needed
-
-### 🔧 Configuration Improvements
-- New slash commands (.claude/commands/)
-- YAML resources (.claude/commands/shared/)
-- Core configs (CLAUDE.md, RULES.md, etc.)
-
-## Development Guidelines
-
-### File Structure
-```
-SuperClaude/
-├── CLAUDE.md, RULES.md, PERSONAS.md, MCP.md  # Core configs
-├── .claude/commands/                          # Slash commands
-├── .claude/commands/shared/                   # YAML resources
-├── install.sh                                # Installation script
-└── README.md                                 # Documentation
-```
-
-### Code Standards
-- **YAML**: 2-space indentation, descriptive keys
-- **Markdown**: Clear headers, consistent formatting
-- **Shell**: Bash compatibility, error handling
-- **No executables**: Config framework only
-
-### Testing
-- Test install.sh on clean system
-- Verify slash commands work in Claude Code
-- Check YAML syntax validity
-- Test personas & MCP integration
-
-## Submission Process
-
-### 1. Before You Start
-- Search existing issues & PRs
-- Create issue for discussion (features)
-- Fork repository
-
-### 2. Development
-- Create feature branch
-- Make focused commits
-- Follow naming conventions
-- Test thoroughly
-
-### 3. Pull Request
-- Use PR template
-- Clear title & description
-- Link related issues
-- Request review
-
-### 4. Review Process
-- Maintainer review required
-- Address feedback promptly
-- Keep PR up to date
-- Squash commits if requested
-
-## Issue Guidelines
-
-### Bug Reports
-Include:
-- SuperClaude version
-- Claude Code version
-- Operating system
-- Steps to reproduce
-- Expected vs actual behavior
-- Error messages
-
-### Feature Requests
-Include:
-- Use case description
-- Proposed solution
-- Alternative solutions considered
-- Additional context
-
-## Slash Command Development
-
-### Creating New Commands
-1. **File**: `.claude/commands/your-command.md`
-2. **Format**: Follow existing command structure
-3. **Flags**: Use consistent flag patterns
-4. **Documentation**: Include examples
-5. **Integration**: Update index.md
-
-### Command Structure
-```markdown
-# Command Name
-Description & purpose
-
-## Flags
-- --flag1: Description
-- --flag2: Description
-
-## Examples
-/user:command --flag1
-```
-
-### YAML Resources
-1. **Location**: `.claude/commands/shared/`
-2. **Purpose**: Reusable configurations
-3. **Naming**: descriptive-name.yml
-4. **Structure**: Clear, documented sections
-
-## Persona Development
-
-### Guidelines
-- **Core Belief**: What drives this persona
-- **Primary Question**: Key question they ask
-- **Decision Pattern**: How they prioritize
-- **MCP Tools**: Which tools they prefer
-
-### Testing Personas
-- Test with various scenarios
-- Verify MCP integration
-- Check decision consistency
-- Document use cases
-
-## Documentation Standards
-
-### Writing Style
-- Concise & clear
-- Use symbols from legend
-- Bullet points > prose
-- Include examples
-
-### UltraCompressed Mode
-- Use abbreviations
-- Remove articles (the, a, that)
-- Symbol shortcuts (→, &, w/)
-- Auto-generate legends
-
-## Community Guidelines
-
-### Be Respectful
-- Professional communication
-- Constructive feedback only
-- Help newcomers
-- Credit contributions
-
-### Quality First
-- Test before submitting
-- Document changes
-- Follow established patterns
-- Consider maintenance impact
-
-## Getting Help
-
-### Resources
-- README.md → Overview & installation
-- Issues → Bug reports & discussions
-- Wiki → Extended documentation
-- Discussions → Community Q&A
-
-### Contact
-- Create issue for bugs/features
-- Use discussions for questions
-- Tag maintainers for urgent issues
-
-## Developer Certificate of Origin (DCO)
-
-By contributing to this project, you agree to the Developer Certificate of Origin (DCO). This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution.
-
-The DCO is legally binding statement that assures contributors have the right to submit their work under the project's license. All commits must be signed off with:
-
-```
-git commit -s -m "Your commit message"
-```
-
-This adds a `Signed-off-by` line to your commit message.
-
-## Recognition
-
-Contributors are recognized through:
-- GitHub contributor graph
-- CHANGELOG.md mentions
-- Issue/PR acknowledgments
-- Community discussions
-
-### Notable Contributors
-- @amgiiine - Commands Cheat Sheet and documentation improvements
-
----
-
-**Ready to contribute?** Create an issue or submit a PR!
-
-*SuperClaude v4.0.0 | Community-driven configuration framework*

package/SuperClaude/Commands_Cheat_Sheet.md

@@ -1,160 +0,0 @@
-# SuperClaude Commands Cheat Sheet
-
-## Analysis & Debugging Commands
-
-### `/user:analyze` - Multi-dimensional code analysis
-- `--code` - Code quality review
-- `--arch` - Architecture analysis
-- `--profile` - Performance profiling
-- `--security` - Security assessment
-- `--perf` - Performance bottlenecks
-- `--watch` - Continuous monitoring
-- `--interactive` - Guided improvement
-
-### `/user:troubleshoot` - Debug and fix issues
-- `--investigate` - Analyze issues
-- `--fix` - Complete bug fixing
-- `--five-whys` - Root cause analysis
-- `--prod` - Production issues
-
-### `/user:explain` - Technical explanations
-- `--depth [ELI5/Beginner/Intermediate/Expert]` - Set depth
-- `--visual` - Include diagrams
-- `--uc` - Ultra-compressed (~30% size)
-
-## Development Commands
-
-### `/user:build` - Build projects/features
-- `--react` - React app
-- `--api` - API with docs
-- `--magic` - UI generation
-- `--init` - New project
-- `--feature` - Feature implementation
-- `--tdd` - Test-driven development
-- `--watch` - Live reload
-
-### `/user:test` - Testing utilities
-- `--e2e` - End-to-end tests
-- `--integration` - Integration tests
-- `--coverage` - Coverage reports
-- `--watch` - Auto-test on changes
-- `--interactive` - Real-time feedback
-
-### `/user:dev-setup` - Development environment setup
-- Initialize development environment
-- Configure tools and dependencies
-
-## Improvement & Maintenance
-
-### `/user:improve` - Code/performance optimization
-- `--quality` - Code structure
-  - `--solid` - SOLID principles
-  - `--refactor` - Clean code
-  - `--metrics` - Quality reports
-- `--perf` - Performance optimization
-- `--iterate` - Iterative improvement (85% threshold)
-- `--watch` - Continuous improvement
-
-### `/user:cleanup` - Project maintenance
-- `--code` - Remove dead code, debug logs
-- `--files` - Clean build artifacts
-- `--deps` - Remove unused dependencies
-- `--git` - Clean branches/history
-- `--cfg` - Clean configurations
-- `--all` - Comprehensive cleanup
-- `--dry-run` - Preview changes
-
-### `/user:scan` - Security validation
-- `--validate` - Pre-execution safety
-- `--security` - Full security analysis
-- `--quick` - Fast critical issues
-- `--strict` - Zero-tolerance mode
-
-## Operations Commands
-
-### `/user:deploy` - Application deployment
-- `--env [dev/staging/prod]` - Target environment
-- `--rollback` - Revert deployment
-- `--plan` - Preview deployment
-
-### `/user:git` - Git workflow management
-- `--status` - Repository status
-- `--commit` - Commit changes
-- `--branch` - Branch management
-- `--sync` - Fetch/pull/push
-- `--merge` - Merge branches
-- `--stash` - Temporary changes
-- `--history` - Commit history
-- `--checkpoint` - Create snapshot
-- `--rollback` - Revert to checkpoint
-
-### `/user:migrate` - Database/code migration
-- Handle schema changes
-- Data migration workflows
-
-## Design & Documentation
-
-### `/user:design` - Software architecture
-- `--api` - REST/GraphQL design
-- `--ddd` - Domain-driven design
-- `--prd` - Product requirements
-
-### `/user:document` - Generate documentation
-- `--api` - API documentation
-- `--user` - User guides
-- `--uc` - Ultra-compressed (~70% reduction)
-
-### `/user:estimate` - Time/complexity predictions
-- Project estimation
-- Task complexity analysis
-
-## Workflow Commands
-
-### `/user:spawn` - Spawn specialized agents
-- `--task "<description>"` - Define specific task
-- Parallel execution capability
-- Specialized expertise (Frontend/Backend/DevOps/Data)
-
-### `/user:load` - Project context loading
-- Load project configuration
-- Initialize context
-
-## Universal Flags
-
-### Thinking Modes (apply to any command)
-- `--think` - Multi-component analysis
-- `--think-hard` - Complex system analysis
-- `--ultrathink` - Critical/complete redesign
-
-### MCP Server Controls
-- `--c7` - Force Context7 (docs)
-- `--seq` - Force Sequential (analysis)
-- `--magic` - Force Magic (UI)
-- `--pup` - Force Puppeteer (browser)
-- `--all-mcp` - Enable all MCPs
-- `--no-mcp` - Disable all MCPs
-
-### Planning & Documentation
-- `--plan` - Show plan before execution
-- `--watch` - Continuous monitoring
-- `--interactive` - Step-by-step guidance
-- `--uc` or `--ultracompressed` - Reduce output ~70%
-
-## Usage Pattern
-```
-/user:<command> [arguments] [flags]
-```
-
-## Examples
-- `/user:analyze --code --security --think`
-- `/user:build --react --magic --tdd`
-- `/user:troubleshoot --fix --prod --ultrathink`
-- `/user:improve --perf --iterate`
-- `/user:git --commit --plan`
-
-## Output Locations
-- Reports: `.claudedocs/reports/`
-- Metrics: `.claudedocs/metrics/`
-- Documentation: `/docs/[category]/`
-
-Version: SuperClaude v4.0.0

package/SuperClaude/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2024 NomenAK
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.