1,181 件 ・ 関連度順
概要と使いどころ
Analyse existing written feedback for quality, specificity, actionability, and impact on student learning. Use when reviewing teacher or peer feedback to improve feedback practices.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Generates multiple means of engagement, representation, and action/expression for a given learning goal. Produces specific, practical alternatives — not generic options — and recommends the highest-impact single change.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and redesign AI-generated feedback for pedagogical quality, timing, and learning impact. Use when building or reviewing automated feedback in digital learning tools.
日本語の概要は準備中です。原文の説明を表示しています。
Compact the current conversation into a handoff document for another agent to pick up.
日本語の概要は準備中です。原文の説明を表示しています。
UI typography on Apple platforms — text styles and Dynamic Type, the San Francisco family (Pro/Rounded/Compact/Mono/New York + width axis), optical sizes, tracking vs kerning, leading adjustments, and custom-font scaling. Use when choosing fonts, building type hierarchy, fixing truncation/legibility, or making custom fonts respect Dynamic Type.
日本語の概要は準備中です。原文の説明を表示しています。
the R package BioNAR, developed to step by step analysis of PPI network. The aim is to quantify and rank each protein’s simultaneous impact into multiple complexes based on network topology and clustering. Package also enables estimating of co-occurrence of diseases across the network and specific clusters pointing towards shared/common mechanisms.
日本語の概要は準備中です。原文の説明を表示しています。
已有功能的需求变更闭环（门禁式七步）。触发硬条件：要改的功能已经实现并跑起来了。当用户说"改需求""需求变更""调整交互""改功能""重构流程"，或改动容易散到多个文件、碰到鉴权/存储/配置/权限、需要可靠验证 + 回滚方案时使用。流程：锁 scope 写 change brief → 从代码确认当前行为（不靠记忆和假设）→ 影响面与风险评估 + 回滚计划 → 提出新设计等用户批准（**未获批准绝不动代码**）→ 小而局部的 diff → 跑固定回归清单 → 更新文档和决策日志。产出：change brief + 代码 diff + 回归记录 + decision log。不适用于：全新功能从零做（走 issue-pool → page-solution-design（有界面时）→ backend-logic-design（有规则需讨论时）→ prd-test-writer）、只改视觉样式不动任何逻辑（按已有界面直接调整）、新想法还没定要不要做（先用 issue-pool 入池）、写 PRD/测试用例（用 prd-test-writer）、提交推送发版（用 git-push）。注意：本 skill 的七步流程通用于任何项目，但 scripts/impact_scan.sh 与 references/chrome-extension-regression-example.md 是 Chrome 扩展示例；通用回归使用 references/regression-checklist.md，按项目实际选择检查。
日本語の概要は準備中です。原文の説明を表示しています。
Weekly cross-project error overview from PostHog - enumerates every project the OAuth grant covers, pulls the last 7 days of error-tracking issues per project, ranks them by impact, flags what's new vs ongoing, and sends one digest with per-project totals, the top issues, and a clickable link to a full committed report of every issue.
日本語の概要は準備中です。原文の説明を表示しています。
One lifecycle poll over everything vuln-scanner produces - PR and advisory status, PVR triage transitions, and pending-disclosure aging, with a stars-secured impact headline and one action queue.
日本語の概要は準備中です。原文の説明を表示しています。
Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Amazon profit analysis and revenue optimization. Revenue waterfall analysis, hidden fee identification, ACoS impact assessment, return cost calculation, and profitability optimization strategies. Use when the user asks about Amazon profit analysis, profitability calculation, fee analysis, margin optimization, or revenue breakdown.
日本語の概要は準備中です。原文の説明を表示しています。
Amazon Buy Box strategy and optimization framework. Eligibility factor analysis, competitive pricing strategies, FBA vs FBM impact assessment, seller performance optimization, and Buy Box winning tactics. Use when the user asks about Amazon Buy Box, winning Buy Box, Buy Box eligibility, or Buy Box optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.
日本語の概要は準備中です。原文の説明を表示しています。
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt at session start — prose is for humans, JSON is for the loop.
日本語の概要は準備中です。原文の説明を表示しています。
Create a concise continuation prompt that a fresh agent session can paste in to resume a long or degraded session. Use when the user asks for a handoff prompt, restart prompt, continuation prompt, context transfer, fresh-session resume, or a compact summary for opening a new session. Do not use for ordinary summaries, task-forest maintenance, durable user-profile updates, automatic session creation, code execution, or external publishing.
日本語の概要は準備中です。原文の説明を表示しています。
Line-by-line copy editing and improvement for marketing content. Polish existing copy for clarity, conciseness, impact, and conversion. Trigger phrases: "edit my copy", "improve this copy", "polish this text", "copy edit", "make this clearer", "tighten this up", "proofread", "review my copy", "make this more persuasive", "fix my writing".
日本語の概要は準備中です。原文の説明を表示しています。
Use when an ad account needs a systematic CONFIGURATION audit — 84 checkpoints across account, campaign, ad set, ad, tracking, and optimization, scored into a Health Score out of 100, quick wins ranked by impact, regional benchmarks, and a dropshipping checklist, covering Meta, Google, and TikTok. Trigger on 'ads audit', 'audit my ad account', 'is my Meta setup correct', 'health score for the account', 'review my Google Ads', 'we inherited this account and it is a mess'. Not for — diagnosing why the numbers moved this week, see `03-performance-eval-global`; planning fresh budget, see `54-media-plan-global`; rebuilding the campaign hierarchy, see `52-account-structure-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, building or reviewing UI/UX for a web or mobile app: picking styles, color palettes, typography, layout, animation or charts, or checking accessibility and touch targets. Priority-ranked rules ordered by impact.
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured meeting notes from transcripts or pasted text. Use when someone says "meeting notes", "process this transcript", "summarize this call", "notes from today's meeting", or pastes/references a meeting transcript. Auto-enriches attendees from stakeholder directory, routes output to correct project subfolder, flags downstream artifact impacts (PRD, deck, architecture), and proposes CLAUDE.local.md updates. Produces date-first Markdown files.
日本語の概要は準備中です。原文の説明を表示しています。
Compact the current conversation into a handoff document for another agent to pick up.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.
日本語の概要は準備中です。原文の説明を表示しています。
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
日本語の概要は準備中です。原文の説明を表示しています。
CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations). Run periodically or before releases. NOT part of the distributed plugin.
日本語の概要は準備中です。原文の説明を表示しています。