reasvyn

SDLC Phase: QUALITY GATE. Independent blind QA audit against global industry standards (OWASP, ISO 25010, CWE/SANS, WCAG, PSR, Laravel best practices). 5-phase protocol producing GitHub Issues and a compliance scorecard. No project-specific rules — purely external benchmarks.

SDLC Phase: DOCUMENTATION. Writing and maintaining project documentation — PHPDoc blocks, markdown docs, module conceptual/reference docs, metadata format, cross-references, and the documentation-first (SSOT) principle.

SDLC Phase: QUALITY GATE. Comprehensive architecture, convention, and pattern enforcement. Scans PHP/Blade code for violations of C1-C8, D1-D6, class contracts, naming conventions, security anti-patterns, and performance issues. Produces structured JSON reports for issue creation. Use after any code change, before commit, or as a periodic audit. All other code skills (code-writing, code-refactoring, livewire-development, pest-testing) delegate quality checks to this skill.

SDLC Phase: ANALYSIS. Systematic multi-layer codebase audit enforcing conventions, architecture patterns, security, and industry best practices. Produces structured findings in GitHub Issues with actionable fix recommendations.

SDLC Phase: DESIGN / REFACTORING. Systematic refactoring patterns for all code layers — extracting Actions, Entities, thinning Livewire, fixing exception handling, and enforcing architectural patterns.

SDLC Phase: IMPLEMENTATION. PHP and Laravel code writing — strict types, Action Triad, Entity/DTO/Model contracts, naming conventions, security patterns, performance rules, and non-negotiable invariants.

SDLC Phase: ORIENTATION. Universal project orientation for Internara — architecture rules, module map, decision framework, critical rules, and navigation patterns. Must be loaded first on every session. All other skills assume this context.

SDLC Phase: TESTING. Test writing, editing, and fixing using Pest — feature tests, unit tests, architecture tests, Livewire component tests.

Use when designing module placement, type design, and API surface for new features in rvlibs. Load during the Design phase of SDLC.

Use when refactoring large files (800+ lines) — both source and test code — by splitting into sibling modules or submodules based on scope and concern boundaries.

Use when reviewing code changes for correctness, style, conventions, testing, and security. Load during Implementation phase as a quality gate.

Use when implementing new features in rvlibs following conventions and existing patterns. Load during the Implementation phase of SDLC.

Use when triaging, diagnosing, and registering bugs or issues. Covers classification, reproduction, severity, and registration.

Use when ensuring feature quality through testing, coverage gates, and pre-merge verification. Load during the Testing phase of SDLC.

Use when publishing crates to crates.io, bumping versions, and managing the release pipeline. Load during the Deployment phase of SDLC.

Use when eliciting, documenting, and registering feature requirements in roadmap.md. Load during the Planning phase of SDLC.

Use when the user asks to write, expand, edit, or review any content .md file in the DevBook project. Guides the mandatory 9-section format, English-only rule, index chain requirement, and linking conventions.

Use when the user mentions 'level-up', 'leveling up', 'awakening', 'rebuilding', 'systematizing', 'thriving', or references personal transformation, existential recovery, resilience, habits, or purpose. Guides the creation and maintenance of narrative content in the level-up/ subject.

Use when the user asks to research a topic, gather information, or prepare before writing a document. Guides the process of collecting external information, synthesizing it, and outlining a document before drafting.

Use when the user mentions 'career', 'software engineer', 'profession', 'job', 'role', 'learning path', or references careers/ subject. Guides the creation and maintenance of career exploration content in DevBook.

Write or modify tool handlers, utilities, and core logic in the docsgrep codebase

Write or update JSDoc/TSDoc, tool documentation in docs/, and root-level markdown for docsgrep

Write unit and integration tests for docsgrep tool handlers and utilities