Explore skills
Showing 31951–31980 of 77079 skills
一键生成 PageObject + 配套测试。触发:新增页面、生成页面、gen page、create page、添加页面对象。
DanielSuo117/velocitai
Stars: 158Claude CodeCodex替换占位定位符为真实选择器(六级优先级)。触发:替换定位符、locator、selector、定位失败、元素找不到、DOM 分析。
DanielSuo117/velocitai
Stars: 158Claude CodeCodexis_page_loaded() 四种验证模式与调用层级。触发:页面断言、is_page_loaded、page loaded、页面加载验证。
DanielSuo117/velocitai
Stars: 158Claude CodeCodex表单保存后验证(Toast / 重定向 / 数据对比 / 富文本清空)。触发:保存验证、toast、重定向检测、Meta+A、保存成功判断。
DanielSuo117/velocitai
Stars: 158Claude CodeCodex复核运行期自愈提案并写回 PageObject。触发:选择器失效、定位符漂移、自愈提案、proposals.jsonl、用例误报不通过。
DanielSuo117/velocitai
Stars: 158Claude CodeCodex运行 pytest + 结构化分析失败原因。触发:运行测试、跑测试、run test、pytest、失败分析、allure。
DanielSuo117/velocitai
Stars: 158Claude CodeCodexAsk which skill or flow fits your situation. A router over the skills in this repo.
JesusFilm/core
Stars: 24Claude CodeCodexReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
JesusFilm/core
Stars: 24Claude CodeCodexDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
JesusFilm/core
Stars: 24Claude CodeCodexScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
JesusFilm/core
Stars: 24Claude CodeCodexBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
JesusFilm/core
Stars: 24Claude CodeCodexTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
JesusFilm/core
Stars: 24Claude CodeCodexTeach the user a new skill or concept, within this workspace.
JesusFilm/core
Stars: 24Claude CodeCodexTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
JesusFilm/core
Stars: 24Claude CodeCodexBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
JesusFilm/core
Stars: 24Claude CodeCodexReference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
JesusFilm/core
Stars: 24Claude CodeCodexUse when auditing a user-facing app — web, mobile (iOS/Android/React Native/Flutter), desktop, CLI, or games — for accessibility barriers or WCAG 2.2 conformance, before shipping UI changes, or in response to concerns about screen-reader, keyboard, low-vision, motor, cognitive, or photosensitive users. Not for general bug hunting or code correctness.
Ovid/paad
Stars: 154Claude CodeCodexUse when assessing the architectural health of a codebase — before a major refactor, when onboarding to an unfamiliar repo, after rapid growth, when planning a redesign, or to surface structural strengths and risks before they become expensive. Not for fixing what it finds, and not for reviewing a branch diff.
Ovid/paad
Stars: 154Claude CodeCodexEXPERIMENTAL. Use when looking for meaningfully duplicated logic in a codebase, especially duplicate behavior hidden behind different names, different syntax, different control flow, or independently evolved implementations. Not for style issues, not for syntactic clone detection, and not for fixing what it finds.
Ovid/paad
Stars: 154Claude CodeCodexEXPERIMENTAL. Use when code needs a security review against the OWASP Top 10:2025 — access control, misconfiguration, supply chain, cryptography, injection, insecure design, authentication, integrity, logging and alerting, and mishandled exceptional conditions. Not for penetration testing a running system, not for infrastructure-only scanning, and not for fixing what it finds.
Ovid/paad
Stars: 154Claude CodeCodexUse when reviewing current branch for bugs before pushing or merging, when wanting a thorough multi-agent review of local changes, or when preparing work for human review. Not for codebase structure, not for code style, and not for fixing what it finds.
Ovid/paad
Stars: 154Claude CodeCodexUse when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope creep, or design drift between intent and action documents. Needs both documents; not for checking code against a spec.
Ovid/paad
Stars: 154Claude CodeCodexEXPERIMENTAL. Use when working the project-wide out-of-scope backlog at .reviews/code/backlog.md and .reviews/security/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is the agentic-review skill — and not for reviewing a branch diff.
Ovid/paad
Stars: 154Claude CodeCodexUse when working through architectural flaws documented in a .reviews/architecture/ report — selecting which flaws to fix, resuming a partial fix session across multiple sittings, or applying structural changes that need to be tracked back to a report. Not for producing that report — run the agentic-architecture skill first if there isn't one.
Ovid/paad
Stars: 154Claude CodeCodexUse when a session is running out of context and the work needs to continue in a fresh one, or when starting a session meant to pick up where an earlier one stopped. Not for compacting in place — that is /compact — and not for specifying work that has not started, which is a plan.
Ovid/paad
Stars: 154Claude CodeCodexUse when reviewing a spec, PRD, requirements doc, or design plan before implementation begins — especially when the doc feels too big, bundles unrelated features, may contradict the current codebase, or seems vague, infeasible, or thin on security and error handling. Not for cross-checking a spec against a plan — that's the alignment skill.
Ovid/paad
Stars: 154Claude CodeCodexUse when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is the pushback skill.
Ovid/paad
Stars: 154Claude CodeCodexAnalyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.
Ovid/paad
Stars: 154Claude CodeCodexUse when making a small, quick change — a bug fix, typo, minor feature, tweak, or anything the user calls "vibe coding" — that looks like 1-3 files in the same module
Ovid/paad
Stars: 154Claude CodeCodexInteractive logo & brand design strategist. Runs a strategy workshop, narrows a creative direction, lands a single centralized concept, then outputs a condensed branding table plus 10+ logo ideas with rationale. Use when the user wants to design a logo, develop a brand identity, write a logo brief, brainstorm logo concepts, or run brand strategy before sketching. Triggers include "design a logo", "logo ideas", "brand identity", "help me with my logo", "logo brief", "what should my logo be".
posva/dotfiles
Stars: 16Claude CodeCodex