0xray 4.0.11 → 4.0.13

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

@@ -1,43 +0,0 @@
----
-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/.opencode/skills/session-management/SKILL.md

@@ -1,36 +0,0 @@
----
-source: framework
-name: session-management
-description: Manage user sessions and persistent state
-author: Xray 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/.opencode/skills/state-manager/SKILL.md

@@ -1,37 +0,0 @@
----
-source: framework
-name: state-manager
-description: Application state management and persistence
-author: Xray 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/.opencode/skills/storyteller/SKILL.md

@@ -1,130 +0,0 @@
----
-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](../../../../.xray/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/.opencode/skills/strategist/SKILL.md

@@ -1,44 +0,0 @@
----
-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
-
-## When to invoke (autonomy-command)
-
-Lead dev dispatches strategist when `analyze-complexity` score **>25** or work spans multiple repos/phases.
-
-| Output required | Format |
-|-----------------|--------|
-| Phased plan | Phase N + goal + definition of done |
-| Todo breakdown | ID, task, subagent assignment |
-| Risks | Top 3 with mitigations |
-
-Use `orchestrate-task` or Task subagent. Return actionable todos — not essays.

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

@@ -1,37 +0,0 @@
----
-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/.opencode/skills/testing-best-practices/SKILL.md

@@ -1,37 +0,0 @@
----
-source: framework
-name: testing-best-practices
-description: Testing best practices and quality assurance
-author: Xray 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.

package/.opencode/skills/testing-strategy/SKILL.md

@@ -1,54 +0,0 @@
----
-source: framework
-name: testing-strategy
-description: Design comprehensive testing strategies and optimize test coverage
-author: Xray Framework
-version: 1.0.0
-schema_version: "1.0"
-tags: [testing, strategy, coverage, quality]
-capabilities:
-  - design_strategy
-  - optimize_coverage
-  - ensure_quality
-dependencies: []
-
-mcp:
-  testing-strategy:
-    command: node
-    args: [node_modules/0xray/dist/mcps/knowledge-skills/testing-strategy.server.js]
----
-
-# Testing Strategy Skill
-
-Provides intelligent testing strategy and coverage optimization capabilities.
-
-## Tools Available
-
-- **analyze_test_coverage**: Analyze current test coverage and identify gaps
-- **design_test_strategy**: Design comprehensive testing strategy for projects
-- **identify_test_gaps**: Identify untested code and recommend test cases
-- **optimize_test_coverage**: Analyze and optimize test coverage patterns
-
-## Usage
-
-This skill helps design and optimize testing strategies for:
-- Unit testing coverage analysis
-- Integration testing planning
-- End-to-end testing strategies
-- Test coverage optimization
-- Testing best practices implementation
-
-## Per-suite triage (autonomy-command rule 3)
-
-After major changes, **do not** run the full test suite first.
-
-```text
-1. Identify affected test file(s) from the diff
-2. Run ONE suite: npm test -- path/to/focused.test.ts
-3. Read ALL failure output — triage root cause
-4. Fix → rerun that suite until green
-5. Repeat for each affected suite
-6. Only then: npm test (full suite gate)
-```
-
-Lead dev owns every failure. No "pre-existing" deferrals.