ariaxhan

Turn a borrowed metaphor, analogy, or cross-domain inspiration into a testable mechanism, or prove it is decoration and discard it. Use when a design leans on language from another field ("immune system", "evolution", "market", "quorum", "crystallization"),…

Design systems so a failure can never present as success. Use when building or reviewing pipelines, extractors, reconciliations, checkers, or any computation whose output humans act on; when missing inputs, unreadable files, or crashes could pass silently;…

A compact decision protocol for non-trivial choices, reviews, governance calls, and live disagreement. Use implicitly at decision points, even when nobody says "debate", whenever a choice is high-impact, hard to reverse, policy-bearing, or has multiple…

Search for the existing spine before building anything new. Use when about to create a file, module, helper, wrapper, config system, or process: "should I add a new X", "where should this live", "build a helper for this", "we need a system for this", or when…

Split substantial work into units by verification boundary, not by file or feature. Use when planning implementation order, breaking down a big task, or sequencing a build: "how should I split this", "what order should I build this in", "break this down",…

Write the session handoff while the verified context is still loaded, before the window or budget runs out. Use when context is running low mid-work, when pausing substantial work ("wrap up", "hand this off", "save state for the next session", "we'll pick…

Delegate implementation to cheap or small models safely by pre-deciding everything. Use when splitting work across agent lanes, picking a model tier, or writing a worker prompt: "can a small model do this", "delegate this", "fan this out", "spawn workers for…

Draft skill for building and releasing iOS or macOS Catalyst apps. Current coverage is the App Store Connect API key TestFlight upload path; expand before publishing into the full lifecycle from app/design import through build, test, metadata, screenshots,…

Show KERNEL help. The unified skill system, state operations, agents, current plugin status. Triggers: help, how, what, skills, commands.

Write the guided acceptance pass a human runs against a real build: literal taps, real inputs, expected outcome per step, worst case first, bundled to cost one sitting. Triggers: testflight, human pass, acceptance test, before we ship, hand it to the user,…

Release-gate sequence: validate → review → push → tag. Wraps kernel:git mechanics with the pre-ship safety chain. Triggers: ship, release, push to main, ready to merge, deploy.

Solution exploration and implementation. Generate 2-3 approaches, pick simplest. Never implement first idea. Triggers: build, implement, create, feature, add.

Unified entry point for new AND resumed work. Research → classify → scope → execute for new tasks; manifest validate → divergence check → bounded context compile → resume for kernel.handoff/v1 / kernel.checkpoint/v1 manifests. Triggers: start, begin, do,…

Explicit landing-page build and deployment operator. Loads marketing strategy and frontend judgment, scaffolds the smallest suitable site, verifies rendered behavior, and deploys to the user's or project's configured target.

Context-led frontend design and UI implementation. Derives art direction from the product, audience, brand, content, and existing design system; prevents generic AI defaults without imposing a Kernel house style. Triggers: frontend, ui, styling, css, visual,…

Multi-agent orchestration. Lane contracts, worker-model doctrine, fault tolerance, worktree isolation. Triggers: orchestrate, coordinate, agents, parallel, spawn, contract, tier 2, tier 3.