shinpr/claude-code-workflows

test-implement

Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.

First seen Mar 13, 2026

Installation

$ npx skills add shinpr/claude-code-workflows --skill test-implement

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from shinpr/claude-code-workflows · top by installs.

npx skills add shinpr/claude-code-workflows

Browse all from shinpr/claude-code-workflows

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 679
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,269 B
  • docs SUMMARY.md 243 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 31 installs

SKILL.md

Test Implementation Patterns

Reference Selection

Test Type Reference When to Use
Unit / Integration [references/frontend.md](references/frontend.md) Implementing React component tests with the repository's configured runner and network mocking layer
E2E [references/e2e.md](references/e2e.md) Implementing browser-level E2E tests in the existing harness, or Playwright when the approved work introduces a harness

Common Principles

AAA Structure

All tests follow Arrange-Act-Assert:

  • Arrange: Set up preconditions and inputs
  • Act: Execute the behavior under test
  • Assert: Verify the expected outcome

Test Independence

  • Each test runs independently without depending on other tests
  • No shared mutable state between tests
  • Deterministic execution — mock random and time dependencies

Naming

  • Test names describe expected behavior from user perspective
  • One test verifies one behavior