testing
/testing
Enforce TDD workflow and testing best practices for Penpot. Use when implementing features, fixing bugs, or modifying behavior. Reads testing memory for full guidance.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MPL-2.0, otwarta.
What it does and when to use it
Enforce TDD workflow and testing best practices for Penpot. Use when implementing features, fixing bugs, or modifying behavior. Reads testing memory for full guidance.
Original author description
Enforce TDD workflow and testing best practices for Penpot. Use when implementing features, fixing bugs, or modifying behavior. Reads testing memory for full guidance.
How it works
- When to Use
- Workflow
- Required Reading
- Key Rules
- Verification
SKILL.md preview
--- name: testing description: Enforce TDD workflow and testing best practices for Penpot. Use when implementing features, fixing bugs, or modifying behavior. Reads testing memory for full guidance. --- # Testing Skill Enforces test-driven development and Penpot testing conventions. ## When to Use - Implementing new logic or behavior - Fixing any bug (reproduction test required) - Modifying existing functionality - Adding edge case handling **Skip:** Pure configuration changes, documentation updates, or static content with no behavioral impact. ## Workflow Follow TDD (Red → Green → Refactor) whenever practical: 1. **RED** — Write a failing test first 2. **GREEN** — Write minimal code to pass 3. **REFACTOR** — Clean up while tests stay green For bug fixes, use the Prove-It Pattern: write a test that reproduces the bug, confirm it fails, implement the fix, confirm it passes. ## Required Reading Before writing any test, read: 1. `.serena/memories/testing.md` — cross-cutting testing principles, TDD workflow, anti-patterns, execution discipline 2. Module-specific testing memory for the affected module: - `mem:common/testing` — CLJC unit tests - `mem:frontend/testing` — CLJS unit tests, Playwright E2E - `mem:backend/testing` — JVM clojure.test conventions - `mem:exporter/testing` — exporter unit tests ## Key Rules - Every behavior change needs a test - Test state, not interactions - DAMP over DRY — tests are specifications; duplication is OK if each test is self-contained and readable - Prefer Real > Fake > Stub > Mock - Arrange-Act-Assert structure - One assertion per concept - Never pipe test output to filters — redirect to file first - Register new test files in the module's runner/entrypoint ## Verification After completing implementation: - [ ] Every new behavior has a test - [ ] All tests pass for touched modules - [ ] Bug fixes include a reproduction test - [ ] Lint/formatter passes
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · penpot/penpot | 90 | MPL-2.0 |
| iuliandita/skills | 100 | MIT |
| wrongstack/wrongstack | 100 | MIT |
| langwatch/langwatch | 100 | Apache-2.0 |
| mcouthon/agents | 100 | MIT |
| nteract/nteract | 100 | BSD-3-Clause |
| kettleofketchup/DraftForge | 100 | GPL-3.0 |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| TheBeardedBearSAS/claude-craft | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 0b112b44aecc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 92tdd
機能追加・バグ修正の前に使用。テストファーストで実装する規律スキル。 - 100tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 90% line / 70% branch coverage including unit, integration, and E2E tests. - 100tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests. - 100tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests. - 100tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests. - 100tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.