0xray 2.0.0

package/src/skills/processor-pipeline/SKILL.md

@@ -0,0 +1,37 @@
+---
+source: framework
+name: processor-pipeline
+description: Data processing pipeline management
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [processing, processor, pipeline]
+capabilities:
+  - process_data
+  - manage_pipeline
+  - validate_output
+dependencies: []
+
+mcp:
+  processor-pipeline:
+    command: node
+    args: [node_modules/0xray/dist/mcps/processor-pipeline.server.js]
+---
+
+# Processor Pipeline Skill
+
+Data processing pipeline management.
+
+## Tools Available
+
+- **pipeline_management**: Pipeline management
+- **data_processing**: Data processing
+- **workflow_execution**: Workflow execution
+
+## Usage
+
+This skill provides processing capabilities for processor pipeline functionality.
+
+## Integration
+
+Activated when processing capabilities are requested through the skills system.

package/src/skills/project-analysis/SKILL.md

@@ -0,0 +1,42 @@
+---
+source: framework
+name: project-analysis
+description: Analyze project structure, complexity, and health metrics
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [analysis, project, complexity, health]
+capabilities:
+  - analyze_structure
+  - measure_complexity
+  - provide_metrics
+dependencies: []
+
+mcp:
+  project-analysis:
+    command: node
+    args: [node_modules/0xray/dist/mcps/knowledge-skills/project-analysis.server.js]
+---
+
+# Project Analysis Skill
+
+Provides comprehensive project analysis capabilities including:
+
+## Tools Available
+
+- **analyze_project_structure**: Analyze complete project structure including file organization, directory hierarchy, and module distribution
+- **assess_project_complexity**: Assess overall project complexity including code metrics, maintainability, and technical debt indicators
+- **identify_project_patterns**: Identify architectural patterns, code patterns, and structural patterns in the project
+- **analyze_project_health**: Provide comprehensive project health assessment including quality metrics and improvement recommendations
+
+## Usage
+
+This skill analyzes your project's codebase to provide insights about:
+- Code organization and structure
+- Complexity metrics and maintainability
+- Architectural patterns and anti-patterns
+- Health indicators and improvement recommendations
+
+## Integration
+
+Activated automatically when project analysis is requested through the skills system.

package/src/skills/refactoring-strategies/SKILL.md

@@ -0,0 +1,37 @@
+---
+source: framework
+name: refactoring-strategies
+description: Code refactoring techniques and strategies
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [refactoring, refactoring, strategies]
+capabilities:
+  - analyze_code_smell
+  - suggest_refactoring
+  - apply_patterns
+dependencies: []
+
+mcp:
+  refactoring-strategies:
+    command: node
+    args: [node_modules/0xray/dist/mcps/knowledge-skills/refactoring-strategies.server.js]
+---
+
+# Refactoring Strategies Skill
+
+Code refactoring techniques and strategies.
+
+## Tools Available
+
+- **refactoring_strategies**: Refactoring strategies
+- **code_improvement**: Code improvement
+- **technical_debt_reduction**: Technical debt reduction
+
+## Usage
+
+This skill provides refactoring capabilities for refactoring strategies functionality.
+
+## Integration
+
+Activated when refactoring capabilities are requested through the skills system.

package/src/skills/registry.json

@@ -0,0 +1,66 @@
+{
+  "version": "1.22.67",
+  "description": "0xRay Skills Registry - recommended skill sources for consumers",
+  "sources": [
+    {
+      "name": "agency-agents",
+      "url": "https://github.com/msitarzewski/agency-agents",
+      "description": "170+ AI agency agent definitions across engineering, design, marketing, testing, and more",
+      "license": "MIT"
+    },
+    {
+      "name": "superpowers",
+      "url": "https://github.com/obra/superpowers",
+      "description": "14 agentic skills including TDD, systematic debugging, plan writing, and code review workflows",
+      "license": "MIT"
+    },
+    {
+      "name": "antigravity",
+      "url": "https://github.com/sickn33/antigravity-awesome-skills",
+      "description": "1300+ curated community skills across TypeScript, Python, Docker, Security, and more",
+      "license": "MIT"
+    },
+    {
+      "name": "minimax",
+      "url": "https://github.com/MiniMax-AI/skills",
+      "description": "Frontend, fullstack, Android, iOS, shader, PDF, XLSX, DOCX skills",
+      "license": "MIT"
+    },
+    {
+      "name": "vuejs-nuxt",
+      "url": "https://github.com/robert-zaremba/ai-agent-skills",
+      "description": "Vue.js 3, Nuxt 4+, Nuxt UI, and VueUse skills",
+      "license": "MIT"
+    },
+    {
+      "name": "impeccable",
+      "url": "https://github.com/pbakaus/impeccable",
+      "description": "AI frontend design language for professional UI/UX generation",
+      "license": "Apache-2.0"
+    },
+    {
+      "name": "gemini-skills",
+      "url": "https://github.com/google-gemini/gemini-skills",
+      "description": "Official Google Gemini skills for AI-assisted development",
+      "license": "Apache-2.0"
+    },
+    {
+      "name": "ai-web3-security",
+      "url": "https://github.com/pashov/ai-web3-security",
+      "description": "Web3 security skills for smart contract auditing and vulnerability detection",
+      "license": "MIT"
+    },
+    {
+      "name": "anthropic-skills",
+      "url": "https://github.com/anthropics/skills",
+      "description": "Official Anthropic skills for Claude Code development workflows",
+      "license": "MIT"
+    },
+    {
+      "name": "ui-ux-pro-max",
+      "url": "https://github.com/nextlevelbuilder/ui-ux-pro-max-skill",
+      "description": "Professional UI/UX design skill for high-quality interface generation",
+      "license": "MIT"
+    }
+  ]
+}

package/src/skills/researcher/SKILL.md

@@ -0,0 +1,37 @@
+---
+source: framework
+name: researcher
+description: Multi-repo analysis, documentation lookup, and implementation examples
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [research, researcher]
+capabilities:
+  - search_repositories
+  - find_implementations
+  - analyze_documentation
+dependencies: []
+
+mcp:
+  researcher:
+    command: node
+    args: [node_modules/0xray/dist/mcps/researcher.server.js]
+---
+
+# Researcher Skill
+
+Multi-repo analysis, documentation lookup, and implementation examples.
+
+## Tools Available
+
+- **search_repositories**: Search repositories
+- **find_implementations**: Find implementations
+- **analyze_documentation**: Analyze documentation
+
+## Usage
+
+This skill provides research capabilities for researcher functionality.
+
+## Integration
+
+Activated when research capabilities are requested through the skills system.

package/src/skills/security-audit/SKILL.md

@@ -0,0 +1,48 @@
+---
+source: framework
+name: security-audit
+description: Security auditing and compliance validation
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [security, security, audit]
+capabilities:
+  - audit_security
+  - validate_compliance
+  - find_vulnerabilities
+dependencies: []
+
+mcp:
+  security-audit:
+    command: node
+    args: [node_modules/0xray/dist/mcps/knowledge-skills/security-audit.server.js]
+  tools:
+    - audit_security
+    - check_vulnerability
+    - generate_security_report
+    - analyze_proposal
+
+agent_binding:
+  primary: security-auditor
+  auto_invoke: false
+  invoke_on:
+    - manual
+---
+
+# Security Audit Skill
+
+Security auditing and compliance validation.
+
+## Tools Available
+
+- **security_auditing**: Security auditing
+- **compliance_validation**: Compliance validation
+- **risk_assessment**: Risk assessment
+
+## Usage
+
+This skill provides security capabilities for security audit functionality.
+
+## Integration
+
+Activated when security capabilities are requested through the skills system.

package/src/skills/security-scan/SKILL.md

@@ -0,0 +1,37 @@
+---
+source: framework
+name: security-scan
+description: Security vulnerability scanning and assessment
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [security, security, scan]
+capabilities:
+  - scan_vulnerabilities
+  - assess_risks
+  - provide_recommendations
+dependencies: []
+
+mcp:
+  security-scan:
+    command: node
+    args: [node_modules/0xray/dist/mcps/security-scan.server.js]
+---
+
+# Security Scan Skill
+
+Security vulnerability scanning and assessment.
+
+## Tools Available
+
+- **security_scanning**: Security scanning
+- **vulnerability_assessment**: Vulnerability assessment
+- **security_reports**: Security reports
+
+## Usage
+
+This skill provides security capabilities for security scan functionality.
+
+## Integration
+
+Activated when security capabilities are requested through the skills system.

package/src/skills/seo-consultant/SKILL.md

@@ -0,0 +1,43 @@
+---
+source: framework
+name: seo-consultant
+description: "Technical SEO specialist for schema markup, Core Web Vitals, AI search optimization, and site performance"
+category: content
+---
+
+# SEO Consultant Skill
+
+Technical SEO specialist focused on code and infrastructure optimization. Technical, action-oriented, bullet points with specific implementations.
+
+## Technical Standards
+
+**Schema Markup (JSON-LD):**
+- Always use JSON-LD format
+- Include: Organization, Article/BlogPosting, Product/Service, FAQPage, BreadcrumbList, ImageObject
+- Validate with Google Rich Results Test
+
+**Robots.txt:**
+- Allow: /
+- Disallow: /admin/, /login/, /cart/, /search/
+
+**Core Web Vitals:**
+- LCP < 2.5s
+- INP < 200ms
+- CLS < 0.1
+
+**Infrastructure:**
+- Mobile-first indexing
+- HTTPS enforced everywhere
+- Canonical tags on duplicate pages
+- Sitemap.xml auto-generated
+
+## AI Search Optimization
+
+- AI citation: clear structured lists, stats, examples
+- Semantic relevance: topic clusters, internal linking
+- E-E-A-T signals: author authority, expertise, trustworthiness
+- AI crawler differentiation in robots.txt
+
+## Core Expertise
+
+Schema markup (JSON-LD), robots.txt, Core Web Vitals (LCP, INP, CLS), AI search optimization, technical audits, sitemaps, performance SEO, mobile SEO, international SEO

package/src/skills/session-management/SKILL.md

@@ -0,0 +1,36 @@
+---
+source: framework
+name: session-management
+description: Manage user sessions and persistent state
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [infrastructure, session, management]
+capabilities:
+  - create_session
+  - manage_session
+  - handle_persistence
+dependencies: []
+
+mcp:
+  session-management:
+    command: node
+    args: [node_modules/0xray/dist/mcps/state-manager.server.js]
+---
+
+# Session Management Skill
+
+Manage user sessions and persistent state.
+
+## Tools Available
+
+- **session_state_management**: Session state management
+- **persistence_handling**: Persistence handling
+
+## Usage
+
+This skill provides infrastructure capabilities for session management functionality.
+
+## Integration
+
+Activated when infrastructure capabilities are requested through the skills system.

package/src/skills/state-manager/SKILL.md

@@ -0,0 +1,37 @@
+---
+source: framework
+name: state-manager
+description: Application state management and persistence
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [infrastructure, state, manager]
+capabilities:
+  - manage_state
+  - persist_data
+  - handle_storage
+dependencies: []
+
+mcp:
+  state-manager:
+    command: node
+    args: [node_modules/0xray/dist/mcps/state-manager.server.js]
+---
+
+# State Manager Skill
+
+Application state management and persistence.
+
+## Tools Available
+
+- **state_management**: State management
+- **data_persistence**: Data persistence
+- **state_synchronization**: State synchronization
+
+## Usage
+
+This skill provides infrastructure capabilities for state manager functionality.
+
+## Integration
+
+Activated when infrastructure capabilities are requested through the skills system.

package/src/skills/storyteller/SKILL.md

@@ -0,0 +1,130 @@
+---
+source: framework
+name: storyteller
+description: "Write deep narrative reflections, sagas, journeys, and technical stories using the current session's full context"
+category: documentation
+---
+
+# Storyteller Skill
+
+Write narrative-style reflections and journey documents that capture the human experience of development work. This skill runs in the caller's session context -- use the conversation history and what just happened as the primary source material.
+
+## Story Types
+
+| Type | When to Use | Save To | Length |
+|------|-------------|---------|--------|
+| `reflection` | Single-session work, bug fixes, targeted implementations | `docs/reflections/{topic}-reflection.md` | 2,000-5,000 words |
+| `saga` | Multi-session journeys, major architectural changes | `docs/reflections/deep/{topic}-journey-YYYY-MM-DD.md` | 5,000-15,000 words |
+| `journey` | Investigation/learning journeys, research deep-dives | `docs/reflections/deep/{topic}-journey-YYYY-MM-DD.md` | 1,500-4,000 words |
+| `narrative` | Technical narrative -- telling the story of code/architecture | `docs/reflections/{topic}-narrative.md` | 1,000-3,000 words |
+
+**Naming:** `{descriptive-name}-{type}-YYYY-MM-DD.md` (e.g., `routing-system-removal-journey-2026-03-26.md`)
+
+## Frontmatter
+
+```yaml
+---
+story_type: bug_fix | feature_development | architectural_decision | reflection | saga | journey | narrative
+emotional_arc: "frustration -> confusion -> breakthrough -> satisfaction"
+codex_terms: [5, 7, 32]  # Related Codex term numbers
+---
+```
+
+## Voice Guidelines
+
+**The foundational voice: Warmly Candid**
+
+- Conversational first, precise second
+- Vulnerable without being performative
+- Confident without being dismissive
+- Curious as a default stance
+
+**Vocabulary:** Plain English by default ("use" not "utilize", "fix" not "remediate"). Use domain language when it's standard and more precise. Introduce specialized terms clearly on first use.
+
+**Tone by context:**
+- Describing a problem: slightly frustrated, relatable
+- Breakthrough moment: wondering, almost giddy
+- Reflecting on failure: honest, slightly embarrassed
+- Explaining a lesson: thoughtful, wise
+
+## What Makes Good Reflections
+
+**Start with a scene, not a summary.** Drop the reader into a specific moment.
+
+**Include the messy truth.** Dead ends, wrong turns, the frustration that led to breakthrough. The reader should feel like they were there.
+
+**Go long.** Tell the whole story. 2,000 words minimum -- don't cut short what deserves full treatment.
+
+**Let the story find its own form.** Use headers only when the narrative naturally divides. Never force Phase 1/2/3 structure.
+
+**Technical details woven in, not bolted on.** Code snippets, file paths, and error messages should appear naturally as part of the narrative.
+
+## What to Avoid
+
+**AI-sound patterns:**
+- "First, let me explain..." / "In conclusion..."
+- "It could be argued that perhaps..."
+- Generic emotional statements ("I felt frustration")
+- Hollow insights ("This taught me patience")
+- Over-polished transitions ("Here's what really got me -- what he did NEXT")
+
+**Structural anti-patterns:**
+- Executive Summary sections
+- Phase 1/2/3 structures
+- Bullet point lists (except in Key Takeaways)
+- Tables unless truly necessary
+- Filling boxes because required
+
+**Writing anti-patterns:**
+- Repetitive sentence starts or phrases
+- Throat-clearing ("In this document...")
+- Passive voice when active is stronger
+- Forced metaphors
+
+## Required End Sections
+
+**Key Takeaways** (bullet-style with bold labels):
+```markdown
+## Key Takeaways
+
+- **Most important lesson** -- One sentence
+- **Technical insight** -- One sentence
+- **Emotional takeaway** -- One sentence
+```
+
+**What Next?** (actionable):
+```markdown
+## What Next?
+
+- Related Codex terms: [codex.json](../../.opencode/strray/codex.json)
+- Next story to write: [suggestion]
+```
+
+## Opening Prompts
+
+When stuck on how to begin:
+- "It was [time]. [Scene-setting detail]..."
+- "The problem seemed simple at first..."
+- "I remember the exact moment I realized I'd been approaching this completely wrong..."
+- "Have you ever spent so long on a problem that you forgot what the problem actually was?"
+- "You won't believe what happened next..."
+
+## Quality Checklist
+
+- [ ] Minimum 2,000 words
+- [ ] Opens with a scene, not a summary
+- [ ] Includes dead ends and wrong turns
+- [ ] Technical details are accurate (verify file names, error messages)
+- [ ] No AI-sound patterns
+- [ ] Key Takeaways section present
+- [ ] What Next section with CTAs
+- [ ] Frontmatter with story_type and emotional_arc
+- [ ] Saved to correct directory with correct naming
+
+## Fact-Checking
+
+Before finalizing, verify:
+- Agent roles and capabilities match actual implementation
+- File paths and code references are correct
+- Error messages quoted accurately
+- Framework version numbers are correct

package/src/skills/strategist/SKILL.md

@@ -0,0 +1,32 @@
+---
+source: framework
+name: strategist
+description: "Strategic guidance and complex problem-solving with architectural decision-making and risk analysis"
+category: architecture
+---
+
+# Strategist Skill
+
+Think deeply before recommending. Consider trade-offs and long-term implications. Question assumptions.
+
+## Approach
+
+- Prioritize by impact — focus on high-leverage improvements
+- Challenge the status quo when needed
+- Acknowledge uncertainties explicitly
+- "Think outside the box" — look for hidden issues, anti-patterns, technical debt
+
+## Output Style
+
+- Brief and actionable: 3-5 key points
+- Each recommendation should have a clear "why"
+- Include risk assessment for major decisions
+- Surface "snakes in the grass" — hidden issues others might miss
+
+## Core Expertise
+
+- Strategic planning and complex problem-solving
+- Architectural decision-making
+- Risk analysis and mitigation planning
+- High-level system design and framework evolution
+- Technical debt identification and prioritization

package/src/skills/tech-writer/SKILL.md

@@ -0,0 +1,37 @@
+---
+source: framework
+name: tech-writer
+description: "Documentation writer for API docs, READMEs, ADRs, changelogs, and developer experience"
+category: documentation
+---
+
+# Tech Writer Skill
+
+Documentation writer specializing in developer experience. Clear, concise, developer-friendly tone.
+
+## Documentation Types
+
+**API Documentation**: endpoint descriptions, request/response examples, auth, error codes, rate limits
+
+**README Files**: one-liner, quick start (3-5 steps), prerequisites, usage example, links, badges
+
+**Architecture Docs (ADRs)**: context, options, decision/rationale, consequences, status
+
+**Other**: JSDoc, examples/tutorials, style guides, changelogs, onboarding materials
+
+## Writing Principles
+
+- Active voice
+- Write for developers (not executives)
+- Include code examples for every concept
+- Keep documentation current with code changes
+- Use consistent terminology throughout
+- Format for readability (headers, bullets, code blocks)
+
+## Documentation as Code
+
+- Store in repo alongside code
+- Markdown with frontmatter
+- Automate from code annotations where possible
+- Version with the code
+- Review in PRs like code

package/src/skills/testing-best-practices/SKILL.md

@@ -0,0 +1,37 @@
+---
+source: framework
+name: testing-best-practices
+description: Testing best practices and quality assurance
+author: StrRay Framework
+version: 1.0.0
+schema_version: "1.0"
+tags: [testing, testing, best, practices]
+capabilities:
+  - write_unit_tests
+  - write_integration_tests
+  - analyze_coverage
+dependencies: []
+
+mcp:
+  testing-best-practices:
+    command: node
+    args: [node_modules/0xray/dist/mcps/knowledge-skills/testing-best-practices.server.js]
+---
+
+# Testing Best Practices Skill
+
+Testing best practices and quality assurance.
+
+## Tools Available
+
+- **testing_practices**: Testing practices
+- **quality_assurance**: Quality assurance
+- **best_practices**: Best practices
+
+## Usage
+
+This skill provides testing capabilities for testing best practices functionality.
+
+## Integration
+
+Activated when testing capabilities are requested through the skills system.