「write」の検索結果

Rewrite and check technical writing to follow Simplified Technical English (ASD-STE100). Use when asked to simplify docs, rewrite in STE / plain technical English, write clear procedures or warnings, or flag hard-to-read or ambiguous technical text for a global / non-native audience.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "write a LinkedIn post", "draft a post about", "help me post on LinkedIn", "create LinkedIn content", or when Genesis proactively generates post ideas during surplus compute. Also triggered by content calendar execution or when the user shares a topic they want to write about.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "write a hook for my post", "give me opening lines", "help me start this LinkedIn post", "I need a better opener", or when the linkedin-post-writer skill needs strong opening options. Also triggered by "my posts aren't getting clicks" or "how do I get people to read my posts".

日本語の概要は準備中です。原文の説明を表示しています。

Create or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself (architecture, trade-offs, failure modes) use /ship:arch-design first — it hands back here to record the decision.

日本語の概要は準備中です。原文の説明を表示しています。

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.

日本語の概要は準備中です。原文の説明を表示しています。

Use when writing or formatting an ADR document using the MADR template, applying Definition of Done (E.C.A.D.R.) criteria, or verifying ADR completeness. Triggers on "write the ADR", "format as MADR", "check ADR quality", "mark gaps in ADR". Also triggers when a decision has been extracted and needs to become a document. Does NOT extract decisions from conversations (use adr-decision-extraction) or orchestrate the full extract-confirm-write workflow (use write-adr).

日本語の概要は準備中です。原文の説明を表示しています。

Write essays, articles, and blog posts in Paul Graham's voice — plain, spoken prose that reasons out loud and lands surprising true claims, not AI filler. Use when asked to write or rewrite something "like Paul Graham", "in PG's style", or to make a piece read like a person thinking on the page rather than generated text. Built from a stylistic model of 18 of his essays (see SOURCES.md).

日本語の概要は準備中です。原文の説明を表示しています。

Write, restructure, classify, and review documentation with the Diataxis framework. Use when the user asks to create, improve, audit, or reorganize documentation of any kind: knowledge bases, help centers, onboarding guides, process docs, manuals, runbooks, product or API docs, tutorials, how-to guides, references, explanations. Also use when the user mentions Diataxis, docs taxonomy, or documentation architecture, or asks why a document feels confusing. Also use for Simplified Technical English (ASD-STE100) or controlled-language rewrites of English technical docs. Not for marketing, legal, sales, press, or fiction writing unless the user wants a Diataxis-style analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Write insurance proposals for commercial accounts. TRIGGERS - Use when user needs help with insurance-proposal-writer related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Write insurance blog content for SEO and education. TRIGGERS - Use when user needs help with insurance-blog-writer related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Write a developer quickstart — minimal steps from zero to first successful API call. Use when asked to "write a quickstart", "get users from zero to first API call", or "write a getting started guide".

日本語の概要は準備中です。原文の説明を表示しています。

Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".

日本語の概要は準備中です。原文の説明を表示しています。

Use before you shorten, compress, or rewrite the BODY of an existing SKILL.md or agent .md — the moment you are about to cut text to reduce length. First inventory the file's operational anchors (exact code / command / API snippets, fail-closed workflow guards, and rule / threshold statements), preserve every one, then judge the rewrite by expected downstream task cost (exploration, debugging, recovery tokens) rather than by the resulting line count. A shorter skill that strips an anchor makes the agent MORE expensive per task, so length is never the objective and rewrite is not compression. Backed by Preserving Operational Anchors When Compressing Agent Instructions (arxiv 2606.09421v2). Triggers on shortening or refactoring a skill or agent body.

日本語の概要は準備中です。原文の説明を表示しています。

Research an issue deeply and present all context to the user. but the user writes the code. The LLM investigates code paths, finds relevant files, explains patterns, and identifies constraints. The user thinks through the approach and implements it. Use when ready to start working on an issue after oss-prep-to-contribute. Not for writing tests or documentation as a standalone contribution. Use oss-write-tests or oss-write-docs for those.

日本語の概要は準備中です。原文の説明を表示しています。

Write a full YouTube video description under 5,000 characters with a first-150-character hook (the only part visible before Show more, and what shows in search and suggested), timestamped chapters, naturally placed keywords, links, and a clear call to action. Covers long-form and YouTube Shorts. Becomes the create-post content that publishes with the video. Use to write or rework a description. Not for the title (use yt-title-optimizer) or the spoken opening (use yt-hook-scripter).

日本語の概要は準備中です。原文の説明を表示しています。

Appwrite is an open-source backend platform for web, mobile, and AI apps. This skill helps agents use Appwrite's real services—Auth, Databases, Storage, Functions, Messaging, Realtime, and Sites—instead of inventing a generic backend workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Decide what to borrow, adapt, or write before building something. Use when the user describes an app, tool, CLI, or feature they want to build and needs to know which parts already exist as open-source GitHub repos (BORROW), which are worth reading and adapting (KITBASH), and which to just write (WRITE). Every repository named is checked against the live GitHub API, so invented ones never reach the user.

日本語の概要は準備中です。原文の説明を表示しています。

Expert VSL (Video Sales Letter) and product marketing video storyboard writer. Use when creating sales videos, product demos, explainer videos, social media video content, or marketing video scripts. Use when asked to "write a video script", "create a VSL", "storyboard a sales video", or "script a product demo". Produces storyboard scripts optimized for handoff to motion designer and Remotion video production.

日本語の概要は準備中です。原文の説明を表示しています。

Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.

日本語の概要は準備中です。原文の説明を表示しています。

Write or fix the hook of a papercut reel. Produces the SAY / WRITE / SHOW / ALIGN block, five variants scored with the hook check, the frame-0 cover title and the motion out of the hook. Use for "write a hook for...", or when a reel's first three seconds lose people.

日本語の概要は準備中です。原文の説明を表示しています。

Full AI-assisted workflow for long-form SEO content (2,000+ words). Covers JTBD strategy, E-E-A-T quality standards, and 5 production phases: research, outline, draft, editing, and SEO/publishing. Built for B2B marketing agency context. Use when: user wants to write or optimize an SEO article, mentions "SEO content", "blog post", "GTM article", "long-form content", or asks to create content with keyword strategy.

日本語の概要は準備中です。原文の説明を表示しています。

NestJS testing patterns: Test.createTestingModule for unit/integration, mocking providers, e2e tests with INestApplication + supertest, ORM mocking (TypeORM/Prisma/Mongoose), test fixtures. Use this skill to: - Write unit tests for services with mocked dependencies. - Write integration tests with real DI but mocked external services. - Write e2e tests for HTTP endpoints via supertest. - Mock repositories/Prisma client correctly. - Cover services and controllers to ≥80%. Do NOT use this skill for: - Test framework setup (Jest/Vitest config — usually already in place). - Frontend tests. - Load testing (out of QA scope).

日本語の概要は準備中です。原文の説明を表示しています。

Apply the Minimum Sufficient Language (MSL) principle through the MSL Kernel to write anything a reader must act on. Bind the reader and what they already know, partition facts from the machinery that produced them, emit each admitted fact as an action, a verification, a judgment, or a state, and stop when every claim is checkable and the reader can act. Use for status updates, work-in-progress reports to your own user, closeout and convergence comments, tickets, pull request and review write-ups, incident and postmortem notes, emails, memos, and any draft for readers outside the work. Also use when the user says MSL, Minimum Sufficient Language, write this for stakeholders, drop the jargon, make this readable, or asks for a paste-ready draft.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever the user wants to create, improve, rewrite, review, tailor, or ATS-optimize a PRODUCT MANAGER resume or CV. Triggers include any mention of 'PM resume', 'product manager resume', 'product resume', 'PM CV', 'product management CV', plain-language asks like 'create my resume', 'build my CV', 'optimize my resume', 'review my resume', 'make it ATS-friendly', 'tailor my resume to this job description', 'help me get hired', the Spanish terms 'hoja de vida' or 'curriculum vitae', or a request to turn product/PM experience into a resume, quantify product impact, write PM bullet points, or prepare a resume for an APM, PM, Senior, Lead, Group, Director of Product, Head of Product, or CPO application. Also use for AI Product Manager, Growth PM, Platform/Technical PM, and Product Owner resumes. Do NOT use for engineering-only resumes, LinkedIn rewrites, portfolios, or cover letters unless the resume is the main deliverable.

日本語の概要は準備中です。原文の説明を表示しています。