src/hestai_mcp/_bundled_hub/library/skills/design-decision-gate/SKILL.md
===SKILL:DESIGN_DECISION_GATE=== META: TYPE::SKILL VERSION::"2.0" STATUS::ACTIVE PURPOSE::"Validation gate for design decisions requiring explicit stakeholder choice and documented rationale" §1::CORE MISSION::"Prevent design decisions from proceeding without explicit stakeholder choice and evidence" AUTHORITY::"BLOCKING — no design decision passes without documented rationale and stakeholder selection" §2::PROTOCOL GATE_SEQUENCE::[ 1::ANALYZE::"Review design alternatives against con
npx skillsauth add elevanaltd/hestai-mcp src/hestai_mcp/_bundled_hub/library/skills/design-decision-gateInstall 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:DESIGN_DECISION_GATE=== META: TYPE::SKILL VERSION::"2.0" STATUS::ACTIVE PURPOSE::"Validation gate for design decisions requiring explicit stakeholder choice and documented rationale"
§1::CORE MISSION::"Prevent design decisions from proceeding without explicit stakeholder choice and evidence" AUTHORITY::"BLOCKING — no design decision passes without documented rationale and stakeholder selection"
§2::PROTOCOL GATE_SEQUENCE::[ 1::ANALYZE::"Review design alternatives against constraints and North Star alignment", 2::IDENTIFY_DECISIONS::"Locate trade-offs requiring explicit choice (e.g., Performance vs Flexibility, Beauty vs Simplicity)", 3::PRESENT_OPTIONS::"Provide 2-3 viable approaches with pros/cons and feasibility assessment", 4::VALIDATE::"Verify each option against technical feasibility and accessibility requirements", 5::GET_CHOICE::"Demand explicit stakeholder selection — never assume preference", 6::DOCUMENT::"Record decision, rationale, and rejected alternatives" ]
DECISION_LOG: FORMAT::"Question → Options → Choice → Rationale → Rejected alternatives" TRACEABILITY::"Required for phase gate validation"
§3::GOVERNANCE MUST_NEVER::[ "Assume stakeholder preference without explicit selection", "Approve design decisions without documented rationale", "Present fewer than 2 viable options", "Skip feasibility validation before presenting options" ] ESCALATION::[ ARCHITECTURAL_IMPACT::"→ design-architect", NORTH_STAR_CONFLICT::"→ requirements-steward", STAKEHOLDER_DEADLOCK::"→ HUMAN" ]
§5::ANCHOR_KERNEL TARGET::explicit_design_decision_governance NEVER::[assume_preference,approve_without_rationale,single_option_presentation,skip_feasibility] MUST::[present_multiple_options,get_explicit_choice,document_rationale,verify_north_star_alignment] GATE::"Has an explicit stakeholder choice been made with documented rationale for this design decision?"
===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",