npm - port-nuker - Versions diffs - 1.0.0 → 1.0.3 - Mend

port-nuker 1.0.0 → 1.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2052) hide show

package/.agent/skills/skills/3d-web-experience/SKILL.md DELETED Viewed

@@ -1,254 +0,0 @@
----
-name: 3d-web-experience
-description: "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience."
-source: vibeship-spawner-skills (Apache 2.0)
----
-# 3D Web Experience
-**Role**: 3D Web Experience Architect
-You bring the third dimension to the web. You know when 3D enhances
-and when it's just showing off. You balance visual impact with
-performance. You make 3D accessible to users who've never touched
-a 3D app. You create moments of wonder without sacrificing usability.
-## Capabilities
-- Three.js implementation
-- React Three Fiber
-- WebGL optimization
-- 3D model integration
-- Spline workflows
-- 3D product configurators
-- Interactive 3D scenes
-- 3D performance optimization
-## Patterns
-### 3D Stack Selection
-Choosing the right 3D approach
-**When to use**: When starting a 3D web project
-```python
-## 3D Stack Selection
-### Options Comparison
-| Tool | Best For | Learning Curve | Control |
-|------|----------|----------------|---------|
-| Spline | Quick prototypes, designers | Low | Medium |
-| React Three Fiber | React apps, complex scenes | Medium | High |
-| Three.js vanilla | Max control, non-React | High | Maximum |
-| Babylon.js | Games, heavy 3D | High | Maximum |
-### Decision Tree
-```
-Need quick 3D element?
-└── Yes → Spline
-└── No → Continue
-Using React?
-└── Yes → React Three Fiber
-└── No → Continue
-Need max performance/control?
-└── Yes → Three.js vanilla
-└── No → Spline or R3F
-```
-### Spline (Fastest Start)
-```jsx
-import Spline from '@splinetool/react-spline';
-export default function Scene() {
-  return (
-    <Spline scene="https://prod.spline.design/xxx/scene.splinecode" />
-  );
-}
-```
-### React Three Fiber
-```jsx
-import { Canvas } from '@react-three/fiber';
-import { OrbitControls, useGLTF } from '@react-three/drei';
-function Model() {
-  const { scene } = useGLTF('/model.glb');
-  return <primitive object={scene} />;
-}
-export default function Scene() {
-  return (
-    <Canvas>
-      <ambientLight />
-      <Model />
-      <OrbitControls />
-    </Canvas>
-  );
-}
-```
-```
-### 3D Model Pipeline
-Getting models web-ready
-**When to use**: When preparing 3D assets
-```python
-## 3D Model Pipeline
-### Format Selection
-| Format | Use Case | Size |
-|--------|----------|------|
-| GLB/GLTF | Standard web 3D | Smallest |
-| FBX | From 3D software | Large |
-| OBJ | Simple meshes | Medium |
-| USDZ | Apple AR | Medium |
-### Optimization Pipeline
-```
-1. Model in Blender/etc
-2. Reduce poly count (< 100K for web)
-3. Bake textures (combine materials)
-4. Export as GLB
-5. Compress with gltf-transform
-6. Test file size (< 5MB ideal)
-```
-### GLTF Compression
-```bash
-# Install gltf-transform
-npm install -g @gltf-transform/cli
-# Compress model
-gltf-transform optimize input.glb output.glb \
-  --compress draco \
-  --texture-compress webp
-```
-### Loading in R3F
-```jsx
-import { useGLTF, useProgress, Html } from '@react-three/drei';
-import { Suspense } from 'react';
-function Loader() {
-  const { progress } = useProgress();
-  return <Html center>{progress.toFixed(0)}%</Html>;
-}
-export default function Scene() {
-  return (
-    <Canvas>
-      <Suspense fallback={<Loader />}>
-        <Model />
-      </Suspense>
-    </Canvas>
-  );
-}
-```
-```
-### Scroll-Driven 3D
-3D that responds to scroll
-**When to use**: When integrating 3D with scroll
-```python
-## Scroll-Driven 3D
-### R3F + Scroll Controls
-```jsx
-import { ScrollControls, useScroll } from '@react-three/drei';
-import { useFrame } from '@react-three/fiber';
-function RotatingModel() {
-  const scroll = useScroll();
-  const ref = useRef();
-  useFrame(() => {
-    // Rotate based on scroll position
-    ref.current.rotation.y = scroll.offset * Math.PI * 2;
-  });
-  return <mesh ref={ref}>...</mesh>;
-}
-export default function Scene() {
-  return (
-    <Canvas>
-      <ScrollControls pages={3}>
-        <RotatingModel />
-      </ScrollControls>
-    </Canvas>
-  );
-}
-```
-### GSAP + Three.js
-```javascript
-import gsap from 'gsap';
-import ScrollTrigger from 'gsap/ScrollTrigger';
-gsap.to(camera.position, {
-  scrollTrigger: {
-    trigger: '.section',
-    scrub: true,
-  },
-  z: 5,
-  y: 2,
-});
-```
-### Common Scroll Effects
-- Camera movement through scene
-- Model rotation on scroll
-- Reveal/hide elements
-- Color/material changes
-- Exploded view animations
-```
-## Anti-Patterns
-### ❌ 3D For 3D's Sake
-**Why bad**: Slows down the site.
-Confuses users.
-Battery drain on mobile.
-Doesn't help conversion.
-**Instead**: 3D should serve a purpose.
-Product visualization = good.
-Random floating shapes = probably not.
-Ask: would an image work?
-### ❌ Desktop-Only 3D
-**Why bad**: Most traffic is mobile.
-Kills battery.
-Crashes on low-end devices.
-Frustrated users.
-**Instead**: Test on real mobile devices.
-Reduce quality on mobile.
-Provide static fallback.
-Consider disabling 3D on low-end.
-### ❌ No Loading State
-**Why bad**: Users think it's broken.
-High bounce rate.
-3D takes time to load.
-Bad first impression.
-**Instead**: Loading progress indicator.
-Skeleton/placeholder.
-Load 3D after page is interactive.
-Optimize model size.
-## Related Skills
-Works well with: `scroll-experience`, `interactive-portfolio`, `frontend`, `landing-page-design`

package/.agent/skills/skills/README.md DELETED Viewed

@@ -1,201 +0,0 @@
-# Skills Directory
-**Welcome to the skills folder!** This is where all 179+ specialized AI skills live.
-## 🤔 What Are Skills?
-Skills are specialized instruction sets that teach AI assistants how to handle specific tasks. Think of them as expert knowledge modules that your AI can load on-demand.
-**Simple analogy:** Just like you might consult different experts (a designer, a security expert, a marketer), skills let your AI become an expert in different areas when you need them.
----
-## 📂 Folder Structure
-Each skill lives in its own folder with this structure:
-```
-skills/
-├── skill-name/              # Individual skill folder
-│   ├── SKILL.md             # Main skill definition (required)
-│   ├── scripts/             # Helper scripts (optional)
-│   ├── examples/            # Usage examples (optional)
-│   └── resources/           # Templates & resources (optional)
-```
-**Key point:** Only `SKILL.md` is required. Everything else is optional!
----
-## How to Use Skills
-### Step 1: Make sure skills are installed
-Skills should be in your `.agent/skills/` directory (or `.claude/skills/`, `.gemini/skills/`, etc.)
-### Step 2: Invoke a skill in your AI chat
-Use the `@` symbol followed by the skill name:
-```
-@brainstorming help me design a todo app
-```
-or
-```
-@stripe-integration add payment processing to my app
-```
-### Step 3: The AI becomes an expert
-The AI loads that skill's knowledge and helps you with specialized expertise!
----
-## Skill Categories
-### Creative & Design
-Skills for visual design, UI/UX, and artistic creation:
-- `@algorithmic-art` - Create algorithmic art with p5.js
-- `@canvas-design` - Design posters and artwork (PNG/PDF output)
-- `@frontend-design` - Build production-grade frontend interfaces
-- `@ui-ux-pro-max` - Professional UI/UX design with color, fonts, layouts
-- `@web-artifacts-builder` - Build modern web apps (React, Tailwind, Shadcn/ui)
-- `@theme-factory` - Generate themes for documents and presentations
-- `@brand-guidelines` - Apply Anthropic brand design standards
-- `@slack-gif-creator` - Create high-quality GIFs for Slack
-### Development & Engineering
-Skills for coding, testing, debugging, and code review:
-- `@test-driven-development` - Write tests before implementation (TDD)
-- `@systematic-debugging` - Debug systematically, not randomly
-- `@webapp-testing` - Test web apps with Playwright
-- `@receiving-code-review` - Handle code review feedback properly
-- `@requesting-code-review` - Request code reviews before merging
-- `@finishing-a-development-branch` - Complete dev branches (merge, PR, cleanup)
-- `@subagent-driven-development` - Coordinate multiple AI agents for parallel tasks
-### Documentation & Office
-Skills for working with documents and office files:
-- `@doc-coauthoring` - Collaborate on structured documents
-- `@docx` - Create, edit, and analyze Word documents
-- `@xlsx` - Work with Excel spreadsheets (formulas, charts)
-- `@pptx` - Create and modify PowerPoint presentations
-- `@pdf` - Handle PDFs (extract text, merge, split, fill forms)
-- `@internal-comms` - Draft internal communications (reports, announcements)
-- `@notebooklm` - Query Google NotebookLM notebooks
-### Planning & Workflow
-Skills for task planning and workflow optimization:
-- `@brainstorming` - Brainstorm and design before coding
-- `@writing-plans` - Write detailed implementation plans
-- `@planning-with-files` - File-based planning system (Manus-style)
-- `@executing-plans` - Execute plans with checkpoints and reviews
-- `@using-git-worktrees` - Create isolated Git worktrees for parallel work
-- `@verification-before-completion` - Verify work before claiming completion
-- `@using-superpowers` - Discover and use advanced skills
-### System Extension
-Skills for extending AI capabilities:
-- `@mcp-builder` - Build MCP (Model Context Protocol) servers
-- `@skill-creator` - Create new skills or update existing ones
-- `@writing-skills` - Tools for writing and validating skill files
-- `@dispatching-parallel-agents` - Distribute tasks to multiple agents
----
-## Finding Skills
-### Method 1: Browse this folder
-```bash
-ls skills/
-```
-### Method 2: Search by keyword
-```bash
-ls skills/ | grep "keyword"
-```
-### Method 3: Check the main README
-See the [main README](../README.md) for the complete list of all 179+ skills organized by category.
----
-## 💡 Popular Skills to Try
-**For beginners:**
-- `@brainstorming` - Design before coding
-- `@systematic-debugging` - Fix bugs methodically
-- `@git-pushing` - Commit with good messages
-**For developers:**
-- `@test-driven-development` - Write tests first
-- `@react-best-practices` - Modern React patterns
-- `@senior-fullstack` - Full-stack development
-**For security:**
-- `@ethical-hacking-methodology` - Security basics
-- `@burp-suite-testing` - Web app security testing
----
-## Creating Your Own Skill
-Want to create a new skill? Check out:
-1. [CONTRIBUTING.md](../CONTRIBUTING.md) - How to contribute
-2. [docs/SKILL_ANATOMY.md](../docs/SKILL_ANATOMY.md) - Skill structure guide
-3. `@skill-creator` - Use this skill to create new skills!
-**Basic structure:**
-```markdown
----
-name: my-skill-name
-description: "What this skill does"
----
-# Skill Title
-## Overview
-[What this skill does]
-## When to Use
-- Use when [scenario]
-## Instructions
-[Step-by-step guide]
-## Examples
-[Code examples]
-```
----
-## Documentation
-- **[Getting Started](../GETTING_STARTED.md)** - Quick start guide
-- **[Examples](../docs/EXAMPLES.md)** - Real-world usage examples
-- **[FAQ](../FAQ.md)** - Common questions
-- **[Visual Guide](../docs/VISUAL_GUIDE.md)** - Diagrams and flowcharts
----
-## 🌟 Contributing
-Found a skill that needs improvement? Want to add a new skill?
-1. Read [CONTRIBUTING.md](../CONTRIBUTING.md)
-2. Study existing skills in this folder
-3. Create your skill following the structure
-4. Submit a Pull Request
----
-## References
-- [Anthropic Skills](https://github.com/anthropic/skills) - Official Anthropic skills
-- [UI/UX Pro Max Skills](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) - Design skills
-- [Superpowers](https://github.com/obra/superpowers) - Original superpowers collection
-- [Planning with Files](https://github.com/OthmanAdi/planning-with-files) - Planning patterns
-- [NotebookLM](https://github.com/PleasePrompto/notebooklm-skill) - NotebookLM integration
----
-**Need help?** Check the [FAQ](../FAQ.md) or open an issue on GitHub!

package/.agent/skills/skills/ab-test-setup/SKILL.md DELETED Viewed

@@ -1,232 +0,0 @@
----
-name: ab-test-setup
-description: Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
----
-# A/B Test Setup
-## 1️⃣ Purpose & Scope
-Ensure every A/B test is **valid, rigorous, and safe** before a single line of code is written.
-- Prevents "peeking"
-- Enforces statistical power
-- Blocks invalid hypotheses
----
-## 2️⃣ Pre-Requisites
-You must have:
-- A clear user problem
-- Access to an analytics source
-- Roughly estimated traffic volume
-### Hypothesis Quality Checklist
-A valid hypothesis includes:
-- Observation or evidence
-- Single, specific change
-- Directional expectation
-- Defined audience
-- Measurable success criteria
----
-### 3️⃣ Hypothesis Lock (Hard Gate)
-Before designing variants or metrics, you MUST:
-- Present the **final hypothesis**
-- Specify:
-  - Target audience
-  - Primary metric
-  - Expected direction of effect
-  - Minimum Detectable Effect (MDE)
-Ask explicitly:
-> “Is this the final hypothesis we are committing to for this test?”
-**Do NOT proceed until confirmed.**
----
-### 4️⃣ Assumptions & Validity Check (Mandatory)
-Explicitly list assumptions about:
-- Traffic stability
-- User independence
-- Metric reliability
-- Randomization quality
-- External factors (seasonality, campaigns, releases)
-If assumptions are weak or violated:
-- Warn the user
-- Recommend delaying or redesigning the test
----
-### 5️⃣ Test Type Selection
-Choose the simplest valid test:
-- **A/B Test** – single change, two variants
-- **A/B/n Test** – multiple variants, higher traffic required
-- **Multivariate Test (MVT)** – interaction effects, very high traffic
-- **Split URL Test** – major structural changes
-Default to **A/B** unless there is a clear reason otherwise.
----
-### 6️⃣ Metrics Definition
-#### Primary Metric (Mandatory)
-- Single metric used to evaluate success
-- Directly tied to the hypothesis
-- Pre-defined and frozen before launch
-#### Secondary Metrics
-- Provide context
-- Explain _why_ results occurred
-- Must not override the primary metric
-#### Guardrail Metrics
-- Metrics that must not degrade
-- Used to prevent harmful wins
-- Trigger test stop if significantly negative
----
-### 7️⃣ Sample Size & Duration
-Define upfront:
-- Baseline rate
-- MDE
-- Significance level (typically 95%)
-- Statistical power (typically 80%)
-Estimate:
-- Required sample size per variant
-- Expected test duration
-**Do NOT proceed without a realistic sample size estimate.**
----
-### 8️⃣ Execution Readiness Gate (Hard Stop)
-You may proceed to implementation **only if all are true**:
-- Hypothesis is locked
-- Primary metric is frozen
-- Sample size is calculated
-- Test duration is defined
-- Guardrails are set
-- Tracking is verified
-If any item is missing, stop and resolve it.
----
-## Running the Test
-### During the Test
-**DO:**
-- Monitor technical health
-- Document external factors
-**DO NOT:**
-- Stop early due to “good-looking” results
-- Change variants mid-test
-- Add new traffic sources
-- Redefine success criteria
----
-## Analyzing Results
-### Analysis Discipline
-When interpreting results:
-- Do NOT generalize beyond the tested population
-- Do NOT claim causality beyond the tested change
-- Do NOT override guardrail failures
-- Separate statistical significance from business judgment
-### Interpretation Outcomes
-| Result               | Action                                 |
-| -------------------- | -------------------------------------- |
-| Significant positive | Consider rollout                       |
-| Significant negative | Reject variant, document learning      |
-| Inconclusive         | Consider more traffic or bolder change |
-| Guardrail failure    | Do not ship, even if primary wins      |
----
-## Documentation & Learning
-### Test Record (Mandatory)
-Document:
-- Hypothesis
-- Variants
-- Metrics
-- Sample size vs achieved
-- Results
-- Decision
-- Learnings
-- Follow-up ideas
-Store records in a shared, searchable location to avoid repeated failures.
----
-## Refusal Conditions (Safety)
-Refuse to proceed if:
-- Baseline rate is unknown and cannot be estimated
-- Traffic is insufficient to detect the MDE
-- Primary metric is undefined
-- Multiple variables are changed without proper design
-- Hypothesis cannot be clearly stated
-Explain why and recommend next steps.
----
-## Key Principles (Non-Negotiable)
-- One hypothesis per test
-- One primary metric
-- Commit before launch
-- No peeking
-- Learning over winning
-- Statistical rigor first
----
-## Final Reminder
-A/B testing is not about proving ideas right.
-It is about **learning the truth with confidence**.
-If you feel tempted to rush, simplify, or “just try it” —
-that is the signal to **slow down and re-check the design**.