テスト設計、脆弱性診断、品質保証（1.4万 件）
Authoritative reference for Pi (@earendil-works/pi-coding-agent): install, configure, run, and extend it. Use for the CLI and configuration, providers and models, extensions, skills, MCP, codemode, the SDK/RPC, security and trust, design philosophy, and the pi repository's internals and contribution rules.
日本語の概要は準備中です。原文の説明を表示しています。
File notes into the right folder in the user's Obsidian vault and audit/reorganize its structure, via the `obsidian` CLI and the `00_Index/Folder_Map.md` map note. Use when a note needs filing, when the user asks where a note belongs, or wants to tidy, deduplicate, audit, or restructure folders. Requires the Obsidian app to be running.
日本語の概要は準備中です。原文の説明を表示しています。
Build one-page HTML/PDF resumes from copy-paste YAML using one of 12 official templates. HARD GATES: deliver exactly one A4 page; never invent a layout — copy assets/templates/<id> into output/<id>/ and edit that copy only. Keep a full inventory in raw.data.yaml. For each job, COPY selected entries into resume.data.yaml (polish there), then apply that file to a template. Apply pasted YAML by replacing visible text in the official resume.html, then run QA. Default template is basic-a4. Use when creating, iterating, polishing copy, migrating, exporting, or designing resume/CV HTML/PDF. For polishing resume copy, prefer writing-oriented models (Claude Fable 5 / Claude Opus 4.6-4.7 or Opus 5 / Kimi K3 / GLM-5.1-5.3-max / Qwen 3.8 Max); do not use GPT-5.6 Terra/Luna or GPT-5.5 Instant.
日本語の概要は準備中です。原文の説明を表示しています。
Search with feature attributions — return WHY each match scored where it did. Use when debugging recall quality, auditing for bias, or explaining results to a user.
日本語の概要は準備中です。原文の説明を表示しています。
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
日本語の概要は準備中です。原文の説明を表示しています。
Add durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and store evidence. Use for E2E, Playwright/Cypress, regression tests, or quality gates. Not exploratory QA.
日本語の概要は準備中です。原文の説明を表示しています。
Run Ship's full production workflow from raw requirement to PR: design, dev, E2E, review, QA, refactor, and handoff. Use only for explicit /ship:auto, auto pipeline requests, or end-to-end delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Static code review of the active diff: trace changed paths and report concrete P1/P2/P3 correctness, security, or spec bugs with file:line evidence. Use for code review or bug checks. Not runtime QA.
日本語の概要は準備中です。原文の説明を表示しています。
Runtime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review.
日本語の概要は準備中です。原文の説明を表示しています。
Live developer experience audit. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Security audit: supported static findings; qualified profiles add reproduction and repair candidates. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Audits an existing lesson against UDL's three principles — engagement, representation, and action/expression. Identifies specific access barriers and suggests concrete modifications ranked by impact.
日本語の概要は準備中です。原文の説明を表示しています。
After the learner demonstrates understanding of a concept, present near-transfer and far-transfer challenges. Use to test whether learning is portable or task-specific — this is what separates understanding from familiarity.
日本語の概要は準備中です。原文の説明を表示しています。
The learner teaches the concept to the AI, which plays a curious novice peer and identifies gaps through authentic questions. Use when the learner wants to test their understanding — teaching forces a different kind of organisation than studying.
日本語の概要は準備中です。原文の説明を表示しています。
Generate retrieval practice questions at varied difficulty levels for a topic or concept. Use when creating quiz starters, revision activities, or low-stakes testing materials.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a proposed assessment for construct validity, reliability, and alignment to learning objectives. Use when reviewing or quality-assuring assessments before deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Design a structured protocol for auditing AI-generated text against Ennis's six CT standards. Use when students need to critically evaluate AI output in any subject.
日本語の概要は準備中です。原文の説明を表示しています。
Build and test iOS apps on simulator with XcodeBuildMCP.
日本語の概要は準備中です。原文の説明を表示しています。
Takes a curriculum framework and a statutory or accreditation requirement list; produces a coverage table, gap summary, and CSV showing which framework content covers each requirement and where gaps exist.
日本語の概要は準備中です。原文の説明を表示しています。
Run browser tests for pages affected by the current branch or PR.
日本語の概要は準備中です。原文の説明を表示しています。
[BETA] Hands-off end-to-end branch dogfood pass with browser testing, auto-fixes, regression tests, and fix commits.
日本語の概要は準備中です。原文の説明を表示しています。
Refresh docs/solutions learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless docs/solutions is explicit.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.
日本語の概要は準備中です。原文の説明を表示しています。
Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.
日本語の概要は準備中です。原文の説明を表示しています。