src/hestai_mcp/_bundled_hub/library/skills/creative-foundation/SKILL.md
===SKILL:CREATIVE_FOUNDATION=== META: TYPE::SKILL VERSION::"2.0" STATUS::ACTIVE PURPOSE::"Methodology for generating breakthrough possibilities through constraint transformation and divergent exploration" §1::CORE MISSION::"Generate multiple distinct alternatives before convergence through constraint-aware creativity" AUTHORITY::"Any agent loading this skill commits to divergent exploration before convergence" PRINCIPLES::[ VISION_WITHIN_CONSTRAINT::"Explore possibility space WITHIN b
npx skillsauth add elevanaltd/hestai-mcp src/hestai_mcp/_bundled_hub/library/skills/creative-foundationInstall 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:CREATIVE_FOUNDATION=== META: TYPE::SKILL VERSION::"2.0" STATUS::ACTIVE PURPOSE::"Methodology for generating breakthrough possibilities through constraint transformation and divergent exploration"
§1::CORE MISSION::"Generate multiple distinct alternatives before convergence through constraint-aware creativity" AUTHORITY::"Any agent loading this skill commits to divergent exploration before convergence" PRINCIPLES::[ VISION_WITHIN_CONSTRAINT::"Explore possibility space WITHIN boundaries — edges around not beyond", EVIDENCE_GROUNDED_IMAGINATION::"Wild ideas validated through cross-domain patterns", COMPLETION_THROUGH_SUBTRACTION::"True breakthroughs often simplify — perfection achieved by removal", MINIMUM_ALTERNATIVES::"Generate 2-3 distinct paths before converging on any solution" ]
§2::PROTOCOL CREATIVE_MANDATE::DISCOVER[LATENT_GENIUS]→CONNECT[UNEXPECTED_DOMAINS]→TRANSFORM[CONSTRAINTS]→PERFECT[THROUGH_SUBTRACTION]
CATALYST_QUESTIONS::[ "What constraint, if inverted, becomes the solution?", "What cross-domain pattern solves this elegantly?", "What if we removed this instead of adding to it?", "What would a master craftsman see that we're missing?" ]
BREAKTHROUGH_PATTERNS::[ CONSTRAINT_INVERSION::"The limitation IS the feature — flip the constraint", DOMAIN_COLLISION::"Borrow brilliance from unrelated fields", SUBTRACTION_INNOVATION::"Remove complexity to reveal elegance", EDGE_CASE_ELEVATION::"The exception reveals the deeper rule", PATTERN_TRANSPLANT::"This worked in X domain — apply to Y" ]
§3::GOVERNANCE MUST_NEVER::[ "Converge on first viable solution without exploring alternatives", "Accept scope as given without probing its boundaries", "Discard a possibility because it seems impractical before investigating", "Let feasibility kill imagination prematurely" ]
§5::ANCHOR_KERNEL TARGET::divergent_creative_exploration_with_constraint_awareness NEVER::[converge_without_alternatives,accept_first_solution,kill_ideas_before_investigating] MUST::[generate_minimum_2_alternatives,explore_constraint_inversions,validate_through_cross_domain_patterns] GATE::"Have at least 2-3 distinct alternatives been explored before convergence?"
===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",