api-coverage
01Skill Claude CodeCodex
Map API endpoints against existing API tests to show what is tested and what is missing. Use when the user runs /api-coverage or asks which endpoints are covered.
Skill Claude CodeCodex
Map API endpoints against existing API tests to show what is tested and what is missing. Use when the user runs /api-coverage or asks which endpoints are covered.
Skill Claude CodeCodex
Turn a test failure into a structured bug report with repro steps, severity, and expected vs actual. Use when the user runs /bug-from-failure or asks to file a bug from a failing test.
Skill Claude CodeCodex
Map spec files against requirements or features to show what is covered, missing, and redundant. Use when the user runs /coverage-map or asks what is tested.
Skill Claude CodeCodex
Explain any file in the suite in plain language, teaching the pattern behind the code. Use when the user runs /explain or asks what a file does or why it is structured a certain way.
Skill Claude CodeCodex
Diagnose failing or unstable tests: flaky selector vs timing issue vs real bug, with a concrete fix. Use when the user runs /flake-check or reports a flaky or intermittent test.
Skill Claude CodeCodex
Generate a k6 load test script with ramp-up stages and pass/fail thresholds. Use when the user runs /load-k6 or asks for a load or performance test.
Skill Claude CodeCodex
Generate a Playwright API test file covering success, errors, auth failure, and invalid input. Use when the user runs /new-api-spec or asks for tests for an API endpoint.
Skill Claude CodeCodex
Generate a typed Playwright Page Object following Autoframe conventions. Use when the user runs /new-page or asks for a Page Object for a URL, page, or feature.
Skill Claude CodeCodex
Generate an E2E spec file with happy path, negative, and edge cases pre-written. Use when the user runs /new-spec or asks for tests for a feature or page.
Skill Claude CodeCodex
Restructure messy Playwright tests to follow Autoframe conventions, extracting Page Objects and fixtures. Use when the user runs /refactor or asks to clean up existing tests.
Skill Claude CodeCodex
Generate a non-technical test coverage summary for stakeholders like PMs, CTOs, or boards. Use when the user runs /report or asks for a shareable summary of test coverage.
Skill Claude CodeCodex
Review a spec file from a QA perspective: weak assertions, missing coverage, implementation-focused tests. Use when the user runs /review-spec or asks for a review of their tests.
Skill Claude CodeCodex
Bootstrap the Autoframe framework for a specific product: asks about the app, then wires a ready-to-run Playwright suite. Use when the user runs /setup, asks to set up or initialize Autoframe, or wants to start a test suite for their app.
Skill Claude CodeCodex
Convert requirements (pasted text, Notion, Jira, or Linear link) into a runnable Playwright spec. Use when the user runs /tc-to-spec or provides requirements to turn into tests.
Instructions file
Instructions for kint4/autoframe, covering autoframe — claude instructions, what is autoframe?, stack (non-negotiable), file locations and folder structure.