Results for “test”

Create app store screenshots and preview videos for Apple App Store and Google Play with exact platform specs, device mockups, and gallery ordering guidance.

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Guides the creation of high-quality MCP servers that let LLMs interact with external services through well-designed tools, covering planning, implementation, testing, and evaluation.

Submits or updates a Wall of Apps entry in the App-Store-Connect-CLI repository using the `asc apps wall submit` command, with dry-run preview and confirmation.

Optimize non-signup forms such as lead capture, contact, demo request, application, survey, quote, and checkout forms to maximize completion while preserving data usefulness.

Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.

Use before any writing to stress-test whether a result clears Science's (AAAS) desk-reject filter — broad significance and general interest across disciplines. Decides Science vs Science Advances vs a specialist journal before you invest in prose.

Use when deciding which nejm-* sub-skill to invoke next, or when sequencing a clinical manuscript from significance test through response to reviewers for The New England Journal of Medicine. Routes — it does not replace — the specialized skills.

Use when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.

Exploit SSRF vulnerabilities in AWS EC2-hosted applications to extract IAM credentials and User Data from the Instance Metadata Service, including techniques for bypassing basic filters against IMDSv1.

Threat modeling workflow for software systems: scope, data flow diagrams, STRIDE analysis, risk scoring, and turning mitigations into backlog and tests. Use when designing new features, reviewing architecture changes, handling sensitive data, or hardening auth/payment/multi-tenant flows.

Diagnose and fix failing CircleCI builds quickly and safely. Use when users ask to investigate failed CircleCI jobs, triage flaky pipelines, identify root causes from logs, and implement minimal fixes in configuration, test setup, or build-related code paths.

Write, review, debug, or test Python datetime, date, timedelta, timezone, and zoneinfo code, especially UTC conversion, DST gaps and folds, recurring local schedules, parsing, and interval boundaries.

This skill should be used when the user asks to "run pentest commands", "scan with nmap", "use metasploit exploits", "crack passwords with hydra or john", "scan web vulnerabilities with nikto", "enumerate networks", or needs essential penetration testing command references.

Create implementation-ready engineering plans for WelineFramework. Use in Plan mode, or when the user requests detailed requirements, code modification points, task cards, test cases, acceptance criteria, risk and rollback design, or a handoff package for execution-oriented AI agents.

Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.

Configure ViewModel state emission with StateFlow, SharedFlow, and sealed UiState classes in Android. Use for state modeling and sharing policies; defer generic lifecycle collection, navigation-event plumbing, Hilt injection, test code, and configuration-change recipes to their specific skills.

Use when making changes to existing systems to ensure those changes don't break existing functionality. This skill provides procedures for identifying at-risk areas, adding regression tests, and validating changes don't cause unintended side effects.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Prevent repeated AI coding-agent mistakes by turning failures into durable instructions, drift checks, regression tests, failure memory, and adoption reports tailored to the target repository.

Simulates real-world adversary operations to test an organization's detection and response capabilities through the full attack lifecycle, from reconnaissance to objective completion.

Automates SOC 2 Type II audit preparation including gap assessment, evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring.

Escribe mensajes de commit, PRs e issues con tono humano en español rioplatense o técnico en inglés, siguiendo reglas de atomicidad, límite de 300 líneas y verificación previa de tests.

Conducts end-to-end user research, from study design through behavioral insight synthesis, using frameworks like Nielsen's Heuristics, SUS, and User Journey Mapping.

Mantém a coerência visual entre peças geradas por IA usando modelo fixo, prompt base, seed e referência de estilo, com teste de coerência e biblioteca de prompts.

Audits AGENTS.md and CLAUDE.md files for bloat, redundancy, and ineffective rules, then runs A/B evals to prove which instructions are dead weight.

Solve single- and multi-objective optimization problems with NSGA-II/III, MOEA/D, and other evolutionary algorithms, including Pareto front analysis, constraint handling, and benchmarking on standard test problems.

Routes authentication and authorization testing efforts by identifying the primary attack surface — login mechanics, object authorization, browser trust boundaries, or identity protocols such as JWT/OAuth/SAML — before selecting a deeper skill.

Shared vocabulary for designing deep modules — a small interface hiding a lot of behavior. Use when designing or improving a module's interface, deciding where a seam belongs, deciding whether to extract or merge modules, or making code more testable.

Analyze product data and manage product tooling in PostHog. Use when the user wants product analytics or insights, HogQL/SQL queries, feature flags, experiments and A/B tests, error tracking, session replay, surveys, LLM analytics, dashboards, data warehouse, or PostHog documentation.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

The learner teaches the concept to the AI, which plays a curious novice peer and identifies gaps through authentic questions. Use when the learner wants to test their understanding — teaching forces a different kind of organisation than studying.

Co-author structured documents (specs, PRDs, RFCs) through a 3-stage workflow: context gathering, drafting, and reader testing. Use when writing proposals, technical specs, or similar structured content. Repo decision-memory system (INDEX.md, rejected alternatives, agent rules) → docs-adr.

Maximize form completion rates for lead capture, contact, demo request, application, survey, quote, and checkout forms by diagnosing friction and applying evidence-based optimizations.

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Self-contained code review checklist — formatting, type safety, duplication, readable conditions, logic-out-of-UI, test coverage, comment quality. Adapts to whatever tooling the project actually has (skips Prettier/TypeScript/test-runner checks if unconfigured). Use before merging, after completing a feature, or any time you want a second pass on code quality. In Claude Code, prefer the official `code-review` skill or `pr-review-toolkit`/`feature-dev` code-reviewer agents instead — both are real, installed, and go deeper than this checklist. This copy exists for Codex/Cursor portability, where those agents aren't available.