Shared tdd
A collection of Claude Code skills for iOS, MERN, NEAN, and shared development workflows
npx -y skills add edfenton/claude-skills --skill shared-tddAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
TDD policy — red-green-refactor workflow and evidence requirements for all platforms.
SKILL.md
1.1 KB, as published. Nobody here has run it
Purpose
Mandate test-driven development across all platforms. Platform coding standards reference this for the TDD workflow, then add platform-specific test tooling and conventions.
TDD workflow (mandatory)
For any new behavior or bug fix:
-
Red — Write failing test(s) first
- Derive test cases from acceptance criteria
- Run tests to confirm failure
- Do NOT write implementation code yet
-
Green — Write minimum code to pass
- No feature creep beyond test requirements
- Run tests after each change
-
Refactor — Clean up while tests stay green
- Improve code quality without changing behavior
Bug fixes
Bug fixes require a failing test that reproduces the issue before the fix is written.
Completion gate
Stories cannot be marked complete without test files. Test files must exist before marking a story done.
TDD evidence
When implementing features, document in commit or PR:
- Which tests were written first
- Confirmation that tests failed before implementation