claude-code-templates 1.21.1 → 1.21.2

package/.github/workflows/publish-package.yml

@@ -1,125 +0,0 @@
-name: Publish Package to GitHub Packages
-
-on:
-  release:
-    types: [published]
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Version to publish (e.g., patch, minor, major, or specific version like 1.15.0)'
-        required: true
-        default: 'patch'
-
-permissions:
-  contents: write
-  packages: write
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '18'
-          registry-url: 'https://npm.pkg.github.com'
-          scope: '@davila7'
-
-      - name: Configure package for GitHub Packages
-        working-directory: ./cli-tool
-        run: |
-          # Update package.json for GitHub Packages
-          npm pkg set name="@davila7/claude-code-templates"
-          npm pkg set repository.type="git"
-          npm pkg set repository.url="git+https://github.com/davila7/claude-code-templates.git"
-          npm pkg set publishConfig.registry="https://npm.pkg.github.com"
-          
-          echo "Updated package.json for GitHub Packages:"
-          cat package.json
-
-      - name: Install dependencies
-        working-directory: ./cli-tool
-        run: npm ci
-
-      - name: Run tests
-        working-directory: ./cli-tool
-        run: npm test
-
-      - name: Bump version
-        working-directory: ./cli-tool
-        run: |
-          if [[ "${{ github.event.inputs.version }}" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
-            # Specific version provided
-            npm version ${{ github.event.inputs.version }} --no-git-tag-version
-          else
-            # Semver bump (patch, minor, major)
-            npm version ${{ github.event.inputs.version || 'patch' }} --no-git-tag-version
-          fi
-          
-          NEW_VERSION=$(node -p "require('./package.json').version")
-          echo "NEW_VERSION=$NEW_VERSION" >> $GITHUB_ENV
-
-      - name: Publish to GitHub Packages
-        working-directory: ./cli-tool
-        run: npm publish
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Create and push git tag
-        run: |
-          git config --local user.email "action@github.com"
-          git config --local user.name "GitHub Action"
-          
-          git add cli-tool/package.json
-          git commit -m "chore: bump version to ${{ env.NEW_VERSION }}"
-          git tag "v${{ env.NEW_VERSION }}"
-          git push origin main
-          git push origin "v${{ env.NEW_VERSION }}"
-
-      - name: Create GitHub Release
-        run: |
-          gh release create "v${{ env.NEW_VERSION }}" \
-            --title "Claude Code Templates v${{ env.NEW_VERSION }}" \
-            --notes "## 📦 New Release: v${{ env.NEW_VERSION }}
-
-          **Installation:**
-          \`\`\`bash
-          npm install -g @davila7/claude-code-templates
-          \`\`\`
-
-          **GitHub Packages:**
-          \`\`\`bash
-          npm install -g @davila7/claude-code-templates --registry=https://npm.pkg.github.com
-          \`\`\`
-
-          **What's Changed:**
-          - Package published to GitHub Packages
-          - Available as @davila7/claude-code-templates
-          - Full CLI functionality with all aliases (cct, claude-init, etc.)
-
-          **Usage:**
-          \`\`\`bash
-          npx @davila7/claude-code-templates --help
-          cct --help  # If installed globally
-          \`\`\`
-
-          🤖 Generated automatically by GitHub Actions"
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Summary
-        run: |
-          echo "🎉 Package Published Successfully!"
-          echo "================================="
-          echo "Package: @davila7/claude-code-templates"
-          echo "Version: ${{ env.NEW_VERSION }}"
-          echo "Registry: GitHub Packages"
-          echo ""
-          echo "Install with:"
-          echo "npm install -g @davila7/claude-code-templates --registry=https://npm.pkg.github.com"

package/.mcp.json

@@ -1,4 +0,0 @@
-{
-  "mcpServers": {
-  }
-}

package/CLAUDE.md

@@ -1,482 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-This is a Node.js CLI tool for setting up Claude Code configurations and providing real-time analytics. The project uses modern JavaScript/Node.js development practices and includes a comprehensive analytics dashboard with modular architecture.
-
-## Development Commands
-
-### Package Management
-- `npm install` - Install all dependencies
-- `npm install --save <package>` - Install a production dependency
-- `npm install --save-dev <package>` - Install a development dependency
-- `npm update` - Update all dependencies
-- `npm audit` - Check for security vulnerabilities
-- `npm audit fix` - Fix security vulnerabilities
-
-### Application Commands
-- `npm start` - Run the CLI tool
-- `npm run analytics:start` - Start the analytics dashboard server
-- `npm run analytics:test` - Run analytics-specific tests
-- `node src/analytics.js` - Direct analytics server startup
-
-### Testing Commands
-- `npm test` - Run all tests with Jest
-- `npm run test:watch` - Run tests in watch mode
-- `npm run test:coverage` - Run tests with coverage report
-- `npm run test:unit` - Run unit tests only
-- `npm run test:integration` - Run integration tests only
-- `npm run test:e2e` - Run end-to-end tests
-- `npm run test:analytics` - Run analytics module tests
-- `npm run test:all` - Run comprehensive test suite
-
-### Code Quality Commands
-- `npm run lint` - Run ESLint (if configured)
-- `npm run format` - Format code (if configured)
-- `node --check src/analytics.js` - Check syntax
-
-### Development Tools
-- `npm run dev:link` - Link package for local development
-- `npm run dev:unlink` - Unlink package
-- `npm version patch|minor|major` - Bump version
-- `npm publish` - Publish to npm registry
-
-## Analytics Dashboard
-
-### Quick Start
-```bash
-# Start the analytics dashboard
-npm run analytics:start
-
-# Open browser to http://localhost:3333
-# The dashboard provides real-time monitoring of Claude Code sessions
-```
-
-### Key Features
-- **Real-time Session Monitoring** - Live tracking of active Claude Code conversations
-- **Conversation State Detection** - "Claude working...", "User typing...", "Awaiting input..."
-- **Performance Analytics** - System health, memory usage, and performance metrics
-- **WebSocket Integration** - Real-time updates without polling
-- **Export Capabilities** - CSV/JSON export of conversation data
-- **Browser Notifications** - Desktop alerts for state changes
-
-### Architecture
-The analytics dashboard follows a modular architecture with:
-- **Backend Modules**: StateCalculator, ProcessDetector, ConversationAnalyzer, FileWatcher, DataCache
-- **Frontend Components**: Dashboard, ConversationTable, Charts, Services
-- **Real-time Communication**: WebSocket server with notification management
-- **Performance Monitoring**: Comprehensive metrics and health monitoring
-- **Testing Framework**: Unit, integration, and performance tests
-
-## Technology Stack
-
-### Core Technologies
-- **Node.js** - Runtime environment (v14.0.0+)
-- **Express.js** - Web server framework
-- **WebSocket** - Real-time communication (ws library)
-- **Chokidar** - File system watching
-- **Jest** - Testing framework
-
-### Frontend Technologies
-- **Vanilla JavaScript** - No framework dependencies for maximum compatibility
-- **Chart.js** - Data visualization
-- **WebSocket Client** - Real-time updates
-- **CSS3** - Modern styling with responsive design
-
-### Development Tools
-- **fs-extra** - Enhanced file system operations
-- **chalk** - Terminal string styling
-- **boxen** - Terminal boxes
-- **commander** - CLI argument parsing
-- **inquirer** - Interactive command line prompts
-
-### CLI Dependencies
-- **commander** - Command-line interface framework
-- **inquirer** - Interactive command line prompts
-- **ora** - Terminal spinners
-- **boxen** - Terminal boxes for notifications
-- **open** - Cross-platform file opener
-
-### Analytics Dependencies
-- **express** - Web server framework
-- **ws** - WebSocket library for real-time communication
-- **chokidar** - File system watcher
-- **fs-extra** - Enhanced file system operations
-- **chalk** - Terminal string styling
-
-### Testing Framework
-- **Jest** - JavaScript testing framework
-- **jest-watch-typeahead** - Interactive test watching
-- Comprehensive test coverage with unit, integration, and performance tests
-
-### Code Quality Tools
-- **ESLint** - JavaScript linting (if configured)
-- **Prettier** - Code formatting (if configured)
-- **Node.js built-in** - Syntax checking with `node --check`
-
-## Project Structure Guidelines
-
-### File Organization
-```
-src/
-├── index.js             # CLI entry point
-├── analytics.js         # Analytics dashboard server
-├── analytics/           # Analytics modules
-│   ├── core/           # Core business logic
-│   │   ├── StateCalculator.js
-│   │   ├── ProcessDetector.js
-│   │   ├── ConversationAnalyzer.js
-│   │   └── FileWatcher.js
-│   ├── data/           # Data management
-│   │   └── DataCache.js
-│   ├── notifications/   # Real-time communication
-│   │   ├── WebSocketServer.js
-│   │   └── NotificationManager.js
-│   └── utils/          # Utilities
-│       └── PerformanceMonitor.js
-├── analytics-web/       # Frontend components
-│   ├── index.html      # Main dashboard page
-│   ├── components/     # UI components
-│   ├── services/       # Frontend services
-│   └── assets/         # Static assets
-├── templates/           # Configuration templates
-└── utils/              # CLI utilities
-tests/
-├── unit/               # Unit tests
-├── integration/        # Integration tests
-├── e2e/               # End-to-end tests
-└── fixtures/          # Test data
-```
-
-### Naming Conventions
-- **Files/Modules**: Use PascalCase for classes (`StateCalculator.js`), camelCase for utilities
-- **Classes**: Use PascalCase (`StateCalculator`)
-- **Functions/Variables**: Use camelCase (`getUserData`)
-- **Constants**: Use UPPER_SNAKE_CASE (`API_BASE_URL`)
-- **Private methods**: Prefix with underscore (`_privateMethod`)
-
-## Node.js Guidelines
-
-### Module Organization
-- Use CommonJS modules (`module.exports`, `require()`)
-- Organize related functionality into classes
-- Keep modules focused and single-purpose
-- Use dependency injection for testability
-- Document public APIs with JSDoc comments
-
-### Code Style
-- Use meaningful variable and function names
-- Keep functions focused and single-purpose
-- Use async/await for asynchronous operations
-- Handle errors appropriately with try/catch blocks
-- Use console logging with appropriate levels (chalk for styling)
-
-### Best Practices
-- Use `fs-extra` for enhanced file operations
-- Prefer `path.join()` for cross-platform path handling
-- Use async/await instead of callbacks where possible
-- Handle process signals for graceful shutdown
-- Use environment variables for configuration
-
-## Testing Standards
-
-### Test Structure
-- Organize tests to mirror source code structure
-- Use descriptive test names that explain the behavior
-- Follow AAA pattern (Arrange, Act, Assert)
-- Use Jest fixtures and mocks for test data
-- Group related tests in `describe` blocks
-
-### Test Categories
-- **Unit Tests** - Test individual modules and functions in isolation
-- **Integration Tests** - Test module interactions and complete workflows
-- **Performance Tests** - Test system performance and memory usage
-- **E2E Tests** - Test complete user scenarios end-to-end
-
-### Jest Configuration
-```javascript
-// jest.config.js
-module.exports = {
-  testEnvironment: 'node',
-  collectCoverageFrom: [
-    'src/**/*.js',
-    '!src/**/*.test.js'
-  ],
-  coverageThreshold: {
-    global: {
-      branches: 70,
-      functions: 70,
-      lines: 70,
-      statements: 70
-    }
-  }
-};
-```
-
-### Coverage Goals
-- Aim for 70%+ overall test coverage (80%+ for core modules)
-- Write unit tests for business logic
-- Use integration tests for module interactions
-- Mock external dependencies and services
-- Test error conditions and edge cases
-
-### Test Examples
-```javascript
-// Unit test example
-describe('StateCalculator', () => {
-  let stateCalculator;
-  
-  beforeEach(() => {
-    stateCalculator = new StateCalculator();
-  });
-  
-  it('should detect active state for recent messages', () => {
-    const messages = [/* test data */];
-    const lastModified = new Date();
-    
-    const state = stateCalculator.determineConversationState(messages, lastModified);
-    
-    expect(state).toBe('active');
-  });
-});
-```
-
-## Dependency Management
-
-### Node.js Environment Setup
-```bash
-# Ensure Node.js 14+ is installed
-node --version
-
-# Install dependencies
-npm install
-
-# Install development dependencies
-npm install --save-dev jest
-
-# Link for local development
-npm link
-```
-
-### Package Management Best Practices
-- Use `package.json` for dependency management
-- Pin major versions to avoid breaking changes
-- Use `npm audit` to check for security vulnerabilities
-- Keep dependencies up to date with `npm update`
-
-## Analytics Modular Architecture
-
-### Implementation Details
-The analytics dashboard has been refactored into a modular architecture in 4 phases:
-
-#### Phase 1: Backend Modularization
-- **StateCalculator** - Conversation state detection logic
-- **ProcessDetector** - Running process detection and correlation
-- **ConversationAnalyzer** - Message parsing and analysis
-- **FileWatcher** - Real-time file system monitoring
-- **DataCache** - Multi-level caching system
-
-#### Phase 2: Frontend Modularization  
-- **Dashboard** - Main component orchestration
-- **ConversationTable** - Interactive conversation display
-- **Charts** - Data visualization components
-- **StateService** - Reactive state management
-- **DataService** - API communication with caching
-- **WebSocketService** - Real-time communication
-
-#### Phase 3: Real-time Communication
-- **WebSocketServer** - Server-side WebSocket management
-- **NotificationManager** - Event-driven notifications
-- **Real-time Updates** - Live conversation state changes
-- **Fallback Mechanisms** - Polling when WebSocket unavailable
-
-#### Phase 4: Testing & Performance
-- **Comprehensive Test Suite** - Unit, integration, and performance tests
-- **PerformanceMonitor** - System health and metrics tracking
-- **Memory Management** - Automatic cleanup and optimization
-- **Production Readiness** - Performance monitoring and error tracking
-
-## Security Guidelines
-
-### Dependencies
-- Regularly update dependencies with `npm audit` and `npm update`
-- Use `npm audit` to check for known vulnerabilities
-- Pin major versions in package.json to avoid breaking changes
-- Use environment variables for sensitive configuration
-
-### Code Security
-- Validate input data appropriately
-- Use environment variables for API keys and configuration
-- Implement proper error handling without exposing sensitive information
-- Sanitize file paths and user inputs
-- Use HTTPS for production deployments
-
-## Development Workflow
-
-### Before Starting
-1. Check Node.js version compatibility (14.0.0+)
-2. Run `npm install` to install dependencies
-3. Check syntax with `node --check src/analytics.js`
-4. Run initial tests with `npm test`
-
-### During Development
-1. Use meaningful variable and function names
-2. Run tests frequently to catch issues early: `npm run test:watch`
-3. For frontend changes, let user handle analytics server startup - don't run `npm run analytics:start` automatically
-4. Use meaningful commit messages
-
-### Before Committing
-1. Run full test suite: `npm test`
-2. Check syntax: `node --check src/analytics.js`
-3. Test analytics functionality: `npm run analytics:test`
-4. Ensure no console errors in browser (if testing frontend)
-5. Run performance tests if available
-
-## Component System Architecture
-
-### Core Component Types
-
-This CLI tool manages a comprehensive component system for Claude Code configurations:
-
-#### 🤖 Agents (600+ specialists)
-AI specialists organized by domain expertise:
-- **Development**: `frontend-developer`, `fullstack-developer`, `devops-engineer`
-- **Security**: `security-auditor`, `penetration-tester`, `compliance-specialist`
-- **Data/AI**: `data-scientist`, `ml-engineer`, `nlp-engineer`
-- **Business**: `product-strategist`, `business-analyst`, `legal-advisor`
-
-#### ⚡ Commands (200+ automations)
-Custom slash commands for development workflows:
-- **Setup**: `/setup-ci-cd-pipeline`, `/setup-testing`, `/migrate-to-typescript`
-- **Performance**: `/optimize-bundle`, `/performance-audit`, `/add-caching`
-- **Testing**: `/generate-tests`, `/setup-e2e`, `/test-coverage`
-- **Documentation**: `/update-docs`, `/generate-api-docs`, `/create-guide`
-
-#### 🔌 MCPs (Model Context Protocol Integrations)
-External service connections:
-- **Databases**: `postgresql-integration`, `supabase`, `mysql-integration`
-- **Development**: `github-integration`, `context7`, `filesystem-access`
-- **Browser**: `playwright-mcp`, `browsermcp`, `browser-use-mcp-server`
-
-#### ⚙️ Settings
-Claude Code configuration files:
-- **Performance**: `performance-optimization`, `bash-timeouts`, `mcp-timeouts`
-- **Security**: `read-only-mode`, `deny-sensitive-files`, `allow-git-operations`
-- **Statuslines**: `context-monitor`, `git-branch-statusline`, `time-statusline`
-
-#### 🪝 Hooks
-Automation triggers for development workflows:
-- **Git**: `auto-git-add`, `smart-commit`, `pre-commit-validation`
-- **Notifications**: `discord-notifications`, `slack-notifications`, `telegram-notifications`
-- **Performance**: `performance-monitor`, `lint-on-save`, `test-runner`
-
-### Component Installation System
-
-#### CLI Installation Patterns
-```bash
-# Install specific components
-npx claude-code-templates@latest --agent <name>
-npx claude-code-templates@latest --command <name>
-npx claude-code-templates@latest --mcp <name>
-npx claude-code-templates@latest --setting <name>
-npx claude-code-templates@latest --hook <name>
-
-# Batch installation
-npx claude-code-templates@latest --agent security-auditor --command security-audit --setting read-only-mode
-
-# Interactive mode
-npx claude-code-templates@latest
-```
-
-#### Special Component Features
-
-**Statusline System with Python Scripts**
-- Statuslines can reference external Python scripts
-- Files are downloaded automatically to `.claude/scripts/` relative to project
-- Example: `statusline/context-monitor` installs both JSON config and Python script
-- Implementation in `src/index.js:installIndividualSetting()`:
-
-```javascript
-if (settingName.includes('statusline/')) {
-  const pythonFileName = settingName.split('/')[1] + '.py';
-  const pythonUrl = githubUrl.replace('.json', '.py');
-  additionalFiles['.claude/scripts/' + pythonFileName] = {
-    content: pythonContent,
-    executable: true
-  };
-}
-```
-
-### Component Generation System
-
-The `generate_components_json.py` script creates the component catalog:
-- Scans all component directories recursively
-- Excludes `.py` files from public listings (they remain as background dependencies)
-- Generates `docs/components.json` for the web interface at aitmpl.com
-- Handles file content embedding and metadata extraction
-
-## Important Implementation Notes
-
-### Path Handling
-- **Relative Paths**: Always use relative paths like `.claude/scripts/` for project-local files
-- **Cross-platform**: Use `path.join()` for cross-platform compatibility
-- **No Hardcoding**: Never hardcode user home directories or absolute paths
-
-### Context Monitor Implementation
-The statusline context monitor system demonstrates key architectural patterns:
-- **Component Download**: Automatic download of related files (Python scripts)
-- **Relative Installation**: Files installed relative to project, not globally
-- **Background Dependencies**: Python files excluded from public component listings
-- **Dynamic Loading**: Components loaded and executed dynamically by Claude Code
-
-### Error Handling Patterns
-- Use try/catch blocks for async operations
-- Log errors with appropriate context using chalk for styling
-- Provide helpful error messages to users
-- Handle missing files or directories gracefully
-- Implement fallback mechanisms for network operations
-
-### Component Development Guidelines
-
-#### Adding New Components
-1. **Structure**: Follow existing directory patterns in `cli-tool/components/`
-2. **Naming**: Use descriptive, hyphenated names (`security-auditor.md`)
-3. **Documentation**: Include clear descriptions and usage examples
-4. **Testing**: Add tests for complex logic components
-5. **Generation**: Run `python generate_components_json.py` to update catalog
-
-#### Modifying Existing Components
-1. **Backward Compatibility**: Ensure changes don't break existing installations
-2. **Version Management**: Consider version bumping for breaking changes
-3. **Testing**: Test component installation with `--setting`, `--agent`, etc.
-4. **Documentation**: Update component descriptions if functionality changes
-
-### Publishing Workflow
-
-#### Version Management
-```bash
-# Bump version (automatically updates package.json)
-npm version patch   # 1.20.2 -> 1.20.3
-npm version minor   # 1.20.3 -> 1.21.0  
-npm version major   # 1.21.0 -> 2.0.0
-
-# Publish to npm
-npm publish
-```
-
-#### Pre-publish Checklist
-1. All tests passing (`npm test`)
-2. Component catalog updated (`python generate_components_json.py`)
-3. No hardcoded paths or sensitive information
-4. Version bumped appropriately
-5. Git commits include all relevant files
-
-### Component Security
-- Never include hardcoded credentials or API keys in components
-- Validate all user inputs in components
-- Use relative paths (`.claude/scripts/`) instead of absolute paths
-- Review components for potential security vulnerabilities before publishing
-
-This codebase represents a comprehensive Claude Code component ecosystem with real-time analytics, modular architecture, and extensive automation capabilities. The system is designed for scalability, maintainability, and ease of use while providing powerful development workflow enhancements.

package/CODE_OF_CONDUCT.md

@@ -1,82 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [dan.avila7@gmail.com](mailto:dan.avila7@gmail.com). All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.