3.2만건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code implementation, refactoring, and bugfixes for create-vue-dsfr. Use for implementing features, refactoring code, or fixing bugs. Read the shared project skill before acting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git commit, branch, and pull request conventions for create-vue-dsfr. Use before creating commits, branches, issues, or PRs. This skill has priority over other project skills for commit and PR work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code implementation, refactoring, and bugfixes. USE FOR: implementing features; refactoring code; fixing bugs; modifying existing code. DO NOT USE FOR: writing tests (separate skill); documentation (separate skill); commit conventions (separate 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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate built features through conversational UAT
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Display project statistics — phases, plans, requirements, git metrics, and timeline
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Retroactive 6-pillar visual audit of implemented frontend code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, query, and inspect the project knowledge graph in .planning/graphs/
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start a new milestone cycle — update PROJECT.md and route to requirements
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Show available GSD commands and usage guide
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (the agent picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifies and exploits insecure local data storage vulnerabilities in Android and iOS mobile applications including unencrypted databases, world-readable files, insecure SharedPreferences, plaintext credential storage, and improper keychain/keystore usage. Use when performing mobile penetration testing focused on OWASP M9 (Insecure Data Storage) or assessing compliance with MASVS-STORAGE requirements. Activates for requests involving mobile data storage security, local storage exploitation, SharedPreferences analysis, or mobile data leakage assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect and exploit race condition vulnerabilities in web applications using Turbo Intruder's single-packet attack technique to bypass rate limits, duplicate transactions, and exploit time-of-check-to-time-of-use flaws.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Testing WebSocket implementations for authentication bypass, cross-site hijacking, injection attacks, and insecure message handling during authorized security assessments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifying and exploiting Insecure Direct Object Reference vulnerabilities to access unauthorized resources by manipulating object identifiers in API requests and URLs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifying and exploiting SSRF vulnerabilities to access internal services, cloud metadata, and restricted network resources during authorized penetration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not display but the API transmits. This maps to OWASP API3:2023 Broken Object Property Level Authorization. Activates for requests involving API data leakage testing, excessive data exposure, response filtering bypass, or API over-fetching.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scans GitHub Actions workflows and CI/CD pipeline configurations for supply chain attack vectors including unpinned actions, script injection via expressions, dependency confusion, and secrets exposure. Uses PyGithub and YAML parsing for automated audit. Use when hardening CI/CD pipelines or investigating compromised build systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.