Claude Skills by thedixitjain

Hyperflow ship phase. Use when the user is ready to release — verbs like ship, push, release, deploy, \"cut a release\", \"ready to push\". Runs pre-push gates (lint + typecheck + build + tests + security sweep), then asks before pushing. Never --no-verify, never force-push to main.

Hyperflow execution phase. Use when a task file exists in .hyperflow/tasks/ and the work needs building — verbs like build, implement, add, refactor, \"wire up\", \"run the plan\", \"execute the task\". Works batches sequentially with self-review and per-task commits. In Antigravity there is no sub-agent fan-out — the single agent does each batch itself.

Hyperflow planning phase. Use when a request needs shaping before code — a rough prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. Verbs like plan, design, brainstorm, explore, \"should we\", \"what's the best way to\", scope, decompose, \"plan out\", \"break down\", \"enhance this prompt\". Thinking, not building. Writes an optional spec to .hyperflow/specs/<slug>.md and a task file to .hyperflow/tasks/<slug>.md, then hands off to hyperflow-dispatch.

Hyperflow project setup. Use when starting hyperflow in a new project or refreshing its cache — \"init hyperflow\", \"set up hyperflow\", \"refresh hyperflow\", \"scaffold hyperflow\". One-shot setup of the .hyperflow/ project cache + memory and the .agent/workflows/hyperflow* slash commands. Does not start the plan → dispatch chain.

Hyperflow project status. Use to see current hyperflow state — \"what is hyperflow doing\", \"show task progress\", \"where are we\". Read-only — reports in-flight tasks, memory count, and progress. Never modifies state or runs work.

Hyperflow auto-routing mode. Use to control how aggressively hyperflow auto-routes — \"make hyperflow sticky\", \"stop using hyperflow\", \"auto-route to hyperflow\", \"disable hyperflow auto-routing\". Sets on (every task-shaped message routes) / auto (intent-verb messages route — default) / off (no auto-routing).

Hyperflow debugging. Use for bugs, test failures, runtime errors, broken builds, or \"this doesn't work\" reports — verbs like debug, \"fix it\", solve, \"why is X failing\", \"Y is broken\", or a pasted stack trace. Systematic root-cause analysis before any patch — never blind-patch symptoms.

| Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, or another single-agent surface. Auto-invoke for non-trivial engineering work: build, implement, add, refactor, debug, fix, review, audit, plan, scope, design, brainstorm, ship, or deploy. Trigger with /hyperflow:hyperflow, \"use hyperflow\", \"apply the doctrine\", or automatically on any task-shaped message.

'ADHD-friendly output formatting for Claude Code. Restructures responses with evidence-based cognitive accessibility: chunking, visual hierarchy, front-loaded key points, and progressive disclosure. Three modes: clean, flow (default), zen. Use when user says \"hyperfocus\", \"focus mode\", \"adhd mode\", \"adhd friendly\", or invokes /hyperfocus. '

Adversarial multi-agent planning skill for omo-senpi. Self-orchestrates a 5-member hostile team (categories unspecified-low, unspecified-high, deep, ultrabrain, artistry) via the native lead team tools for ruthless cross-critique debate, distills only the insights that survive the attacks, then MANDATORILY hands the distilled bundle to a planner task (load_skills ulw-plan) for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, ...

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

Use when preparing an accepted IEEE ICSME paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran two-column format and page budget, the IEEE eCopyright form, integrating the reviewer-required and author-response changes without scope creep, permanentizing data-availability links, and the ROSE-Festival artifact handoff.

Generate evidenced opportunities or

| Implementation tracking documents for maintaining living records of what was built, what is pending, what failed, and what dead ends were explored. Covers the full tracking document template, dead ends prevention, cross-iteration continuity, spec compaction, and inter-session feedback protocol. Trigger phrases: \"implementation tracking\", \"track progress\", \"session tracking\", \"what did the agent do\", \"dead ends\", \"failed approaches\"

Execute one bounded RED to GREEN experiment

Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.

Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.

Implements a feature from its specification. Reads the spec, designs architecture, writes code and tests. Delegates to the Forja (Dev) agent.

Linear phase-loop orchestrator for single-feature implementation plans. Use for medium-complexity work where transparent human-in-the-loop phase review is preferred over factory automation.

Implementation agent that executes a single task and creates handoff on completion

Harness-agnostic version of `/implement`. Drives a single workshop ticket through the SWE→Tester loop in ONE conversation, with the role prompts bundled as `agents/software-engineer.md` and `agents/tester.md` instead of being launched as subagents. Resolves the ticket from `implement_yourself/tasks/`, creates an `implementing/from-scratch` branch (a fixed default — not derived from the ticket; subsequent tickets stack on top), adopts the software-engineer role to implement, then switches to t...

Drive a single workshop ticket through the inner SWE↔Tester loop. Resolves the ticket from `implement_yourself/tasks/`, creates an `implementing/from-scratch` branch (a fixed default — not derived from the ticket; subsequent tickets stack on top), launches the software-engineer agent to implement it, then routes by archetype — Tester runs on logic tickets, orchestrator spot-checks the SWE's AC walk on glue/bootstrap tickets, fast-path file existence check on docs tickets (Tester HARD-OFF). Lo...

'Implements endpoint Data Loss Prevention (DLP) controls to detect and prevent sensitive data exfiltration through email, USB, cloud storage, and printing. Use when deploying DLP agents, creating content inspection policies, or preventing unauthorized data movement from endpoints. Activates for requests involving DLP, data exfiltration prevention, content inspection, or sensitive data protection on endpoints. '

'This skill covers implementing Open Policy Agent (OPA) and Gatekeeper for policy-as-code enforcement in Kubernetes and CI/CD pipelines. It addresses writing Rego policies, deploying OPA Gatekeeper as a Kubernetes admission controller, testing policies in development, and integrating policy evaluation into deployment pipelines. '

Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to \"improve the animations\", \"audit the motion\", \"make this app feel better\", or wants a roadmap of animation fixes rather than a review of a single diff.

Audit and improve an entire agentic-development setup, including skills, context, memory, tools, models, permissions, hooks, workflow habits, and secrets hygiene. Invoke for setup reviews, workflow grading, Goblin Mode, or questions about what to improve. Supports shallow, deep, ultra, and yolo modes. Use domain-specific skills for a single model, report, or tenant.

Equips sellers with macro industry trends by analyzing trending data and specific analyst/competitor channels.

Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).

Initialize team config for a project. Creates .agenteam/config.yaml (or legacy agenteam.yaml) and generates .codex/agents/*.toml.

Set up docflow in a repo with no docs yet: scaffold the docs tree, write docflow.json, add agent guidance. Use when asked to \"set up docflow\", \"initialize docs\", \"scaffold docs\", or \"make this repo use docflow\".

First-time Archcore setup. Detects repo scale and shape, then composes a full first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm, plus host wiring (MCP config, hooks, CLAUDE.md/AGENTS.md managed block). Imports agent-instruction files — aggregate files (CLAUDE.md/AGENTS.md/.cursorrules) as link stubs, modular rule fil...

Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to \"write a case study\", \"document a customer success story\", \"create social proof content\", or \"write about how [customer] uses the product\".

Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to \"audit our content\", \"what's our SEO state\", \"where are the content gaps\", or before designing a content strategy.

Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar.

Automate Insighto AI tasks via Rube MCP (Composio). Always search tools first for current schemas.

> Install or update the M365 Agents Toolkit (ATK) CLI and VS Code extension. Triggers: \"install atk\", \"update atk\", \"install agents toolkit\", \"update agents toolkit\", \"install the toolkit\", \"setup atk\", \"get atk\", \"install atk cli\", \"install atk extension\", \"install atk vsix\", \"update the vs code extension\", \"install latest atk\", \"upgrade atk\"

Route tasks via the 3-tier model selector and learned patterns; emits a routing rationale via hooks_explain

Publish or fetch learned patterns across projects via IPFS (Pinata) -- the cross-project pattern transfer that hooks_transfer enables

Use when targeting International Conference on Autonomous Agents and Multiagent Systems (AAMAS) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for agents and multiagent systems.

Decode an international (non-US) VIN using the CarsXE API. Use this when a user provides a VIN from a European, Asian, or other non-US vehicle and wants to decode it.

Use when building the theoretical argument of an International Organization (IO) manuscript into a generalizable theory of international politics — whether rationalist/formal (bargaining, signaling, delegation, cooperation), constructivist/ideational, or empirical with explicit international mechanisms. IO rewards a portable IR theory over a bare finding. Structures the argument; it does not run analyses.

Register a Cognitum Seed device by endpoint and establish agent bridge

Use when preparing an accepted IPSN-lineage paper for camera-ready, covering de-anonymization, the ACM Primary Article Template and the dual ACM/IEEE metadata (CCS concepts, ORCID, DOI, IEEE PDF eXpress/e-copyright), integrating required changes without scope creep, permanentizing dataset/firmware links, and the artifact-award handoff.

Design background Data Atlas style agents for Itô basket research, market discovery, parameter drafting, and human-in-the-loop editing. Use for architecture and workflow planning, not live order execution.

Tinder for your Claude Code skills. Reviews a sorted deck of every installed skill and lets you swipe keep / delete / skip on each one. Use when the user wants to bulk-clean their skill collection, triage unused skills, or do interactive skill cleanup. Trigger with '/janitor-swipe'.

| Behavioral guardrails for Cavekit agents. Four principles — think before coding, simplicity first, surgical changes, goal-driven execution — that prevent over-engineering, silent assumptions, scope creep, and unfocused work. Every task-builder, reviewer, planner, and inspector must internalize these before writing a single line. Trigger phrases: \"guardrails\", \"karpathy\", \"scope creep\", \"over-engineering\", \"stop adding features\", \"surgical fix\".

Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to \"grow existing customers\", \"increase NRR\", \"design upsell\", or \"how do we get customers to expand\".

Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to \"build health scoring\", \"how do we predict churn\", \"what signals indicate a customer is at risk\", or \"design our health model\".

Write churn prevention and win-back playbooks — risk intervention sequences, save conversation guides, and win-back email campaigns. Use when asked to \"prevent churn\", \"save at-risk customers\", \"win back churned customers\", or \"build a save play\".