hmj1026
UserAI Agent Skill for building verified, citation-backed courses in Google NotebookLM
Categories
Indexed Skills (101)
notebooklm-course-builder
以條件式瀏覽器自動化或 14 階段嚮導建構 NotebookLM 課程教材。適用於：(1) 將課程大綱轉為包含來源引用、逐節講義、Quiz 與 Study Guide 的完整課程；(2) 規劃 Notebook 與研究分群、來源審核、Coverage 分析；(3) 自動操作 NotebookLM 或延續既有建置進度。
claude-health
Claude Code config health check + plugin sync. Use when: auditing .claude/ structure, checking naming, verifying hook setup, detecting plugin version drift, syncing installed assets. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations.
code-explore
Pure Claude code investigation. Use when: tracing execution paths, understanding architecture, diagnosing issues. Not for: dual-perspective review (use code-investigate), code review (use codex-code-review). Output: analysis report with findings.
code-investigate
Dual-perspective code investigation. Use when: deep code analysis needing both Claude and Codex perspectives. Not for: quick exploration (use code-explore), code review (use codex-code-review). Output: integrated findings from dual analysis.
dhpk-session-usage-audit
Audits dhpk usage evidence in the current user home, correlates session failures with installed agents and package versions, verifies candidate defects, and prepares deduplicated GitHub issue evidence. Not for: remote fleet scans or automatic source changes. Output: redacted report, verified findings, and confirmed issue handoff. Explicit invocation only.
skill-health-check
Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
yii1-security-audit
Yii 1.1（PHP 5.6）框架安全白盒靜態審計。Use when：對 Yii 1.1 專案查找漏洞、驗證 accessRules/checkAccess/CSRF/SQL injection/CUploadedFile/Session 設定，或框架安全複查（即使用戶只說「檢查這個 Controller 有沒有安全問題」也應觸發）。Not for：Yii2 專案、非 PHP 專案、純業務邏輯演算法審查。Output：依 AUTH/CSRF/XSS/SQL/CFG/LOGIC/FILE 分類、含檔名:行號 + 可觀測 PoC + Yii API 修復建議的審計報告。
adaptive-dev-workflow
Workflow router for substantial changes. Use when: a feature, bugfix, refactor, security, perf, or OpenSpec change needs classifying into Feature Delivery, Bug Investigation & Fix, or Lightweight Maintenance before heavy context loads. Not for tiny edits, investigation already underway, code review, or apply-ready OpenSpec tasks. Output: workflow classification + required artifacts + gate checklist.
agent-architecture-audit
Full-stack diagnostic for agent and LLM applications — audits the 12-layer agent stack for wrapper regression, memory pollution, tool-discipline failures, hidden repair loops, and rendering corruption. Use when: shipping an agent/LLM feature, an agent degrades after adding wrapper/memory/tool layers, the same model works in the playground but breaks in your wrapper, or debugging agent behavior >15 min with no root cause. Not for: general code debugging, code review, or security scanning (use security-review). Output: severity-ranked findings with code-first fixes.
agy-commit
Delegate git smart commit to agy-cli. Use when: committing changes via agy-cli's git-smart-commit skill (offload commit batching to Antigravity). Not for: a single simple commit, or when agy-cli is unavailable. Output: grouped commits created by agy-cli plus a git log summary.
agy-fast-worker
Offload a self-contained, clearly-specified mechanical task to the agy (Antigravity) CLI backend and relay its result, with the heavy output quarantined in the agy-fast-worker subagent. Use when: a mechanical batch with a precise task spec (target files + change intent + verification command) should run on the cheap high-throughput agy tier (default model `Gemini 3.5 Flash (High)`) instead of the in-process sonnet fast-worker, and the agy CLI is available. Not for: ambiguous specs (escalate), work needing this conversation context (agy sees a fresh session — the prompt must be self-contained), or the default in-process path (use plain `fast-worker`). Output: the verification result + the working-tree-derived edited-file list, or an honest BLOCKED report — never simulated.
bug-fix
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.
dhpk-feature-verify
Feature verification (READ-ONLY, P0-P5). Use when: verifying feature behavior after deployment, validating API responses, diagnosing production issues, post-deploy smoke test. Not for: modifying data (use dhpk-adaptive-dev-workflow in feature mode), code review (use dhpk-change-review), writing tests (use dhpk-tdd-workflow), security audit (use dhpk-security-review). Output: a P0-P5 verification report with pass/fail evidence per check.
dhpk-issue-analyze
GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use dhpk-adaptive-dev-workflow in bug mode), code exploration (use dhpk-codebase-exploration). Output: classified analysis + verdict assessment + investigation strategy.
dhpk-opsx-apply-goal
Unattended OpenSpec goal generator for an existing change-id that needs a bounded fresh-session implementation goal. Not for: authoring, applying in the current session, verifying, syncing, or archiving. Output: an analysis summary plus one pasteable /goal condition, or a hard-stop report.
dhpk-project-setup
Project configuration initialization: first-time setup, auto-detecting the framework, and replacing CLAUDE.md placeholders. Not for: ongoing config checks (use dhpk-claude-health), skill creation (use dhpk-create-skill). Output: configured CLAUDE.md + project settings + rules + hooks.
dhpk-prompt-optimize
Rewrite a raw task prompt into a model-aware, effort-calibrated version before you run it. Use when: the user asks to "optimize this prompt", "improve this prompt for Claude", "what effort should I use", "make this a good API prompt/template", or pastes a rough instruction before a big Claude Code or API task. Detects the target model (current session or a named one), classifies task complexity, recommends an effort level (low/medium/high/xhigh/max, plus the dhpk agent-frontmatter/Claude Code equivalent), asks up to 4 AskUserQuestion questions only for missing required info, then applies model-specific behavioral rewrites. Not for: generic few-shot/CoT/template technique coaching with no model or effort selection (use prompt-engineering-patterns), or auditing token/cache budget (use dhpk-harness-budget). Output: optimized prompt block + effort recommendation with rationale + bullet list of rewrites applied.
dhpk-release-creator
Cuts a new release of a software project or plugin, coordinating release configuration, version files, changelog, validation, and the fixed git/PR/tag/CI sequence. Not for: PHP package publication or ordinary commits. Output: a validated release preparation or publication result with the human merge gate preserved.
dhpk-adaptive-dev-workflow
Adaptive delivery workflow for substantial changes. Use when: a feature, bugfix, refactor, security, perf, or OpenSpec change needs one classification into Feature Delivery, Bug Investigation & Fix, or Lightweight Maintenance, with branch behavior and gates before heavy context loads. Not for tiny edits, investigation already underway, code review, or apply-ready OpenSpec tasks. Output: workflow classification + branch artifacts + delivery-loop gate checklist.
dhpk-agent-architecture-audit
Full-stack diagnostic for agent and LLM applications — audits the 12-layer agent stack for wrapper regression, memory pollution, tool-discipline failures, hidden repair loops, and rendering corruption. Use when: shipping an agent/LLM feature, an agent degrades after adding wrapper/memory/tool layers, the same model works in the playground but breaks in your wrapper, or debugging agent behavior >15 min with no root cause. Not for: general code debugging, code review, or security scanning (use change-verdict). Output: severity-ranked findings with code-first fixes.
dhpk-agy-commit
Delegates git smart commit to agy-cli's dhpk-git-smart-commit skill, offloading commit batching to Antigravity. Not for: a single simple commit, or when agy-cli is unavailable. Output: grouped commits created by agy-cli plus a git log summary.
dhpk-agy-fast-worker
Use when offloading a precise self-contained mechanical task to the agy CLI when available. Require target files, intent, and verification command; keep output in the agy-fast-worker subagent. Not for ambiguity, conversation-dependent work, or default fast-worker use. Output: verified edited files or honest BLOCKED evidence.
dhpk-change-review
Code review using Codex MCP. Use when: PR review, code audit, or a second opinion on changes. Not for: document review (use dhpk-doc-review), security-specific audit (use dhpk-security-review), or test coverage review (use dhpk-test-review). Output: severity-ranked findings with file:line evidence, a reviewer-degradation state, and a fail-closed merge gate.
dhpk-claude-health
Claude Code config health check + plugin sync: audits .claude/ structure, checks naming, verifies hook setup, detects plugin version drift, and syncs installed assets. Not for: skill quality (use dhpk-skill-health-audit), code review (use dhpk-change-review). Output: health report + fix recommendations.
dhpk-codebase-exploration
Explore an unfamiliar codebase with a focused symbol/flow trace, optionally run an independent second perspective, or request a depth-controlled explanation. Use when: tracing execution, understanding architecture, or diagnosing a code path. Not for: change review, security audit, or implementation. Output: evidence-backed flow findings with explicit gaps.
dhpk-codex-architect
Codex architecture consulting, including bounded adversarial option convergence. Use when: designing features, evaluating architecture, comparing options, or running independent proposal and critique rounds. Not for: implementation (use dhpk-codex-implement), code review (use dhpk-change-review). Output: architecture advice + design recommendations.
dhpk-codex-bridge
Use when an explicit CLI handoff or blind second opinion should go to the GPT-5.6 family through one-shot codex exec: gpt-5.6-sol/high for read-only or gpt-5.6-luna/xhigh for workspace-write. Not for context-dependent or iterative work, or retired MCP codex-* review loops. Output: the bounded, redacted codex exec result.
dhpk-codex-implement
Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use dhpk-change-review), architecture advice (use dhpk-codex-architect). Output: implemented code + review loop.
dhpk-composer-package-hygiene
Composer-published package contract review. Use when: deciding semver, auditing public API or composer.json, validating Laravel package discovery, or coordinating a package release. Not for: everyday application code, language idioms, or Laravel-specific authoring mechanics. Output: a contract verdict, audited manifest, or release gate backed by the package-contract reference.
dhpk-create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /dhpk:deep-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard. Not for: feature-level problem-space analysis (use /dhpk:deep-analyze for 1-requirements.md lifecycle doc), tech specs (use dhpk-tech-spec), code implementation (use dhpk-adaptive-dev-workflow in feature mode). Output: request ticket with status tracking, referencing parent dhpk-tech-spec.
dhpk-create-skill
Creates a new Claude Code skill, or refactors an existing one to dhpk conventions (lean SKILL.md + progressive disclosure, trigger-rich description, validation gate), from a request to "create a skill", "make a skill", "refactor this skill", or to capture a workflow as a reusable skill. Not for: writing a slash command (use command-creator) or auditing skill quality only (use /check-skill). Output: a validated skill package with an explicit diff summary and routing/verification evidence.
dhpk-cross-agent-sync
Compares Claude-first configuration across Codex, Antigravity, AGY native plugins, and Cursor to align cross-platform skills, commands, agents, hooks, or orchestration. Produces reviewable plans, OpenSpec tasks, dry-run/apply reports, and a configured-platform PASS/FAIL/BLOCKED validation gate (NOT_CONFIGURED/SKIP_INCOMPATIBLE stay visible without failing it; legacy PARTIAL is a deprecated compat field). Not for reverse sync, single-platform edits, or missing Claude source.
dhpk-deploy-list
Cross-project deploy file-list generator (schema=v1). Use when: building a deploy/release checklist from git history, listing which files to ship for a deploy, 部署清單, deploy list/checklist. Scope via --anchor (in-code markers), --deploy-commits (pinned commits), or whole base..head; filters dev-only paths (tests, docs, CI, AI harness) and groups by ecosystem preset (php-yii, laravel, node, python, generic, or a custom preset). Not for: plain commit lookup (git log), raw diffs (git diff), or actually running the deploy. Output: a deterministic deploy checklist (deploy-list.sh stdout, forwarded verbatim).
dhpk-doc-review
Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use dhpk-change-review), test review (use dhpk-test-review). Output: 5-dimension rating table + gate.
dhpk-execution-checklist
End-of-task self-check for substantive repository changes. Use after the final Edit/Write before replying or smart-commit, especially for source, SQL/repository/migration, auth/crypto/money/upload, high-volume-table, frontend/template-script, harness, policy, or documentation changes. Not for trivial typo-only edits or research/planning with no pending commit. Output: a gated wrap-up reply with changed files, verification, and risks/open questions.
dhpk-execution-policy
Execution-policy router for dhpk software-engineering work. Use when choosing a task flow or OpenSpec route at kickoff, checking post-edit reviewer obligations, recovering from an anti-loop stop, or shaping a blocked/completion reply. Not for: substantial-change classification (use dhpk-adaptive-dev-workflow), an investigation already underway (use dhpk-root-cause-investigation), pure code tracing, or mid-workflow execution. Output: one next route plus the required gates and completion shape.
dhpk-feasibility-study
Feasibility analysis from first principles. Use when: evaluating solutions before dhpk-tech-spec, comparing approaches, risk assessment. Not for: implementation (use dhpk-adaptive-dev-workflow in feature mode), architecture advice (use dhpk-codex-architect). Output: quantitative comparison + recommendation.
dhpk-git-history-investigation
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use dhpk-codebase-exploration), issue analysis (use dhpk-issue-analyze). Output: history trace + root cause report.
dhpk-git-smart-commit
將雜亂的 git 變更依邏輯分群、逐批提交,適用於需要把多項變更拆成多個邏輯一致 commit 的情境。Not for: 單一小變更或只��要一個 commit（直接 commit 即可）。Output: 可直接執行的分組提交計畫與 commit 指令。
dhpk-gitnexus-cli
Run GitNexus CLI commands (analyze, status, clean, wiki, list). Use when: indexing or re-indexing a repo, checking index freshness, generating a wiki, listing indexed repos. Not for: querying the graph (use dhpk-gitnexus-exploring), tool/schema reference (use dhpk-gitnexus-guide). Output: the npx gitnexus command to run + next step.
dhpk-gitnexus-debugging
Trace bugs and errors through the GitNexus knowledge graph. Use when: debugging a failure, tracing an error to its origin, finding callers of a suspect symbol, investigating unexpected behavior. Not for: general architecture understanding (use dhpk-gitnexus-exploring), change blast-radius (use dhpk-gitnexus-impact-analysis), CLI/index ops (use dhpk-gitnexus-cli). Output: a root-cause hypothesis with the call chain + files to inspect.
dhpk-gitnexus-exploring
Explore and understand a codebase via the GitNexus knowledge graph. Use when: asking how code works, understanding architecture, tracing execution flows, or exploring unfamiliar code. Not for: blast-radius of a change (use dhpk-gitnexus-impact-analysis), bug tracing (use dhpk-gitnexus-debugging), CLI/index ops (use dhpk-gitnexus-cli). Output: a code-flow explanation grounded in graph queries + the files to read.
dhpk-gitnexus-guide
Reference for GitNexus MCP tools, resources, and graph schema. Use when: asking what GitNexus tools exist, how to query the graph, or for MCP resource / schema reference. Not for: CLI commands (use dhpk-gitnexus-cli), task flows (use dhpk-gitnexus-exploring / dhpk-gitnexus-debugging / dhpk-gitnexus-impact-analysis / dhpk-gitnexus-refactoring). Output: the right tool / resource / skill to use next.
dhpk-gitnexus-impact-analysis
Assess the blast radius of a code change via the GitNexus graph. Use when: asking what breaks if you change X, who depends on a symbol, or for a pre-commit safety check. Not for: understanding how code works (use dhpk-gitnexus-exploring), bug tracing (use dhpk-gitnexus-debugging), performing the rename/refactor (use dhpk-gitnexus-refactoring). Output: a depth-ranked dependents list + risk level.
dhpk-gitnexus-refactoring
Safely rename, extract, split, move, or restructure code using the GitNexus graph + coordinated rename. Use when: renaming a symbol across files, extracting a module, splitting a function/service, moving code. Not for: understanding code (use dhpk-gitnexus-exploring), pre-change risk only (use dhpk-gitnexus-impact-analysis), bug tracing (use dhpk-gitnexus-debugging). Output: an ordered refactor plan + verified multi-file edits.
dhpk-harness-budget
Audits Claude Code context-window token consumption across agents, skills, MCP, rules, and CLAUDE.md; produces prioritized token-savings fixes. Use when: context feels bloated, after adding components, or checking headroom. Not for: trimming harness structure (use dhpk-harness-revise), backfilling .claude/ (use dhpk-harness-fill), or checking hook/plugin health (use dhpk-claude-health). Output: budget report + ranked fixes.
dhpk-harness-fill
Explore-driven meta-workflow SSOT: 5-phase parallel inventory → fill in .claude/ infrastructure. Backfills .claude/skills/agents/rules + per-layer CLAUDE.md in one shot (≤3 Explore agents in parallel per round) when explicitly invoked via /dhpk:dhpk-harness-fill. Not for: single-file patches (use Edit), specific symbol lookups (use cx definition / gitnexus_impact), PR review (route through the sentinel chain to the matching reviewer agent). Output: list of created / modified files + conventional commit message draft.
dhpk-harness-revise
Trims and validates the project harness (.claude/ or .codex/) for a harness audit request, after major rule additions, or as periodic maintenance. Detects the active environment and ensures consistency, hygiene, and trigger preservation. Not for: business code review. Output: inventory snapshot, gap list with severity, proposed fixes, validation results.
dhpk-laravel-package-author
Cross-version Laravel package authoring. Use when: designing a service provider, facade, version-conditional binding, publishable artifact, discovery contract, or package compatibility surface. Not for: application code, one-major API details, Composer release hygiene, or deep Testbench matrix mechanics. Output: an authoring decision or package design with provider, facade, publishing, discovery, and compatibility gates.
dhpk-laravel-testbench-matrix
Orchestra Testbench matrix mechanics for Laravel packages spanning multiple majors. Use when: choosing Testbench pins, defining PHP × Laravel cells, building the shared TestCase, provisioning per-cell databases, running prefer-lowest, or validating package discovery. Not for: single-major packages, application test suites, Laravel package authoring outside the matrix, or semver decisions. Output: a per-cell CI matrix, TestCase design, and evidence-backed test gate.
dhpk-module-design
Use when users need architecture decisions, module boundaries, or implementation guidance for software development tasks. Supports design, review, compare, and bounded adversarial modes. Not for pure documentation editing or non-technical writing tasks. Output: actionable, stack-neutral architecture guidance with explicit seams, trade-offs, and implementation-ready recommendations.
dhpk-next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
dhpk-onepassword-session
Initializes a 1Password CLI session for Claude Code so op stops triggering biometric auth on every Bash call — for a session that needs 1Password secrets, keeps hitting biometric prompts, or needs OP_SESSION set up. Not for: storing/rotating secrets, non-1Password vaults, configuring op itself. Output: cached session file (token or app mode) + op wrapper.
dhpk-opsx-load-context
Load opsx-apply-resume Resume Phase context via a 3-tier fallback (claude-mem pinned obs → compact JSON → handoff summary), optionally fetching cross-session observations. Use when: opsx-apply-resume enters Resume Phase Steps 1b–1d. Not for: saving observations (use dhpk-opsx-post-observation) or goal generation (use dhpk-opsx-apply-goal). Output: CONTEXT_SOURCE + session_goal/completed/in_progress/cross_session_observations fields.
dhpk-opsx-post-observation
Post a session observation to claude-mem from opsx-apply-resume Save Phase — builds a JSON payload and runs post-obs.sh as a non-blocking background post (the caller collects the result before the handoff write, so the POST overlaps Save-Phase Steps 4–6). Use when: opsx-apply-resume Save Phase Step 3b, right after compact-save extracts L0/session_goal/completed/key_decisions. Not for: loading Resume context (use dhpk-opsx-load-context) or goal generation (use dhpk-opsx-apply-goal). Output: OBS_PID + OBS_RESULT_FILE path for the caller to wait on.
dhpk-polyfill-version-matrix-audit
Audit multi-major-version polyfill code for branch coverage and CI-matrix gaps. Use when: a library spans multiple dep majors (Monolog 2/3, Laravel 6/7+, PHPUnit 8-11) using version_compare / class_exists / method_exists guards, or after a "fix: polyfill ..." commit. Not for: single-version libraries, application code, version-detection-only helpers. Output: branch + matrix-gap audit report.
dhpk-pr-review
PR self-review workflow — review changes for correctness/security/perf, produce checklist, scan for unrelated changes in squash merges. Use when reviewing your own branch before opening a PR, after a squash merge needs hygiene check, or when running `/dhpk:dhpk-pr-review` command. Not for: independent diff review (use `dhpk-change-review`), dedicated DB or security audits (use `dhpk-security-review`), test adequacy (use `dhpk-test-review`), or non-PR exploratory reading (use `dhpk-codebase-exploration`). Output: review notes + PR checklist + an explicit mergeable / needs-revision gate. Includes advisory scan for squash merge unrelated changes per `squash-merge-hygiene` capability.
dhpk-project-audit
Project health audit with deterministic scoring. Use when: evaluating project quality, onboarding to new codebase, periodic health checks. Not for: runtime performance analysis, security-specific audits (use /dhpk:change-verdict --mode security). Output: 5-dimension score + actionable findings.
dhpk-risk-assess
Uncommitted code risk assessment with breaking change detection, blast radius analysis, and scope metrics. Use when: evaluating PR risk, pre-commit risk check, large refactoring review. Not for: security vulnerabilities (use /codex-security), code correctness (use /codex-review-fast). Output: 3-dimension weighted score + risk level + gate.
dhpk-root-cause-investigation
Root-cause investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and cross-layer data-flow tracing. Use when users ask to investigate or trace a bug, regression, flaky test, or root cause (including 測試失敗、效能異常、調查 Bug、追蹤資料流). Not for direct implementation when the root cause is already confirmed, ordinary code review, or pure feature work. Output: a phase-based evidence report, confirmed root cause or explicit blocked state, solution options, stop-loss state, and next actions.
dhpk-rules-distill
Scans installed skills to extract cross-cutting principles and distill them into rules (append, revise, or create rule files), for periodic rules maintenance, after installing new skills, or when a dhpk-skill-stocktake surfaces patterns that should be rules. Not for: creating skills (use dhpk-create-skill), one-off rule edits, code review. Output: candidate report (principle + evidence + verdict) for user approval.
change-verdict
Read-only verdicts for code changes, pull requests, security, tests, documents, or change risk. Use when judging an existing change or evidence set. Not for implementing fixes, generating tests, editing documents, clearing gates, or architecture-only design. Output: evidence-backed findings, degradation state, and READY, BLOCKED, or INCONCLUSIVE.
code-trace
Trace unfamiliar code, diagnose a reproducible failure, investigate history, or select one code-navigation tool. Use when evidence must follow symbols, callers, data flow, regressions, or tool choice. Not for implementing a confirmed fix, reviewing a proposed diff, or plain-text/document search. Output: an evidence-backed trace, root-cause state, history report, or executable tool route.
dhpk-fastapi-pro
FastAPI + SQLAlchemy 2.0 async patterns + review checklist: routers, Depends DI, Pydantic schemas, session/transaction discipline, Alembic safety, auth/CORS/errors. Use when writing or reviewing FastAPI routes, async repositories, or migrations. Not for non-web Python. Output: layered, transaction-safe API.
dhpk-ios-icon-gen
Generate iOS/macOS asset-catalog imagesets (1x/2x/3x PNG + Contents.json) from SF Symbols (Apple-native, offline, macOS) or the Iconify API (275k+ open-source icons, online). Use when adding icons to an Xcode asset catalog, replacing placeholder glyphs, or searching for an icon that matches a project's style. Not for general SwiftUI design, arbitrary raster editing, or production code changes. Output: an imageset path plus generated PNG and Contents.json verification. Part of the xcode-tooling module; requires the swift module.
dhpk-ios-platform
Use when iOS SDK guidance is needed for privacy-sensitive persistence, CryptoKit/Keychain, OCR, camera, biometrics, notifications, HealthKit, or privacy manifests. Requires swift. Not for SwiftUI composition or pure Swift language work. Output: SDK-specific implementation or review guidance with privacy and verification gates.
dhpk-js-lint-config
ESLint/TypeScript configuration guidance for tier selection, global-list synchronization, static gates, or frontend-review consistency. Use when editing eslint.config.js or tsconfig.json, adding globals, or planning lint migration. Not for ordinary JS logic. Output: a tier decision and verification evidence.
dhpk-js-static-check-strategy
Progressive `// @ts-check` per-leaf rollout playbook for legacy JS bundles. Covers the three-list legacy-globals sync (ESLint globals / TypeScript ambient .d.ts / JSDoc typedef), tsconfig exclude strategy for type-check-resistant files, leaf classification (typedef-widening-fixable vs permanent-exclude), line-anchored progress-grep traps, and Phase-2 exit-gate semantics. Use when planning a per-leaf cleanup PR, introducing a new leaf-level global, editing tsconfig's exclude list, interpreting /ts-check-status output, or validating the strict-checkJs exit gate. Not for everyday JavaScript feature work or isolated lint-rule lookups; use the sibling dhpk-js-lint-config and references/static-checks.md for those. Output: a per-leaf classification, three-list change set, and exit-gate evidence.
dhpk-legacy-characterization-tests
Write characterization tests for untested legacy code to lock current behavior before refactoring. Use when users want to safely refactor legacy controllers/models/services, add regression safety nets, or prepare code for extraction. Trigger words: characterization test, lock behavior, legacy test, safe refactor, 行為鎖定, 特徵測試, 安全重構. Not for: greenfield code, already well-tested modules, or pure bug fixes. Output: characterization test files + coverage delta report.
dhpk-library-dual-testsuite-map
Map edited file paths to the correct testsuite(s) for libraries with a framework-agnostic Core layer and a framework-specific glue layer. Use when editing any `src/**` file in a library whose phpunit.xml declares multiple testsuites (commonly `core` + `laravel`, or `core` + `symfony`, etc.) and you need to know which `composer test:*` command(s) to run. Not for single-testsuite projects or full framework integration orchestration. Output: the selected suite(s), boundary warning, and the commands to run. Saves the round-trip of "I ran the wrong suite, the failing test is in the other one". Companion to (not duplicate of) `dhpk-polyfill-version-matrix-audit` which works at the version-guard level; this skill works at the directory level.
dhpk-matrix-cell-onboard
Checklist + procedure for adding a new PHP / Laravel / PHPUnit / Monolog cell to a multi-major library's CI matrix. Use when extending support to a new runtime version (e.g. "add PHP 8.3 + Laravel 12"), bumping a dep major (e.g. "Monolog 4 came out, plan the cell"), or restoring a dropped cell. Not for patch-only changes that do not alter the support matrix. Output: a cell plan with composer, workflow, polyfill, Testbench, and focused-test gates. Cross-checks `composer.json` constraints, `.github/workflows/*.yml` matrix rows, Testbench mapping for Laravel, and triggers a polyfill-coverage check for the new cell's dep versions. Pairs with `dhpk-laravel-testbench-matrix` (per-cell Testbench install) and `dhpk-composer-package-hygiene` (semver of raising the floor).
dhpk-nextjs-15-5-notes
Next.js 15.5 (current stable; the 15.x line ends at v15.5.19) signature features and traps. Use when writing or reviewing Next.js 15.5 code or a package constrained to ^15.5. Covers typegen, typed routes, beta Turbopack production builds, and the next lint deprecation. Not for application business logic; pair with `dhpk-react-18-notes` or `dhpk-react-19-notes` for React guidance and `dhpk-nextjs-16-notes` for the upgrade target. Output: version-specific guidance, migration traps, and verification gates.
dhpk-nextjs-16-notes
Use when working on Next.js 16 framework code or 15→16 upgrades: Turbopack, async Request APIs, Node floor, removed APIs, and image changes. Not for application business logic. React 18.2+ or 19 is supported; pair with `dhpk-react-18-notes` or `dhpk-react-19-notes` for React-language guidance and `dhpk-nextjs-15-5-notes` for the upgrade source. Output: migration traps and verification gates.
dhpk-openspec-artifact-guard
Use when validating OpenSpec artifact shape, delta placement, task/git alignment, and safe change slugs. Apply while editing OpenSpec files or reviewing them before archive. Not for implementation or archive itself. Output: a verdict with artifact and task evidence.
dhpk-php-8x-features
Use when the project's PHP floor permits 8.x syntax, when reviewing whether a 7.4-and-up library can adopt an 8.x idiom conditionally, or when designing an API with attributes, enums, readonly, or newer types. Not for everyday business logic, 7.4 baseline guidance, or legacy 5.6 code. Output: a feature recommendation or migration decision with its minimum PHP version and library-floor rule.
dhpk-php-modern-pro
PHP 7.4–8.x idiom and dual-version library-packaging guidance. Use for public APIs, version-conditional shims, supported floors, or composer constraints. Not for routine business logic. Output: a compatibility decision and verification gates.
dhpk-php-runtime-router
Use when implementing or reviewing Laravel, Symfony, modern PHP, or PHP 5.6/Yii code. Detect runtime first and load only matching references; select Laravel major before framework-coupled edits. Not for frontend-only work. Output: compatibility-safe guidance and verification gates.
dhpk-pytest-async
Async pytest + pytest-asyncio testing: asyncio_mode=auto, SQLite fixtures, httpx.AsyncClient + ASGITransport, unit/integration split, coverage floor, live markers. Use when writing or reviewing async FastAPI/SQLAlchemy tests, or enforcing dhpk-tdd-workflow. Not for production code. Output: offline-green async tests.
dhpk-python-pro
Modern Python (3.10+) review checklist: typing, dataclasses/pydantic, async-await discipline, logging over print, exception chain, ruff+pyright. Use when writing or reviewing backend Python (async FastAPI/SQLAlchemy). Not for non-backend or pre-3.10 code. Output: typed, ruff/pyright-clean code.
dhpk-python-static-checks
Static-check strategy for Python — ruff rule selection (lint vs format), pyright-strict vs mypy trade-offs, progressive typing adoption, per-file/per-line suppression discipline, and how the dhpk python module's post-edit + pre-commit hooks invoke them. Use when configuring ruff/pyright/mypy or triaging their output. Not for runtime debugging or test design; use dhpk-python-pro or dhpk-pytest-async. Output: a tool configuration or triage plan with commands and pass/fail gates.
dhpk-react-18-notes
Use when working on React 18 guidance for ^18 projects, root setup, concurrent rendering, StrictMode, or 17→18/18→19 upgrades. Not for ordinary application logic. Remains a separate React 18 route; pair with `dhpk-react-19-notes` for 18→19 changes and `dhpk-nextjs-15-5-notes` or `dhpk-nextjs-16-notes` for Next integration. Output: migration traps and verification gates.
dhpk-react-19-notes
Use when working on React 19 guidance for Actions, new hooks, refs, providers, Server Components, or 18→19 upgrades. Not for ordinary application logic. Remains a separate React 19 route; pair with `dhpk-react-18-notes` for the 18 baseline and `dhpk-nextjs-16-notes` for Next integration. Output: migration traps and verification gates.
dhpk-swift-language
Swift language guidance for concurrency, optionals, value/reference design, property wrappers, and errors across Swift 5.10/6. Use for .swift implementation or review. Not for SwiftUI composition or iOS SDK APIs. Output: compatibility and verification decisions.
dhpk-swift-test-strategy
iOS testing strategy for Swift Testing, XCTest, UI automation, async actors, and RED-first coverage. Use when writing or reviewing iOS tests or choosing test targets. Not for non-test app code. Requires swift. Output: RED-first tests and a three-layer coverage plan.
dhpk-swiftui-architecture
SwiftUI architecture guidance for MVVM, Observation, navigation, state ownership, Combine, and UIKit interop. Use when building screens, view models, or routes. Requires swift. Not for iOS SDK APIs or pure Swift language work. Output: architecture and verification guidance.
dhpk-repo-intake
Project initialization inventory (one-time), for first onboarding a project or rebuilding cache after structural changes. Not for: day-to-day development (read cache directly), finding specific files (use dhpk-codebase-exploration). Output: project map with entrypoints + test map + next steps.
bug-investigation
Root-cause investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and cross-layer data-flow tracing. Use when users ask to investigate or trace a bug, regression, flaky test, or root cause (including 測試失敗、效能異常、調查 Bug、追蹤資料流). Not for direct implementation when the root cause is already confirmed, ordinary code review, or pure feature work. Output: a phase-based evidence report, confirmed root cause or explicit blocked state, solution options, stop-loss state, and next actions.
legacy-code-characterization
Write characterization tests for untested legacy code to lock current behavior before refactoring. Use when users want to safely refactor legacy controllers/models/services, add regression safety nets, or prepare code for extraction. Trigger words: characterization test, lock behavior, legacy test, safe refactor, 行為鎖定, 特徵測試, 安全重構. Not for: greenfield code, already well-tested modules, or pure bug fixes. Output: characterization test files + coverage delta report.
multi-ai-sync
Compare and synchronize Claude-first agent configuration across Codex, Gemini, and Antigravity (.agent). Generate read-only plans, create OpenSpec tasks, apply safe sync changes with dry-run preview and writable-path fallback, and validate post-sync results. Use when aligning `.claude` skills, commands, hooks, agents, or orchestration rules to other AI platforms, when comparing multi-platform agent setup drift, or when preparing a Claude-to-Codex/Gemini/.agent migration. Also matches requests such as `sync claude to codex`, `align multi-platform AI config`, `同步 claude 技能到 codex`, or `對齊多 AI 設定`. Not for single-platform edits, reverse sync, or missing `.claude` source.
php-pro
Use when building, debugging, refactoring, testing, or reviewing PHP code in Laravel, Symfony, generic modern PHP, or legacy PHP 5.6 + Yii 1.1 codebases. Detect the active runtime first, then load only the matching reference set; for Laravel, confirm the resolved major version and load the version-specific reference before touching bootstrap/app.php, middleware, exceptions, auth, testing infrastructure, or Laravel-coupled packages. Not for frontend-only or non-PHP tasks. Output: runtime-matched implementation or review guidance with compatibility and verification gates.
php56-yii-dev
Generic backend development workflow for legacy Yii 1.x applications running on PHP 5.6 that must stay compatible with future PHP 7 upgrades. Use when implementing, refactoring, debugging, testing, or reviewing Yii 1.x backend code such as Controllers, FormModels, CActiveRecord, services, repositories, DAO queries, validation rules, security hardening, or domain-driven design boundaries. Includes pragmatic DDD placement, Context7-first knowledge refresh, and full TDD guidance. Not for frontend-only work, documentation-only edits, or non-PHP stacks. Output: a PHP 5.6-safe implementation or review plan with TDD and compatibility evidence.
fastapi-pro
FastAPI + SQLAlchemy 2.0 async patterns + review checklist: routers, Depends DI, Pydantic schemas, session/transaction discipline, Alembic safety, auth/CORS/errors. Use when writing or reviewing FastAPI routes, async repositories, or migrations. Not for non-web Python. Output: layered, transaction-safe API.
nextjs-15-5-notes
Next.js 15.5 (current stable; the 15.x line ends at v15.5.19 — 15.6 never shipped stable, canary only before the jump to 16.0) signature features and traps. Use when writing or reviewing code in a Next.js 15.5 project, or a package whose package.json constraint is ^15.5. Covers next typegen, stable typed routes, beta Turbopack production builds, and the next lint deprecation (removed in 16). Not for application business logic — load when working on framework-touching code (App Router files, next.config, build tooling) or planning a 15.5 -> 16 upgrade. Output: version-specific guidance, migration traps, and verification gates.
nextjs-16-notes
Next.js 16 (current stable major, now at 16.2.x) signature features and the breaking-change traps from 15.x -> 16.0. Use when writing or reviewing code in a Next.js 16 project, or planning an upgrade from Next.js 15.x. Covers Turbopack-by-default (dev and build), the async-only Request APIs (params/searchParams/cookies/headers), the Node.js 20.9+ floor, the removal of next lint and AMP, next/image priority -> preload, removed runtime-config APIs, and the 16.1 next upgrade CLI. Not for application business logic — load when working on framework-touching code or planning a 15.x -> 16 upgrade. Note: Next.js 16 supports React 18.2+ or 19 — React 19 is recommended but NOT required. Output: version-specific guidance, migration traps, and verification gates.
phpunit-10-notes
PHPUnit 10.x (February 2023) signature features and the breaking-change traps from 9 → 10. Use when writing or reviewing tests in a PHPUnit 10 project, or when migrating a PHPUnit 9 suite to 10. Covers PHP 8.1 floor, the attribute-style annotation system (#[DataProvider] / #[CoversClass] / #[Group] / #[Test]) that replaces (but does not yet remove) doc-comment annotations, the test runner CLI rewrite, TestListener removal, and the static-data-provider requirement. Not for everyday assertion writing or PHP < 8.1 projects (stay on phpunit-9-modern). Output: a 9 → 10 migration plan. Pair with phpunit-9-modern for the API conventions that carry forward unchanged.
pytest-async
Async pytest + pytest-asyncio testing: asyncio_mode=auto, SQLite fixtures, httpx.AsyncClient + ASGITransport, unit/integration split, coverage floor, live markers. Use when writing or reviewing async FastAPI/SQLAlchemy tests, or enforcing TDD. Not for production code. Output: offline-green async tests.
python-pro
Modern Python (3.10+) review checklist: typing, dataclasses/pydantic, async-await discipline, logging over print, exception chain, ruff+pyright. Use when writing or reviewing backend Python (async FastAPI/SQLAlchemy). Not for non-backend or pre-3.10 code. Output: typed, ruff/pyright-clean code.
react-18-notes
React 18 (March 2022) signature features and the migration traps from 17 -> 18. Use when writing or reviewing code in a React 18 project, or a package whose package.json constraint is ^18 (or ^18.2). Covers createRoot/hydrateRoot, automatic batching, the opt-in concurrent features (startTransition/useTransition/useDeferredValue), streaming SSR (renderToPipeableStream), the new hooks (useId/useSyncExternalStore/useInsertionEffect), and StrictMode effect double-invocation. Not for application business logic — load when working on React root setup, concurrent-rendering code, or planning a 17 -> 18 (or 18 -> 19) upgrade. Pairs cross-stack with the nextjs modules; React 18.2+ is the floor Next.js 16 supports. Output: version-specific guidance, migration traps, and verification gates.
react-19-notes
React 19 (December 2024) signature features and the breaking-change traps from 18 -> 19. Use when writing or reviewing code in a React 19 project, or planning an upgrade from React 18. Covers Actions and async transitions, the new hooks (useActionState/useOptimistic/useFormStatus and the use() API), ref as a regular prop (forwardRef deprecated), <Context> as a provider, document metadata hoisting, resource preloading (preload/preinit), stable Server Components/Actions, and the removal of long-deprecated APIs (ReactDOM.render/hydrate, propTypes/defaultProps on function components, legacy Context, string refs). Not for application business logic — load when working on React-language code or planning an 18 -> 19 upgrade. Note: React 19 is recommended but NOT required for Next.js 16 (React 18.2+ also works). Output: version-specific guidance, migration traps, and verification gates.
swift-test-strategy
iOS test strategy across Swift Testing (@Test / #expect / #require / parameterized @Test(arguments:) / traits / suites) and XCTest (UI tests, performance metrics), XCUITest automation (XCUIApplication, launch-argument test seams), and swift-snapshot-testing. Defines a 3-layer taxonomy (unit / integration / UI) mapped to iOS test targets, async patterns for actor-isolated services, and RED-first guidance. Use when writing or reviewing iOS tests, choosing Swift Testing vs XCTest, structuring test targets, testing async/actor code, or planning coverage for a feature/bugfix. Not for non-test app code (swift / swiftui / ios-platform); output is RED-first test files plus a 3-layer coverage plan. Requires the swift module.
Showing top 100 of 101 skills by quality score. Browse the full catalog at /browse.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.