By alialavia
Write genuine property-based tests: find real invariants, name oracles, avoid tautologies and shrink-hostile generators. Includes a language-agnostic core skill plus Hypothesis (Python) helpers.
Hypothesis-specific patterns for property-based testing in Python — strategies, RuleBasedStateMachine, settings, and Hypothesis ecosystem gotchas. Use this skill whenever the task involves Hypothesis tests, the `hypothesis` package, `@given`, `st.` strategies, `RuleBasedStateMachine`, `@example`, or any Python property-based testing work. This skill pairs with the core `property-based-testing` skill, which handles property discovery and design — load both together for any Hypothesis task. This skill does not re-derive the workflow; it assumes the core skill is loaded and only covers Hypothesis syntax, idioms, and library-specific patterns.
Find genuine property-based tests for existing code, design new code so properties hold by construction, and diagnose property-test failures — always contract-first, reading the implementation only after properties have been designed. Use this skill whenever the user asks for property-based tests, PBT, QuickCheck-style tests, invariant tests, generative tests, or fuzz tests, in any language (Python/Hypothesis, TypeScript/fast-check, Rust/proptest, Haskell/QuickCheck, Scala/ScalaCheck, etc.). Also use it whenever the task mentions properties, invariants, oracles, generators, arbitraries, shrinking, stateful/model-based testing, or a property test that is failing — even if the user doesn't say "property-based" explicitly. Pair this skill with the library-specific skill (pbt-hypothesis, pbt-fast-check, etc.) when one is available — this skill handles property discovery, design, and failure interpretation; the library skill handles syntax, strategies/arbitraries, and ecosystem-specific patterns. Without this skill, generated property tests tend to degenerate into trivial example tests, tautologies that reimplement the function under test, or properties silently coupled to the current implementation rather than the contract.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Property-based testing skills for Claude Code.
Most "property-based" tests generated by LLMs aren't actually property-based — they're tautologies (assert add(x, 5) == x + 5), glorified example tests, or self-oracles that reimplement the function under test. These skills enforce the procedure that catches those failures: write the property in English, name the oracle, and reject obvious traps before touching a generator.
property-based-testing — Language-agnostic core. Workflow for finding real invariants, an annotated catalog of anti-patterns, and a taxonomy of property categories with examples in Python, TypeScript, Rust, and Haskell.pbt-hypothesis — Hypothesis-specific (Python). Strategies, RuleBasedStateMachine, settings/profiles, and Hypothesis-specific traps. Pairs with the core skill.Both skills auto-activate when the task mentions properties, invariants, oracles, generators, shrinking, or property-based testing in any form.
In Claude Code:
/plugin marketplace add alialavia/pbt-skills
/plugin install pbt@pbt-skills
That's it — the skills become available in every session.
.claude-plugin/marketplace.json ← marketplace manifest
skills/
├── property-based-testing/
│ ├── SKILL.md
│ └── references/
│ ├── anti-patterns.md
│ └── property-catalog.md
└── pbt-hypothesis/
├── SKILL.md
└── references/
├── settings.md
├── stateful.md
└── strategies.md
Library-specific companion skills (pbt-fast-check, pbt-proptest, pbt-quickcheck, …) are welcome. Add a new folder under skills/, follow the same SKILL.md + references/ shape, and append the path to the skills array in .claude-plugin/marketplace.json.
MIT — see LICENSE.
npx claudepluginhub alialavia/pbt-skills --plugin pbtWrite property-based tests for PostgreSQL using sqlproof. Includes a core skill (when to use sqlproof, fixtures, bootstrap a new project) plus focused per-pattern skills (RLS policies, RPC functions, stateful tests, CI/CD setup). Pairs with alialavia/pbt-skills for the foundational property-testing patterns.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Frontend design skill for UI/UX implementation
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns