Aos tdd

Skill riz007/architect-os/skills/aos-tdd

AI-native software engineering operating system for modern application architecture, scaffolding, and AI-assisted development.

Install

npx -y skills add riz007/architect-os --skill aos-tdd

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

1 stars1 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

Test-driven workflow for adding or changing behavior — write a failing test first, make it pass, then refactor. Use proactively when implementing new business logic, a service method, a bug fix that needs a regression test, or any change where correctness matters. Also use when the user asks to "add tests", improve coverage, or write tests for existing code.

SKILL.md

2.0 KB, as published. Nobody here has run it

Test-driven development

This is a model-invoked discipline. When the change is behavioral, drive it with tests.

The loop: red → green → refactor

Red — write one failing test that describes the next small increment of behavior. Run it; confirm it fails for the right reason.
Green — write the minimum code to make it pass. Don't gold-plate.
Refactor — clean up names, duplication, and structure with the test as your net. Re-run; stay green.

Repeat in small steps. Each step is one behavior, not one whole feature.

Test quality rules (ArchitectOS)

Name tests by behavior: should throw ConflictError when email is already registered — not test1, not testCreate.
Mock only at boundaries — HTTP, DB, external APIs. Don't mock the unit under test.
Cover error paths and edges, not just the happy path. Every throw deserves a test.
Keep tests isolated — no shared mutable state, no order dependence, no real network.
Arrange-Act-Assert structure; one logical assertion per test.
Test the contract, not the implementation — avoid asserting on private internals.

The test pyramid

Favor many fast unit tests, fewer integration tests, very few end-to-end tests. If you reach for an e2e test to cover logic a unit test could catch, push it down.

When fixing a bug

Write the failing regression test first (it reproduces the bug), then fix. See aos-debugging for the full diagnosis loop.

On-demand suite audit

For a full review of an existing test suite's balance, naming, isolation, and coverage, use /aos-qa.