Run work in an isolated workspace: git worktree + devcontainer, driven through the fr isolation CLI (exec-bridge). Use when feature work must not touch the base repo, when fr-brainstorming or fr-goal needs a workspace, when the operator says "isolate this" / "run it in the container", or to clean up after a merged PR.…
Multi-agent deep research on Codex. Use for questions that need many sources and a written, fully-cited report — "research X", "deep dive on X", "compare X vs Y", "should I adopt / build on X". Breaks the question into independent strands, spawns researcher subagents in parallel, triangulates the evidence, synthesizes…
Standing session rules that must be loaded at the start of every session, before any other work. Covers the quality bar (never trade correctness for token savings), the total ban on em-dashes, the useEffect ban, the comment policy, and per-commit/per-push authorization. After loading, wait for the user's actual…
Review the current diff against path-scoped rules (secrets, RLS/tenant scoping, Stripe webhook verification, input validation, scope), flag changed code lacking tests, and run a quick security pass. Reports findings; nothing auto-fixed without approval.
Enforces risk-based coding profiles, impact mapping, adversarial planning, and strict verification gates before making edits, audits, or structural modifications.
Evidence-driven dissection of an existing service, written plan, or codebase area. Interrogates every entity (table, field, component, endpoint, module, boundary) against ground truth from multiple sources at once, red-teams each verdict devil's-advocate style, and arrives at the minimal-build optimization plan. Runs…
Run boundary and structure validators against a Hydrogen storefront project. Reports cross-module imports, reverse imports from shared layers, dumping-ground folders, barrel files, forbidden Remix imports, and missing/duplicated route manifests.
Use when debugging failures, writing tests, starting multi-step tasks, modifying build systems, integrating APIs, or validating assumptions before heavy execution.
Use when the user wants to design, redesign, build, critique, audit, polish, theme, animate, adapt, or otherwise improve a Flutter app's UI or UX. Covers full apps, screens, widgets, components, forms, onboarding, empty states, navigation, dashboards, and settings. Handles Material 3 theming, Cupertino/iOS adaptation…
Locks in opinionated frontend code patterns for Next.js 16 + TanStack Query v5 + FSD projects. ALWAYS invoke when writing data-fetching code (NEVER useEffect+fetch — always TanStack Query), creating forms (always react-hook-form + zod), introducing client state (Zustand for client-global only — NEVER for server data…
Execute an approved plan or specification with targeted implementation, tests, evidence, review, and independent verification. Use for “implement this”, “execute the plan”, “build this feature”, “write the code”, or “refactor without changing behavior”.
Use when you are spawned as the PM of a simply harness project and your brief references a .simply/LEDGER.md work ledger or this skill. Grants fleet authority, routing doctrine, safe worker lifecycle, and the signal protocol back to the auditor.
Anti-sycophancy protocol (明辨). Use whenever the user contradicts, corrects, or pushes back on one of your conclusions; when you notice you are about to reverse a position mainly because the user insisted; or when a disagreement has run two or more rounds without new evidence. Classifies the dispute (fact / tradeoff /…
Use when the clodex router hands off a run at stage open or plan, when a run the router resumed shows no recorded plan or a plan with no standing approval, or when plan-review findings on such a run still need dispositions before work can start.
Repair and synchronize Codex CLI model catalogs for OpenAI-compatible third-party providers. Use when /model shows stale, missing, duplicated, or nested "All models" entries; reasoning efforts or context windows disagree with upstream; a provider exposes /models but Codex does not refresh it; or modelcatalogjson and…
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
A workflow for splitting a code change into independent tasks and assigning them to multiple command-line AI coding agents. Each agent works in its own Git worktree, an isolated copy of the repository.
Use for configurable, high-rigor app execution across repos. Selects the lightest safe workflow mode from an app profile, creates or uses a slice manifest, and routes product, tracker, code-intelligence, UI/UX, and verification gates without hard-coding one app's rules.
Use when reviewing or writing code that contains Russian-language UI strings, i18n locale files (ru.json, ru.yml, ru.po), Russian comments, or transliterated identifiers (polzovatel, tovar, kolichestvo). Triggers on mixed English-code + Russian-content projects. Does not cover typography, spelling, or ё/е.
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?".
★not rated 1 3mo agoA58 tokens
originalMIT
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: