3,451 件 ・ 関連度順
概要と使いどころ
Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware cryptanalysis, encryption analysis, key recovery assessment, or ransomware decryption feasibility.
日本語の概要は準備中です。原文の説明を表示しています。
Execute the implementation planning workflow using the plan template to generate design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Perform cross-artifact consistency analysis across spec.md, plan.md, and tasks.md. Use after task generation to identify gaps, duplications, and inconsistencies before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Break down implementation plans into actionable task lists. Use after planning to create a structured task breakdown. Generates tasks.md with ordered, dependency-aware tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate custom quality checklists for validating requirements completeness and clarity. Use to create unit tests for English that ensure spec quality before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Execute the implementation plan by processing and executing all tasks defined in tasks.md
日本語の概要は準備中です。原文の説明を表示しています。
Synchronize project documentation with recent code changes, refactors, and feature implementations in the current branch.
日本語の概要は準備中です。原文の説明を表示しています。
Start a working doc — a drafting space where spec-level and implementation thinking co-exist before splitting into specs, plan, and test cases
日本語の概要は準備中です。原文の説明を表示しています。
Audit this card's mockups or implementation against the design library
日本語の概要は準備中です。原文の説明を表示しています。
Review the product engineer's post-implementation testing notes for how thoroughly they cover the card's requirements and risk, and whether regression-worthy cases are automated at the right level of the test hierarchy
日本語の概要は準備中です。原文の説明を表示しています。
Review implementation for common security vulnerabilities
日本語の概要は準備中です。原文の説明を表示しています。
Secure Solana wallet generation using official Solana Labs libraries — Ed25519 keypairs, memory zeroization, vanity address generation, offline-only operation, and multi-language implementations (Rust, TypeScript, Bash).
日本語の概要は準備中です。原文の説明を表示しています。
Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions "qedgen", "lean proof", "formal proof", "verify my code", "prove correctness", "formal verification", or wants mathematical guarantees about their implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.
日本語の概要は準備中です。原文の説明を表示しています。
Integration review after stable code. Audit tier for high-risk surfaces; planning tier for optional low-risk review. Produces a review note and fix list — no implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Development methodology rules (Clean Architecture, TDD flow, 3-Strike rule, decision priority) that govern planning, implementation, and review. Load before designing, staging, implementing, or reviewing code changes.
日本語の概要は準備中です。原文の説明を表示しています。
Tutor the user step by step on a plan, implementation, codebase, or topic to pay down understanding debt left by AI tooling. Explicit invocation only.
日本語の概要は準備中です。原文の説明を表示しています。
Quiz the user on a plan, implementation, or codebase to pay down understanding debt left by AI tooling. Explicit invocation only.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a codebase as a read-only senior advisor, prioritize evidence-backed improvements, and write self-contained implementation plans. Use for codebase audits, improvement roadmaps, focused planning, plan review, plan reconciliation, or executing an existing improve plan through an isolated Codex worktree. The advisor never edits source code; execution uses codex-improve and returns to the main agent for review.
日本語の概要は準備中です。原文の説明を表示しています。
Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Review product designs before engineering handoff or release for flow and state coverage, business-rule alignment, implementation clarity, accessibility, responsiveness, analytics, and testability.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when developing code using Test-Driven Development (TDD) methodology. Use this skill when the user wants to write tests first before implementation, needs guidance on the red-green-refactor cycle, or explicitly requests TDD-style development. Triggers include requests like "develop this feature using TDD", "write tests first", "help me with test-driven development", or "implement this following TDD practices". The skill guides through writing failing tests, implementing minimal code to pass, and refactoring while maintaining test coverage.
日本語の概要は準備中です。原文の説明を表示しています。