Delegate a bounded task from a Codex session to a Fable-powered Cursor Agent in the same Herdr workspace, then wait for and collect the result. Use when Codex should bring in Fable for an independent read-only review or make Fable the sole writer for an implementation while Codex pauses and reviews afterward. Trigger…
Delegate a bounded task from a Codex session to Grok 4.6 with xhigh reasoning in the same Herdr workspace, then wait for and collect the result. Use when Codex should ask Grok for a strong independent opinion, read-only review, architecture or debugging analysis, second opinion, or explicitly authorized…
Delegate a bounded task from a Codex session to GPT-5.6 Sol in the same Herdr workspace, then wait for and collect the result. In review mode, require Sol to use parallel GPT-5.6 Terra subagents with medium reasoning for read-only context gathering before Sol makes the final judgment. Use for requests such as "ask…
Build, critique, and iterate high-converting marketing or product landing pages using React + Vite + TypeScript + Tailwind and shadcn/ui components, with all icons sourced from Iconify. Use when the user asks for a landing page, sales page, signup page, CRO improvements, above-the-fold vs below-the-fold structure…
Live-test any Electron desktop app with native-devtools-mcp, Chrome DevTools Protocol, screenshots, OCR, and accessibility tools. Use when the user asks for Electron UI verification, MCP-driven app control, renderer CDP interaction, native desktop automation, screenshots, or OCR-driven checks.
Determine runtime owner, first-fix layer, and canonical long-term module or package owner in layered codebases. Use when placing code across UI vs platform shell vs runtime orchestration vs domain or application vs shared core vs adapter or integration layers, debugging ownership issues, removing duplicate policy…
Turn complex, technical, ambiguous, or verbose material into clear language without losing important detail. Use when the user asks to simplify an answer, identify what matters, compare options, recommend an action, or make the next step explicit.
Decide where durable test coverage belongs and clean up temporary test probes. Use while testing a bug fix or architectural change, or before finishing work that added tests, fixtures, snapshots, diagnostics, or temporary assertions. Select one owning layer, reuse canonical suites, merge unique signal, and remove…
Find duplicate ownership, hidden second sources of truth, and contract drift in layered codebases. Use when reviewing normalization, validation, defaulting, canonicalization, persistence mapping, runtime-vs-durable state, duplicated helpers, query or cache ownership, or any "who owns this rule?" architecture question.…
Enforce a hard-cut cleanup policy: keep one canonical implementation and delete compatibility, migration, fallback, adapter, coercion, and dual-shape code. Use for pre-release or internal-draft refactors where the goal is one final shape, especially when changing schemas, contracts, persisted state, routing…
Performs root-cause-first debugging and review by tracing expected behavior to the first unintended side effect before changing contracts, parsing, or types. Use when debugging protocol errors, deserialization failures, null payloads, missing fields, restore or hydration issues, state-ownership bugs, unexpected…
Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents. Use when a user asks for GitHub reference projects, examples, prior art, inspiration, implementation patterns, or includes "$search-context" in a coding prompt.
Concise git workspace snapshot for the current directory. Use when asked to show current branch, cwd, repo root, whether the current directory is a worktree, local dirty status, or whether other worktrees have uncommitted changes.
Run local Go health checks (tests, coverage, lint) in Go repositories that contain go.mod/go.sum. Use when the user asks to run or interpret local Go test/coverage/lint workflows using tools like lazygotest, gocovsh, tparse, and golangci-lint. Do not use for Rust or non-Go projects.
Run a reusable JavaScript supply-chain security baseline with pnpm-first hardening, release-age gating, lifecycle-script controls, exotic dependency checks, CI install checks, and optional incident IOC profiles.
Run or install repo security leak checks with BetterLeaks and Trivy. Use when asked to scan for leaked secrets, vulnerable dependencies, misconfigurations, add secret-leak guardrails, add BetterLeaks, add forbidden-path hooks, or run secleak-check before release.
Run shellcheck on shell scripts after editing scripts or when debugging shell errors. Use for linting scripts in a repo (especially scripts/), catching issues like set -u with unset vars, bad subshell usage, or quoting mistakes.
Use this skill when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification package for coding agents. Creates PRD/product spec, UX flows, design system brief, technical architecture, ADRs…
Use Claude Code directly from Astra's current task to design or implement UI/UX and frontend work, with Astra owning sequencing, review, and integration. Use when the user invokes $claude-designer or requests this workflow.
Have Codex review a feature or change from Claude Code, then let Claude address the findings and request verification. Use for an independent review of implementation, acceptance criteria, architecture, or UI evidence while Claude remains the implementer.
Apply focused code-quality checks when implementing or reviewing behavioral changes. Use for maintainability, framework fit, data safety and meaningful verification; not visual design or a full security audit.
Right-size CI from measured run data instead of stacking pipeline mechanics. Use when CI is slow, expensive, flaky, or runs too often; when the user asks to clean up, speed up, split, or reduce GitHub Actions, GitLab CI, or other pipelines; when reviewing a CI proposal for over-engineering; and before you yourself add…
Status report for a user running several coding agents. MUST read this file before answering whenever a message is or contains "/sitrep", "$sitrep" or "sitrep", also mid-turn. Shows what needs the user's answer first (numbered, self-contained options, recommendation), then product map, active work and blockers.
★not rated 139 todayA68 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: