ariaxhan
- 41 skills
- 0 followers
- 6 hours ago last updated
- ▌ Prep Site For AI · ariaxhan bundleMake a website legible to LLMs, AI search engines, and autonomous agents (structured data (JSON-LD), llms.txt, semantic server-rendered HTML, machine-readable facts, crawler access, and provenance signals) so AI systems quote you correctly instead of skipping or hallucinating about you. Use when prepping a site for AI search / generative engines (GEO), making content agent-readable, exposing facts to LLM crawlers, or fixing why AI tools misrepresent a business. Triggers include "prep my site for AI", "make this AI-readable", "GEO / generative engine optimization", "why does ChatGPT get my business wrong", "add structured data / llms.txt", "is my site crawlable by AI".
- ▌ Secure Keys · ariaxhan bundleAudit and lock down how AI tools hold API keys and credentials. Finds exposed keys across code, config files, .env files, environment variables, shell history, and git history; moves connections to OAuth / "Sign in with X" where one exists; migrates the rest into secure storage (macOS Keychain, a cloud secrets manager, or Cloudflare AI Gateway) with runtime retrieval instead of files; flags what to rotate; and tightens scope, spend caps, expiry, and IP rules. Trigger on "secure my keys", "audit my credentials/secrets", "find exposed API keys", "lock down my secrets", "key hygiene", "did I leak a key", or after wiring up an MCP server or a new integration.
- ▌ Audit Website Quality · ariaxhan bundleAudit a website or page against the full quality policy bank (SEO, accessibility, performance, responsive layout, security, content/anti-slop, link integrity, and structured data) and produce graded findings. Use when reviewing a site before launch, auditing an AI- or template-generated site, checking "is this site actually good", or diagnosing why a page ranks/converts/reads poorly. Works on any site regardless of how it was built. Triggers include "audit my site", "review this website", "is this page ready to ship", "check SEO and accessibility", "why does this site feel generic".
- ▌ Reality Audit · ariaxhan bundleAudit a "done" report or near-final artifact against reality. Use when an AI agent or a person reports work as finished, or when something substantial is about to be sent, published, submitted, or shipped. Separates corroborated structure from self-reported metrics, hunts real defects before release, and returns a trust or ship/hold verdict tied to live checks.
- ▌ Commission Work · ariaxhan bundleCreate or refine a commission before substantial delegated work. Use when starting a non-trivial coding, research, writing, or planning effort; when the user asks to "scope this", "write a commission", "shape the work", "make the brief", or when an agent needs authority, boundaries, outcomes, and verification before executing. Produces a commission document.
- ▌ Humanize AI Prose · ariaxhan bundleRewrite AI-generated text into genuinely human prose with seven ordered transform passes: add real named specifics, fix the structure, kill the tells (em-dashes, intensifiers, negative parallelism, meta-signposts), admit real limits, and read it aloud.
- ▌ Debate Decisions · ariaxhan bundleA 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 plausible paths that evidence alone cannot settle. Skip for trivial, cheap-to-reverse, or deterministically decidable choices.
- ▌ Create Portable Skill · ariaxhan bundleCreate, audit, or package a portable Claude/Codex skill. Use when building a new skill, converting an existing workflow into a reusable skill, reviewing whether something is a real skill or just a rule/reference/kit, or preparing a skills repository catalog.
- ▌ Train A Taste Model · ariaxhan bundleTrain a small model on your own archive that learns your personal taste and ranks new items the way you would, using implicit curation signals you already produced instead of hand-labeling thousands of examples.
- ▌ Agent Tradition · ariaxhan bundleGive AI coding agents durable institutional memory: purpose, falsifiable beliefs, narrative lessons, and hook-enforced session accountability, so each session makes the next one smarter instead of starting blind.
- ▌ Extract Invariants · ariaxhanTurn 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"), when someone proposes copying how another domain solves a problem, or when reviewing a system whose names sound deeper than its code. Produces either a named domain-free invariant with evidence and falsifiers, or an explicit rejection with the reason it failed.
- ▌ Build And Release IOS App · ariaxhan bundleDraft 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, TestFlight, and App Review submission.
- ▌ Experiment On Rules · ariaxhan bundleTreat prompts, rules, workflows, habits, or methodology claims as hypotheses and test them with evidence. Use when the user asks to "run an experiment", "prove this rule", "test this methodology", "validate this workflow", "is this actually working", or decide whether to keep, change, or kill an operating rule. Produces hypotheses, experiment designs, evidence, confidence updates, and recommendations.
- ▌ Audit The Premise · ariaxhan bundleStress-test the assumption baked into a task before spending real effort on it. Use when a request asserts something is broken, true, already decided, or unchanged before you act on it: "fix the broken X", "since Tuesday it's been down", "just flip the existing thing", "the data already has Y". Triggers include "is this problem even real", "check the assumption before I start", "the request says X but is that true". Produces a confirmed-or-corrected understanding, a logged disagreement when the premise was wrong, and a safer revised plan.
- ▌ Secure Code Changes · ariaxhan bundleReview or implement code changes with security constraints. Use when touching auth, secrets, credentials, permissions, payments, PII, input validation, SQL queries, file uploads, LLM/prompt features, or when the user asks for a security review. Produces a threat-aware checklist, findings, and fixes.
- ▌ Dream Solution Space · ariaxhan bundleExpand a problem's solution space before committing. Use when the user asks to "dream", "brainstorm deeply", "find a better frame", "generate competing approaches", "stress test options", or when the obvious answer feels too easy. Produces grounded perspectives, adversarial critique, integrity scores, and a recommendation.
- ▌ Hunt Research Sources · ariaxhan bundleRun a wide research source hunt and return a ranked findings report. Use when the user asks to "hunt for sources", "go find sources on X", "scan the web for", "do a research sweep", "find the best sources", or compare many sources before deciding what matters. Produces a sourced report with accepted findings, rejected sources, conflicts, and gaps.
- ▌ Synthesize Learnings · ariaxhan bundleDistill accumulated notes and lessons from many sessions into durable insight. Use when scattered learnings, journal entries, meeting takeaways, or decisions have piled up across time and need consolidating: "run a retrospective across my notes", "what have I learned", "clean up and promote my lessons", "synthesize my journal", "find the patterns in my notes". This is cross-session synthesis, distinct from writing up one session. Produces a deduped, contradiction-resolved note set, a list of promoted patterns with evidence, and a health summary.
- ▌ Build Sites As Specs · ariaxhan bundleArchitect a website-generation system that structurally cannot produce slop, by compiling a validated specification into output instead of generating HTML directly. Use when building an AI site generator, a templating/CMS pipeline, a multi-tenant site builder, or any system where a model or template produces web pages and you keep getting hallucinated facts, inconsistent structure, weak SEO/accessibility, and unmaintainable markup. Triggers include "build a website generator", "AI keeps generating slop sites", "how do I make site generation reliable", "spec-driven site building", "stop the model inventing facts on the page".
- ▌ Design API Contracts · ariaxhan bundleDesign or review API contracts for HTTP/REST services and agent-facing endpoints. Use when creating routes, endpoints, status codes, pagination, error responses, versioning, OpenAPI specs, idempotency, or API behavior for AI clients. Produces a clear API contract and review checklist.
- ▌ Design Loud Failures · ariaxhan bundleDesign 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; when a tool "found" an explanation that feels too convenient; or on "make this fail loudly", "could this lie to us", "harden the failure paths". Produces named invariants, explicit skip and no-answer states, honest cause classes, and adversarial regression fixtures.
- ▌ Refactor Code Safely · ariaxhan bundleRefactor code without changing behavior. Use when the user asks to clean up, simplify, rename, restructure, extract, inline, move code, reduce duplication, or modernize internals while preserving behavior. Produces a scoped refactor with before/after checks.
- ▌ Forge Autonomous Work · ariaxhan bundleRun a bounded autonomous work loop that generates competing approaches, implements iteratively, runs acceptance checks, stress-tests the result, learns from the output, and either ships or reports why it cannot. Use when the user asks to "forge this", "run autonomously", "take this end to end", "iterate until done", "iterate until tests pass", or provides runnable acceptance criteria for hands-off implementation. Produces an artifact, evidence log, passing checks or escalation record, and final verdict.
- ▌ Extract Source To Notes · ariaxhan bundleIngest one external source into structured notes. Use when the user drops a Medium article, blog post, paper, URL, transcript, or pasted text and asks to "extract this", "process this article", "distill this URL", "pull the insights from this", or capture one source with provenance. Produces raw provenance, distilled claims, contradictions, tags, and follow-up sparks.
- ▌ Manage A Knowledge Base · ariaxhan bundleRun a personal knowledge base or second brain as a system, not a junk drawer. Use for any stage of a notes collection: "process my inbox / triage my captures", "find contradictions across my notes", "synthesize / weave these notes together", "prune / clean up my ideas list", "archive stale notes / decay scan", "check my notes for broken links or missing metadata", "manage my vault / zettelkasten / second brain". Produces filed notes, collision logs, synthesis notes, a pruned idea list, archive decisions, and an integrity report, depending on the phase invoked.
- ▌ Verify Adversarially · ariaxhan bundleEarn "done" by splitting verification into two roles: a fresh-context agent attacks the work, and the coordinator adjudicates every finding. Use before declaring a subsystem complete, before trusting a green report, after delegated work returns, or on "verify this", "is it actually done", "attack this change", "red-team this", "prove it works". Green tests prove the code does what the tests say; this pass proves the tests say enough.
- ▌ Review AI Code Quality · ariaxhan bundleReview AI-generated or recently changed code for common quality failures. Use when reviewing code, validating an implementation, checking "is this ready", auditing AI-authored changes, or looking for edge cases, validation gaps, error handling problems, duplication, and needless complexity. Produces prioritized findings and required fixes.
- ▌ Brainstorm With Entropy · ariaxhan bundleGenerate genuinely novel ideas by injecting entropy, ranked by surprise instead of safety. Use when the user asks to brainstorm, generate ideas, find an angle, or name something: "what could I build/make/write", "I need fresh ideas", "help me think of", "I'm stuck on the obvious options". Triggers also include "brainstorm with me" and "give me something unexpected". Produces a ranked list of ideas, each tagged with the technique that produced it, its core insight, its risk, and a cheap validation signal.
- ▌ Write Session Chronicle · ariaxhan bundleWrite an honest session chronicle after substantial work. Use when wrapping up coding, research, writing, planning, or agent work; when the user asks to "write the chronicle", "record what happened", "wrap this up", "leave a handoff", or preserve decisions/failures for the next session. Produces a chronicle document with changed files, checks, failures, deferred work, and disagreements.
- ▌ Critique Vision Handoff · ariaxhan bundleAdversarially review vision handoff docs, seed docs, architecture briefs, or implementation plans before they reach coding agents. Use when the user asks to "critique this vision", "review my handoff", "stress test this spec", "break this plan", "find the holes", or check whether a planning document is ready for implementation. Produces a severity-rated critique with concrete fixes.
- ▌ Keep A Confidence Ledger · ariaxhan bundleMaintain one honest map of what is actually true about every subsystem in a project. Use when landing or verifying work changes a subsystem's state, at session close, or when someone asks "what's the state of X", "is X done", "how far along are we", "what's actually working". Replaces percentages and vibes with exactly four evidence- backed states, so a handoff or a status answer never overstates reality.
- ▌ Delegate To Worker Models · ariaxhan bundleDelegate 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 these", "which model for this task". Encodes the lane contract template, the pre-verified guide requirement, and the honest track record of where cheap models succeed and where they quietly fail.
- ▌ Debug Code Systematically · ariaxhan bundleDebug code with a scientific method instead of guessing. Use when fixing bugs, regressions, crashes, stack traces, failing tests, unexpected behavior, or "not working" reports. Produces a reproduced failure, tested hypotheses, isolated root cause, fix, and regression check.
- ▌ Orchestrate Coding Agents · ariaxhan bundleCoordinate multiple AI coding agents safely. Use when splitting implementation, review, testing, research, or refactor work across agents; when tasks can run in parallel; or when the user asks to orchestrate, spawn agents, delegate, parallelize, or manage tiered work. Produces scoped contracts, isolated work, and merged findings.
- ▌ Extend Before Inventing · ariaxhan bundleSearch 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 reviewing work that added a parallel version of something that already existed. A close match gets extended, not re-implemented; built-in beats library beats custom.
- ▌ Harden Rules Into Hooks · ariaxhan bundleEnforce the agent rules that must never break with hooks the agent can't bypass (secret scans, destructive-command guards, format gates) instead of prose instructions it quietly ignores under load.
- ▌ Research Failures First · ariaxhan bundleBefore building anything non-trivial, research real-world failure modes from production post-mortems and issue trackers and produce a committed symptom→cause→fix→URL map, instead of donating your own debugging time or asking the model to hallucinate what could break.
- ▌ Test The Measuring Stick · ariaxhan bundleCheck whether a score, grade, or ranking actually has teeth before you trust it. Use when relying on any quality number: an AI grading its own or another AI's output, a rubric score on writing, a relevance ranking, a benchmark result. Triggers include "is this quality score real", "does my grader/eval actually work", "can I trust this ranking", "does this benchmark mean anything". Produces a dummy-answer result, a cheap-floor comparison, and a verdict on whether the measure is trustworthy.
- ▌ Write Project Vision Handoff · ariaxhan bundleCreate implementation-ready project handoff documents from planning context. Use when the user asks to "write a vision handoff", "create a seed document", "prepare this for a coding agent", "turn this plan into VISION.md", or transfer a planned system to an implementation agent. Produces VISION.md and FLOWCHARTS.md plus only directly useful supplementary docs.
- ▌ Hand Off Before Context Death · ariaxhan bundleWrite 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 this up later"), or when a session is stuck re-reading the same failure. Ten minutes of writing while context is loaded replaces hours of rediscovery.
- ▌ Decompose By Verification Boundary · ariaxhan bundleSplit 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", "plan the implementation", "where do I start". A unit of work is the smallest change with its own gate; if you cannot name the gate for a piece, the piece is too big. Produces an ordered plan where every unit lands green before the next starts.