Test design

Skill eooo-io/ai-native-engineering-doctrine/04-agent-skills/test-design

AI-native engineering harness: doctrine-only, fork-and-curate scaffold for standards, agent skills, tool adapters, and review rubrics.

Install

npx -y skills add eooo-io/ai-native-engineering-doctrine --skill test-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 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

Design practical tests for business logic, integrations, APIs, and regression protection.

SKILL.md

1.2 KB, 216 tokens by cl100k_base, as published. Nobody here has run it

Test Design

Purpose

Produce a lean, useful test plan for a change or component — enough coverage to catch the failures that matter, not enough to drown the change under fixture maintenance.

Test types

Unit tests for pure logic and small functions.
Component tests for module-level behavior with realistic dependencies.
Integration tests for database, queue, API, or external boundaries.
Acceptance-style tests for user-visible behavior or contract surfaces.

Output format

## Scope

## Test plan

### Unit
### Component
### Integration
### Acceptance

## Edge and failure cases

## Tests intentionally not included

Rules

Prefer meaningful coverage over coverage theater.
Tests must be runnable by the project's existing tooling.
Include edge cases and failure cases — happy-path-only suites lie about quality.
Avoid brittle tests that assert implementation details without protecting behavior.
If a test type is intentionally skipped, name it in "Tests intentionally not included" and say why.