5,564 件 ・ 関連度順
概要と使いどころ
Write comprehensive Product Requirements Documents with user stories, acceptance criteria, technical specifications, wireframe descriptions, and prioritization frameworks (RICE, MoSCoW). Create clear specifications for product teams.
日本語の概要は準備中です。原文の説明を表示しています。
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
Technical documentation specialist and knowledge curator for game projects. Use when the user asks to talk to Paige or requests the Technical Writer.
日本語の概要は準備中です。原文の説明を表示しています。
Bidirectional Figma skill — read designs and write back to Figma. READ: extract tokens, map Vue/Reka UI components, translate Auto Layout to Tailwind. WRITE: push components, screens, and design tokens from code to Figma. Requires /figma:figma-use skill before every use_figma call.
日本語の概要は準備中です。原文の説明を表示しています。
Threads Content Specialist. Writes Threads-native posts — short, direct, opinion-led, made for conversation. Strictly enforces the 500 character limit with a count on every post. Supports standalone posts and threads (connected posts). Reads brand-style.md and content-calendar.md. Flags infographic opportunities for /publisher. Output to outputs/threads/.
日本語の概要は準備中です。原文の説明を表示しています。
X/Twitter Content Specialist. Writes X-native posts — hooks, threads, and standalone tweets optimised for the platform. Strictly enforces the 280 character limit with a count on every post. Supports standalone tweets and X threads (1/ format). Reads brand-style.md and content-calendar.md. Optional X trend research via Tasty Content MCP. Output to outputs/x/.
日本語の概要は準備中です。原文の説明を表示しています。
LinkedIn Content Specialist. Writes LinkedIn-native posts for SMB clients — first-person, professional-but-human, built for LinkedIn's format and algorithm. Not adapted captions: posts written from first principles for the platform. Reads brand-style.md and content-calendar.md. Flags posts that would benefit from a Blotato infographic. Output to outputs/linkedin/.
日本語の概要は準備中です。原文の説明を表示しています。
Brand onboarding setup skill. Captures a client's visual identity, content patterns, audience, and goals through evidence capture + pre-filled client doc + structured intake. Writes context/brand-style.md as the foundation for all social skills. Run once per client before using /social-creative-designer, /content-calendar, or /caption-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Writes on-brand social media captions for SMBs. Takes post concepts or a content calendar and produces ready-to-post captions with hooks, body copy, CTAs, and hashtags. Reads brand-style.md for voice and tone. Supports Instagram, LinkedIn, Facebook, TikTok, and X. Batch and single-post modes. Optional trend and competitor research via Firecrawl and SerpApi.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a text prompt, a photo, or a live video clip into hand-made-looking p5.js animation — pencil handwriting that writes itself, photos repainted as brushstroke art with paint-on animation and camera moves, and short videos (iPhone Live Photos included) repainted frame-by-frame as a living painting. Trigger on: "handwritten text animation", "paint this photo", "painted video", "sketch effect", "turn my live photo into a painting", "write-on effect". Everything is 100% code: p5.brush strokes rendered headlessly, no image models.
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured feature specifications through a collaborative product interview. Acts as a senior PM and business analyst pair — arrives with a point of view, challenges scope, proposes options at every decision. Composes the requirement-quality atom for spec quality enforcement and collaborative-judgment for surfacing genuine decisions. Produces an epic/feature hierarchy in .lattice/requirements/ that serves as direct input to design-blueprint. Use when the user says 'forge requirements', 'write requirements', 'spec this feature', 'create a feature spec', 'define this epic', 'write a PRD', 'spec out what we are building', or 'requirement forge'.
日本語の概要は準備中です。原文の説明を表示しています。
Apply test quality principles when generating or reviewing test code. Enforces Arrange-Act-Assert structure, one behavior per test, assertion quality, test isolation, meaningful naming, and test data management. Use when writing tests, reviewing test code, or when the user mentions 'write tests', 'test this', 'test quality', 'test review', 'improve tests', or 'test structure'. Loaded automatically by the code-generating molecules (code-forge, refactor-safely, bug-fix). This skill governs the craft of writing individual test cases -- not what to test (that is driven by the code being implemented) but how to write tests that are reliable, readable, and maintainable.
日本語の概要は準備中です。原文の説明を表示しています。
Writes and executes SQL queries from simple SELECTs to complex multi-table JOINs, aggregations, and subqueries. Use when the user asks to query a database, write SQL, run a SELECT statement, retrieve data, filter records, or generate reports from database tables.
日本語の概要は準備中です。原文の説明を表示しています。
Find academic papers across up to 8 sources (OpenAlex / Semantic Scholar / CrossRef / PubMed / arXiv for English, OpenReview for AI venues, plus native-Chinese retrieval via NSSD 国家哲社文献中心 + yiigle 中华医学期刊) with adjustable depth — Quick scan (5 min) to Audit prep (3 hr). Use when the user wants to find papers, run a literature search, gather references, scope a research topic, search Chinese-language / 中文原生 literature (中文文献/中文核心/CSSCI/C刊/国内研究/国内文献/中华××期刊/心理学报/经济研究), or filter results by journal tier (中科院分区/一区/几区, Q1, JCR/SJR quartile, 影响因子/impact factor, 期刊分区, 顶刊/top journal, '按分区筛'), or export paste-ready professional search strategies / 检索式 for external databases (PubMed / WOS / Scopus / Embase / 知网 CNKI / 万方 / SinoMed — '写检索式', '导出检索式', 'WOS 检索式', '知网专业检索', 'search strategy', 'boolean search strategy'). Triggers on search verbs ('find papers', 'literature search', 'papers about X'), review types ('scoping review', 'systematic review', 'SR prep', 'literature review', 'lit review', 'help me write a lit review'), Chinese ('找文献', '找论文', '论文搜索', '学术检索', '文献检索', '文献综述', '综述前期', '求文献', '中文文献', '中文核心', 'CSSCI', 'C刊', '国内研究', '找中文的'). Outputs Shadcn HTML report + BibTeX/RIS/CSV + PRISMA-S log. Do NOT use for: concept explanations ('what is X' / 'X 是什么', e.g. '影响因子怎么算'), writing ('帮我写' / 'help me write a paragraph'), single-paper interpretation or PDF download with metadata (use paper-downloader-portable), or when the user already has a literature set (use literature-set-review).
日本語の概要は準備中です。原文の説明を表示しています。
Research and write evidence-backed listicles, product roundups, and best-of comparisons with optional SandBase SERP, page, review, and screenshot evidence. Use for ‘best tools’, ‘top products’, roundup, SEO, GEO, or answer-engine content; do not use for an unresearched promotional ranking presented as independent advice.
日本語の概要は準備中です。原文の説明を表示しています。
Build Spring Boot 4.x applications following the best practices. Use this skill: * When developing Spring Boot applications using Spring MVC, Spring Data JPA, Spring Modulith, Spring Security * To create recommended Spring Boot package structure * To implement REST APIs, entities/repositories, service layer, modular monoliths * To use Thymeleaf view templates for building web applications * To write tests for REST APIs and Web applications * To write ArchUnit tests for testing architecture * To configure the recommended plugins and configurations to improve code quality, and testing while using Maven. * To use Spring Boot's Docker Compose support for local development * To create Taskfile for easier execution of common tasks while working with a Spring Boot application
日本語の概要は準備中です。原文の説明を表示しています。
Use AI to write NEW test code from specs, PRDs, user stories, code diffs, bug reports, or OpenAPI specs. Staged pipeline: requirements extraction → risk analysis → coverage matrix → scenario generation → oracle design → test code → human review, with guardrails against hallucinated APIs and weak assertions. Use when: "generate tests from spec," "tests from PRD," "tests from user story," "auto-generate test cases," "AI write tests for me." Not for: testing AI/LLM features in your product — use ai-system-testing. Not for: auditing a pre-existing test suite you did not just generate — use ai-qa-review (Step 7 here only reviews tests THIS pipeline produced). Related: playwright-automation, unit-testing, api-testing, qa-project-context.
日本語の概要は準備中です。原文の説明を表示しています。
Write production-grade Playwright tests in TypeScript: Page Object Model, fixtures, auto-waiting, user-facing locators, parallel execution, CI integration, sharding, and 2025-2026 feature awareness. Includes an explicit "do not" list for AI agents. Use when: "Playwright," "write E2E test," "page object," "new Playwright suite," "Playwright config." Not for: fixing one flaky test at runtime — use test-reliability. Not for: bulk regenerating selectors after a UI refactor — use selector-drift-recovery. Not for: visual baseline creation/management — use visual-testing. Not for: deep WCAG/axe audits — use accessibility-testing. Related: visual-testing, ci-cd-integration, api-testing, test-reliability, selector-drift-recovery, accessibility-testing.
日本語の概要は準備中です。原文の説明を表示しています。
Remove AI-generated patterns from QA reports, bug reports, test summaries, status updates, and quality communications. Detects and rewrites robotic test-result language, template-sounding status updates, inflated severity descriptions, and generic stakeholder reports — without inventing facts. Makes QA writing sound like a real engineer wrote it. Use when: "humanize report," "rewrite QA summary," "fix test report," "make this sound human," "clean up status update." Not for: general prose, blog, or marketing-copy cleanup — use the global humanizer skill. Not for: classifying or routing CI failures — use ai-bug-triage. Related: ai-bug-triage, qa-metrics, qa-dashboard, quality-postmortem.
日本語の概要は準備中です。原文の説明を表示しています。
UX-тексты на русском языке: кнопки, формы, ошибки, пустые состояния, онбординг, подтверждения, уведомления, пуши и микрокопия. Use this skill whenever the user asks to write, rewrite, review, choose, or improve interface copy, product messages, UI strings, transactional emails, push notifications, toasts, snackbars, forms, empty states, onboarding, errors, confirmations, labels, tooltips, or button text. Триггеры: «текст для кнопки», «сообщение об ошибке», «текст в форму», «пустое состояние», «подпись к полю», «текст тоста», «снекбар», «онбординг», «пуш-уведомление», «микрокопия», «UX-текст», «что написать на экране…», «лейбл поля», «тултип», «подтверждение удаления», «письмо-уведомление». Для статей и постов см. skills statya и redaktura; для проектного словаря — redpolitika.
日本語の概要は準備中です。原文の説明を表示しています。
Короткие русскоязычные посты для Telegram, LinkedIn, Instagram и других соцсетей: пост с нуля, пост из статьи, анонс в канал, переписывание первой строки, усиление хука и финала. Use this skill whenever the user asks to write, rewrite, draft, shorten, or improve a Russian social media post, Telegram channel post, LinkedIn post, Instagram caption, channel announcement, post from an article, or first-line hook. Триггеры: «пост в телеграм», «пост для канала», «пост в LinkedIn», «пост в Instagram», «короткий пост», «напиши пост», «анонс в канал», «пост из статьи», «первая строка не цепляет», «перепиши пост». Для статей и лонгридов см. skill statya; для лендингов и продающих страниц — promo; для интерфейса — ux-copy.
日本語の概要は準備中です。原文の説明を表示しています。
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
日本語の概要は準備中です。原文の説明を表示しています。
Writes architecture decision records (ADRs) and keeps the rest of a project's documentation true after a change: README, reference comments on public interfaces and the changelog. Use when a user says "write an ADR", "record this decision", "document why we chose X", "set up a decision log", "supersede the old decision", "update the README", "add a changelog entry" or "document this API". Produces records in the Nygard or MADR format, a Keep a Changelog entry, and a script that checks the log for gaps and broken supersession links.
日本語の概要は準備中です。原文の説明を表示しています。