「writing」の検索結果

Build AI grant writing assistance systems. TRIGGERS - Use when user needs help with ai-grant-writer-system related tasks.

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

Build AI email writing systems. TRIGGERS - Use when user needs help with ai-email-writer-system related tasks.

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

Build AI documentation writing. TRIGGERS - Use when user needs help with ai-documentation-writer related tasks.

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

Build AI blog writing systems. TRIGGERS - Use when user needs help with ai-blog-writer-system related tasks.

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

Conventions for writing justfile recipes in Nix-based projects.

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

Generate PDFs from LaTeX (.tex) or Markdown (.md) using Tectonic, a self-contained TeX engine. Use whenever the user wants a PDF, whether converting markdown, compiling existing LaTeX, writing a document from scratch (reports, resumes, letters, CVs), or live-rebuilding while the user edits. Trigger on words like "make a PDF", "convert to PDF", "render this markdown", "compile this tex", "latex", "tectonic", "typeset" — even when the tool is never named.

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

Behavioral guidelines to reduce common LLM coding mistakes. Derived from Andrej Karpathy's observations. Use ALWAYS when writing, reviewing, or refactoring code. Covers assumption surfacing, simplicity, surgical edits, and goal-driven execution with verification.

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

Use when creating new skills, editing existing skills, or verifying skills work before deployment. Applies Test-Driven Development to process documentation — watch agents fail without the skill, write the skill that addresses those failures, then close loopholes.

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

Use when you have a spec or requirements for a multi-step task, before touching code or producing output. Turns a design into bite-sized, copy-pasteable tasks with exact paths and complete code.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Use when upgrading an existing TypeScript codebase from Inngest SDK v3 to v4, or when fixing mixed v3/v4 API usage. Covers detecting current SDK usage, moving triggers into createFunction options, replacing EventSchemas with eventType/staticSchema, moving serve options to the client, updating realtime imports, rewriting step.invoke string IDs, checkpointing/serverless runtime settings, Connect option changes, and verification.

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

Use when writing Swift code for Apple platforms - iOS, macOS, visionOS. Covers Swift 6 concurrency, actors, Sendable, async/await, SwiftUI, MVVM architecture, Metal GPU programming, RealityKit ECS, visionOS scenes, interpolation/animation, advanced collection types, property wrappers, Combine bridging, error handling, testing, and API design patterns.

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

REQUIRED before writing code for any feature touching auth, payments, credentials, tokens, sessions, file upload, user data, untrusted input, deserialization, network endpoints, or data deletion. Scope by that surface, not the task label — a research/experimental/local-only feature with none of it doesn't need this. Invoke it, record answers inline in the design doc or PR description, then write the code. Skipping this is how auth bypass, token leakage, and delete-the-wrong-record bugs ship. If the feature touches any of those surfaces and this hasn't run, the design is incomplete — do not proceed to implementation.

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

Use when writing a Shipfox workflow from an idea or adapting an existing workflow without a template.

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

Complete toolkit for programmatic video creation with Remotion + React. Covers animations, timing, rendering (CLI/Node.js/Lambda/Cloud Run), captions, 3D, charts, text effects, transitions, and media handling. Use when writing Remotion code, building video generation pipelines, or creating data-driven video templates.

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

Teaches you how to delegate tasks to Cowork so clearly that you get exactly what you asked for — every time. Use when learning how to give better instructions, for improving your delegation technique, during early Cowork adoption when results feel off, when writing clearer task descriptions, or when the user says "how do I ask cowork to do things", "delegation tips", "better instructions", "cowork isn't doing what I want", "help me delegate", "my results are bad", "how do I give better prompts", "cowork keeps getting it wrong", "I don't know how to use this", or "how do I get good results".

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

Use this skill when writing sprint contracts in VCSDD strict mode. Provides grading criteria patterns, dimension weight guidelines, and pass threshold formulation for the 5 review dimensions.

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

Use this skill when writing Phase 1b verification architecture documents. Provides purity boundary mapping, proof obligation design, and tier assignment guidance.

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

Use when evidence needs grading before anyone reasons from it — the user asks "how reliable is this?", "grade this source", "check this report", "can I trust this article?", "is this corroborated?", or hands over a URL, a pasted report or a Liberty91 event ahead of an ACH or assessment. The Quality of Information Check from the CIA Tradecraft Primer, adapted for vendor and press CTI reporting. Resolves each document to its originating source, splits it into claims, and grades every claim on two written elements, access level (how the source knows) and claim support (what backs the statement), with a stated rationale, using a fixed rubric with hard caps. The grade is not an Admiralty rating. Five outlets citing one vendor report count as one source; anything that cannot be traced to a primary is capped, not guessed. Returns a graded claim table, gaps, a deception screen and JSON. /ach, /threat-assessment and /writing-assessments run it first by default.

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

Use when the user asks for a YARA rule, "write YARA for this sample/family", or `/hash-investigation` / `/malware-analysis` surfaces a sample worth a static-content rule. Pattern-matching rules for identifying malicious files.

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

Use when you need to know where a piece of reporting actually came from — the user gives an article URL and asks "where does this come from?", "who is the original source?", "is this just a rewrite?", or another skill needs the provenance chain before grading or citing a report. Follows an article's links and named attributions back to the originating vendor, government, victim or actor document and returns the chain, the primary's stated access and confidence language, publication dates, and every hop it could not resolve. Deterministic — a script or the Liberty91 platform resolves the chain; the model does not reconstruct it from memory. Invoked by /quality-of-information-check, /threat-actor-profiling, /campaign-tracking and /intelligence-writing. Works on any URL with no API key.

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

Use when the user asks to write a threat / risk / vulnerability assessment, or wants the appropriate template for each type. Distinct structures and section ordering per assessment kind. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Confidence is capped by the weakest load-bearing claim, and at Moderate when the evidence is ungraded.

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

Detect and remove the tells of AI-generated writing in BOTH English and Spanish, and read back the evidence honestly. Use when the user asks to "de-AI" / "humanize" / "un-slop" a draft, to examine whether text carries the tells (delve, tapestry, "it's not just X, it's Y", "here's the thing", em-dash overuse, an assistant's own closing line left in the document), to compare documents for overlap, or mentions signs-of-ai / SignsOfAI. Backed by the SignsOfAI engine — for a measured 0–100 score, sentence-rhythm burstiness, originality, citations, a writer baseline or perplexity, hand off to that engine (web app, CLI or MCP server) as described below. It cannot determine who wrote a text and must never imply that it can.

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

Comprehensive testing skill covering unit, integration, and e2e testing with TDD. Use when writing tests, improving coverage, or setting up testing infrastructure. Keywords: test, TDD, unit test, integration, e2e, coverage, mock, jest, vitest

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