Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 39241–39270 of 53857 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| saas-test-flakinessBasinfy/Basinfy-SaaS-StudioFind flaky tests from CI logs — aggregates pass rates, spots intermittent failures, recommends quarantine. After multiple runs. | Stars: 12 | Updated | Claude CodeCodex | Unverified | Install |
| saas-test-helpersBasinfy/Basinfy-SaaS-StudioGenerate stack-specific test helper libraries — assertion utilities, mock session factories, API test clients in tests/helpers/. Reduces test boilerplate. | Stars: 12 | Updated | Claude CodeCodex | Unverified | Install |
| saas-test-setupBasinfy/Basinfy-SaaS-StudioScaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint. | Stars: 12 | Updated | Claude CodeCodex | Unverified | Install |
| saas-usability-testBasinfy/Basinfy-SaaS-StudioStructured usability test report template, or turn existing usability test notes into structured feedback. | Stars: 12 | Updated | Claude CodeCodex | Unverified | Install |
| saas-ux-designBasinfy/Basinfy-SaaS-StudioSection-by-section UX spec authoring for a screen, flow or App Shell. Reads the customer journey to provide context; also project-wide accessibility. | Stars: 12 | Updated | Claude CodeCodex | Unverified | Install |
| saas-ux-reviewBasinfy/Basinfy-SaaS-StudioValidate a UX spec, App Shell design or pattern library — accessibility, PRD alignment, readiness. APPROVED / NOT ASSESSED / NEEDS REVISION / MAJOR REVISION NEEDED. | Stars: 12 | Updated | Claude CodeCodex | Unverified | Install |
| saas-vertical-sliceBasinfy/Basinfy-SaaS-StudioPre-production validation — end-to-end build to confirm the full loop is achievable before committing to Production. After PRDs, architecture, UX specs. | Stars: 12 | Updated | Claude CodeCodex | Unverified | Install |
| adversarial-reviewnledford/engineering-review-boardSkeptically verify completed changes, agent work, merge readiness, and hidden regressions. Use after implementation when claims need independent proof; do not use as the primary implementation or ordinary code-review workflow. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| api-designnledford/engineering-review-boardAPI design and contract guidance. Use when defining, changing, reviewing, or testing service or public interface contracts: HTTP/REST resources, RPC/GraphQL operations, webhooks, event/message schemas, request/response/error envelopes, pagination/filtering/sorting, idempotency, versioning/deprecation/backward compatibility, OpenAPI/AsyncAPI/JSON Schema/protobuf artifacts, SDK or CLI public surfaces, or consumer/provider compatibility. Do not use for ordinary language/framework implementation, Rust handler mechanics, SQL schema/query design, architecture boundary selection, security controls, BDD/TDD mechanics, observability instrumentation, or documentation-only API references after the contract is set; load those existing skills instead or alongside it when their trigger is primary. Use semantic-versioning when the primary question is choosing or applying a patch, minor, or major release bump after contract impact is understood. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| architecture-reviewnledford/engineering-review-boardReview architectural boundaries, dependency direction, ports and adapters, Clean/Onion/Hexagonal/DDD hybrids, and modular monolith structure. Use for architecture-focused audits of existing systems or changes; do not use for ordinary implementation or architecture design without a review request. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| behavior-driven-developmentnledford/engineering-review-boardApply Behavior-Driven Development to clarify user-visible behavior, acceptance criteria, business workflows, and executable examples before or during implementation. Do not use to author formal .feature syntax; use gherkin. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| brainstormingnledford/engineering-review-boardStructured ideation for ambiguous software engineering work. Use when agents need to generate multiple options, compare tradeoffs, or converge on a recommendation before implementation, architecture, domain modeling, API design, migration, refactor, testing strategy, or debugging choices after systematic reproduction. Do not use for simple mechanical tasks, obvious single-path fixes, or active unexplained symptoms; use systematic-debugging first. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| ci-release-engineeringnledford/engineering-review-boardImplement, change, review, or test checked-in CI and release provider configuration, including workflow triggers, job graphs, matrices, caches, artifacts, permissions, concurrency, environments, automated versioning, tags, releases, and package or binary publication. Do not use to choose a semantic patch, minor, or major bump from application changes; use semantic-versioning. Do not use for underlying language/test commands, Justfile wrappers, manual Git operations, final ship/hold decisions, unexplained CI failures, supply-chain-only or security-review-only audits, or production deployment infrastructure implementation. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| clean-architecturenledford/engineering-review-boardClean Architecture guidance centered on the dependency rule, entities, use cases/interactors, and interface adapters that keep business policy independent from frameworks, databases, and UI. Use when the main design question is how policy flows through use cases and adapter boundaries. Use hexagonal-architecture when named inbound/outbound ports around external actors are the main concern, onion-architecture when explicit concentric domain/application rings are the requested model, and architecture-review for a read-only audit. Do not use for simple CRUD, prototypes, or framework-convention-first apps where added layers reduce clarity. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| code-reviewnledford/engineering-review-boardPerform repository-local code reviews. Use for requested diff or pull-request audits, final focused review after implementation, or changes that affect behavior, APIs, domain boundaries, tests, security, workflows, dependencies, CI, documentation, or agent instructions. Do not use as the primary workflow for repository-wide technical-debt portfolio audits, implementation, active failure debugging, or design-only threat modeling. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| container-engineeringnledford/engineering-review-boardImplement, change, review, or test Dockerfile, Containerfile, .dockerignore, BuildKit/OCI image, and Docker Compose configuration, including build contexts and stages, caches, runtime users, entrypoints, health checks, ports, networks, volumes, secrets, lifecycle, and resource or privilege controls. Do not use for routine command execution or log inspection, Kubernetes/Helm/ECS/Nomad/cloud deployment, application-only changes, supply-chain-only or security-review-only audits, hosted CI pipelines, final ship decisions, or unexplained container failures. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| create-agent-skillnledford/engineering-review-boardCreate or improve reusable agent skills. Use when the user asks to create a new skill, update an existing skill, define skill instructions, scaffold a SKILL.md-based skill directory, validate skill structure, or turn repeated agent workflows into a global or project skill. Do not use for ordinary documentation edits, application implementation, or ignored third-party runtime skills. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| csharp-dotnet-engineeringnledford/engineering-review-boardC# and .NET engineering guidance. Use when adding, changing, reviewing, testing, packaging, restoring, building, publishing, or refactoring C# source, SDK-style .csproj projects, Directory.Build.props/targets, global.json, .sln/.slnx solutions, MSBuild, NuGet PackageReference, ASP.NET Core, Blazor, EF Core, or .NET test projects. Do not use for database-native schema/query design, general WebAssembly host/guest/runtime decisions, checked-in CI/release-provider configuration, Docker/OCI/Compose configuration, or a public API contract; use the owning SQL, WebAssembly, CI/release, container, or API skill instead. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| css-scss-stylingnledford/engineering-review-boardCSS, SCSS/Sass, and Tailwind CSS styling guidance. Use when adding, changing, reviewing, refactoring, adopting, or migrating .css, .scss, .sass, CSS modules, design tokens, cascade layers, container/media queries, responsive layout, stylesheet build pipelines, Tailwind or other utility-class conventions, CSS-in-JS, or styling integration in HTML, JavaScript/TypeScript, PHP/Smarty templates, Python templates, or Rust Leptos/Axum apps. Use ux-accessibility-review for interface accessibility or UX audits. Use language/framework skills for non-styling implementation mechanics and do not use for behavior changes with no styling surface. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| data-platform-engineeringnledford/engineering-review-boardData-platform engineering guidance for implementing, changing, reviewing, or testing source-to-landing ingestion, post-landing lakehouse or warehouse transformations, analytical semantic contracts, Power BI semantic models and DAX, and Microsoft Fabric or Power BI operations. Use for CDC, watermarks, replay, Delta tables, medallion layers, analytical grain, governed metrics, TMDL, RLS or OLS, refresh, promotion, gateways, capacity, recovery, and runbooks. Do not use for application domain modeling, physical OLTP database design, generic distributed protocols, generic UX, or final release decisions. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| dependency-supply-chain-reviewnledford/engineering-review-boardDependency and software supply-chain security review. Use for dependency audits, SBOM/SCA output, CVE/GHSA advisories, package or binary provenance, registry trust, manifests, lockfiles, checksums/signatures, install/postinstall scripts, vendored/generated code, transitive dependency risk, CI actions, container or base-image pinning, or package-manager security policy. Do not use for routine package-manager workflow, language-specific dependency implementation, or third-party API docs without a supply-chain risk question. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| digital-asset-managementnledford/engineering-review-boardDigital asset management (DAM) engineering guidance for photo and video ingest, asset identity, immutable originals, derivatives, metadata, non-destructive edits, organization, smart collections, hierarchies, viewing, sharing, and validation. Use when building, changing, reviewing, or testing a photo/video catalog, media library, asset browser, editing workflow, or related API and data model. Do not use for standalone codec implementation, generic SQL/API/CSS work, or non-media document management without a DAM lifecycle. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| documentation-engineeringnledford/engineering-review-boardDocumentation engineering guidance. Use when creating, editing, refactoring, or reviewing Markdown docs, README files, API docs, code comments, docstrings, examples, Rustdoc, pydoc, Javadoc, JSDoc/TSDoc, PHPDoc, perldoc/POD, XMLDoc/PasDoc, DocC, documentation tests, or developer-facing instructions. Do not use for code-only changes unless docs or comments are part of the change. For reusable SKILL.md contracts, use create-agent-skill. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| domain-driven-designnledford/engineering-review-boardApply Domain-Driven Design to complex business logic and module boundaries. Use when modeling domains, bounded contexts, aggregates, value objects, repositories, domain services, policies, domain events, ubiquitous language, or refactoring toward clearer domain behavior. Do not use for focused audits of an existing domain model; use domain-modeling. Avoid simple CRUD or data-centric work without meaningful domain pressure. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| domain-modelingnledford/engineering-review-boardReview tactical DDD models, aggregates, entities, value objects, invariants, domain services, and ubiquitous language. Use for a focused audit of an existing domain model; do not use to design a new model or force DDD onto simple data-centric work. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| donsetch-web-researchnledford/engineering-review-boardUse the DonSeTch MCP server for public web research, source discovery, URL or PDF retrieval, bounded same-domain crawling, OCR, and evidence capture with web_search, web_fetch, web_crawl, or web_screenshot. Use when current external evidence is needed. Do not use for repository-local facts, structured GitHub platform objects, signed-in browser interaction, checked-in Playwright tests, private or sensitive resources, or DonSeTch installation, configuration, and upgrades unless explicitly requested. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| gherkinnledford/engineering-review-boardWrite clear, idiomatic formal Gherkin feature specifications. Use when creating or editing .feature files, Scenario Outlines, Examples tables, Background sections, dialect keywords, or step wording. Do not use for behavior clarification before a formal artifact; use behavior-driven-development. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| git-commitnledford/engineering-review-boardWrite high-quality git commits and commit messages. Use when the user asks to commit changes, split a working tree into logical commits, improve commit messages, prepare reviewer-friendly new commits, or apply Conventional Commits guidance in any plain git repository. Do not use for amend/fixup/autosquash, branch operations, integration, recovery, push, tags, or worktrees; use git-workflows. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| git-workflowsnledford/engineering-review-boardSafe Git branch, remote, history-inspection, integration, rewrite, conflict, recovery, tag, and worktree workflows. Use when switching or restoring, fetching/pulling/pushing, managing upstreams or remotes, inspecting history with log/blame/bisect, merging/rebasing/squashing/cherry-picking/reverting/resetting, resolving conflicts, recovering with reflog, or managing tags and worktrees. Do not use for commit grouping or message drafting, checked-in CI/release automation, code review, GitHub pull-request operations, or release-readiness decisions. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| hexagonal-architecturenledford/engineering-review-boardHexagonal Architecture / Ports and Adapters guidance centered on how external actors drive or are driven by an application through explicit inbound and outbound ports and adapters. Use when classifying port ownership, replacing delivery or infrastructure mechanisms, or testing the core through those seams. Use clean-architecture when entities, use cases/interactors, and interface-adapter policy flow are primary, onion-architecture for explicit concentric domain/application rings, and architecture-review for a read-only audit. Do not use for simple CRUD, prototypes, or trivial pass-through interfaces. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |