agentsclimarketplace

Test

10,627 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Tdd

    dayfinggg/claude-code-codex-skills/codex/skills/tdd Skill

    8★ repo

    Implement behavior through verified red-green-refactor cycles. Use when the user explicitly requests TDD or red-green-refactor, or when an agreed workflow requires test-first development. Do not trigger merely because a bug or suitable test surface exists; do not use for prototypes, generated artifacts, mechanical changes, or when test infrastructure would exceed scope.

  • Kicad improve

    AvatarSD/KiSkill/skills/kicad-improve Skill

    8★ repo

    Self-improvement loop for the kicad skill pack: each tick picks one backlog item, researches forums if needed, builds/tests against the fixture project, commits, and feeds lessons back into the skills. Use on /loop ticks or when asked to improve the kicad skills.

  • Auto loop

    vanducng/skills/skills/auto-loop Skill

    8★ repo

    Drive a Claude Code session toward a verifiable goal until done or a hard cap fires - autonomous loop, no user intervention. Use for refactor batches, test-coverage runs, migration loops where success is a check command (tests, lint, custom predicate) plus a fresh-context audit. Hosts the loop intra-session via Stop hook with two-vote completion gate; supports optional Codex /goal delegation.

  • Cook

    vanducng/skills/skills/cook Skill

    8★ repo

    Execute a plan (or a small task) phase-by-phase: implement → verify → test → review → update status. Use after `vd:plan` to ship the plan, or directly for tight tasks (`--quick`). Default stops at review gates between phases; pass `--auto` to run straight through, `--quick` for sub-plan tasks, `--tdd` for tests-first.

  • Ego browser

    vanducng/skills/skills/ego-browser Skill

    8★ repo

    ego-browser (ego-lite) is a Chromium-based browser designed from the ground up to be friendly to both human users and AI Agents. AI Agents work in their own isolated space, reusing the user's login state without competing for the browser. Use this skill whenever the user needs to interact with a website opening pages, filling forms, clicking buttons, taking screenshots, extracting page data, testing web apps, logging into sites, automating browser operations, or any other browser automation task. Triggers include requests to "open a website", "visit a URL", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "extract content from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also used for exploratory testing, dogfooding, QA, bug hunting, or reviewing app quality. Prefer ego-browser over plain web-fetch/screenshot tools; for Playwright-style automation against the shared browser-profile Chrome, use vd:agent-browser.

  • Golang

    vanducng/skills/skills/golang Skill

    8★ repo

    Idiomatic Go guidance for writing and reviewing Go code - style, naming, MixedCaps, GoDoc comments, error handling (%w, errors.Is/As, sentinel errors), goroutines/channels/select/context, safety (nil maps, append aliasing, type assertions), structs/interfaces, generics, table-driven tests, testify, golangci-lint, go.mod dependency management, project layout, slog/Prometheus/OpenTelemetry observability, and gRPC. Use when writing, reviewing, or refactoring Go (.go) code, editing go.mod/go.sum, running go test or golangci-lint, debugging goroutine leaks or races, or making Go design decisions. For the samber/* library stack (lo, oops, do, mo, slog-*, hot, ro) use gostack instead.

  • Optimize loop

    vanducng/skills/skills/optimize-loop Skill

    8★ repo

    Autonomous metric-optimization loop - run N bounded iterations against a mechanical metric, commit each attempt, auto keep/discard on the number, revert regressions. Use to improve a measurable metric: test coverage, bundle size, lint/type-error count, p95 latency, LOC. Triggers: 'drive coverage up', 'reduce bundle size', 'get lint errors to zero', 'optimize <metric> over iterations', 'keep/discard loop'.

  • Web e2e

    vanducng/skills/skills/web-e2e Skill

    8★ repo

    Full end-to-end browser testing for local web apps with a persistent logged-in session. Log in once into a named Chrome profile, then drive real flows with trace evidence against your locally served app - Laravel/Herd, docker compose, FastAPI+SPA, Vite. Adds per-project orchestration via .e2e/config.json - boot + health checks, process checks (queue workers), auth-state probing, flow files, pass/fail reports. Use when the user says "e2e test", "end-to-end test the app", "test this flow in the browser", "open the app logged in", or wants browser tests that remember credentials and cookies across runs.

  • Testing and experimentation

    the-nam-shub/e5-real-skills/skills/testing-and-experimentation Skill

    no license8★ repo

    Guidance for B2B marketers on how to design, run, and learn from marketing experiments—covering budget allocation, channel testing, creative validation, measurement methodology, and experimentation culture. Trigger when a user is planning a test, evaluating a channel, allocating experimentation budget, or trying to prove causality in marketing.

  • Swiftui max

    Dev869/swift-tothemax/skills/swiftui-max Skill

    8★ repo

    Expert SwiftUI guidance for building UI on iOS, iPadOS, macOS, watchOS, tvOS, and visionOS. Use whenever writing, reviewing, refactoring, or debugging ANY SwiftUI code — views, view modifiers, layout, navigation (NavigationStack/SplitView, deep links), lists and scrolling, animation and transitions, state management (@State, @Binding, @Observable, Observation, environment), Liquid Glass adoption, toolbars, sheets and presentations, widgets/Live Activities, UIKit/AppKit interop, or SwiftUI performance problems (slow lists, hitches, excessive view updates). ALSO use it when building common UI components (bottom sheets, tab bars, onboarding, infinite scroll, skeletons, charts, forms, toasts), choosing or adding UI libraries (Pow, Lottie, Nuke, Kingfisher, snapshot testing, Inject hot reload, TCA), building a design system (tokens, themes, component packages), or iterating visually (simulator screenshots, previews, snapshot tests). Trigger on mentions of SwiftUI, "build a screen/view", "make it look good", @Observable, ObservableObject migration, NavigationView, glassEffect, WidgetKit, or any *View struct with a body. For pure Swift language/concurrency questions, the sibling swift-language skill applies instead.

  • Deploy verify

    kensaurus/cursor-kenji/skills/deploy-verify Skill

    8★ repo

    Post-deploy smoke test combining all 5 MCPs (Sentry + Supabase + Langfuse CLI + Playwright + Firecrawl) into one workflow. Auto-detects deployment context, checks Sentry for new errors (with Seer AI root-cause on P0s), verifies Supabase migration health and logs, confirms Langfuse trace pipeline, runs Playwright smoke test on critical paths, and produces a ship-or-rollback verdict. Works with any project. Use when asked to: "verify deploy", "post-deploy check", "smoke test production", "check if deploy is healthy", "ship or rollback", "post-release check", "verify release", "deploy health check", or "run post-deploy".

  • Mobile emulator test

    kensaurus/cursor-kenji/skills/mobile-emulator-test Skill

    8★ repo

    QA a native Android build end-to-end on the emulator. Use for "test on emulator", "QA Android build", "verify native build", "white screen", "cache rehydration", "Expo dev-client QA", "adb reverse". Pairs Metro/adb walk with Supabase + Sentry MCPs for three-layer CRUD verification.

  • Mushi integration

    kensaurus/cursor-kenji/skills/mushi-integration Skill

    8★ repo

    Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.

  • Plan test coverage

    kensaurus/cursor-kenji/skills/plan-test-coverage Skill

    8★ repo

    User-story-driven test coverage audit and plan — no test writing in this pass. Derives stories from real code, builds story-to-test traceability matrix, detects fake-green and weak tests, multi-lens coverage (branch/path/risk/integration/mutation). Coverage numbers from real runs or [NEEDS RUN]. Natural lock-in after stub-wiring. Use when asked to "test coverage plan", "coverage audit", "traceability matrix", "fake-green tests", "uncovered user stories", "plan tests for critical flows", "mutation testing plan", or "what's not tested".

  • Test playwright

    kensaurus/cursor-kenji/skills/test-playwright Skill

    8★ repo

    Close the PDCA loop on the work you just did. After implementing changes, drive the LIVE app on localhost through the Playwright browser MCP like a real end user — manually, in a visible (headed) browser, clicking and typing one action at a time, NEVER through scripts or test runners — exercising every page, component, and flow the current session touched. Reproduce real user journeys, hunt for pain points, and FIX them as you go (full-stack: UI/UX + backend + DB), using already-enabled MCP servers (Sentry for production errors, Supabase for schema/logs/data, Firecrawl for research). Red-team your own work, give brutally honest critique, and suggest feature/UX improvements. Generic across any repo and stack. Use after building or changing a feature, or when the user says "test this with playwright", "test my changes", "test on localhost like a user", "PDCA this", "did you actually test it", "red-team this feature", or "verify the work end-to-end".

  • Test qa

    kensaurus/cursor-kenji/skills/test-qa Skill

    8★ repo

    Generic webapp QA fallback — use only when no project-specific QA skill applies (project-local QA skills take precedence; use mobile-emulator-test for native builds). For unit tests use test-unit. Drives a visible (headed) browser manually through the Playwright MCP like a real user — clicking and typing one action at a time, never via scripts or test runners. Auto-discovers pages, entities, and auth from the codebase, generates user stories, performs real CRUD with data-pipeline verification (FE -> API -> DB -> FE), audits UX quality, tests edge cases, and produces a pass/fail report. Use when asked to "QA the app", "test the app", "find bugs", "run QA", "test CRUD", "smoke test", "check for dead buttons", or "test like a real user" AND no project-specific QA skill matches the repo.

  • Test red team

    kensaurus/cursor-kenji/skills/test-red-team Skill

    8★ repo

    Adversarial red-team of a running web, React Native, or Capacitor hybrid app. Drives a visible (headed) browser by hand — Playwright browser MCP (web/PWA), Android WebView attach (Capacitor), or adb tap-walk (native) — never scripted test files. Attacks every feature across 4 dimensions: UI/UX, data pipeline, security (OWASP-mapped), and performance. Cross-references Sentry telemetry, Supabase DB-layer mutation truth and RLS, and current OWASP/MASVS guidance. Produces a severity-ranked defect list with repro steps and evidence. Generic across any repo and stack. Use when asked to "red team this app", "attack my app", "break it", "find all the defects", "adversarial test", "pre-launch hardening", "pentest the app", or "full app QA". Distinct from test-playwright (session PDCA), test-qa (happy-path crawl), and audit-security (static code review).

  • Test unit

    kensaurus/cursor-kenji/skills/test-unit Skill

    8★ repo

    Write effective unit tests with best practices for any project. Auto-detects test framework (Jest, Vitest, pytest, Go test, etc.), researches current testing patterns via Firecrawl, fetches testing library docs via Context7, and uses Sentry MCP to identify production errors that lack test coverage. Use when writing tests, creating test cases, improving test coverage, increasing confidence before release, or when the user mentions testing.

  • Workflow build feature

    kensaurus/cursor-kenji/skills/workflow-build-feature Skill

    8★ repo

    End-to-end feature build workflow: spec → TDD → implement → smoke test → PR. Sequences workflow-spec-tdd, test-unit, test-playwright, and workflow-pr into a single tracked loop. The single entry point for "build a feature", "implement this", "add X", "ship a new capability", or any non-trivial feature request. Asks for scope clarification before starting if the request is ambiguous. Generic across web, mobile, and full-stack repos.

  • Workflow spec tdd

    kensaurus/cursor-kenji/skills/workflow-spec-tdd Skill

    8★ repo

    Stop vibe-coding with a spec → plan → TDD loop before writing a line. Use for any non-trivial feature, refactor, or bug fix on web, React Native, or Capacitor. Use when asked to "build", "implement", "add a feature", "this keeps breaking", "do it properly", or when LLM output keeps being wrong.

  • Skillci guardrails

    kabirnarang39/skillci/skills/skillci-guardrails Skill

    8★ repo

    Use this skill whenever you create, edit, or review a Claude Skill — any SKILL.md file, or the eval cases/config next to one. Most SKILL.md files today are written or edited by an agent, not typed by hand, so this closes the loop by having the agent that just wrote the skill also author it defensively and verify it, the same way a linter and test suite run after any other code change. Trigger phrases include "write a skill", "create a SKILL.md", "add a new skill", "edit this skill", "update the skill's frontmatter/description/triggers", or any diff that touches a SKILL.md path.

  • Testing patterns

    0xMassi/claude-skills/testing-patterns Skill

    8★ repo

    Testing standards and patterns across TypeScript (Vitest), Rust (cargo test), Swift (Swift Testing), and Go (go test). Covers file conventions, mock strategies, async testing, CI integration, and anti-patterns based on real project usage.

  • Test first implementation

    stark-ai-de/agent-skills/incubator/skills/engineering-workflows/test-first-implementation Skill

    8★ repo

    Implement behavior with a red-green-refactor loop, observable tests, and small vertical slices. Use when the user asks for TDD, test-first work, regression-first fixes, or a feature that needs clear behavior before implementation.

  • Browser testing with devtools

    hamzabellouch/agent-skills/Frontend Design and UI/browser-testing-with-devtools Skill

    8★ repo

    Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

    The same file is in 3 other repositories

  • Webapp testing

    hamzabellouch/agent-skills/Frontend Design and UI/webapp-testing Skill

    8★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Detection engineering coverage evaluation

    hamzabellouch/agent-skills/Google Cloud and GKE/detection-engineering-coverage-evaluation Skill

    8★ repo

    Automates the end-to-end detection engineering workflow in Google SecOps using MCP tools. Use when fetching threat intelligence from blogs, generating Threat Detection Opportunities (TDOs), simulating attacker behavior with synthetic UDM events, evaluating rule coverage, generating new YARA-L 2.0 rules to close coverage gaps, and with user approval, deploy them to SecOps. Don't use when asked to perform threat hunting actions, and SOC investigative actions.

  • Marketing ab testing

    hamzabellouch/agent-skills/Marketing and Growth/marketing-ab-testing Skill

    8★ repo

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

    The same file is in 3 other repositories

  • Marketing analytics

    hamzabellouch/agent-skills/Marketing and Growth/marketing-analytics Skill

    8★ repo

    When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-testing.

    The same file is in 3 other repositories

  • K6 and locust load testing

    hamzabellouch/agent-skills/Performance and Load Testing/k6-and-locust-load-testing Skill

    8★ repo

    Production-grade load, stress, spike, and endurance testing using Grafana k6 and Python Locust. Use when designing performance test suites, defining SLAs/SLOs, simulating distributed user traffic, and automating performance regression gates in CI/CD pipelines.

  • Test driven development

    hamzabellouch/agent-skills/Software Engineering and Workflows/test-driven-development Skill

    8★ repo

    Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

    The same file is in 7 other repositories

  • Workflow superpowers test driven development

    hamzabellouch/agent-skills/Software Engineering and Workflows/workflow-superpowers-test-driven-development Skill

    8★ repo

    Use when implementing any feature or bugfix, before writing implementation code

    The same file is in 10 other repositories

  • Onboard sim

    bks-lab/open-bridge/skills/onboard-sim Skill

    8★ repo

    Adversarial onboarding-safety simulation. Builds a leak-SAFE sandbox that reproduces a fresh PUBLIC-origin open-bridge clone with the push guard armed, drives a naive first-time-user session inside it (default: a cheap model such as Haiku; or a model-free scripted run for CI), then DETERMINISTICALLY asserts that no USER data — identity/agent, work/, client content on a user/* branch — reached the would-be-public upstream. The whole sandbox upstream is a local bare repo, so testing for a leak can never cause one. Use to verify the public-origin push guard (rules/push-guard.md + scripts/hooks/pre-push) end-to-end whenever onboarding, the hook, rules/operations.md, or session-start change, and as the standing pre-promote / CI gate for that surface. Trigger: "/onboard-sim", "onboard sim", "simulate onboarding", "run the onboarding simulation", "leak sim", "test the push guard", "does my bridge leak", "mirror-safety sim".

  • Scenario quality skill

    jscraik/Agent-Skills/Infrastructure/tests/fixtures/skills_sdk/scenario_quality_skill Skill

    8★ repo

    Fixture skill with promotable eval scenario metadata.

  • Valid skill

    jscraik/Agent-Skills/Infrastructure/tests/fixtures/skills_sdk/valid_skill Skill

    8★ repo

    Minimal valid Codex skill source fixture for JSC-391 scaffold tests.

  • Talk cormack tests lie observability ai

    jscraik/Agent-Skills/Plugins/aidevcon/skills/talk-cormack-tests-lie-observability-ai Skill

    8★ repo

    Use when the user asks about Justin Cormack's AI Native DevCon talk on tests, observability, AI-generated behavior, evidence, instrumentation, and keeping AI systems honest when test signals are incomplete.

  • Talk roberts ai native brownfield

    jscraik/Agent-Skills/Plugins/aidevcon/skills/talk-roberts-ai-native-brownfield Skill

    8★ repo

    Use when the user asks about Katie Roberts''s talk "Stop Maintaining, Start Evolving: Applying AI-Native Practices to Brownfield Codebases" — including questions about using AI to build large complex systems (her ~350k-line Rust S3 clone experiment), test oracles, flaky tests with AI agents, why 100% test coverage is the wrong goal, human-in-the-loop AI coding, AI-assisted performance engineering, using the type system to enforce invariants, tracing as an AI debugging tool, or applying her approach to brownfield/legacy modernisation work.

  • He tdd

    jscraik/Agent-Skills/Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-tdd Skill

    8★ repo

    Build behavior-safe code changes with TDD and RED/GREEN evidence. Use when he-plan or he-work requires TDD for a concrete behavior target.

  • Evals router

    jscraik/Agent-Skills/Skills/agent-ops/evals-router Skill

    8★ repo

    Use when evaluating LLM or RAG outputs: audit eval coverage, analyze failed traces, write binary judge prompts, validate judges against labels, generate targeted synthetic cases, evaluate retrieval quality, or plan review tooling. Do not use for ordinary software test implementation.

  • Testing

    jscraik/Agent-Skills/Skills/agent-ops/testing Skill

    8★ repo

    Choose validation proof for tests, CI, coverage, evals, and closeout evidence: map changed files to repo-native commands, classify pass/fail/blocked ownership, preserve trace/regression artifacts, and keep local, CI, Tessl, external-review, tracker, and runtime truth separate. Use when users ask what tests to run, why validation failed, what proof is enough, or whether command evidence supports a claim.

  • Ui visual regression

    jscraik/Agent-Skills/Skills/frontend-ui/ui-visual-regression Skill

    8★ repo

    Review, triage, and validate visual regression diffs. Use when the user wants snapshot-change analysis, layout regression evidence, Storybook diffs, Playwright screenshots, or Argos review.

  • Code reviewer

    PIXARTSeu/Synapse/.agents/skills/code-reviewer Skill

    no license8★ repo

    Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.

  • Playwright expert

    PIXARTSeu/Synapse/.agents/skills/playwright-expert Skill

    no license8★ repo

    Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.

    The same file is in 1 other repository

  • Python pro

    PIXARTSeu/Synapse/.agents/skills/python-pro Skill

    no license8★ repo

    Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.

    The same file is in 3 other repositories

  • Test driven development

    PIXARTSeu/Synapse/skills/test-driven-development Skill

    no license8★ repo

    Use when implementing any feature or bugfix, before writing implementation code

  • Test master

    PIXARTSeu/Synapse/.agents/skills/test-master Skill

    no license8★ repo

    Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.

  • Code reviewer

    PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/code-reviewer Skill

    no license8★ repo

    Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.

  • Playwright expert

    PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/playwright-expert Skill

    no license8★ repo

    Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.

    The same file is in 1 other repository

  • Python pro

    PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/python-pro Skill

    no license8★ repo

    Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.

    The same file is in 3 other repositories

  • Test driven development

    PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/test-driven-development Skill

    no license8★ repo

    Use when implementing any feature or bugfix, before writing implementation code

  • Test master

    PIXARTSeu/Synapse/packages/codegraph/data/lifecycle-skills/test-master Skill

    no license8★ repo

    Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.

  • Ab testing

    PIXARTSeu/Synapse/packages/codegraph/data/skill/ab-testing Skill

    no license8★ repo

    When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." Includes full Next.js TypeScript implementation and statistical analysis. For tracking implementation, see analytics-tracking.

  • Analytics tracking

    PIXARTSeu/Synapse/packages/codegraph/data/skill/analytics-tracking Skill

    no license8★ repo

    When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." Includes full Next.js TypeScript implementation. For A/B test measurement, see ab-testing.

  • Ci cd

    PIXARTSeu/Synapse/packages/codegraph/data/skill/ci-cd Skill

    no license8★ repo

    CI/CD pipelines for Next.js + Payload CMS projects. GitHub Actions workflows, testing pipelines, preview deployments, Docker builds, Coolify auto-deploy, release automation. Use when setting up CI/CD, automating builds/tests/deploys, or configuring GitHub Actions.

  • Test driven development

    PIXARTSeu/Synapse/packages/codegraph/data/skill/test-driven-development Skill

    no license8★ repo

    Use when implementing any feature or bugfix, before writing implementation code

  • Testing

    PIXARTSeu/Synapse/packages/codegraph/data/skill/testing Skill

    no license8★ repo

    Testing knowledge base - Vitest, Playwright, Testing Library, accessibility testing. Use when setting up a test suite, writing unit/E2E tests, implementing visual regression tests, or testing accessibility.

  • Rust best practices

    adulari/forge/crates/forge-skills/builtin/rust-best-practices Skill

    8★ repo

    Write, review, or refactor Rust so it is idiomatic, safe, and maintainable. Use this skill whenever the task involves Rust code — implementing a feature in a `.rs` file, reviewing a Rust PR or module, refactoring a crate, designing a public API, fixing clippy or borrow-checker complaints, deciding how to structure error handling, or splitting an oversized function or file. Trigger even when the user does not say "best practices" explicitly: any request to "write this in Rust", "clean up this Rust code", "is this idiomatic", "add a Cargo crate", "handle these errors properly", or "make this compile without unwrap" should pull in this skill. Covers ownership and borrowing, error handling (Result / `?` / thiserror / anyhow), API design, module and crate layout, size limits, unsafe, dependencies, testing, and the verification steps (fmt, clippy, test) that must pass before the work is called done.

  • Webapp testing jp

    LinkX-Japan/ai-souken-workflows/claudecode/skills/webapp-testing-jp Skill

    no license8★ repo

    Simplified Japanese web application testing skill covering unit tests, E2E tests, integration tests, Japanese text validation, IME input testing, and naming conventions. Triggers on requests for Webテスト, テスト自動化, E2Eテスト, 日本語テスト, Japanese web testing.

  • Refactor

    mgiovani/cc-arsenal/skills/refactor Skill

    8★ repo

    45 production-grade AI agent skills for real dev workflows. Code review, shipping, docs, git. Works with any skill-compatible agent.

  • Review code

    mgiovani/cc-arsenal/skills/review-code Skill

    8★ repo

    Runs a comprehensive multi-agent code review of a PR, commit, or the whole codebase across six dimensions (correctness, performance, code style, test coverage, error handling, and simplicity/over-engineering) and returns a severity-ranked report with file:line findings and fix suggestions. Use when the user wants a thorough code review, asks to review a PR or diff, or wants over-engineered code flagged for simplification. Analysis only, identifying issues without modifying code, committing, or running tests. Not for a security-focused audit (use review-security), a visual/UX design critique (use review-design), a deep performance-only investigation with profiling and query-level analysis (use review-perf), or a heavier multi-agent PR review team with adversarial/security passes (use team-review).

  • Test suite

    mgiovani/cc-arsenal/skills/test-suite Skill

    8★ repo

    Generates a test suite by analyzing coverage gaps, prioritizing critical and untested code paths, then writing tests in parallel that match the project's existing patterns. Use when the user wants to write tests, add test coverage, generate test cases, improve testing, or analyze coverage gaps. Supports pytest, vitest, jest, and all major test frameworks. Not for debugging a specific failing test (use fix-bug).