Quality

Code Review provides a checklist and best practices for reviewing code changes. Use it to check correctness, quality, security, performance, and maintainability before merging.

Frontend Testing Guide explains how to write unit, integration, and E2E tests for frontend components, hooks, forms, and user flows. It is used when building or reviewing frontend test coverage and test structure.

Playwright E2E Testing covers initialization, Page Object Models, auth reuse, API mocks, visual regression, multi-browser runs, CI integration, and debugging. Use it to automate end-to-end verification of key web flows.

Technical Standards defines naming, code organization, error handling, and test expectations for consistent TypeScript code. Use it when setting team conventions or reviewing code quality.

Test Execution detects a project’s test framework, runs unit, integration, or E2E tests, and parses the results. Use it when you need to verify changes with real test output and coverage.

Test Strategy defines the test pyramid and coverage expectations for unit, integration, and E2E tests. It is used to plan QA coverage, verify core user paths, and check security and performance basics.

Security Audit reviews code and dependencies for common vulnerabilities before deployment or during PR reviews. It checks for secrets, dependency issues, injection risks, auth flaws, and transport security.

Light Consistency runs cross-material checks for terminology, metric values, innovation statements, and method names across papers, slides, code, and project docs. Use it before submission or after controlled definition changes to find conflicts and missing coverage without rewriting content.

Light Experiment Coding implements frozen research plans as minimal, test-first experiment code with controls for leakage and reproducibility. Use it to build or review training, preprocessing, and evaluation runs with raw artifacts for result analysis.

Research Ethics checks research outputs for integrity, consent, disclosure, and publication-risk issues. Use it before submission, data or code release, and human- or animal-subject research decisions.

Code Structure explains how to split orchestration logic from shared operational mechanics in a service layer. Use it when repeated workflows need the same low-level operations or when refactoring duplicated blocks across actions.

Evidence-Driven Testing records annotated proof while you verify app behavior by hand or with scripted probes. Use it when a change needs verifiable evidence, such as UI flows, headless checks, or measured output for a PR or issue.