screenshots
Take screenshots of components affected by recent changes, either from the running application (with e2e authentication) or from Storybook.
Usage:
/screenshots- Detect changed components and take screenshots automatically/screenshots navigate to /settings, open the "Profile" tab, screenshot the form- Follow custom instructions to take screenshots
Instructions:
-
Check for custom instructions:
- If
$ARGUMENTSis provided and non-empty, run step 2 (prerequisites), then jump to step 6 (Custom instructions mode) - If
$ARGUMENTSis empty, continue with the automatic detection flow below (steps 2–5, then 7–10)
- If
-
Check prerequisites:
- Run
playwright-cli --helpto verify the Playwright CLI is available - If the command fails (not found or errors), display the following message and STOP:
## Missing Prerequisite: Playwright CLI Playwright CLI is not installed. This skill requires the Playwright CLI for taking screenshots.
- Run
More from morphet81/cheat-sheets
translate-pdf
Translate a PDF document from one language to another. Extracts text to structured Markdown, translates it, and builds a new translated PDF. Requires a Python environment with pymupdf, markdown, and weasyprint.
80create-jira-ticket
Create a JIRA ticket from user instructions via acli. Uses project from the current branch when possible, lists project epics, recommends the best epic, asks confirmation before creating, uses ADF descriptions, and can attach Figma designs via the Jira integration.
80localise
Generate an HTML translation helper page for Lokalise. Use when the user provides English text (singular/plural) and wants translations across all 23 supported languages, rendered as an interactive HTML page with copy buttons. Triggers on phrases like "translate for Lokalise", "generate translations", "translation table", or when the user provides English strings and mentions languages/i18n/localization.
79update-jira-ticket
Compare the JIRA ticket description to changes made in the current branch and propose description edits and/or comments to keep the ticket accurate and well-documented.
79verify-test-cases
Verify test cases in all test files modified since branching out from base branch. Checks that test cases make sense, have no duplications, and provide meaningful coverage. Spawns parallel agents for multi-file analysis. After the user confirms test-case changes, runs coverage (npm test:coverage or Jest/Vitest fallback) and fixes tests until coverage passes.
79merge-base-branch
Select base branch (from .agent, git history, or main), fetch, stop if already up to date, commit all WIP, merge, resolve conflicts, then lint, tests at 100% coverage, and build—with commits after each fix phase.
79