@jakkrichm/create-nexus-devflow 2.0.20 → 2.0.21

package/template/.claude/skills/roadmap-strategy/SKILL.md

@@ -1,94 +0,0 @@
----
-name: roadmap-strategy
-description: "[Devflow] Create or refresh product roadmap direction using markdown-first discovery and roadmap artifacts. Use when strategic planning should stay outside the mainline but still follow DevFlow 2.0 contracts."
----
-
-# Roadmap Strategy
-
-## Overview
-
-This skill is the shared behavior layer behind `Roadmap`.
-
-It replaces the older JSON-centered roadmap flow with a markdown-first strategy workflow that still preserves structured validation.
-
-## Related Assets
-
-This skill should reuse and align with:
-
-- `.agent/resources/schemas/roadmap_discovery.template.md`
-- `.agent/resources/schemas/roadmap.template.md`
-- `ROADMAP.md`
-
-## When to Use
-
-- when product direction, priority, or sequencing needs a dedicated roadmap pass
-- when competitor, PRD, research, or delivery insight should be consolidated into strategy
-- when roadmap work should stay outside the numbered mainline but still hand off cleanly into `PRD`, `10-define`, or `20-spec`
-
-## Canonical Artifacts
-
-Use markdown-first artifacts:
-
-- `devflow/roadmap/roadmap-discovery.md`
-- `ROADMAP.md`
-
-- research notes
-- PRD outputs
-- release or insight notes
-
-## Process
-
-### 1. Load Current Strategy Context
-
-Read the minimum useful context:
-
-- existing `ROADMAP.md`
-- `devflow/roadmap/roadmap-discovery.md`
-- current research, competitor notes, PRD, or insights when relevant
-
-### 2. Refresh Discovery
-
-Capture:
-
-- project purpose
-- target users
-- current state
-- constraints
-- market context
-- known gaps
-
-Save discovery notes in `devflow/roadmap/roadmap-discovery.md` using the discovery template.
-
-### 3. Prioritize The Roadmap
-
-Group roadmap work into useful strategic buckets such as:
-
-- near-term improvements
-- medium-term bets
-- long-term bets
-- technical debt and platform readiness
-
-Keep priorities traceable to evidence from stage work, user feedback, competitor findings, or implementation insight.
-
-### 4. Save The Canonical Roadmap
-
-Update `ROADMAP.md` using `.agent/resources/schemas/roadmap.template.md`.
-
-Replace placeholder content fully and keep headings and tables intact so validation can inspect the roadmap structure.
-
-### 5. Route Back
-
-- `PRD` when product framing needs to deepen
-- `10-define` when roadmap decisions should become bounded work
-- `20-spec` when one item is ready for delivery contract work
-- `Brainstorm` when strategy is still too fuzzy to lock
-
-## Output
-
-Return:
-
-- what changed in discovery
-- what changed in the roadmap
-- priority rationale
-- validation result
-- the recommended next command

package/template/.claude/skills/security-review/SKILL.md

@@ -1,63 +0,0 @@
----
-name: security-review
-description: "[Devflow] High-severity security code review and vulnerability audit for folders, projects, files, or diffs."
----
-
-# Security Review, Hardening & Vulnerability Audit
-
-## Overview
-
-This is the comprehensive security master skill for Nexus-DevFlow. It combines static vulnerability scanning, threat modeling, OWASP Top 10 defenses, and code hardening. Treat every external input as hostile, every secret as sacred, and every authorization check as mandatory.
-
----
-
-## 1. The Three-Tier Security Boundary
-
-### Always Do (No Exceptions)
-- **Validate & sanitize all inputs** at the boundary (Zod, Yup, schema validation).
-- **Parameterize all queries** — never concatenate user input into SQL/NoSQL queries.
-- **Encode outputs** to prevent XSS (rely on framework auto-escaping).
-- **Hash credentials** using bcrypt, Argon2, or scrypt.
-- **Enforce secure cookies**: `httpOnly`, `secure`, `sameSite=lax/strict`.
-
-### Never Do
-- **Never commit secrets**, API keys, tokens, or credentials to git.
-- **Never trust client-side checks** as a security barrier.
-- **Never use `eval()`, `exec()`, or raw `innerHTML`** with untrusted user data.
-- **Never expose internal stack traces** or detailed database errors to users.
-
----
-
-## 2. OWASP & Critical Vulnerability Vectors
-
-| Category | Primary Risk | Mandatory Defense |
-| :--- | :--- | :--- |
-| **A01: Broken Access Control** | IDOR, missing role checks | Enforce server-side authorization on every endpoint/data fetch |
-| **A02: Cryptographic Failures** | Plaintext tokens/passwords, weak cipher | Use TLS 1.3, salted hashing, secret managers / `.env` |
-| **A03: Injection** | SQL, NoSQL, OS Command, Template | Parameterized queries, avoid shell spawning with user input |
-| **A04: Insecure Design** | Missing rate limits, business logic flaw | Defense-in-depth, token bucket throttling, safe defaults |
-| **A05: Security Misconfig** | Permissive CORS (`*`), exposed debug endpoints | Restrict CORS origins, disable debug/admin paths in production |
-| **A07: Identification & Auth** | Session fixation, brute-force | Account lockouts, secure session rotation, MFA support |
-| **A08: Software & Data Integrity**| Untrusted CI/CD packages, deserialization | Run `npm audit`, pin dependency hashes, validate payloads |
-| **A09: Logging & Monitoring** | Missing audit logs or logging secrets | Structured logging with PII masking, alert on repeated auth failure |
-| **A10: SSRF** | Fetching internal URLs from user input | Whitelist allowable destination protocols and domains |
-
----
-
-## 3. Security Review Process
-
-1. **Target & Scope**: Inspect targeted files, PR diffs, or entire project directories.
-2. **Trace Trust Boundaries**: Follow untrusted data from entry (HTTP handlers, CLI arguments, file uploads) to sinks (DB, shell, HTML).
-3. **Scan for Secrets & Configs**: Detect hardcoded passwords, private keys, and environment variable leaks.
-4. **Generate Report**: Save formal security audits under:
-   ```text
-   devflow/runs/{ID}-{slug}/security-review.md
-   ```
-
----
-
-## Relationship To DevFlow 2.0
-
-- **Classification**: Companion command & Safety gate
-- **Mainline integration**: Run during `40-execute` or `50-verify` before `70-release`.
-- **Handoff**: P0/P1 security findings block release and return to `40-execute` for immediate remediation.

package/template/.claude/skills/seo-fundamentals/SKILL.md

@@ -1,129 +0,0 @@
----
-name: seo-fundamentals
-description: "[Devflow] SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles."
-allowed-tools: Read, Glob, Grep
----
-
-# SEO Fundamentals
-
-> Principles for search engine visibility.
-
----
-
-## 1. E-E-A-T Framework
-
-| Principle | Signals |
-|-----------|---------|
-| **Experience** | First-hand knowledge, real examples |
-| **Expertise** | Credentials, depth of knowledge |
-| **Authoritativeness** | Backlinks, mentions, industry recognition |
-| **Trustworthiness** | HTTPS, transparency, accurate info |
-
----
-
-## 2. Core Web Vitals
-
-| Metric | Target | Measures |
-|--------|--------|----------|
-| **LCP** | < 2.5s | Loading performance |
-| **INP** | < 200ms | Interactivity |
-| **CLS** | < 0.1 | Visual stability |
-
----
-
-## 3. Technical SEO Principles
-
-### Site Structure
-
-| Element | Purpose |
-|---------|---------|
-| XML sitemap | Help crawling |
-| robots.txt | Control access |
-| Canonical tags | Prevent duplicates |
-| HTTPS | Security signal |
-
-### Performance
-
-| Factor | Impact |
-|--------|--------|
-| Page speed | Core Web Vital |
-| Mobile-friendly | Ranking factor |
-| Clean URLs | Crawlability |
-
----
-
-## 4. Content SEO Principles
-
-### Page Elements
-
-| Element | Best Practice |
-|---------|---------------|
-| Title tag | 50-60 chars, keyword front |
-| Meta description | 150-160 chars, compelling |
-| H1 | One per page, main keyword |
-| H2-H6 | Logical hierarchy |
-| Alt text | Descriptive, not stuffed |
-
-### Content Quality
-
-| Factor | Importance |
-|--------|------------|
-| Depth | Comprehensive coverage |
-| Freshness | Regular updates |
-| Uniqueness | Original value |
-| Readability | Clear writing |
-
----
-
-## 5. Schema Markup Types
-
-| Type | Use |
-|------|-----|
-| Article | Blog posts, news |
-| Organization | Company info |
-| Person | Author profiles |
-| FAQPage | Q&A content |
-| Product | E-commerce |
-| Review | Ratings |
-| BreadcrumbList | Navigation |
-
----
-
-## 6. AI Content Guidelines
-
-### What Google Looks For
-
-| ✅ Do | ❌ Don't |
-|-------|----------|
-| AI draft + human edit | Publish raw AI content |
-| Add original insights | Copy without value |
-| Expert review | Skip fact-checking |
-| Follow E-E-A-T | Keyword stuffing |
-
----
-
-## 7. Ranking Factors (Prioritized)
-
-| Priority | Factor |
-|----------|--------|
-| 1 | Quality, relevant content |
-| 2 | Backlinks from authority sites |
-| 3 | Page experience (Core Web Vitals) |
-| 4 | Mobile optimization |
-| 5 | Technical SEO fundamentals |
-
----
-
-## 8. Measurement
-
-| Metric | Tool |
-|--------|------|
-| Rankings | Search Console, Ahrefs |
-| Traffic | Analytics |
-| Core Web Vitals | PageSpeed Insights |
-| Indexing | Search Console |
-| Backlinks | Ahrefs, Semrush |
-
----
-
-> **Remember:** SEO is a long-term game. Quality content + technical excellence + patience = results.

package/template/.claude/skills/seo-fundamentals/scripts/seo_checker.py

@@ -1,219 +0,0 @@
-#!/usr/bin/env python3
-"""
-SEO Checker - Search Engine Optimization Audit
-Checks HTML/JSX/TSX pages for SEO best practices.
-
-PURPOSE:
-    - Verify meta tags, titles, descriptions
-    - Check Open Graph tags for social sharing
-    - Validate heading hierarchy
-    - Check image accessibility (alt attributes)
-
-WHAT IT CHECKS:
-    - HTML files (actual web pages)
-    - JSX/TSX files (React page components)
-    - Only files that are likely PUBLIC pages
-
-Usage:
-    python seo_checker.py <project_path>
-"""
-import sys
-import json
-import re
-from pathlib import Path
-from datetime import datetime
-
-# Fix Windows console encoding
-try:
-    sys.stdout.reconfigure(encoding='utf-8', errors='replace')
-except:
-    pass
-
-
-# Directories to skip
-SKIP_DIRS = {
-    'node_modules', '.next', 'dist', 'build', '.git', '.github',
-    '__pycache__', '.vscode', '.idea', 'coverage', 'test', 'tests',
-    '__tests__', 'spec', 'docs', 'documentation', 'examples'
-}
-
-# Files to skip (not pages)
-SKIP_PATTERNS = [
-    'config', 'setup', 'util', 'helper', 'hook', 'context', 'store',
-    'service', 'api', 'lib', 'constant', 'type', 'interface', 'mock',
-    '.test.', '.spec.', '_test.', '_spec.'
-]
-
-
-def is_page_file(file_path: Path) -> bool:
-    """Check if this file is likely a public-facing page."""
-    name = file_path.name.lower()
-    stem = file_path.stem.lower()
-    
-    # Skip utility/config files
-    if any(skip in name for skip in SKIP_PATTERNS):
-        return False
-    
-    # Check path - pages in specific directories are likely pages
-    parts = [p.lower() for p in file_path.parts]
-    page_dirs = ['pages', 'app', 'routes', 'views', 'screens']
-    
-    if any(d in parts for d in page_dirs):
-        return True
-    
-    # Filename indicators for pages
-    page_names = ['page', 'index', 'home', 'about', 'contact', 'blog', 
-                  'post', 'article', 'product', 'landing', 'layout']
-    
-    if any(p in stem for p in page_names):
-        return True
-    
-    # HTML files are usually pages
-    if file_path.suffix.lower() in ['.html', '.htm']:
-        return True
-    
-    return False
-
-
-def find_pages(project_path: Path) -> list:
-    """Find page files to check."""
-    patterns = ['**/*.html', '**/*.htm', '**/*.jsx', '**/*.tsx']
-    
-    files = []
-    for pattern in patterns:
-        for f in project_path.glob(pattern):
-            # Skip excluded directories
-            if any(skip in f.parts for skip in SKIP_DIRS):
-                continue
-            
-            # Check if it's likely a page
-            if is_page_file(f):
-                files.append(f)
-    
-    return files[:50]  # Limit to 50 files
-
-
-def check_page(file_path: Path) -> dict:
-    """Check a single page for SEO issues."""
-    issues = []
-    
-    try:
-        content = file_path.read_text(encoding='utf-8', errors='ignore')
-    except Exception as e:
-        return {"file": str(file_path.name), "issues": [f"Error: {e}"]}
-    
-    # Detect if this is a layout/template file (has Head component)
-    is_layout = 'Head>' in content or '<head' in content.lower()
-    
-    # 1. Title tag
-    has_title = '<title' in content.lower() or 'title=' in content or 'Head>' in content
-    if not has_title and is_layout:
-        issues.append("Missing <title> tag")
-    
-    # 2. Meta description
-    has_description = 'name="description"' in content.lower() or 'name=\'description\'' in content.lower()
-    if not has_description and is_layout:
-        issues.append("Missing meta description")
-    
-    # 3. Open Graph tags
-    has_og = 'og:' in content or 'property="og:' in content.lower()
-    if not has_og and is_layout:
-        issues.append("Missing Open Graph tags")
-    
-    # 4. Heading hierarchy - multiple H1s
-    h1_matches = re.findall(r'<h1[^>]*>', content, re.I)
-    if len(h1_matches) > 1:
-        issues.append(f"Multiple H1 tags ({len(h1_matches)})")
-    
-    # 5. Images without alt
-    img_pattern = r'<img[^>]+>'
-    imgs = re.findall(img_pattern, content, re.I)
-    for img in imgs:
-        if 'alt=' not in img.lower():
-            issues.append("Image missing alt attribute")
-            break
-        if 'alt=""' in img or "alt=''" in img:
-            issues.append("Image has empty alt attribute")
-            break
-    
-    # 6. Check for canonical link (nice to have)
-    # has_canonical = 'rel="canonical"' in content.lower()
-    
-    return {
-        "file": str(file_path.name),
-        "issues": issues
-    }
-
-
-def main():
-    project_path = Path(sys.argv[1] if len(sys.argv) > 1 else ".").resolve()
-    
-    print(f"\n{'='*60}")
-    print(f"  SEO CHECKER - Search Engine Optimization Audit")
-    print(f"{'='*60}")
-    print(f"Project: {project_path}")
-    print(f"Time: {datetime.now().strftime('%Y-%m-%d %H:%M:%S')}")
-    print("-"*60)
-    
-    # Find pages
-    pages = find_pages(project_path)
-    
-    if not pages:
-        print("\n[!] No page files found.")
-        print("    Looking for: HTML, JSX, TSX in pages/app/routes directories")
-        output = {"script": "seo_checker", "files_checked": 0, "passed": True}
-        print("\n" + json.dumps(output, indent=2))
-        sys.exit(0)
-    
-    print(f"Found {len(pages)} page files to analyze\n")
-    
-    # Check each page
-    all_issues = []
-    for f in pages:
-        result = check_page(f)
-        if result["issues"]:
-            all_issues.append(result)
-    
-    # Summary
-    print("=" * 60)
-    print("SEO ANALYSIS RESULTS")
-    print("=" * 60)
-    
-    if all_issues:
-        # Group by issue type
-        issue_counts = {}
-        for item in all_issues:
-            for issue in item["issues"]:
-                issue_counts[issue] = issue_counts.get(issue, 0) + 1
-        
-        print("\nIssue Summary:")
-        for issue, count in sorted(issue_counts.items(), key=lambda x: -x[1]):
-            print(f"  [{count}] {issue}")
-        
-        print(f"\nAffected files ({len(all_issues)}):")
-        for item in all_issues[:5]:
-            print(f"  - {item['file']}")
-        if len(all_issues) > 5:
-            print(f"  ... and {len(all_issues) - 5} more")
-    else:
-        print("\n[OK] No SEO issues found!")
-    
-    total_issues = sum(len(item["issues"]) for item in all_issues)
-    passed = total_issues == 0
-    
-    output = {
-        "script": "seo_checker",
-        "project": str(project_path),
-        "files_checked": len(pages),
-        "files_with_issues": len(all_issues),
-        "issues_found": total_issues,
-        "passed": passed
-    }
-    
-    print("\n" + json.dumps(output, indent=2))
-    
-    sys.exit(0 if passed else 1)
-
-
-if __name__ == "__main__":
-    main()

package/template/.claude/skills/server-management/SKILL.md

@@ -1,161 +0,0 @@
----
-name: server-management
-description: "[Devflow] Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands."
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# Server Management
-
-> Server management principles for production operations.
-> **Learn to THINK, not memorize commands.**
-
----
-
-## 1. Process Management Principles
-
-### Tool Selection
-
-| Scenario | Tool |
-|----------|------|
-| **Node.js app** | PM2 (clustering, reload) |
-| **Any app** | systemd (Linux native) |
-| **Containers** | Docker/Podman |
-| **Orchestration** | Kubernetes, Docker Swarm |
-
-### Process Management Goals
-
-| Goal | What It Means |
-|------|---------------|
-| **Restart on crash** | Auto-recovery |
-| **Zero-downtime reload** | No service interruption |
-| **Clustering** | Use all CPU cores |
-| **Persistence** | Survive server reboot |
-
----
-
-## 2. Monitoring Principles
-
-### What to Monitor
-
-| Category | Key Metrics |
-|----------|-------------|
-| **Availability** | Uptime, health checks |
-| **Performance** | Response time, throughput |
-| **Errors** | Error rate, types |
-| **Resources** | CPU, memory, disk |
-
-### Alert Severity Strategy
-
-| Level | Response |
-|-------|----------|
-| **Critical** | Immediate action |
-| **Warning** | Investigate soon |
-| **Info** | Review daily |
-
-### Monitoring Tool Selection
-
-| Need | Options |
-|------|---------|
-| Simple/Free | PM2 metrics, htop |
-| Full observability | Grafana, Datadog |
-| Error tracking | Sentry |
-| Uptime | UptimeRobot, Pingdom |
-
----
-
-## 3. Log Management Principles
-
-### Log Strategy
-
-| Log Type | Purpose |
-|----------|---------|
-| **Application logs** | Debug, audit |
-| **Access logs** | Traffic analysis |
-| **Error logs** | Issue detection |
-
-### Log Principles
-
-1. **Rotate logs** to prevent disk fill
-2. **Structured logging** (JSON) for parsing
-3. **Appropriate levels** (error/warn/info/debug)
-4. **No sensitive data** in logs
-
----
-
-## 4. Scaling Decisions
-
-### When to Scale
-
-| Symptom | Solution |
-|---------|----------|
-| High CPU | Add instances (horizontal) |
-| High memory | Increase RAM or fix leak |
-| Slow response | Profile first, then scale |
-| Traffic spikes | Auto-scaling |
-
-### Scaling Strategy
-
-| Type | When to Use |
-|------|-------------|
-| **Vertical** | Quick fix, single instance |
-| **Horizontal** | Sustainable, distributed |
-| **Auto** | Variable traffic |
-
----
-
-## 5. Health Check Principles
-
-### What Constitutes Healthy
-
-| Check | Meaning |
-|-------|---------|
-| **HTTP 200** | Service responding |
-| **Database connected** | Data accessible |
-| **Dependencies OK** | External services reachable |
-| **Resources OK** | CPU/memory not exhausted |
-
-### Health Check Implementation
-
-- Simple: Just return 200
-- Deep: Check all dependencies
-- Choose based on load balancer needs
-
----
-
-## 6. Security Principles
-
-| Area | Principle |
-|------|-----------|
-| **Access** | SSH keys only, no passwords |
-| **Firewall** | Only needed ports open |
-| **Updates** | Regular security patches |
-| **Secrets** | Environment vars, not files |
-| **Audit** | Log access and changes |
-
----
-
-## 7. Troubleshooting Priority
-
-When something's wrong:
-
-1. **Check if running** (process status)
-2. **Check logs** (error messages)
-3. **Check resources** (disk, memory, CPU)
-4. **Check network** (ports, DNS)
-5. **Check dependencies** (database, APIs)
-
----
-
-## 8. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Run as root | Use non-root user |
-| Ignore logs | Set up log rotation |
-| Skip monitoring | Monitor from day one |
-| Manual restarts | Auto-restart config |
-| No backups | Regular backup schedule |
-
----
-
-> **Remember:** A well-managed server is boring. That's the goal.