auto-context-cli 1.0.0__py3-none-any.whl

auto_context/templates/profile.template.md

@@ -0,0 +1,20 @@
+# Agent Memory & Developer Profile
+
+> **Owner:** {{USERNAME}}  
+> **Initialized:** {{DATE_NOW}}  
+> **Repository:** {{REPO_NAME}}  
+> **Visibility:** Private Central Agent Brain  
+
+---
+
+## 1. Developer Preferences & Communication Style
+- **Language & Tone:** Provide friendly, structured explanations in clear Bengali alongside English technical terms and bash/PowerShell snippets.
+- **Code Architecture:** Adhere to clean code, Single Responsibility Principle (SRP), early return guard clauses, and strict type safety.
+- **Git Hygiene:** Use atomic conventional commits (`feat:`, `fix:`, `docs:`, `refactor:`, `chore:`).
+
+---
+
+## 2. Central Knowledge Base Index
+- **Global Rules:** Defined in `rules/` (automatically synchronized across all local projects).
+- **Reusable Skills:** Stored in `skills/` (available on-demand via Two-Tier Progressive Disclosure).
+- **MCP Server Presets:** Cataloged in `mcp/` (referenced securely via environment variables).

auto_context/templates/rule.template.md

@@ -0,0 +1,19 @@
+---
+name: {{RULE_NAME}}
+description: Custom rule for {{RULE_NAME}}. Explain when and how the agent should apply this rule.
+trigger: always_on
+---
+
+# Rule: {{RULE_TITLE}}
+
+## Objective
+Define the goal and purpose of this rule.
+
+## Guidelines & Constraints
+- **Constraint 1:** Describe specific coding standards, naming conventions, or prohibited patterns.
+- **Constraint 2:** Security protocols, credential management, or access boundaries.
+- **Constraint 3:** Testing or documentation requirements.
+
+## Enforcement
+AI coding agents (Antigravity, Cursor, Claude Code, Copilot) operating in this workspace must adhere strictly to these instructions.
+

auto_context/templates/rules/code-standards.md

@@ -0,0 +1,24 @@
+---
+name: code-standards
+description: Enforces clean code principles, DRY architecture, early return patterns, and defensive error handling.
+trigger: always_on
+---
+
+# Rule: Code Quality & Architecture Standards
+
+## Objective
+Maintain readable, maintainable, modular, and type-safe codebases with clear error handling.
+
+## Guidelines & Constraints
+1. **Defensive Coding & Early Return:**
+   - Prefer guard clauses and early returns to reduce nested indentation.
+   - Always validate inputs and handle edge cases at the beginning of functions.
+2. **Clean Code & Self-Documenting Logic:**
+   - Keep functions focused on a single responsibility (SRP).
+   - Write descriptive variable and function names; avoid cryptic abbreviations.
+   - Preserve existing comments and docstrings.
+3. **Structured Error Handling:**
+   - Never suppress exceptions with empty `catch` or `except` blocks.
+   - Log actionable error messages that include relevant context (e.g. invalid inputs, resource identifiers).
+4. **Conventional Git Commits:**
+   - Write semantic commit messages (`feat:`, `fix:`, `docs:`, `refactor:`, `chore:`).

auto_context/templates/rules/security-boundaries.md

@@ -0,0 +1,21 @@
+---
+name: security-boundaries
+description: Enforces zero plaintext secrets in Git, strict .env protection, and isolated mock data in context.local.md.
+trigger: always_on
+---
+
+# Rule: Security Boundaries & Secret Safety
+
+## Objective
+Prevent credential leakage, indirect prompt injection, and unauthorized network exposure across all code, configuration files, and git commits.
+
+## Guidelines & Constraints
+1. **Zero Hardcoded Secrets:**
+   - API keys, tokens, database passwords, and private keys must NEVER be hardcoded into source code, committed configs, or git history.
+   - All runtime secrets must be loaded via `.env` or system environment variables.
+2. **Local Sandbox Test Data Isolation (`context.local.md`):**
+   - Only dummy/mock credentials (e.g. `admin@test.local`) belong in `context.local.md`.
+   - Real production credentials or live payment keys are strictly prohibited in markdown files.
+   - `context.local.md` must remain strictly git-ignored (`chmod 600`).
+3. **Public Exposure Boundaries:**
+   - Raw database and internal service ports must bind to `127.0.0.1` unless encapsulated by secure tunneling.

auto_context/templates/skill.template.md

@@ -0,0 +1,39 @@
+---
+name: {{SKILL_NAME}}
+version: 1.0.0
+description: Describe what this skill accomplishes and the specific keywords or conditions under which the agent should activate it.
+triggers: ["{{SKILL_NAME}}", "keyword1", "keyword2"]
+---
+
+# Skill: {{SKILL_TITLE}}
+
+## Overview
+Briefly summarize the procedure, workflows, or runbooks taught by this skill.
+
+## When to Activate
+- When the user asks to perform task X.
+- When working on subsystem Y or diagnosing error Z.
+
+## Workflow & Step-by-Step Instructions
+
+### Step 1: Pre-flight & Checks
+* Validate prerequisites, environment variables, or dependencies:
+  ```bash
+  # Check command
+  ```
+
+### Step 2: Core Execution
+* Follow this exact procedure:
+  ```bash
+  # Execution command
+  ```
+
+### Step 3: Verification
+* Verify the expected outcome:
+  ```bash
+  # Verification command
+  ```
+
+## Reference & Troubleshooting
+* Common pitfalls and their solutions.
+

auto_context/templates/skills/browser-testing/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: browser-testing
+version: 1.0.0
+description: Automated web UI verification, Playwright/Puppeteer automation, and dev endpoint testing using context.local.md.
+triggers: ["browser", "playwright", "puppeteer", "ui-test", "login-test", "headless", "screenshot"]
+---
+
+# Skill: Browser Testing & Local UI Verification
+
+## Overview
+Automated procedures for conducting headful or headless browser testing, verifying web UI flows, performing login checks using mock fixtures from `context.local.md`, and preventing credential amnesia.
+
+## When to Activate
+- When verifying frontend web pages, UI components, forms, or authentication flows.
+- When running Playwright, Puppeteer, or Chrome DevTools automated actions.
+- When capturing screenshots or checking console errors on local dev servers.
+
+## Workflows & Procedures
+
+### 1. Pre-Flight Credential Resolution (The Mock Vault Rule)
+* **Rule:** Before launching any browser test or asking the user for test logins, **ALWAYS read `context.local.md`**.
+* Locate the seed user or admin account under Section 2:
+  ```markdown
+  | Role | Username / Email | Mock Password |
+  | Admin | admin@test.local | adminpass123 |
+  ```
+* NEVER hardcode real passwords or live user accounts into test scripts.
+
+### 2. Playwright Quick Verification Script Pattern
+```javascript
+import { test, expect } from '@playwright/test';
+
+test('Verify dev portal and mock login', async ({ page }) => {
+  // Navigate to local frontend URL defined in context.local.md
+  await page.goto('http://localhost:3000');
+
+  // Verify page title
+  await expect(page).toHaveTitle(/Dev/);
+
+  // Fill credentials from context.local.md
+  await page.fill('input[name="email"]', 'admin@test.local');
+  await page.fill('input[name="password"]', 'adminpass123');
+  await page.click('button[type="submit"]');
+
+  // Assert dashboard entry
+  await expect(page.locator('text=Dashboard')).toBeVisible();
+});
+```
+
+### 3. Capturing Visual Evidence & Debugging
+* Always save screenshots of failed assertions in a local temporary directory:
+  ```javascript
+  await page.screenshot({ path: 'scratch/error-state.png', fullPage: true });
+  ```
+* Review browser console errors:
+  ```javascript
+  page.on('console', msg => console.log('BROWSER LOG:', msg.text()));
+  page.on('pageerror', err => console.log('PAGE ERROR:', err.message));
+  ```

auto_context/templates/skills/docker-ops/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: docker-ops
+version: 1.0.0
+description: Production multi-stage Dockerfile and Compose setup, container diagnostics, cleanup, and logging.
+triggers: ["docker", "container", "compose", "dockerfile", "entrypoint"]
+---
+
+# Skill: Docker Operations & Container Management
+
+## Overview
+Standard operating procedures for containerizing applications, writing secure multi-stage Dockerfiles, managing docker-compose stacks, and diagnosing container failures.
+
+## When to Activate
+- When creating or modifying `Dockerfile` or `docker-compose.yml`.
+- When diagnosing crashed, restarting, or unhealthy containers.
+- When cleaning up dangling images, unused volumes, or container build cache.
+
+## Workflows & Procedures
+
+### 1. Multi-Stage Dockerfile Best Practices
+* **Principle:** Keep production images minimal by separating build tools from runtime.
+* **Non-Root Execution:** Always create and switch to a non-privileged user (e.g. `USER appuser`).
+* **Layer Caching:** Copy dependency manifests (`package.json`, `requirements.txt`, `go.mod`) and install dependencies BEFORE copying the application source code.
+* **Example (Node/Python pattern):**
+  ```dockerfile
+  # Build Stage
+  FROM node:20-alpine AS builder
+  WORKDIR /app
+  COPY package*.json ./
+  RUN npm ci
+  COPY . .
+  RUN npm run build
+
+  # Runner Stage
+  FROM node:20-alpine AS runner
+  WORKDIR /app
+  ENV NODE_ENV=production
+  RUN addgroup -S appgroup && adduser -S appuser -G appgroup
+  COPY --from=builder /app/package*.json ./
+  COPY --from=builder /app/dist ./dist
+  RUN npm ci --omit=dev
+  USER appuser
+  EXPOSE 3000
+  CMD ["node", "dist/index.js"]
+  ```
+
+### 2. Stack Orchestration (`docker-compose.yml`)
+* Keep environment variables decoupled using `.env` referencing (`${VAR_NAME}`).
+* Define explicit health checks and resource limits:
+  ```yaml
+  services:
+    web:
+      build: .
+      ports:
+        - "3000:3000"
+      env_file: .env
+      deploy:
+        resources:
+          limits:
+            cpus: '1.0'
+            memory: 512M
+      healthcheck:
+        test: ["CMD", "wget", "-qO-", "http://localhost:3000/health"]
+        interval: 30s
+        timeout: 5s
+        retries: 3
+  ```
+
+### 3. Diagnostics & Troubleshooting Commands
+* **Inspect logs:** `docker compose logs -f --tail=100 <service>`
+* **Inspect container resource consumption:** `docker stats --no-stream`
+* **Shell into container:** `docker exec -it <container_name> /bin/sh`
+* **Safe Clean-up (reclaim disk space):**
+  ```bash
+  # Remove stopped containers and dangling images
+  docker system prune -f
+  # Remove unused build cache
+  docker builder prune -f
+  ```

auto_context/templates/skills/git-workflow/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: git-workflow
+version: 1.0.0
+description: Conventional commit standards, branch management, safe rebasing, and merge conflict resolution.
+triggers: ["git", "commit", "branch", "pr", "pull-request", "merge", "conflict", "rebase"]
+---
+
+# Skill: Git Workflow & Release Management
+
+## Overview
+Standard procedures for feature branching, atomic conventional commits, interactive rebasing, merge conflict resolution, and safe remote synchronization.
+
+## When to Activate
+- When staging, committing, or pushing code changes to remote repositories.
+- When creating pull requests, managing feature branches, or tagging releases.
+- When resolving git merge or rebase conflicts.
+
+## Workflows & Procedures
+
+### 1. Conventional Commit Specification
+Always format commit messages using structured semantic prefixes:
+* `feat:` A new user-facing feature or CLI command.
+* `fix:` A bug fix or error correction.
+* `docs:` Documentation changes only (e.g. `README.md`, `context.md`).
+* `refactor:` Code restructuring that neither fixes a bug nor adds a feature.
+* `chore:` Build process, tooling, or dependency updates.
+* `test:` Adding or updating automated tests.
+
+**Format:**
+```
+<type>(<optional scope>): <short summary in imperative mood>
+
+[optional body explaining motivation and technical approach]
+
+[optional footer(s), e.g. Closes #123]
+```
+
+### 2. Branching & PR Hygiene
+* Keep `main` / `master` production-ready and protected.
+* Create short-lived feature branches: `git checkout -b feat/feature-name`
+* Before opening a PR or pushing:
+  ```bash
+  git fetch origin
+  git rebase origin/main
+  ```
+
+### 3. Safe Merge Conflict Resolution Runbook
+1. **Identify conflicted files:** `git status` (look for `both modified:`)
+2. **Inspect conflicts:** Look for conflict markers `<<<<<<< HEAD`, `=======`, `>>>>>>>`
+3. **Decide resolution strategy:**
+   - If keeping current branch's changes: `git checkout --ours <file>`
+   - If adopting incoming commit's changes: `git checkout --theirs <file>`
+   - If merging manually: edit file to remove conflict markers and test.
+4. **Complete rebase:**
+   ```bash
+   git add <resolved-files>
+   GIT_EDITOR=true git rebase --continue
+   ```
+5. **Never force-push without lease:** Use `git push --force-with-lease` instead of raw `--force`.

auto_context/templates/skills/server-diagnostics/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: server-diagnostics
+version: 1.0.0
+description: Real-time system health checks, RAM/swap usage, CPU load, open ports, and network connectivity diagnostics.
+triggers: ["health", "ram", "cpu", "swap", "diagnostics", "server", "port", "disk", "uptime"]
+---
+
+# Skill: Server Diagnostics & Resource Health
+
+## Overview
+Comprehensive runbook for assessing server stability, inspecting hardware memory buffers, verifying swap allocation, auditing listening network ports, and monitoring active background processes.
+
+## When to Activate
+- When experiencing system slowdowns, high latency, or OOM (Out-Of-Memory) kill events.
+- When checking server resource headroom before running heavy builds or containers.
+- When verifying open ports, firewall status, or Cloudflare tunnel connectivity.
+
+## Workflows & Procedures
+
+### 1. Memory & Buffer Diagnostics
+```bash
+# Check physical RAM and swap file availability
+free -h
+
+# Check top 5 memory-consuming processes
+ps aux --sort=-%mem | head -n 6
+```
+* **Critical Threshold:** Available memory below 200MB warrants immediate cache cleanup or swap expansion.
+
+### 2. CPU Load & Process Monitoring
+```bash
+# Check system uptime and 1m, 5m, 15m load averages
+uptime
+
+# Check top 5 CPU-consuming processes
+ps aux --sort=-%cpu | head -n 6
+```
+
+### 3. Disk Storage & Inode Health
+```bash
+# Inspect filesystem disk usage
+df -h /
+
+# Inspect inode utilization (detects micro-file exhaustion)
+df -i /
+```
+
+### 4. Network Ports & Connectivity Audit
+```bash
+# Check all active TCP/UDP listening sockets with process names
+sudo ss -tulpn
+
+# Verify internet DNS resolution
+nslookup cloudflare.com 1.1.1.1
+```