test-guide

Apply layered test standards to guide testing decisions across components.

Updated Mar 4, 2026

Search Tags:#testing #software-testing #test-standards #decision-flow #qa-process #layered-tests

Ready to run

npx skills add https://github.com/JYC11/filament --skill test-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-guide
Source: https://github.com/JYC11/filament/tree/main/.claude/skills/test-guide
Command: npx skills add https://github.com/JYC11/filament --skill test-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps teams apply a consistent, layered approach to software testing, ensuring requests for tests or test strategy follow established standards.

Core Features & Use Cases

Decision flows: diagrams and rules to select the appropriate test layer (models, store, graph, CLI, daemon, etc.) based on input.
Layer guides: detailed best practices for each testing layer (Models, Store, Graph, CLI Integration, Daemon Integration, etc.), with example scenarios and anti-patterns.
Infrastructure guidance: recommended test infrastructure, ordering for new modules, and patterns to avoid duplicates or gaps.

Quick Start

Apply the decision flow to identify the correct test layer and follow the corresponding layer guide to implement tests.

Frequently Asked Questions about test-guide

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

FAQPage Schema

How do I decide which test layer to use for my software components?▼

Layered testing applies specific best practices to distinct software components like models, stores, graphs, and CLI. It uses decision flows to select the correct layer, ensuring consistent quality and scalable testing infrastructure across the project.

What are common anti-patterns when implementing a software testing strategy?▼

Common anti-patterns in a testing strategy include creating duplicate tests or leaving coverage gaps across layers. Following established layer-by-layer guides and infrastructure expectations helps avoid these pitfalls and ensures scalable practices.

How do I standardize QA processes for models, stores, and CLI components?▼

Standardize QA processes by applying detailed layer guides that define best practices for models, stores, graphs, and CLI components. This establishes consistent infrastructure and decision flows for all testing requests.

Does this testing guide provide infrastructure guidance for new modules?▼

Yes, the guide provides infrastructure guidance including recommended test infrastructure and ordering for new modules. This establishes patterns to avoid duplicates or gaps when expanding your test suite.

Can I use this for test strategy across daemon and dispatch components?▼

Yes, the decision flow supports test strategy across daemon and dispatch components. It provides layer-specific guides and rules to ensure all component types follow established testing standards.

When should I not use a single layer for all my software testing?▼

You should avoid using a single layer for all testing when dealing with diverse components like models, stores, and graphs. Instead, use the decision flow to apply the correct layer-specific standards and avoid anti-patterns.