test-design-principles

Translate universal test-design principles into actionable planning and writing guidance.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/froide-kk/michinushi --skill test-design-principles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-design-principles
Source: https://github.com/froide-kk/michinushi/tree/main/test-design-principles
Command: npx skills add https://github.com/froide-kk/michinushi --skill test-design-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides universal, language-agnostic guidance on test design to help AI-driven testing plans decide what to test, in what order, and how to preserve independence across scenarios.

Core Features & Use Cases

  • Establishes a principled test-design framework that helps identify critical test areas early.
  • Guides test planning workflows for unit, integration, and end-to-end tests across tech stacks.
  • Use case: When starting a new feature, apply these principles to decide test scope and sequencing, ensuring corner cases are covered.

Quick Start

Provide a concise test plan outline applying the universal principles to a new feature.

Frequently Asked Questions about test-design-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are universal test-design principles for robust tests?

Universal test-design principles are language-agnostic guidelines that help determine what to test, in what order, and how to preserve independence across unit, integration, and end-to-end testing scenarios.

How do I plan tests for a new feature across different tech stacks?

You can plan tests by applying a principled framework to decide test scope and sequencing early, ensuring critical areas and corner cases are covered across diverse technology stacks.

How do I ensure my testing covers abnormal paths and boundary cases?

To cover abnormal paths and boundary cases, apply structured test-design principles that emphasize deterministic workflows and early identification of critical test areas during your planning phase.

Can I use these test-design guidelines for both unit and e2e testing?

Yes, these guidelines are language-agnostic and cover unit, integration, and end-to-end testing, providing actionable guidance for planning and writing tests across diverse tech stacks.

What is the best way to structure a test plan for AI-driven testing?

The best way to structure an AI-driven test plan is to use deterministic workflows and principled frameworks, translating universal guidelines into a concise outline that sequences tests and ensures scenario independence.

Why should I not skip test independence when designing integration tests?

Skipping test independence breaks deterministic workflows; these universal principles specifically help preserve independence across scenarios to ensure accurate quality assurance and reliable integration testing.