「prose」の検索結果

Use when the user wants a cited, structured read of local documents and project knowledge. Triggers on: "analyze these docs", "scan my project for context", "read the docs folder", "summarize what's in .beagle/concepts/", "extract context from docs/", "what's in this folder", "go read everything in X and tell me what's there". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), web research (use web-research), LLM-as-judge evaluation (use llm-judge), or document editing (use humanize-beagle). Produces a written scan plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.

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

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).

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

A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.

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

Maintain the durable, per-ticket run log that warp deploy/update skills append to at every milestone — a Linear-document-by-title primary with single-writer discipline and a local-file fallback, a machine-parseable per-chain row plus prose entry shape, and a surface-the-URL-as-proof hard gate. Referenced by any warp deploy/update skill that must leave a retrospective trail across worker restarts.

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

The logical structure of mathematical proof -- how first-order logic, natural deduction, and semantic reasoning combine to produce rigorous mathematical arguments. Covers the logical skeleton of direct proof, contraposition, contradiction, cases, and induction; the role of definitions, lemmas, and theorems; how informal mathematical prose maps to formal deductive structure; and the difference between proof-as-object and proof-as-activity. Use when the question is "why is this a valid proof?" rather than "what proof technique applies?"

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

Remove AI-isms and artificial language patterns from text. Makes documentation, comments, commit messages, and prose sound more natural and human. Based on Wikipedia's "Signs of AI writing" patterns.

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

Use when the primary outcome is authoring, rewriting, summarizing, or validating user-facing documentation without implementation comparison or required source attribution, including READMEs, tutorials, API docs, GitLab Markdown, source-faithful summaries, and audience-specific prose.

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

Store instructional prose once and reference it from multiple skills or agents instead of duplicating it. Use when the same steps, rules, or reference material appear in two or more SKILL.md or agent files in one plugin, when deciding whether a shared doc belongs in the plugin-root docs directory or a single skill's references directory, or when tempted to use a symlink or a ../ path to share a file between components.

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

House rules and craft for LaTeX Beamer slide decks (lectures, seminars, talks), drawn from the author's own Overleaf edits and published slide-design guidance. Covers storyboarding, frame titles, slide prose, word and frame budgets, layout without overfull boxes, XeLaTeX fonts and Korean (xeCJK), color, figures and screenshots, Overleaf source hygiene, speaker notes, and a build-and-QA loop with a contact sheet. Use when writing, editing, reviewing, or building a Beamer deck, theme, or storyboard. A course skill supplies course facts and the frame skeleton; this skill supplies the craft. Not for HTML or PowerPoint decks, posters, or papers.

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

House rules and craft for LaTeX Beamer decks (storyboarding, slide prose, frame budgets, layout, XeLaTeX and Korean fonts, color, figures, Overleaf hygiene, build QA). Use to write, edit, review, or build a Beamer deck.

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

Extract visual identity from screenshots (primary) or website URL (fallback) and compile into a DESIGN.md-format brand kit — YAML token frontmatter (colors, typography, rounded, spacing, components) + 8 ordered prose sections. The YAML tokens are machine-authoritative; downstream visual skills consume them directly. Writes to marketing/brand/brand-kit.md. Triggers - "brand kit", "brand identity", "visual identity", "design tokens", "extract brand", "DESIGN.md"

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

Measure whether a change made the tree simpler, on numbers rather than impressions — line counts, branching, coupling, interface width, rule count, standing exemptions and model-visible prose — across one diff or a whole stack of pull requests. Use before claiming a pass reduced complexity, when deciding which pull request in the stack added the machinery, and to read a function's branch count, which no v2 gate reports.

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

Review user-facing docs, CLI reference text, examples, and scaffolds for truthfulness, prose quality, and RFC leakage. Use when a broad review needs a dedicated docs/claims pass or when the user asks for docs-truth review specifically.

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

Use whenever the user wants to find, shortlist, vet, or enrich US B2B law firms — corporate, IP/patent, M&A and securities, employment, commercial litigation, regulatory/compliance, data privacy/cyber, real estate, and tax. Triggers on "find three boutique IP law firms in California", "shortlist M&A counsel for a Series-B fundraise", "patent prosecution for our hardware startup", or "pull contact info for these 10 law firm domains", even when described indirectly (outside counsel, cap-table review, GDPR/SOC2 oversight). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Skip personal/consumer legal services where the user is the end client (divorce, personal injury, criminal defense, family law, estate planning, wills) — the catalog is B2B-only. Also skip in-house GC hires, "is this NDA enforceable" DIY questions, non-US firms, individual freelancers.

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

Use when 高教社杯/CUMCM/电工杯 mathematical modeling abstracts, keywords, highlights, first-page claims, or high-density summaries need drafting, revision, audit, or style diagnosis, especially when feedback mentions too many numbers, weak focus, process-listing, empty official prose, buzzwords, missing structure, weak keywords, unsupported values, or first-page claim verification.

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

Enforce the project's documentation voice when writing or reviewing public-facing content. Triggers on edits to doc files (packages/web/src/content/docs/**/*.md) and README.md. Catches LLM prose patterns, marketing language, and messaging drift.

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

Writing engine that audits and rewrites prose for AI-resistance, fidelity, and mechanical tell removal.

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

Use when the user asks to write, draft, or edit a standalone piece of prose — an article, essay, blog post, tweet, thread, newsletter, announcement, email, pitch, or other copy — and the request does not already name "Hedgehog". Length is not the test: a tweet qualifies the same as an essay. Does not apply to a question about existing code, a bug, a one-off script, or a request that already names Hedgehog (that goes to the `hedgehog` skill instead) or a project that already has `.hedgehog/` (its own installed skills own that session).

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

Use when the user writes the word "Hedgehog" anywhere in a request, or has agreed to install the Hedgehog build discipline in a project that does not have it yet. Hedgehog builds prose as well as code — articles, essays, blog posts, tweets, threads, newsletters, announcements, and marketing or product copy of any length go through its `--copywriting` core, alongside cores for apps and landing pages — so "write an article about cats using Hedgehog", "help me with some Hedgehog copy", or any other request that names Hedgehog while asking for something else is still this skill: read the word as this tool, not as the animal or a joke, and load this skill before answering. Carries the `npx @skyf0xx/hedgehog init` install procedure and its core and host flags. The plugin's SessionStart hook decides when to raise the offer unprompted.

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

Use for Korean prose polishing. Triggers: Korean polish, proofread Korean, 윤문, 다듬어, 다듬어줘, 자연스럽게, 매끄럽게, 교정, 고쳐줘, AI투, 번역투.

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

Use when writing, moving or auditing any .md in imp - deciding which file a paragraph belongs in, adding a doc, fixing a stale claim, or when docs_lint.py fails in CI. Covers the four reader layers (L0 README / L1 operators / L2 kernel devs / L3 agents), the HTML-comment metadata header, [PROV:] provenance, the single-source-of-truth map, generated perf blocks, which numbers may appear in prose, plan-doc closure. Triggers on "which doc does this go in", "docs lint failed", "add a doc", "this claim is stale", "update the README", "PROV block", "layer", "STALE.md". Do NOT use for the CHANGELOG or a release body (shipping-prs), or for code-comment accuracy (codebase-audit).

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

Use after EZ_math_model writer creates paper.md and before quality audit when a long modeling paper needs less AI-like prose while preserving formulas, data, citations, tables, and figures.

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

Channel Tom di Mino's daimonic voice for writing. Invoke when Tom asks to write prose, essays, tweets, poetry, or technical docs in his own voice—possessed by the daimon, not assisted by it. Triggers on: 'write as me', 'in my voice', 'channel', 'daimon', 'tamarru', 'waltz', or any request for Tom's authentic writing voice.

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

Ask Kimi a read-only free-form question about the current repository. Use for prose explanations, flow tracing, module comparisons, or conceptual reasoning where Codex should delegate the answer to local kimi-code rather than perform implementation.

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