Playwright browser automation. Navigates URLs, takes screenshots, checks accessibility tree, interacts with UI elements, and reports findings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
테스트 설계, 취약점 진단, 품질 보증 (1.4만건)
Playwright browser automation. Navigates URLs, takes screenshots, checks accessibility tree, interacts with UI elements, and reports findings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomous project bootstrapper. Generates complete project from a description — structure, code, tests, docs, config. Orchestrates ba → plan → design → fix → test → docs → git in one pipeline. The "0 to production-ready" skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code quality review — patterns, security, performance, correctness. Finds bugs, suggests improvements, triggers fix for issues found. Escalates to opus for security-critical code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy + marketing orchestrator. Use when user says 'launch', 'ship to production', 'deploy and announce', or 'go live'. Runs the full pipeline — pre-flight tests, deployment, live verification, marketing asset creation, and announcement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates agent claims against evidence trail. Use when verifying an agent has actually done what it claims — auto-fires at workflow end. Catches 'done' without proof, 'tests pass' without output, 'fixed' without verification. Called by cook and team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply code changes and fixes. Writes implementation code, applies bug fixes, and verifies changes with tests. Core action hub in the development mesh.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Meta-validator for HARD-GATEs. Use when auditing whether a skill's mandatory constraints were actually followed during a workflow (not just claimed). Called by cook, team, and audit for discipline compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-implementation red-team analysis. Use when a plan is high-risk, critical path, or expensive to reverse. Challenges plans before code is written — finds edge cases, security holes, scalability bottlenecks, error propagation risks, and integration conflicts. Catches flaws at plan time (10x cheaper than post-implementation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate and resolve Course Management Platform CloudWatch alert issues end to end. Use when Codex is asked to inspect a CMP GitHub alert issue, pull dev or production AWS logs, diagnose 5xx responses or failed background work, fix an incident with test-driven development, validate a fix in dev, or deploy and verify an authorized production fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintainer-only skill for refreshing VitaeContext wiki knowledge from official sources. Use only from a local repository clone when a maintainer asks to refresh one module, audit all module wiki entries, or audit module source lists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php + tests/bootstrap.php wiring, phpunit.xml.dist <env> pins (force DB name + table prefix, default connection coordinates, pin CRAFT_ENVIRONMENT against server-scoped locks), why --configuration= defeats DB isolation, throwing fail-closed DB guards, installing the plugin under test, process-timezone pinning, per-test site fixtures, idempotent Install migrations, stale service caches when components get swapped, muting audit sinks, queue stubs, factories, HTTP/DB assertions, CI jobs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing, and debugging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test a product concept with Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions, ending in a complete PRFAQ document. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up, adopt, refresh, or audit a repository's agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfalls. Use when invoked by name
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate automated API and end-to-end tests for implemented features. Use when the user says "create qa automated tests for [feature]"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test a half-formed idea in a questioning conversation, with different personas probing its weak points, until the user can act on it or drop it with confidence. Optionally writes a short brief for planning skills to build on. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs the evals of a BMad skill through the agent harness the user works in and reports what they show: baseline against the bare model, variant against a stripped or prior version, quality against a rubric, and trigger accuracy of the description with an optional optimization loop. Use when the user asks to evaluate, benchmark, test the triggers of, grade, or compare versions of a skill, or when the bmad-toolsmith skill asks for an eval of a skill it built.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews Rust test code for unit test patterns, integration test structure, async testing, mocking approaches, and property-based testing. Covers Rust 2024 edition changes including async fn in traits for mocks,
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute YAML test plan, stop on first failure, output rich debug prompt
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze repo, detect stack, trace changes to user-facing entry points, generate E2E YAML test plan
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vitest testing framework patterns and best practices. Use when writing unit tests, integration tests, configuring vitest.config, mocking with vi.mock/vi.fn, using snapshots, or setting up test coverage. Triggers on describe, it, expect, vi.mock, vi.fn, beforeEach, afterEach, vitest.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.