Audit designs against 19 rules across Figma files and code (HTML/CSS/React/Vue/Tailwind). Auto-detects framework and design system (MUI, Chakra, shadcn/ui, Ant Design, Radix, Bootstrap). Runs code superpowers across all 19 categories: aria, focus, contrast, tokens, responsive, motion, forms, navigation, spacing…
Learn how a GitHub user reviews code from up to a year of their real review comments, then review a change as that person — in chat only, never posted to GitHub. Invoked bare, it ensures the profile exists and is current, then immediately reviews. Use when the user asks to "review this as me" or "like me", asks what a…
A Japanese-language repository audit skill that checks software against the IEEE-CS/ACM Software Engineering Code of Ethics and against deceptive interface patterns. An audit is a documented inspection based on evidence.
Evaluate whether AdCP (Ad Context Protocol, agenticadvertising.org) — or a concrete AdCP implementation such as a seller agent, buyer agent, or orchestrator — is safe, interoperable, operationally viable, and ready for pilot or production use. Combines a weighted decision scorecard, hard safety gates that override any…
Channel operator (IRC handle @techlead) for the mARC agent team. Compiles chat demands into ready-to-execute work, records them on the GitHub Project board/Issues, and dispatches to specialists (@dev, @sre, @design, @sec, @rev, @research). Invoke with /tech-lead to turn discussion into tracked, delegated tasks.
Guide for using openlens to review code. Triggers on: "review my code", "check for bugs", "security scan", "run openlens", "set up code review", "openlens".
Root-cause analysis and QA review for a PR, branch, or stack trace. Detects bugfix vs feature, then for a bugfix finds the commit that introduced the bug (the suspect set, via git blame/log), the bug's life story (intent, releases it shipped in, hotspot recurrence, fix completeness), and explains why it broke; for a…
Run a structured codebase audit — map architecture, assess health (compliance / tests / docs), perform deep analysis (security / performance / code quality), and synthesize a prioritized roadmap. Use this skill when the user says things like 'audit the codebase', 'understand this project', 'find problems', '/audit'…
Use when the user explicitly asks to compare or reuse lessons across projects, inspect another project's documented history, or refresh/rebuild the shared expmemory.md cache. Also use when ADD requests an approved global-cache refresh after project finalization. Do not use for ordinary coding, small changes, or…
Turn exact or picked GitHub issues into independently reviewed draft PRs using isolated Ponytail developers and reviewers. Use for issue-to-PR runs, picked batches, or continuation; batches default to parallel.
A diagram-making workflow that turns confirmed process, architecture, and data-flow descriptions into animated, looping GIFs. It uses SVG as an intermediate format and checks the rendered result before delivery.
Generate and incrementally maintain an interactive architecture map plus a per-module code-quality audit (health scores 0-100, smell findings, lines-of-code, and a clickable dependency graph) for any codebase. Use when the user wants to visualize a project's functional modules, audit or score code quality, check…
A method for reviewing code, bugs, diffs, branches, and pull requests. A diff is the set of changes between two versions of code, and a pull request is a proposed change submitted for review.
Pre-production code review against a user-chosen healthy point. Use whenever a user wants to review a branch before shipping, asks if code is ready to merge, wants blockers identified before a PR lands.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Use when reviewing code for Clean Code, DDD, Harness Engineering, or Agentic Engineering issues. Covers readability, maintainability, testability, observability, and AI-agent guardrails.
Compare current code changes against a PRD to find gaps, deviations, and opportunities. Use before opening a PR, after finishing a feature, or to verify requirement coverage.
Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language. Use this whenever the user asks to write clean code, follow clean-code principles, refactor for clarity, improve naming, reduce complexity or duplication, separate concerns, tighten error handling, work…
Run a bounded SPEC → BUILD → REVIEW → REPAIR workflow until verified or blocked. Explicit invocation only: $specloop in Codex or /specloop in Claude Code.
★not rated 6▲
+2
changed 3d agoA43 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: