flyee 0.1.0

package/core/skills/verification-gate/SKILL.md

@@ -0,0 +1,205 @@
+---
+name: verification-gate
+description: Mechanical verification of task completion. Must-haves (Truths, Artifacts, Key Links), automatic command discovery, verification reports. Absorbed from GSD-2 verification-gate.ts patterns.
+---
+
+# Verification Gate
+
+> **Absorbed from:** GSD-2 `verification-gate.ts`
+> **Purpose:** Verify completion with evidence, not vibes. "Does it work?" not "does it look done?"
+
+---
+
+## 🎯 PURPOSE
+
+Without mechanical verification, task completion is subjective:
+- "I think it works" → ships broken code
+- "The tests pass" → but which tests? All of them?
+- "Looks good" → but is it connected? Does it render?
+
+The Verification Gate makes completion **deterministic**.
+
+---
+
+## 📋 MUST-HAVES
+
+Every task plan includes three categories of must-haves:
+
+### 1. Truths — Observable Behaviors
+
+Things that **must be true** when the task is done. Testable assertions.
+
+```markdown
+## Truths
+- [ ] `GET /api/posts` returns 200 with array of posts
+- [ ] `POST /api/posts` with valid body returns 201
+- [ ] BlogCard renders title and excerpt from post data
+- [ ] BlogCard image uses next/image with blur placeholder
+- [ ] Navigation to /blog shows BlogList with at least 1 card
+```
+
+### 2. Artifacts — Files That Must Exist
+
+Files that **must exist with real implementation** (not stubs, not mocks).
+
+```markdown
+## Artifacts
+- [ ] `src/components/BlogCard.tsx` — min 40 lines, exports BlogCard
+- [ ] `src/components/BlogCard.module.css` — min 15 lines
+- [ ] `src/app/blog/page.tsx` — imports and uses BlogCard
+```
+
+### 3. Key Links — Wiring Between Artifacts
+
+Connections that **must exist** between files. Prevents "island components."
+
+```markdown
+## Key Links
+- [ ] `BlogList.tsx` → `BlogCard.tsx` via import
+- [ ] `BlogCard.tsx` → `usePosts` hook via import or prop
+- [ ] `usePosts.ts` → `/api/posts` via fetch/SWR
+- [ ] `BlogCard.module.css` → imported in `BlogCard.tsx`
+```
+
+---
+
+## 🔍 COMMAND DISCOVERY
+
+Automatically discover verification commands. Priority order:
+
+### 1. Explicit preference (if configured in .flyee/)
+
+```json
+// .flyee/verification-commands.json
+{
+  "commands": ["npm run typecheck", "npm run lint", "npm run test"]
+}
+```
+
+### 2. Task plan verify field
+
+```markdown
+## Verify
+npm run typecheck && npm run test -- --run
+```
+
+### 3. package.json scripts (auto-detected)
+
+Probe for these scripts in order:
+1. `typecheck` → `npm run typecheck`
+2. `lint` → `npm run lint`
+3. `test` → `npm run test`
+
+### 4. Fallback: no commands found
+
+```
+⚠️ No verification commands discovered.
+   Add scripts to package.json: typecheck, lint, test
+   Or create .flyee/verification-commands.json
+```
+
+---
+
+## 📊 VERIFICATION REPORT
+
+Generated after running the gate:
+
+```markdown
+## Verification Report — T03 BlogCard
+
+### Command Results
+| # | Command | Exit | Duration | Status |
+|---|---------|------|----------|--------|
+| 1 | `npm run typecheck` | 0 | 3.2s | ✅ PASS |
+| 2 | `npm run lint` | 0 | 1.8s | ✅ PASS |
+| 3 | `npm run test` | 1 | 12.4s | ❌ FAIL |
+
+### Must-Have Results
+| # | Type | Description | Status | Evidence |
+|---|------|-------------|--------|----------|
+| 1 | Truth | GET /api/posts returns 200 | ✅ | curl output |
+| 2 | Truth | BlogCard renders title | ✅ | component renders |
+| 3 | Artifact | BlogCard.tsx exists, 87 lines | ✅ | file exists |
+| 4 | Artifact | BlogCard.module.css, 42 lines | ✅ | file exists |
+| 5 | Key Link | BlogList → BlogCard import | ✅ | grep confirms |
+| 6 | Key Link | BlogCard → usePosts | ❌ | import missing |
+
+### Verdict: ❌ FAIL
+**Blocking issues:**
+- Test suite failed (1 error in BlogCard.test.tsx)
+- Key Link missing: BlogCard not connected to usePosts hook
+
+**Action required:** Fix test + wire usePosts before completing task.
+```
+
+---
+
+## 🔄 GATE INTEGRATION
+
+### In /task-complete workflow
+
+```
+/task-complete
+  ├── 1. Existing gates (Anti-Mock, DS check, Flyee Sync)
+  ├── 2. 🆕 Must-Haves check (Truths, Artifacts, Key Links)
+  ├── 3. 🆕 Verification Gate (typecheck + lint + test)
+  ├── 4. 🆕 Write Verification Report
+  └── 5. If ALL pass → complete. If ANY fail → BLOCK with details.
+```
+
+### In autonomous execution (/execute --auto)
+
+```
+Loop:
+  Execute task → Run Verification Gate
+  ├── PASS → Mark complete, advance to next
+  └── FAIL → Attempt fix (max 2 retries)
+      ├── Fixed → PASS → advance
+      └── Still failing → BLOCK → stop auto-mode
+```
+
+---
+
+## 🛡️ COMMAND SAFETY
+
+Commands are validated before execution:
+- No shell injection patterns (`;`, `|`, `` ` ``, `$(...)`)
+- First token must be a known command prefix (npm, node, python, etc.)
+- Per-command timeout: 120s default
+- stdout/stderr capped at 10KB per command
+
+---
+
+## ⚡ TASK PLAN TEMPLATE WITH MUST-HAVES
+
+```markdown
+# T03 — BlogCard Component
+
+## Objective
+Create the BlogCard component that renders a post preview.
+
+## Steps
+1. Create BlogCard.tsx with Post prop
+2. Create BlogCard.module.css with design tokens
+3. Wire to usePosts hook
+4. Add hover animation
+5. Verify must-haves
+
+## Must-Haves
+
+### Truths
+- [ ] BlogCard renders title, excerpt, date, author
+- [ ] BlogCard links to /blog/[slug]
+- [ ] Hover shows scale animation per design tokens
+
+### Artifacts
+- [ ] `src/components/BlogCard.tsx` — min 40 lines
+- [ ] `src/components/BlogCard.module.css` — min 15 lines
+
+### Key Links
+- [ ] `BlogList.tsx` → `BlogCard.tsx` via import
+- [ ] `BlogCard.tsx` → Post type from `types/post.ts`
+
+## Verify
+npm run typecheck && npm run test -- --run BlogCard
+```

package/core/skills/vulnerability-scanner/SKILL.md

@@ -0,0 +1,276 @@
+---
+name: vulnerability-scanner
+description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# Vulnerability Scanner
+
+> Think like an attacker, defend like an expert. 2025 threat landscape awareness.
+
+## 🔧 Runtime Scripts
+
+**Execute for automated validation:**
+
+| Script | Purpose | Usage |
+|--------|---------|-------|
+| `scripts/security_scan.py` | Validate security principles applied | `python scripts/security_scan.py <project_path>` |
+
+## 📋 Reference Files
+
+| File | Purpose |
+|------|---------|
+| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |
+
+---
+
+## 1. Security Expert Mindset
+
+### Core Principles
+
+| Principle | Application |
+|-----------|-------------|
+| **Assume Breach** | Design as if attacker already inside |
+| **Zero Trust** | Never trust, always verify |
+| **Defense in Depth** | Multiple layers, no single point |
+| **Least Privilege** | Minimum required access only |
+| **Fail Secure** | On error, deny access |
+
+### Threat Modeling Questions
+
+Before scanning, ask:
+1. What are we protecting? (Assets)
+2. Who would attack? (Threat actors)
+3. How would they attack? (Attack vectors)
+4. What's the impact? (Business risk)
+
+---
+
+## 2. OWASP Top 10:2025
+
+### Risk Categories
+
+| Rank | Category | Think About |
+|------|----------|-------------|
+| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |
+| **A02** | Security Misconfiguration | Defaults, headers, exposed services |
+| **A03** | Software Supply Chain 🆕 | Dependencies, CI/CD, build integrity |
+| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |
+| **A05** | Injection | User input → system commands |
+| **A06** | Insecure Design | Flawed architecture |
+| **A07** | Authentication Failures | Session, credential management |
+| **A08** | Integrity Failures | Unsigned updates, tampered data |
+| **A09** | Logging & Alerting | Blind spots, no monitoring |
+| **A10** | Exceptional Conditions 🆕 | Error handling, fail-open states |
+
+### 2025 Key Changes
+
+```
+2021 → 2025 Shifts:
+├── SSRF merged into A01 (Access Control)
+├── A02 elevated (Cloud/Container configs)
+├── A03 NEW: Supply Chain (major focus)
+├── A10 NEW: Exceptional Conditions
+└── Focus shift: Root causes > Symptoms
+```
+
+---
+
+## 3. Supply Chain Security (A03)
+
+### Attack Surface
+
+| Vector | Risk | Question to Ask |
+|--------|------|-----------------|
+| **Dependencies** | Malicious packages | Do we audit new deps? |
+| **Lock files** | Integrity attacks | Are they committed? |
+| **Build pipeline** | CI/CD compromise | Who can modify? |
+| **Registry** | Typosquatting | Verified sources? |
+
+### Defense Principles
+
+- Verify package integrity (checksums)
+- Pin versions, audit updates
+- Use private registries for critical deps
+- Sign and verify artifacts
+
+---
+
+## 4. Attack Surface Mapping
+
+### What to Map
+
+| Category | Elements |
+|----------|----------|
+| **Entry Points** | APIs, forms, file uploads |
+| **Data Flows** | Input → Process → Output |
+| **Trust Boundaries** | Where auth/authz checked |
+| **Assets** | Secrets, PII, business data |
+
+### Prioritization Matrix
+
+```
+Risk = Likelihood × Impact
+
+High Impact + High Likelihood → CRITICAL
+High Impact + Low Likelihood  → HIGH
+Low Impact + High Likelihood  → MEDIUM
+Low Impact + Low Likelihood   → LOW
+```
+
+---
+
+## 5. Risk Prioritization
+
+### CVSS + Context
+
+| Factor | Weight | Question |
+|--------|--------|----------|
+| **CVSS Score** | Base severity | How severe is the vuln? |
+| **EPSS Score** | Exploit likelihood | Is it being exploited? |
+| **Asset Value** | Business context | What's at risk? |
+| **Exposure** | Attack surface | Internet-facing? |
+
+### Prioritization Decision Tree
+
+```
+Is it actively exploited (EPSS >0.5)?
+├── YES → CRITICAL: Immediate action
+└── NO → Check CVSS
+         ├── CVSS ≥9.0 → HIGH
+         ├── CVSS 7.0-8.9 → Consider asset value
+         └── CVSS <7.0 → Schedule for later
+```
+
+---
+
+## 6. Exceptional Conditions (A10 - New)
+
+### Fail-Open vs Fail-Closed
+
+| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |
+|----------|-----------------|---------------------|
+| Auth error | Allow access | Deny access |
+| Parsing fails | Accept input | Reject input |
+| Timeout | Retry forever | Limit + abort |
+
+### What to Check
+
+- Exception handlers that catch-all and ignore
+- Missing error handling on security operations
+- Race conditions in auth/authz
+- Resource exhaustion scenarios
+
+---
+
+## 7. Scanning Methodology
+
+### Phase-Based Approach
+
+```
+1. RECONNAISSANCE
+   └── Understand the target
+       ├── Technology stack
+       ├── Entry points
+       └── Data flows
+
+2. DISCOVERY
+   └── Identify potential issues
+       ├── Configuration review
+       ├── Dependency analysis
+       └── Code pattern search
+
+3. ANALYSIS
+   └── Validate and prioritize
+       ├── False positive elimination
+       ├── Risk scoring
+       └── Attack chain mapping
+
+4. REPORTING
+   └── Actionable findings
+       ├── Clear reproduction steps
+       ├── Business impact
+       └── Remediation guidance
+```
+
+---
+
+## 8. Code Pattern Analysis
+
+### High-Risk Patterns
+
+| Pattern | Risk | Look For |
+|---------|------|----------|
+| **String concat in queries** | Injection | `"SELECT * FROM " + user_input` |
+| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |
+| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |
+| **Path manipulation** | Traversal | User input in file paths |
+| **Disabled security** | Various | `verify=False`, `--insecure` |
+
+### Secret Patterns
+
+| Type | Indicators |
+|------|-----------|
+| API Keys | `api_key`, `apikey`, high entropy |
+| Tokens | `token`, `bearer`, `jwt` |
+| Credentials | `password`, `secret`, `key` |
+| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |
+
+---
+
+## 9. Cloud Security Considerations
+
+### Shared Responsibility
+
+| Layer | You Own | Provider Owns |
+|-------|---------|---------------|
+| Data | ✅ | ❌ |
+| Application | ✅ | ❌ |
+| OS/Runtime | Depends | Depends |
+| Infrastructure | ❌ | ✅ |
+
+### Cloud-Specific Checks
+
+- IAM: Least privilege applied?
+- Storage: Public buckets?
+- Network: Security groups tightened?
+- Secrets: Using secrets manager?
+
+---
+
+## 10. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Scan without understanding | Map attack surface first |
+| Alert on every CVE | Prioritize by exploitability + asset |
+| Ignore false positives | Maintain verified baseline |
+| Fix symptoms only | Address root causes |
+| Scan once before deploy | Continuous scanning |
+| Trust third-party deps blindly | Verify integrity, audit code |
+
+---
+
+## 11. Reporting Principles
+
+### Finding Structure
+
+Each finding should answer:
+1. **What?** - Clear vulnerability description
+2. **Where?** - Exact location (file, line, endpoint)
+3. **Why?** - Root cause explanation
+4. **Impact?** - Business consequence
+5. **How to fix?** - Specific remediation
+
+### Severity Classification
+
+| Severity | Criteria |
+|----------|----------|
+| **Critical** | RCE, auth bypass, mass data exposure |
+| **High** | Data exposure, privilege escalation |
+| **Medium** | Limited scope, requires conditions |
+| **Low** | Informational, best practice |
+
+---
+
+> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"

package/core/skills/vulnerability-scanner/checklists.md

@@ -0,0 +1,121 @@
+# Security Checklists
+
+> Quick reference checklists for security audits. Use alongside vulnerability-scanner principles.
+
+---
+
+## OWASP Top 10 Audit Checklist
+
+### A01: Broken Access Control
+- [ ] Authorization on all protected routes
+- [ ] Deny by default
+- [ ] Rate limiting implemented
+- [ ] CORS properly configured
+
+### A02: Cryptographic Failures
+- [ ] Passwords hashed (bcrypt/argon2, cost 12+)
+- [ ] Sensitive data encrypted at rest
+- [ ] TLS 1.2+ for all connections
+- [ ] No secrets in code/logs
+
+### A03: Injection
+- [ ] Parameterized queries
+- [ ] Input validation on all user data
+- [ ] Output encoding for XSS
+- [ ] No eval() or dynamic code execution
+
+### A04: Insecure Design
+- [ ] Threat modeling done
+- [ ] Security requirements defined
+- [ ] Business logic validated
+
+### A05: Security Misconfiguration
+- [ ] Unnecessary features disabled
+- [ ] Error messages sanitized
+- [ ] Security headers configured
+- [ ] Default credentials changed
+
+### A06: Vulnerable Components
+- [ ] Dependencies up to date
+- [ ] No known vulnerabilities
+- [ ] Unused dependencies removed
+
+### A07: Authentication Failures
+- [ ] MFA available
+- [ ] Session invalidation on logout
+- [ ] Session timeout implemented
+- [ ] Brute force protection
+
+### A08: Integrity Failures
+- [ ] Dependency integrity verified
+- [ ] CI/CD pipeline secured
+- [ ] Update mechanism secured
+
+### A09: Logging Failures
+- [ ] Security events logged
+- [ ] Logs protected
+- [ ] No sensitive data in logs
+- [ ] Alerting configured
+
+### A10: SSRF
+- [ ] URL validation implemented
+- [ ] Allow-list for external calls
+- [ ] Network segmentation
+
+---
+
+## Authentication Checklist
+
+- [ ] Strong password policy
+- [ ] Account lockout
+- [ ] Secure password reset
+- [ ] Session management
+- [ ] Token expiration
+- [ ] Logout invalidation
+
+---
+
+## API Security Checklist
+
+- [ ] Authentication required
+- [ ] Authorization per endpoint
+- [ ] Input validation
+- [ ] Rate limiting
+- [ ] Output sanitization
+- [ ] Error handling
+
+---
+
+## Data Protection Checklist
+
+- [ ] Encryption at rest
+- [ ] Encryption in transit
+- [ ] Key management
+- [ ] Data minimization
+- [ ] Secure deletion
+
+---
+
+## Security Headers
+
+| Header | Purpose |
+|--------|---------|
+| **Content-Security-Policy** | XSS prevention |
+| **X-Content-Type-Options** | MIME sniffing |
+| **X-Frame-Options** | Clickjacking |
+| **Strict-Transport-Security** | Force HTTPS |
+| **Referrer-Policy** | Referrer control |
+
+---
+
+## Quick Audit Commands
+
+| Check | What to Look For |
+|-------|------------------|
+| Secrets in code | password, api_key, secret |
+| Dangerous patterns | eval, innerHTML, SQL concat |
+| Dependency issues | npm audit, snyk |
+
+---
+
+> **Usage:** Copy relevant checklists into your PLAN.md or security report.