aim-writing-tests

Identify and enforce behavior-focused tests for external contracts and interfaces.

4|1|Updated Apr 18, 2026

Search Tags:#testing #verification #contract-testing #quality-assurance #guardrails #test-driven-development #semantics

Ready to run

npx skills add https://github.com/zccz14/AIM --skill aim-writing-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aim-writing-tests
Source: https://github.com/zccz14/AIM/tree/main/.agents/skills/aim-writing-tests
Command: npx skills add https://github.com/zccz14/AIM --skill aim-writing-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AIM Agents often require new or updated tests when adding, changing, migrating, or reviewing behavior. This skill enforces testing practices that protect external semantics (product behavior, APIs, CLI, UI, contracts, and persistence) rather than exposing current implementation details.

Core Features & Use Cases

Guides how to write, repair, or migrate tests to safeguard external behavior and contracts.
Emphasizes avoiding brittle tests that couple to internal implementation and promotes behavior-focused validation.
Use case: when adding a feature or fixing a bug, update or create tests that verify observable outcomes and contracts, not internal structures.

Quick Start

Apply these guidelines during test creation, modification, migration, or review to ensure semantics are protected.

Frequently Asked Questions about aim-writing-tests

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

FAQPage Schema

How do I write tests that guard API contracts instead of internal implementation?▼

To write tests that guard API contracts, validate observable external behavior and semantics rather than internal code structures. This practice prevents brittle coupling and ensures tests validate actual product behavior safely.

What is behavior-oriented testing and when do I need it?▼

Behavior-oriented testing validates observable outcomes and external contracts, avoiding implementation-specific assertions. You need it when adding features, fixing bugs, or migrating code to ensure changes do not break existing semantics.

How do I migrate tests to avoid brittle coupling to source code?▼

Migrate tests by removing implementation-specific assertions and replacing them with behavior-focused validation. Use safe mocks over internal dependencies to protect external semantics and prevent test breakage during code changes.

Does contract testing work for CLI and UI verification?▼

Contract testing applies to CLI and UI verification by enforcing test practices that protect external behavior and semantics across these interfaces. It ensures observable outcomes remain consistent during code changes.

Why do my tests break when I refactor code without changing behavior?▼

Tests break during refactoring when they contain brittle coupling to internal implementation details. Writing tests that validate external semantics and observable outcomes prevents failures when internal structures change.

When should I use safe mocks over internal dependencies in tests?▼

Use safe mocks over internal dependencies when writing or migrating tests to protect external behavior and contractual semantics. This prevents brittle tests and ensures validation focuses on observable outcomes rather than internal structures.