Results for “behavior-validation”

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.

Defines end-to-end user experience behavior and interaction logic, covering flow design, state machines, error recovery, validation, accessibility, and testable acceptance criteria.

Use this skill for removing accidental complexity, reducing duplication, clarifying boundaries, preserving behavior. Trigger when the task involves programming work related to Code Simplification, production implementation, audits, debugging, strategy, or validation.

Use this skill for crawler behavior, log files, sitemap/indexation analysis, crawl-budget diagnostics. Trigger when the task involves agent profile work related to Crawler Analyst Agent, implementation, audits, debugging, strategy, or validation.

Review a code change for changed behavior that could regress without reliable verification catching it. Use when checking whether a change is adequately verified.

Use when the team needs a strategy for validation errors, API failures, job retries, user-facing error UX, observability, or recovery behavior. Trigger on requests to design error handling across frontend, backend, and integrations.

Write and review unit tests for Vue 3 + TypeScript + Vitest + Pinia codebases, covering components, composables, and stores with behavior-first assertions.

Verify project behavior anchors — compilation, tests, and interaction checks after autonomous runs. NOT the Claude Code built-in /verify (which runs the app to observe a single change working) — this one walks the CLAUDE.md "Features (Behavior Anchors)" list.

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

Agent validation overhaul: reward weight overrides, fitness decline gate, pinned data, staged experiments

Agent validation v4.3.0 — Make agents act effectively by disabling harmful actions, lowering gates, and injecting cross-run learning

Applies practical test-first and regression testing to behavior changes, bug fixes, state transitions, and public contracts.

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Use in TURBO mode before finalizing implementation, architecture, UI/UX, 3D web, mobile, SEO/PPC/growth, or programming work.

Behavior-driven development: Discovery → Formulation → Automation. Use when the user wants to build features or fix bugs via Gherkin scenarios and the BDD lifecycle, or mentions BDD/Gherkin/Executable Specifications. Delegates test implementation to /mattpocock:tdd.

Validate user claims against codebase and git history, trace to root cause, and propose a fix

Detect anomalous user activities including impossible travel, unusual access patterns, privilege abuse, and insider threats using SIEM-based behavioral baselines and statistical analysis.

Diagnoses why someone knows what to do but doesn't do it, using Adlerian psychology to identify root causes like procrastination, perfectionism, or avoidance.

Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack) Voice triggers (speech-to-text aliases): "speed test", "check performance".

Verify code changes work by running them. Proves through execution, not just inspection.

Validate Pleasur.ai Stage 01 blog-keyword candidates with the Business potential, Intent, and Difficulty method using current Ahrefs evidence. Use before AIO vetting and prioritization to reject poor business fits, mismatched search intent, and SERPs the brand cannot realistically win.

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Validates rendered UI with browser or Playwright screenshots after implementation, redesign, responsive changes, or visual regressions.

Validates generated SRS documents against IEEE 830-1998, fixing errors and reporting warnings.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Execution discipline with agency, instinct detection, critical safety rules, trust layer, and error resilience. v2.7 adds timeout handling, checkpointing, and decision logging.

Verify that a change really works before you claim completion

Writes, audits, and troubleshoots Salesforce validation rules, covering formula best practices, bypass patterns, and integration pitfalls.