tester-mindset
Tester Mindset
A test is a small, deliberate meeting with consequence, arranged so truth can arrive before ruin does.
Use this as an orthogonal workflow skill. Compose it with implementation, review, security, product, or documentation skills when the main job is to make confidence earn its keep.
When To Use
- design a test plan, validation strategy, QA approach, or acceptance criteria
- identify edge cases, failure modes, adversarial cases, or missing evidence
- decide whether existing tests, metrics, benchmarks, or demos prove enough
- plan or debrief exploratory testing, chartered sessions, or bug hunts
- review test quality and detect weak, tautological, or proof-theater tests
- turn a vague claim such as "this works" into observable checks
- review a change through the question "what consequence was invited?"
More from n-n-code/n-n-code-skills
project-vendor-boundary
Overlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.
19coding-guidance-cpp
C++ implementation and review skill. Use when writing, modifying, refactoring, or reviewing C++ code, especially modern C++17/20/23 code that needs strong ownership, type safety, and testable design. Portable across C++ repos and build systems.
18project-platform-diagnose
Overlay for environment-sensitive diagnosis — service startup, install issues, platform integration, headless/container behavior, and runtime smoke checks. Portable across repos where build, install, or runtime behavior depends on the local platform.
18documenter
Baseline overlay for substantial documentation authoring or restructuring: README, specs, ADRs, tutorials, how-to guides, reference docs, explanations, API docs, code comments, changelogs, and agent-facing docs. Use when the agent should classify doc type, ground claims in repo truth, and validate examples before finishing.
18security
Security workflow skill for repo-grounded threat modeling, exploit-focused security review, and secure-by-default implementation guidance. Use when the user explicitly asks for security work, or when security properties are the primary concern in a high-risk change. Do not trigger for ordinary code review, routine endpoint work, or general backend implementation just because a repo contains APIs, auth, or secrets.
18project-release-maintainer
Overlay for release-facing docs, install layout, workflows, licenses, and hygiene scripts. Portable across repos with a release/packaging pipeline. Use for publication-facing changes.
17