ali786-c/UpgraderCX Development
/SKILL.md
Rules and instructions for developing the UpgraderCX SaaS project.
development
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add ali786-c/newecome UpgraderCX DevelopmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 6:07 PM5.1s199 files scanned
SKILL.md
- name:
- UpgraderCX Development
- description:
- Rules and instructions for developing the UpgraderCX SaaS project.
UpgraderCX Development Guidelines
Project Structure
- Production UI: Root directory (
index.html,assets/, etc.) - Production Backend:
api/directory - Source Code (UI/Frontend):
c:\Users\Muhammad Aliyan\Downloads\upgradercx-full-project\upgradercx-source updated\artifacts\upgradercx - Upgrader Pay Hub (Source & Hub Project):
c:\Users\Muhammad Aliyan\Downloads\upgradercx-full-project\upgrader-pay-hub
Rules
-
Source of Truth for UI:
- ALL frontend/UI changes MUST be performed in the
upgradercx-source updateddirectory. - Specifically:
upgradercx-source updated/artifacts/upgradercx/src
- ALL frontend/UI changes MUST be performed in the
-
Build & Sync Workflow:
- After making UI changes, run
pnpm run buildinsideupgradercx-source updated/artifacts/upgradercx. - Sync the CONTENTS of the generated
dist/publicfolder directly to the ROOT ofupgradercx-full-project. - IMPORTANT: Delete the
public/folder in the root if it exists; all UI assets (index.html, assets/, etc.) must be at the top level.
- After making UI changes, run
-
Backend Development:
- Backend changes can be made directly in the
api/folder or inupgradercx-source updated/artifacts/laravel-backendand then synced.
- Backend changes can be made directly in the
-
Subfolder Optimization:
- Always ensure
api/index.phpand.htaccessfiles maintain the path refactors for subfolder execution on cPanel.
- Always ensure
-
Mandatory GitHub Push:
- Whenever ANY change is made to the codebase (source, build, or direct), the updated code MUST be pushed to GitHub.
- Target Repo:
https://github.com/ali786-c/newecome. - Command:
git add .,git commit -m "Update from AI assistant",git push origin master.
-
Upgrader Pay Hub Development:
- ALL Pay Hub related code (API and Frontend) MUST be developed in the
c:\Users\Muhammad Aliyan\Downloads\upgradercx-full-project\upgrader-pay-hubdirectory. - Use the dedicated
pay_hub_task.mdandpay_hub_implementation_plan.mdartifacts for this project. - Deployment Note: The Hub will run on an Addon Domain outside
public_html. Ensure all routing and directory references remain relative or absolute-to-root to support this isolation.
- ALL Pay Hub related code (API and Frontend) MUST be developed in the
-
Cross-Project Coordination:
- When integrating the Hub with UpgraderCX, ensure signatures match between both codebases.
Related Skills
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-qa-testing
development
VerifiedTrustedCommunity
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-parallels-smoke
development
VerifiedTrustedCommunity
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.
357,764SKILL.mdUpdated Apr 10, 2026