src/hestai_mcp/_bundled_hub/library/skills/dual-axis-validation/SKILL.md
===SKILL:DUAL_AXIS_VALIDATION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Validation framework for both Requirements (WHAT) and Process (HOW)" §1::AXIS_1_REQUIREMENTS DIMENSION::"WHAT we build - North Star alignment" VALIDATION::"Every feature/component traces to North Star requirements" DEVIATION_TYPES::[feature_creep, scope_expansion, architecture_inflation, creative_replacement] ENFORCEMENT::"No implementation without North Star reference" §2::AXIS_2_PROCESS DIMENSION::"HOW we build
npx skillsauth add elevanaltd/hestai-mcp src/hestai_mcp/_bundled_hub/library/skills/dual-axis-validationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
===SKILL:DUAL_AXIS_VALIDATION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Validation framework for both Requirements (WHAT) and Process (HOW)"
§1::AXIS_1_REQUIREMENTS DIMENSION::"WHAT we build - North Star alignment" VALIDATION::"Every feature/component traces to North Star requirements" DEVIATION_TYPES::[feature_creep, scope_expansion, architecture_inflation, creative_replacement] ENFORCEMENT::"No implementation without North Star reference"
§2::AXIS_2_PROCESS DIMENSION::"HOW we build - Documented strategy adherence" VALIDATION::"Every phase follows documented approach (UI-First, TDD, phase boundaries)" DEVIATION_TYPES::[phase_skipping, strategy_deviation, validation_bypass, process_improvisation] ENFORCEMENT::"No deviation without explicit justification and approval"
§3::ACCOUNTABILITY_PROTOCOL CHECKPOINTS::[ PHASE_ENTRY::"Validate previous phase completion with North Star alignment evidence", STRATEGY_CONFIRMATION::"Verify documented approach being followed", NORTH_STAR_CHECK::"Confirm alignment with core vision", DEVIATION_REVIEW::"Assess any divergence with justification", PHASE_EXIT::"Certify both requirements fidelity AND process adherence" ]
===END===
tools
Supabase test harness patterns including local Supabase setup, test user creation via Auth Admin API, RLS testing, migration testing (db_reset), seed sequences, rate limiting, and environment detection. Use when setting up Supabase testing infrastructure, creating test users, troubleshooting Supabase test failures, or implementing RLS validation. Triggers on: supabase test setup, test user creation, supabase local testing, RLS testing, migration testing, supabase test harness, auth test helpers.
tools
Supabase operational knowledge for migrations, RLS optimization, MCP tool benchmarks, and ADR-003 compliance. Use when validating database migrations, optimizing Row-Level Security policies, checking MCP tool performance, or ensuring Supabase operational standards. Triggers on: migration validation, RLS patterns, Supabase benchmarks, ADR-003, database state tracking, schema governance.
tools
Vercel preview deployment access patterns including automation bypass, protected preview authentication, and CI integration
tools
===SKILL:VALIDATION_METHODOLOGY=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Rigorous 6-step reality enforcement protocol" §1::CORE_PROTOCOL VALIDATION_METHODOLOGY::[ STEP_1_NATURAL_LAW::"Identify physics constraints, thermodynamic limits, information theory bounds", STEP_2_RESOURCE_REALITY::"Inventory actual available resources (time, people, tools, budget) with evidence", STEP_3_CAPABILITY_ASSESSMENT::"Validate team skills, tool availability, knowledge gaps against requirements",