テスト設計、脆弱性診断、品質保証（1.3万 件）
概要と使いどころ
Build and harden high-performance APIs with strong security controls, endpoint budgets, rate limiting, and resilience patterns. Use when tasks involve API latency/throughput tuning, abuse resistance, authz hardening, or API release gates.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates before build/package.
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, and stabilize automated tests in this repository (unit, integration, and E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.
日本語の概要は準備中です。原文の説明を表示しています。
Base implementation skill. Use for code changes, bug fixes, refactors, and script work across .NET/C#, backend APIs, database/ORM, Vue/Quasar frontend, Rust, PowerShell, Docker, K8s, CI/CD, security, observability, and SRE domains. Specialized skills extend this as a base.
日本語の概要は準備中です。原文の説明を表示しています。
Design and enforce privacy and data protection controls across application, API, and database layers. Use when tasks involve PII handling, retention/deletion policies, consent, data minimization, auditability, or compliance-oriented architecture changes.
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, and stabilize automated tests (unit, integration, E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.
日本語の概要は準備中です。原文の説明を表示しています。
Git commit and pull request conventions. USE FOR: writing commit messages; checking Conventional Commits and gitmoji; branch naming; rebase workflow on develop; PR titles and target branch. PRIORITY: this skill overrides other rules when creating commits/PRs. DO NOT USE FOR: code implementation (use code-implementation skill); testing (use test-writing skill); general documentation (use documentation skill).
日本語の概要は準備中です。原文の説明を表示しています。
Unit and integration testing strategy. USE FOR: writing tests; coverage improvements; vitest specs; test refactoring. DO NOT USE FOR: production code changes (use code-implementation skill); documentation (use documentation skill); commits (use commit-conventions skill).
日本語の概要は準備中です。原文の説明を表示しています。
Unit and integration testing strategy for create-vue-dsfr. Use for writing, updating, or refactoring Vitest specs and test coverage. Read the shared project skill before acting.
日本語の概要は準備中です。原文の説明を表示しています。
Use after building a feature — explore it in a real browser to find what nobody predicted, then turn each finding into a deterministic test that guards it forever. Covers the agentic pass, what to generate vs hand-write, and how to skip honestly when a capability is missing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a new feature needs a table, column or capability — evolving the schema so the new thing joins the permission, audit and RLS contract instead of sitting outside it. Covers the DDL/DML split, the resource/capability wiring, and the self-verifying migration.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building, testing or previewing site-os — the BUILD_TARGET=stable dist directory, the four verification gates (build, test, env:check, brand:check), the preview servers on :3000 and :3100, and the failure modes that look like bugs but are not.
日本語の概要は準備中です。原文の説明を表示しています。
Use FIRST when someone asks for a new feature or a change to an existing one — before any schema, code or test. Works out what is actually being asked for, whether to build it or integrate a third party (Trustpilot, Stripe, Calendly and the like), where the data lives, who may do what, and what happens when the vendor is down. Produces a decision, then hands to feature-schema.
日本語の概要は準備中です。原文の説明を表示しています。
Retroactively audit and fill Nyquist validation gaps for a completed phase
日本語の概要は準備中です。原文の説明を表示しています。
Audit milestone completion against original intent before archiving
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
日本語の概要は準備中です。原文の説明を表示しています。
Generate tests for a completed phase based on UAT criteria and implementation
日本語の概要は準備中です。原文の説明を表示しています。
Cross-phase audit of all outstanding UAT and verification items
日本語の概要は準備中です。原文の説明を表示しています。
Retroactively audit an executed AI phase's evaluation coverage — scores each eval dimension as COVERED/PARTIAL/MISSING and produces an actionable EVAL-REVIEW.md with remediation plan
日本語の概要は準備中です。原文の説明を表示しています。
Create phases to close all gaps identified by milestone audit
日本語の概要は準備中です。原文の説明を表示しています。
Tests APIs for Broken Function Level Authorization (BFLA) vulnerabilities where regular users can invoke administrative functions or access privileged API endpoints by directly calling them. The tester identifies admin and privileged endpoints, then attempts to access them with regular user credentials by manipulating HTTP methods, URL paths, and request parameters. Maps to OWASP API5:2023 Broken Function Level Authorization. Activates for requests involving BFLA testing, admin endpoint bypass, function-level access control testing, or API privilege escalation.
日本語の概要は準備中です。原文の説明を表示しています。
Discover and exploit broken link hijacking vulnerabilities by identifying references to expired domains, decommissioned cloud resources, and dead external services that can be claimed by an attacker.
日本語の概要は準備中です。原文の説明を表示しています。
Identifying and exploiting Insecure Direct Object Reference vulnerabilities to access unauthorized resources by manipulating object identifiers in API requests and URLs.
日本語の概要は準備中です。原文の説明を表示しています。