gannonh
- 112 skills
- 0 followers
- 5 hours ago last updated
- ▌ Coderabbit · gannonhAI-powered code review using CodeRabbit.Trigger for any explicit review request AND autonomously when the agent thinks a review is needed (code/PR/quality/security).
- ▌ Ps Tdd · gannonh bundleUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
- ▌ Ps Principle Experience First · gannonh bundleApply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
- ▌ Ps Principle Never Block On The Human · gannonh bundleApply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
- ▌ Ps Principle Sequence Verifiable Units · gannonh bundleApply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
- ▌ Ps Principle Make Operations Idempotent · gannonh bundleApply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
- ▌ Ps Principle Outcome Oriented Execution · gannonh bundleApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
- ▌ Ps Principle Encode Lessons In Structure · gannonh bundleApply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
- ▌ Ps Principle Redesign From First Principles · gannonh bundleApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
- ▌ Ps Principle Migrate Callers Then Delete Legacy Apis · gannonh bundleApply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
- ▌ Ps Principle Separate Before Serializing Shared State · gannonh bundleApply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
- ▌ Kata Help · gannonh bundleShow available Kata skills, displaying the usage guide, explaining skill reference, or when the user asks for help with Kata. Triggers include "help", "show skills", "list skills", "what skills", "kata skills", and "usage guide".
- ▌ Kata Debug · gannonh bundleSystematically debug issues, investigating bugs, troubleshooting problems, or tracking down errors with persistent state across context resets. Triggers include "debug", "investigate bug", "troubleshoot", "find the problem", "why isn't this working", and "debug session".
- ▌ Kata Doctor · gannonh bundleRun health checks on Kata project structure, detecting and fixing format issues. Triggers include "doctor", "health check", "fix roadmap", "check project", "kata doctor".
- ▌ Kata Add Issue · gannonh bundleCapture an idea, task, or issue that surfaces during a Kata session as a structured issue for later work. This skill creates markdown issue files in the .planning/issues/open directory with relevant metadata and content extracted from the conversation. Triggers include "add issue", "capture issue", "new issue", "create issue", "log issue", "file issue", "add todo" (deprecated), "capture todo" (deprecated), "new todo" (deprecated).
- ▌ Kata Add Phase · gannonh bundleAdd planned work discovered during execution to the end of the current milestone in the roadmap. This skill appends sequential phases to the current milestone's phase list, automatically calculating the next phase number. Triggers include "add phase", "append phase", "new phase", and "create phase". This skill updates ROADMAP.md and STATE.md accordingly.
- ▌ Kata Customize · gannonh bundleManage template overrides for customizing Kata output formats. List available templates, copy defaults for local editing, edit overrides, validate template schemas. Triggers include "customize template", "override template", "edit template", "template overrides", "list templates", "show templates", "template customization", "manage templates", "what templates can I customize", "template schema", "custonmize Kata", "custom config".
- ▌ Kata Whats New · gannonh bundleShow what's new in Kata since the installed version, displaying changelog entries, checking for Kata updates, or reviewing recent changes. Triggers include "what's new", "whats new", "show changes", "changelog", "recent changes", and "what changed".
- ▌ Kata Brainstorm · gannonh bundleRun structured brainstorming sessions using paired explorer/challenger agent teams. Explorers generate ideas, challengers play devil's advocate, and 2-3 rounds of debate produce pressure-tested proposals. Use when brainstorming product ideas, exploring feature directions, evaluating strategic options, generating milestone candidates, or when the user says "brainstorm", "explore ideas", "what should we build next", "generate options", or "run an ideation session".
- ▌ Kata Move Phase · gannonh bundleMove a phase between milestones or reorder phases within a milestone. Triggers include "move phase", "move phase to milestone", "reorder phase", "reorder phases".
- ▌ Kata Pause Work · gannonh bundleCreate a context handoff file, pausing work mid-phase, stopping work temporarily, or creating a checkpoint for session resumption. Triggers include "pause work", "stop work", "create handoff", "save progress", and "pause session".
- ▌ Kata Plan Phase · gannonh bundlePlan detailed roadmap phases. Triggers include "plan phase n", "create phase plan", "create a plan" "roadmap planning", and "roadmap phase creation".
- ▌ Kata New Project · gannonh bundleInitialize a new project with deep context gathering and project.md. Triggers include "new project", "start project", "initialize project", "create project", "begin project", "setup project".
- ▌ Kata Resume Work · gannonh bundleResume work from a previous session, restoring context after a break, continuing work after /clear, or picking up where you left off. Triggers include "resume work", "continue work", "pick up where I left off", "restore context", and "resume session".
- ▌ Kata Set Profile · gannonh bundleSwitch model profile for kata agents (quality/balanced/budget). Triggers include "set profile", "set profile".
- ▌ Kata Verify Work · gannonh bundleValidate built features through conversational testing, running UAT, user acceptance testing, checking if features work, or verifying implementation. Triggers include "verify work", "test features", "UAT", "user testing", "check if it works", and "validate features".
- ▌ Kata Check Issues · gannonh bundleReview open issues, selecting an issue to work on, filtering issues by area, pulling GitHub issues, or deciding what to work on next. Triggers include "check issues", "list issues", "what issues", "open issues", "show issues", "view issues", "select issue to work on", "github issues", "backlog issues", "pull issues", "check todos" (deprecated), "list todos" (deprecated), "pending todos" (deprecated).
- ▌ Kata Insert Phase · gannonh bundleInsert urgent work as a decimal phase between existing phases, adding mid-milestone work, or creating intermediate phases. Triggers include "insert phase", "add urgent phase", "create decimal phase", "insert between phases", and "urgent work".
- ▌ Kata Map Codebase · gannonh bundleAnalyze an existing codebase with parallel mapper agents, creating codebase documentation, understanding brownfield projects, or mapping code structure. Triggers include "map codebase", "analyze codebase", "create project context", "document codebase", "understand code", and "codebase map".
- ▌ Kata Remove Phase · gannonh bundleRemove a future phase from roadmap and renumber subsequent phases. Triggers include "remove phase", "remove phase".
- ▌ Kata Add Milestone · gannonh bundleAdd a milestone to an existing project, starting a new milestone cycle, creating the first milestone after project init, or defining what's next after completing work. Triggers include "add milestone", "new milestone", "start milestone", "create milestone", "first milestone", "next milestone", and "milestone cycle".
- ▌ Kata Discuss Phase · gannonh bundleGather phase context through adaptive questioning before planning, clarifying implementation decisions, or exploring gray areas for a phase. Triggers include "discuss phase", "clarify phase", "gather context", "what are the gray areas", and "phase discussion".
- ▌ Kata Execute Phase · gannonh bundleExecute all plans in a phase with wave-based parallelization, running phase execution, or completing phase work. Triggers include "execute phase", "run phase", "execute plans", "run the phase", and "phase execution".
- ▌ Kata Migrate Phases · gannonh bundle[DEPRECATED] Use /kata-doctor instead. Migrate phase directories to globally sequential numbering. Triggers include "migrate phases", "fix phase numbers", "renumber phases", "phase collision", "fix phase collisions", "fix duplicate phases", "phase numbering migration".
- ▌ Kata Research Phase · gannonh bundleResearch how to implement a phase standalone, investigating implementation approaches before planning, or re-researching after planning is complete. Triggers include "research phase", "investigate phase", "how to implement", "research implementation", and "phase research".
- ▌ Kata Track Progress · gannonh bundleCheck project progress, show context, and route to next action (execute or plan). Triggers include "progress".
- ▌ Kata Audit Milestone · gannonh bundleVerify milestone achievement against its definition of done, checking requirements coverage, cross-phase integration, and end-to-end flows. Triggers include "audit milestone", "verify milestone", "check milestone", and "milestone audit". This skill reads existing phase verification files, aggregates technical debt and gaps, and spawns an integration checker for cross-phase wiring.
- ▌ Kata Complete Milestone · gannonh bundleArchive a completed milestone, preparing for the next version, marking a milestone complete, shipping a version, or wrapping up milestone work. Triggers include "complete milestone", "finish milestone", "archive milestone", "ship version", "mark milestone done", "milestone complete", "release version", "create release", and "ship milestone".
- ▌ Kata Configure Settings · gannonh bundleConfigure kata session settings and workflow variants. Triggers include "settings", "configure", "preferences", "workflow config", "workflow variants".
- ▌ Kata Execute Quick Task · gannonh bundleExecute small ad-hoc tasks with Kata guarantees, running quick tasks without full planning, or handling one-off work outside the roadmap. Triggers include "quick task", "quick mode", "quick fix", "ad-hoc task", "small task", and "one-off task".
- ▌ Kata Plan Milestone Gaps · gannonh bundleCreate phases to close all gaps identified by milestone audit. Triggers include "plan milestone gaps", "plan gaps".
- ▌ Kata Review Pull Requests · gannonh bundleRun a comprehensive pull request review using multiple specialized agents. Each agent focuses on a different aspect of code quality, such as comments, tests, error handling, type design, and general code review. The skill aggregates results and provides a clear action plan for improvements. Triggers include "review PR", "analyze pull request", "code review", and "PR quality check".
- ▌ Kata List Phase Assumptions · gannonh bundleSurface Claude's assumptions about a phase approach before planning, checking what Claude thinks, or validating understanding before planning. Triggers include "list assumptions", "what are you thinking", "show assumptions", "phase assumptions", and "what's the plan".
- ▌ Okf · gannonh bundleCreate, read, and maintain Open Knowledge Format documentation bundles in repositories. Use this skill when the user asks for /okf, OKF, Open Knowledge Format, docs-as-knowledge, reading project context from docs, reorganizing docs into an agent-readable bundle, updating docs/specs/ADRs after a session or PR, or adding AGENTS.md instructions for agents to consume and maintain the docs bundle. Supports /okf read, /okf init, and /okf update workflows.
- ▌ Readme · gannonhWrite or rewrite a project README as plain factual documentation covering what the tool is, how to install and run it, what it touches, and how to undo it. Use when the user asks to create, write, rewrite, improve, or review a README, complains their README is too long, too marketing-heavy, or buries the install instructions, or says "make a README" / "fix my README".
- ▌ Handoff · gannonhCompact the current conversation into a handoff document for another agent to pick up.
- ▌ Finalize · gannonh bundleFinalize the current feature branch by running the `simplify`, `strict-quality-review`, and `/okf update` passes in order, each through its own subagent, automatically accepting in-scope fixes and committing after each phase. Use when the user says finalize, finish this branch, prep for PR, polish and review, run final cleanup, or asks to combine `/simplify`, `/strict-quality-review`, and OKF documentation updates before shipping.
- ▌ Simplify · gannonhSimplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
- ▌ Babysit Pr · gannonh bundleBabysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
- ▌ Thermo Run · gannonhLaunch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.
- ▌ Auto Review · gannonh bundleStructured code review closeout. Codex review is the default when no engine is set and is the recommended reviewer. Use this for auto-review, autoreview, second-model review, CodeRabbit, Greptile, Cursor, Codex review, Claude review, PR review, and final quality/security review requests.
- ▌ Kata Linear · gannonhLinear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers include, start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion.
- ▌ Orchestrate · gannonhAct as the lead orchestrator for complex coding work. Use this skill when the user asks to orchestrate, delegate, run agents or workers, fan out work, use parallel agents, coordinate sub-agents, dispatch cloud agents, create worktrees, execute a broad plan, verify a feature, or manage multi-step implementation where independent investigation, implementation, review, or verification could improve speed, quality, or confidence. Prefer this skill for substantial cross-file or acceptance-gated work even when the user does not explicitly say "orchestrate".
- ▌ Update Docs · gannonhRepo-wide documentation sweep for updating project docs, context, ADRs, diagrams, README files, agent instructions, and documentation sites after feature work, decisions, or direction changes. Use this skill whenever the user asks to update docs, refresh documentation, prepare for PR, finish a branch, merge, ship, close out work, record what changed, or align docs with code. It first discovers the repo's key Markdown documentation and docs sites, ignores historical archives by default, presents the proposed docs plan for approval, then updates only the approved docs surgically.
- ▌ Codex Review · gannonhCodex code review closeout: local dirty changes, PR branch vs main, parallel tests.
- ▌ Fix Github CI · gannonh bundleUse when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Trigger words include: 'fix CI', 'debug GitHub Actions', 'gh pr checks', 'CI is red', 'GitHub Actions failed', 'fix the build', and similar phrases indicating a need to investigate and resolve CI failures in a GitHub-hosted repository.
- ▌ Pull Requests · gannonh bundleUse this skill for pull request workflows - creating PRs (branch, commit, push, open), reviewing PRs (code quality, test coverage, issue fixing), addressing PR review comments (fix feedback, respond to reviewers), or merging PRs (CI checks, merge, cleanup). Handles the complete PR lifecycle via gh CLI. Triggers include "create PR", "open PR", "review PR", "merge PR", "address PR comments", "fix review feedback", "respond to reviewer", "push for review", "submit PR".
- ▌ Herdr Delegate · gannonhUse this skill when the user asks to delegate work to worker agents in named Herdr panes.
- ▌ Upstream Assess · gannonh bundleAssess and selectively port changes from the upstream T3 Code fork (pingdotgg/t3code) into Kata Code. Use whenever the user wants to review what upstream has done, assess the diff, decide what to bring in, triage upstream commits, plan a vendor-pull, run an upstream scan, or figure out which upstream changes are worth porting. Covers scanning upstream since the last baseline, grouping commits by effort and risk, recommending Port/Skip/Watch per change, and re-implementing chosen changes as fork-original commits with Kata branding applied from the start.
- ▌ User Acceptance · gannonh bundleUse when finishing a ticket, feature branch, or pull request and the user asks to validate, demo, verify, sign off, show that it works, run UAT, provide acceptance evidence, or decide whether work is ready to merge. This skill gathers tangible evidence that completed work functions as intended, with videos, screenshots, terminal recordings, JSON responses, output files, logs, and a concise human test guide. Use for web apps, CLI and TUI apps, APIs and SDKs, and native apps including Electron-type apps. Trigger on phrases like "UAT", "verify", "show me it works", "demo this", "walk me through", "ready to merge", "can we merge?", "acceptance test", "validate the changes", "sign off", or any request for proof that a feature branch or PR works.
- ▌ Interrogate Plan · gannonh bundleInterrogation session that challenges a spec or plan against the codebase and existing domain model, sharpens terminology, and updates the plan and project context (CONTEXT.md, AGENTS.md, README.md, ADRs) inline as decisions crystallise. Use when the maintainer wants to stress-test a plan against their project's language and documented decisions.
- ▌ Agents Md Improver · gannonh bundleAudit and improve AGENTS.md files in repositories. Use when user asks to check, audit, update, improve, or fix AGENTS.md files. Scans for all AGENTS.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "AGENTS.md maintenance" or "project memory optimization".
- ▌ Address Pr Comments · gannonh bundleHelp address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
- ▌
- ▌ Ps How · gannonh bundleUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.
- ▌ Ps Why · gannonh bundleUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
- ▌ Kata Code E2e Testing · gannonhAuthor local Playwright Electron E2E tests for Kata Code using the reusable harness and Kata-specific flows. Use when adding or updating tests under e2e/.
- ▌ Strict Quality Review · gannonhRun a strict maintainability review with parallel adversarial subagents for abstraction quality, giant files, and spaghetti-condition growth. Use for a strict quality review, deep code quality audit, or especially strict maintainability review.
- ▌ Ps Arena · gannonh bundleSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for ps-arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
- ▌ Ps Swarm · gannonh bundleFan out N parallel workers, drain them, and return one report. Use for ps-swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
- ▌ Ps Teach · gannonh bundleExplain a body of work plainly so a person actually understands it. Runs the `ps-how` and `ps-why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
- ▌ Agent Native Hardening · gannonh bundleTypeScript/JavaScript codebase hardening: maintainability, code quality, architecture cleanup, repo scoring, agent-friendly structure, godfiles, feature folders, DRY, type safety, traversability, feedback loops, worktrees, subagents, swarm refactors.
- ▌ Auditing Accessibility · gannonh bundleComprehensive accessibility audit for iOS/macOS apps - VoiceOver, Dynamic Type, color contrast, touch targets, keyboard navigation, Reduce Motion, and App Store Review preparation
- ▌ Mobile E2e Test Author · gannonhAuthor local Maestro iOS-Simulator E2E flows for the Kata Code mobile app using the reusable TS orchestrator and Kata-specific flows. Use when adding or updating flows under mobile-e2e/.
- ▌ Writing IOS Unit Tests · gannonh bundleUse this skill when writing iOS unit tests, debugging test failures, creating Swift Testing tests, testing SwiftData models, or when the user asks to add tests, fix tests, improve coverage, or test Swift code. Covers Swift Testing framework, ModelContainer lifecycle, and coverage requirements.
- ▌ Ps Recall · gannonh bundleReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
- ▌
- ▌ Ps Reflect · gannonh bundleSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- ▌ Automating IOS Simulator · gannonh bundleUse this skill when the user asks to run an iOS app, launch an app in the simulator, tap or click buttons, interact with simulator UI, automate iOS testing, take screenshots, enter text in fields, swipe or scroll, check accessibility, or perform any iOS simulator interaction. Covers app launching, UI navigation, gestures, form input, and simulator lifecycle management.
- ▌ Ps Architect · gannonh bundleSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for ps-architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
- ▌ Ps Automate Me · gannonh bundleUse for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.
- ▌ Ps Interrogate · gannonh bundleUse for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
- ▌
- ▌ Ps No Comments · gannonh bundleSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- ▌ Ps Poteto Mode · gannonh bundlepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, ps-poteto-mode, or requests to work in this style.
- ▌ Ps Blast Radius · gannonh bundleFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
- ▌ Ps Setup Pstack · gannonh bundleConfigure P-Stack for Pi, Codex, Cursor, OpenCode, and Claude Code. Use when installing P-Stack, choosing its small, medium, and large models, setting reasoning levels, adding harness adapters, or refreshing model identifiers.
- ▌ Auditing App Store Compliance · gannonh bundleComprehensive App Store compliance audit covering all 5 Apple guideline categories (Safety, Performance, Business, Design, Legal) with mandatory GitHub issue output
- ▌ Ps Figure It Out · gannonh bundleDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for ps-figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
- ▌ Collecting Testflight Feedback · gannonhUse this skill when collecting TestFlight feedback, gathering beta tester screenshots, reviewing App Store Connect feedback, or when the user asks to collect TestFlight comments, compile beta feedback, or create a feedback report. Creates consolidated markdown reports from App Store Connect.
- ▌ Ps Show Me Your Work · gannonh bundleKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for ps-show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
- ▌ Ps Technical Writing · gannonh bundleLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for ps-technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
- ▌ Validate Kata Code Nightly Release · gannonh bundleValidate Kata Code nightly releases on macOS with the @Computer plugin. Start and update the nightly app, use its New Project flow to create a timestamp-suffixed nightly UAT project under `/Volumes/EVO/dev`, then execute explicit acceptance criteria for a Codex GPT-5.4-Mini chat, Browser and Files panels, and git commit flow; capture criterion-level screenshots and write an evidence-linked report in the created project. Use when validating or documenting the Kata Code nightly release flow.
- ▌ Ps Principle Prove It Works · gannonh bundleApply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
- ▌ Ps Create Verification Skill · gannonh bundleGenerate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for ps-create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
- ▌ Ps Principle Build The Lever · gannonh bundleApply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
- ▌ Ps Principle Fix Root Causes · gannonh bundleApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
- ▌ Ps Typescript Best Practices · gannonh bundleTypeScript best practices. Use when reading or editing any .ts or .tsx file.
- ▌ Ps Principle Model The Domain · gannonh bundleApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
- ▌ Ps Maintain Verification Skill · gannonh bundlePeriodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for ps-maintain-verification-skill or "audit the verify skill".