port-nuker 1.0.0 → 1.0.1

package/.agent/skills/SECURITY.md

@@ -1,19 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-We track the `main` branch.
-
-## Reporting a Vulnerability
-
-**DO NOT** open a public Issue for security exploits.
-
-If you find a security vulnerability (e.g., a skill that bypasses the "Authorized Use Only" check or executes malicious code without warning):
-
-1. Email: `security@antigravity.dev` (Placeholder)
-2. Or open a **Private Advisory** on this repository.
-
-## Offensive Skills Policy
-
-Please read our [Security Guardrails](docs/SECURITY_GUARDRAILS.md).
-All offensive skills are strictly for **authorized educational and professional use only**.

package/.agent/skills/docs/BUNDLES.md

@@ -1,124 +0,0 @@
-# 📦 Antigravity Skill Bundles
-
-Don't know where to start? Pick a bundle below to get a curated set of skills for your role.
-
-## 🚀 The "Essentials" Starter Pack
-
-_For everyone. Install these first._
-
-- `concise-planning`: Always start with a plan.
-- `lint-and-validate`: Keep your code clean automatically.
-- `git-pushing`: Save your work safely.
-- `kaizen`: Continuous improvement mindset.
-
-## 🛡️ The "Security Engineer" Pack
-
-_For pentesting, auditing, and hardening._
-
-- `ethical-hacking-methodology`: The Bible of ethical hacking.
-- `burp-suite-testing`: Web vulnerability scanning.
-- `owasp-top-10`: Check for the most common flaws.
-- `linux-privilege-escalation`: Advanced Linux security assessment.
-- `cloud-penetration-testing`: AWS/Azure/GCP security.
-
-## 🌐 The "Web Wizard" Pack
-
-_For building modern, high-performance web apps._
-
-- `frontend-design`: UI guidelines and aesthetics.
-- `react-patterns`: Best practices for React (if available).
-- `tailwind-mastery`: Styling superpowers.
-- `form-cro`: Optimize your forms for conversion.
-- `seo-audit`: Get found on Google.
-
-## 🤖 The "Agent Architect" Pack
-
-_For building AI systems._
-
-- `agent-evaluation`: Test your agents.
-- `langgraph`: Build stateful agent workflows.
-- `mcp-builder`: Create your own tools.
-- `prompt-engineering`: Master the art of talking to LLMs.
-
-## 🎮 The "Indie Game Dev" Pack
-
-_For building games with AI assistants._
-
-- `game-development/game-design`: Mechanics and loops.
-- `game-development/2d-games`: Sprites and physics.
-- `game-development/3d-games`: Models and shaders.
-- `game-development/unity-csharp`: C# scripting mastery.
-- `algorithmic-art`: Generate assets with code.
-
-## 🐍 The "Python Pro" Pack
-
-_For backend heavyweights and data scientists._
-
-- `python-patterns`: Idiomatic Python code.
-- `poetry-manager`: Dependency management that works.
-- `pytest-mastery`: Testing frameworks.
-- `fastapi-expert`: High-performance APIs.
-- `django-guide`: The battery-included framework.
-
-## 🦄 The "Startup Founder" Pack
-
-_For building products, not just code._
-
-- `product-requirements-doc`: Define what to build.
-- `competitor-analysis`: Know who you are fighting.
-- `pitch-deck-creator`: Raise capital (or just explain your idea).
-- `landing-page-copy`: Write words that sell.
-- `stripe-integration`: Get paid.
-
-## 🌧️ The "DevOps & Cloud" Pack
-
-_For infrastructure and scaling._
-
-- `docker-expert`: Master containers and multi-stage builds.
-- `aws-serverless`: Go serverless on AWS (Lambda, DynamoDB).
-- `environment-setup-guide`: Standardization for teams.
-- `deployment-procedures`: Safe rollout strategies.
-- `bash-linux`: Terminal wizardry.
-
-## 📊 The "Data & Analytics" Pack
-
-_For making sense of the numbers._
-
-- `analytics-tracking`: Set up GA4/PostHog correctly.
-- `d3-viz`: Beautiful custom visualizations.
-- `sql-mastery`: Write better queries (Community skill).
-- `ab-test-setup`: Validated learning.
-
-## 🎨 The "Creative Director" Pack
-
-_For visuals, content, and branding._
-
-- `canvas-design`: Generate posters and diagrams.
-- `frontend-design`: UI aesthetics.
-- `content-creator`: SEO-optimized blog posts.
-- `copy-editing`: Polish your prose.
-- `algorithmic-art`: Code-generated masterpieces.
-
-## 🐞 The "QA & Testing" Pack
-
-_For breaking things before users do._
-
-- `test-driven-development`: Red, Green, Refactor.
-- `systematic-debugging`: Sherlock Holmes for code.
-- `browser-automation`: End-to-end testing with Playwright.
-- `ab-test-setup`: Validated experiments.
-- `code-review-checklist`: Catch bugs in PRs.
-
-## 🖌️ The "Web Designer" Pack
-
-_For pixel-perfect experiences._
-
-- `ui-ux-pro-max`: Premium design systems/tokens.
-- `frontend-design`: The base layer of aesthetics.
-- `3d-web-experience`: Three.js & R3F magic.
-- `canvas-design`: Static visuals/posters.
-- `responsive-layout`: Mobile-first principles.
-
----
-
-_To use a bundle, simply copy the skill names into your `.agent/skills` folder or use them with your agent._

package/.agent/skills/docs/CI_DRIFT_FIX.md

@@ -1,38 +0,0 @@
-# CI Drift Fix Guide
-
-**Problem**: The failing job is caused by uncommitted changes detected in `README.md` or `skills_index.json` after the update scripts run.
-
-**Error**:
-
-```
-❌ Detected uncommitted changes in README.md or skills_index.json. Please run scripts locally and commit.
-```
-
-**Cause**:
-Scripts like `scripts/generate_index.py` and `scripts/update_readme.py` modify `README.md` and `skills_index.json`, but the workflow expects these files to have no changes after the scripts are run. Any differences mean the committed repo is out-of-sync with what the generation scripts produce.
-
-**How to Fix (DO THIS EVERY TIME):**
-
-1. Run the scripts locally to regenerate README.md and skills_index.json:
-
-   ```bash
-   python3 scripts/generate_index.py
-   python3 scripts/update_readme.py
-   ```
-
-2. Check for changes:
-
-   ```bash
-   git status
-   git diff
-   ```
-
-3. Commit and push any updates:
-   ```bash
-   git add README.md skills_index.json
-   git commit -m "Update README and skills index to resolve CI drift"
-   git push
-   ```
-
-**Summary**:
-Always commit and push all changes produced by the registry or readme update scripts. This keeps the CI workflow passing by ensuring the repository and generated files are synced.

package/.agent/skills/docs/COMMUNITY_GUIDELINES.md

@@ -1,33 +0,0 @@
-# Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-- The use of sexualized language or imagery and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1.
-
-[homepage]: https://www.contributor-covenant.org

package/.agent/skills/docs/EXAMPLES.md

@@ -1,56 +0,0 @@
-# 🧪 Real-World Examples ("The Antigravity Cookbook")
-
-Skills are powerful on their own, but unstoppable when combined.
-Here are three common scenarios and how to solve them using this repository.
-
-## 🥘 Recipe 1: The "Legacy Code Audit"
-
-_Scenario: You just inherited a messy 5-year-old Node.js repo. You need to fix it safely._
-
-**Skills Used:**
-
-1. `concise-planning` (To map the chaos)
-2. `lint-and-validate` (To find the bugs)
-3. `security-audit` (To find the holes)
-
-**The Workflow:**
-
-1. **Plan**: "Agent, use `concise-planning` to create a checklist for refactoring `src/legacy-api.js`."
-2. **Audit**: "Run `security-audit` on the `package.json` to find vulnerable dependencies."
-3. **Fix**: "Use `lint-and-validate` rules to auto-fix the formatting issues in `src/`."
-
----
-
-## 🥘 Recipe 2: The "Modern Web App"
-
-_Scenario: You need to build a high-performance Landing Page in 2 hours._
-
-**Skills Used:**
-
-1. `frontend-design` (For aesthetics)
-2. `react-patterns` (For structure)
-3. `tailwind-mastery` (For speed)
-
-**The Workflow:**
-
-1. **Design**: "Use `frontend-design` to generate a color palette and typography for a 'Cyberpunk Coffee Shop'."
-2. **Scaffold**: "Initialize a Vite project. Then apply `react-patterns` to create the 'Hero' component."
-3. **Style**: "Use `tailwind-mastery` to make the buttons glassmorphic and responsive."
-
----
-
-## 🥘 Recipe 3: The "Agent Architect"
-
-_Scenario: You want to build a custom AI agent that can verify its own code._
-
-**Skills Used:**
-
-1. `mcp-builder` (To build tools)
-2. `agent-evaluation` (To test reliability)
-3. `prompt-engineering` (To refine instructions)
-
-**The Workflow:**
-
-1. **Build**: "Use `mcp-builder` to create a `verify-file` tool."
-2. **Instruct**: "Apply `prompt-engineering` patterns to the System Prompt so the agent always checks file paths."
-3. **Test**: "Run `agent-evaluation` to benchmark how often the agent fails to find the file."

package/.agent/skills/docs/QUALITY_BAR.md

@@ -1,64 +0,0 @@
-# 🏆 Quality Bar & Validation Standards
-
-To transform **Antigravity Awesome Skills** from a collection of scripts into a trusted platform, every skill must meet a specific standard of quality and safety.
-
-## The "Validated" Badge ✅
-
-A skill earns the "Validated" badge only if it passes these **5 automated checks**:
-
-### 1. Metadata Integrity
-
-The `SKILL.md` frontmatter must be valid YAML and contain:
-
-- `name`: Kebab-case, matches folder name.
-- `description`: Under 200 chars, clear value prop.
-- `risk`: One of `[none, safe, critical, offensive]`.
-- `source`: URL to original source (or "self" if original).
-
-### 2. Clear Triggers ("When to use")
-
-The skill MUST have a section explicitly stating when to trigger it.
-
-- **Good**: "Use when the user asks to debug a React component."
-- **Bad**: "This skill helps you with code."
-
-### 3. Safety & Risk Classification
-
-Every skill must declare its risk level:
-
-- 🟢 **none**: Pure text/reasoning (e.g., Brainstorming).
-- 🔵 **safe**: Reads files, runs safe commands (e.g., Linter).
-- 🟠 **critical**: Modifies state, deletes files, pushes to prod (e.g., Git Push).
-- 🔴 **offensive**: Pentesting/Red Team tools. **MUST** have "Authorized Use Only" warning.
-
-### 4. Copy-Pasteable Examples
-
-At least one code block or interaction example that a user (or agent) can immediately use.
-
-### 5. Explicit Limitations
-
-A list of known edge cases or things the skill _cannot_ do.
-
-- _Example_: "Does not work on Windows without WSL."
-
----
-
-## Support Levels
-
-We also categorize skills by who maintains them:
-
-| Level         | Badge | Meaning                                             |
-| :------------ | :---- | :-------------------------------------------------- |
-| **Official**  | 🟣    | Maintained by the core team. High reliability.      |
-| **Community** | ⚪    | Contributed by the ecosystem. Best effort support.  |
-| **Verified**  | ✨    | Community skill that has passed deep manual review. |
-
----
-
-## How to Validate Your Skill
-
-Run the validator script before submitting a PR:
-
-```bash
-python3 scripts/validate_skills.py --strict
-```

package/.agent/skills/docs/SECURITY_GUARDRAILS.md

@@ -1,51 +0,0 @@
-# 🛡️ Security Guardrails & Policy
-
-Antigravity Awesome Skills is a powerful toolkit. With great power comes great responsibility. This document defines the **Rules of Engagement** for all security and offensive capabilities in this repository.
-
-## 🔴 Offensive Skills Policy (The "Red Line")
-
-**What is an Offensive Skill?**
-Any skill designed to penetrate, exploit, disrupt, or simulate attacks against systems.
-_Examples: Pentesting, SQL Injection, Phishing Simulation, Red Teaming._
-
-### 1. The "Authorized Use Only" Disclaimer
-
-Every offensive skill **MUST** begin with this exact disclaimer in its `SKILL.md`:
-
-> **⚠️ AUTHORIZED USE ONLY**
-> This skill is for educational purposes or authorized security assessments only.
-> You must have explicit, written permission from the system owner before using this tool.
-> Misuse of this tool is illegal and strictly prohibited.
-
-### 2. Mandatory User Confirmation
-
-Offensive skills must **NEVER** run fully autonomously.
-
-- **Requirement**: The skill description/instructions must explicitly tell the agent to _ask for user confirmation_ before executing any exploit or attack command.
-- **Agent Instruction**: "Ask the user to verify the target URL/IP before running."
-
-### 3. Safe by Design
-
-- **No Weaponized Payloads**: Skills should not include active malware, ransomware, or non-educational exploits.
-- **Sandbox Recommended**: Instructions should recommend running in a contained environment (Docker/VM).
-
----
-
-## 🔵 Defensive Skills Policy
-
-**What is a Defensive Skill?**
-Tools for hardening, auditing, monitoring, or protecting systems.
-_Examples: Linting, Log Analysis, Configuration Auditing._
-
-- **Data Privacy**: Defensive skills must not upload data to 3rd party servers without explicit user consent.
-- **Non-Destructive**: Audits should be read-only by default.
-
----
-
-## ⚖️ Legal Disclaimer
-
-By using this repository, you agree that:
-
-1. You are responsible for your own actions.
-2. The authors and contributors are not liable for any damage caused by these tools.
-3. You will comply with all local, state, and federal laws regarding cybersecurity.