테스트·보안 스킬

Run user-authorized black-box web security tests and evidence-based reports. Use for 黑盒安全测试、渗透测试、数据泄露、未授权访问、公开 JS/API、登录爆破防护、CORS 或安全响应头检查。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GStack review method for pre-landing code, diff, PR, or implementation review focused on bugs, regressions, missing tests, and release risks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GStack CSO method for broad infrastructure-first security posture review, threat areas, severity calibration, and safe remediation scope.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GStack QA method for web/UI behavior verification and narrow fix loops when the user explicitly allows QA to repair issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GStack investigation method for bugs, incidents, failing tests, regressions, and unclear behavior where evidence and root cause should precede fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GStack developer-experience plan review for setup, local commands, docs, test loops, onboarding friction, and maintainability before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GStack engineering-manager plan review for architecture, data flow, APIs, migrations, edge cases, tests, performance, release risk, and implementation boundaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GStack report-only QA method for checking web or UI behavior, documenting blockers, and preserving evidence without modifying code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Codex adapter for Garry Tan's full gstack methodology across CEO/product pressure, CTO architecture, design, engineering, QA, security, shipping, documentation, and retrospectives. Use when the 总控/CEO or 架构/CTO role needs gstack method routing, implementation-plan hardening, or the user says gstack should help a role.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematic testing methodology for exhaustive branch coverage, edge case identification, and production bug prevention. Use when PR review reveals incomplete test coverage, when tests pass but users report bugs, when code changes break existing features, when verifying all branches and edge cases before merge, when analyzing "it works on my machine" issues, when planning test strategy for new features, or when debugging flaky tests and race conditions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, restyle, or rebuild Chinese academic PowerPoint presentations from papers, theses, reports, figures, notes, templates, screenshots, or visual mockups. Use for presentation planning, Template DNA extraction, slide mockups, template-based editable PPTX generation, editable reconstruction, rendering, and final QA.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enforce traceability from natural-language intent to machine predicates, final observables, evidence, and owner-readable acceptance. Use when conducting any audit, review, QA pass, parity or compliance check, security assessment, code or architecture review, visual or behavioral comparison, data validation, system verification, completion gate, or claim that an implementation satisfies a human request.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds a talk as a beatdeck - a fixed 1920x1080 React stage where one click is one beat, with authored motion, presenter view, overview, and an offline self-contained build. Covers turning source material (PPTX, Keynote/PDF export, Markdown, notes) into a content audit and a scene/beat map, choosing or applying a theme, writing scene layers, automatic beats, and verifying every beat with npm run verify. Use whenever the task is creating, porting, restyling, rehearsing or fixing a presentation, talk, keynote, slide deck or conference session that should feel like a live system rather than slides, or whenever the repo contains src/beatdeck/.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a developer needs a ChatGPT Apps submission import file from an MCP server. Inspect the implementation, generate chatgpt-app-submission.json with app info, tool-hint justifications, positive and negative test cases, then report review findings and outputSchema warnings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are a security engineer. Auto-detect package managers, scan for vulnerabilities and leaked secrets, fix what's fixable, report the rest. Covers the dependency tree and tracked files — reviewing a pending diff's security belongs to a platform-native security-review skill when present.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan dependencies and tracked files for known vulnerabilities and leaked secrets; fix what's fixable, report the rest. For reviewing a pending diff, prefer a platform security-review skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to add, fix, or optimize schema markup / structured data — "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "star ratings in search." For broader SEO, see seo-audit. For AI search optimization, see ai-seo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are a senior test engineer. Auto-detect all test layers (unit, integration, frontend, backend, E2E/system), run them all, write more if coverage is below threshold, and loop until everything passes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to audit or diagnose SEO issues — "technical SEO," "why am I not ranking," "meta tags review," "my traffic dropped," "Google update hit me," "core web vitals," "crawl errors," "indexing issues," or even a vague "my SEO is bad." For pages at scale, see programmatic-seo. For structured data, see schema-markup. For AI search, see ai-seo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cut a versioned release: smoke-test the package, bump the version, tag, publish to PyPI/npm/Docker, and verify the published artifact. Use when asked to release or ship a version.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect and run every test layer (unit, integration, E2E), add tests where coverage is below threshold, and loop until green. Use when asked to test or raise coverage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan, map, or restructure a website's page hierarchy, navigation, URL structure, or internal linking — "sitemap," "information architecture," "IA," "breadcrumbs," "what pages do I need," "how should I organize my site." NOT for XML sitemaps (technical SEO — see seo-audit). For structured data, see schema-markup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.