744 skills · sorted by relevance
Turn a design or requirements document into a working MVP, a minimal product, through small end-to-end feature slices. It coordinates scaffolding, repeated generation and evaluation, reviews, and approval gates, with separate commits for the scaffold and each slice.
Create, update, and debug Docker-based end-to-end tests for the Composio CLI. Covers running the executable, keeping test data separate, checking command output, and maintaining package manifests within the CLI test suite.
Run NemoClaw live end-to-end tests, which check complete workflows, or inspect existing release evidence. Routes requests to local or trusted GitHub workflows and reports the tested commit, results, workflow link, and relevant job links.
Build end-to-end tests that follow user journeys in browsers and mobile simulators or emulators. Guides e2e configuration, AI-driven actions, precise outcome checks, failure investigation, and exploratory bug hunts backed by reproducible tests.
Create and update OpenClaw end-to-end tests in Docker, checking complete workflows. Use fake servers to verify requests and real providers to check service behavior, including image understanding and the final text users receive.
Write or repair React tests around user actions and visible results. Cover components and hooks, simulate network responses, check accessibility, and decide when real browser component tests or end-to-end tests across pages are needed.
Check a DeerFlow installation from code updates through deployment and basic service checks. Supports local and Docker setups, verifies frontend pages and API health, and produces a report with results and troubleshooting recommendations.
Set up Pact tests that record what a frontend expects from an API and verify those expectations against the backend. Review these contract tests to catch incompatible changes and help services be tested and deployed independently.
Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.
Design machine learning workflows from data preparation through training, validation, deployment, and monitoring. Use templates and guidance to connect stages, track versions and experiments, handle failures, and plan gradual releases with rollback options.
Build end-to-end tests with Playwright and Cypress to check complete user workflows, such as login and checkout. Improve test reliability through stable element selection, independent test data, appropriate waits, and debugging with traces and screenshots.
Turn a project idea into a detailed system plan before coding. Organize architecture, data flows, dependencies, and file-level tasks in a linked Markdown workspace, with research references, consistency checks, and saved state for resuming later.
Connect NanoClaw agents to DeltaChat for email-based messaging with end-to-end encryption. Set up direct chats or small group conversations, exchange file attachments, and link each chat to the appropriate agent group.
Guide substantial qwen-code feature development from investigation and design through implementation, testing, and review. Produce design documents and end-to-end test plans, compare behavior before and after changes, and address verified review findings.
Test Qwen Code CLI behavior from model requests through tool execution. Reproduce bugs, check terminal interactions and MCP tool connections, and inspect API logs using real models or mock servers for controlled scenarios.
Run Openwork end-to-end tests, which verify complete user journeys, locally or on Daytona. Check the exact commit and runtime, investigate failures or skipped tests, and report results with commands, counts, and an explicit overall verdict.
Investigate failing or flaky NemoClaw end-to-end tests, which check complete workflows. Trace each assertion through its inputs and implementation, including cleanup and dependent jobs, and produce an evidence ledger to guide authorized repairs and reruns.
Turn a vague research direction into a focused proposal and a detailed experiment roadmap. This workflow connects method refinement with validation planning, producing review records, an experiment tracker, and a summary of what to run next.
Coordinate a research project from a broad topic through literature review, idea selection, experiments, and iterative review. Produce a research summary for writing, with optional paper drafting and PDF compilation, while recording stage progress for later resumption.
Prepare a conference talk from a completed paper, including an outline, Beamer slides, editable PPTX, speaker notes, and a full script. Polish the visuals, check exported files, and optionally audit claims, citations, and anonymity.
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "this feels too complicated", "too many features", "product taste", "saying no", or "is this good enough to ship". Also trigger when critiquing a UI, feature, or roadmap for focus and simplicity, cutting scope to the essential, or pressure-testing the whole experience from first run to daily use. Covers the simplicity audit, the no list, design-is-how-it-works, end-to-end ownership, demo culture, and a Jobs-style review protocol with binary verdicts. For visual design fundamentals, see refactoring-ui. For usability audits, see ux-heuristics. For detail polish, see microinteractions.
The English summary is being prepared. Showing the original description.
Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or weak e2e) and you want system-level tests — "set up e2e", "add end-to-end tests", "scaffold a test gate".
The English summary is being prepared. Showing the original description.
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the user experience, or visualize touchpoints and pain points. Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map. Also triggers when the team has departmental views of users but no shared map of what the experience actually feels like.
The English summary is being prepared. Showing the original description.
Do a task end-to-end — implement, PR, CI loop, ship. ONLY invoke when the user explicitly types `/do` or `$do`; never auto-select from a natural-language request, even one that sounds like an end-to-end task.
The English summary is being prepared. Showing the original description.