'prose' 검색 결과

Audit and repair Pharos documentation against the codebase. Use for documentation update passes, verified-doc drift, source-path/doc-sync failures, methodology/doc routing updates, or requests to verify docs without trusting existing prose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when planning a source-grounded method overview, architecture, pipeline, system/data-flow, mechanism, or agent-workflow figure for a CS or deep-learning paper. Produces an editable figure brief before image generation or manual redrawing; not for plots, tables, or general prose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft or restructure research-paper sections, refine local prose, and audit manuscript-wide consistency. Use for evidence-grounded academic writing and revision, not independent acceptance-risk review or official rebuttal management.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ask Daniel a blocking decision as options with a recommendation and honest pros/cons, rather than prose. Use whenever work is blocked on a judgment call, a product decision, an approval, or a choice between approaches — instead of writing "let me know which you prefer" at the end of a message.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert an existing prose, flat, or loosely organized mathematical proof into a source-mapped Lamport-style hierarchy without repairing or completing its mathematics. Use when a submitted proof needs a traceable hierarchical rendering before a forward Lamport audit or for clearer presentation. Do not use to invent a proof, certify validity, or restructure an already hierarchical proof merely to audit it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit an existing Lamport-style hierarchical mathematical proof forward for validity and whether its hierarchy, scope, dependencies, side conditions, and proof constructs discharge the stated theorem. Use when the central question concerns a top-down proof with numbered levels, subproofs, ASSUME/PROVE, SUFFICES, PICK, CASE, DEFINE, Q.E.D., or prose equivalents. For an ordinary proof that first needs source-preserving hierarchy, use convert-lamport; for conclusion-first AND/OR obligation reconstruction, use reverse-lamport. Do not use to generate or replace a proof, or to audit Lean, Coq, Isabelle, or other proof-assistant source.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when synchronizing frontend project documentation with source-of-truth files such as package.json, lockfiles, config, env examples, routes, API clients or server routes, schemas, components, tests, CI, build/deploy config, ADRs, changelogs, or migration notes. Do not use for general prose polishing only; Chinese triggers include document synchronization, update README, docs sync, environment variable documentation, command list, API Document synchronization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Improve an existing agent SKILL.md through one gated cycle: select the target (default this skill), snapshot the committed baseline, diagnose against skill-design-principles plus four rubric dimensions, apply exactly one focused change, and ship only if a different agent than the author PASSes with quoted evidence. Use when the user says "improve this skill", "improve-skill", "iterate on SKILL.md", or "apply skill-design-principles to a skill". Do not use for code slop over a duration (anneal), generic timeboxed work (timeboxed-iterating), graph orchestration (workgraph), metric hill-climb on a codebase (autoresearch), or stripping slop from existing prose (catalog-deslop).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce a researched long-form article from a topic prompt via an orchestrated pipeline - research agent (first-person sources, working-definition gate), narrative-architecture outline, writer/cold-reviewer loop with an explicit ACCEPT/REVISE verdict contract, then a catalog-deslop pass with a regression gate. The orchestrator dispatches subagents only; the writer never judges its own draft. Use when the user says "article factory", "write an article about X", "run the article pipeline", or asks for a researched long-form piece produced end-to-end. For essays and micro posts in the user's own voice without a research stage, use the prose skill instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator loads these files, fenced as untrusted data, for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when the user says "blog brand", "create brand context", "BRAND.md", "VOICE.md", "establish editorial brand". Not for learning a voice from existing posts (blog-style) or managing persona JSON (blog-persona).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Edit academic prose in LaTeX manuscripts or supplied text at light, moderate, or strict intensity. Improve grammar and clarity while preserving scientific claims, uncertainty, numbers, citations, and LaTeX structure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Summarizes biotech patent families and disputes into litigation-ready intelligence briefs. Trigger when the user provides patent applications, issued patents, PTAB filings, prosecution histories, licensing materials, or litigation documents in biotechnology domains and requests a summary, risk assessment, or FTO analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deep analysis of competitor patent claims: element decomposition, scope interpretation, equivalents prediction, prosecution history estoppel analysis. Automatically converts PDF/DOCX/DOC patent files to structured Markdown via patent-pdf-to-md skill before analysis. Invoke when user asks to analyze/parse competitor patent claims, decompose claim elements, assess claim scope, or perform 权利要求解析/要素分解/保护范围解读. 竞品专利权利要求深度解析：要素分解、保护范围解读、等同范围预判、审查历史限制分析。自动调用patent-pdf-to-md技能将PDF/DOCX/DOC专利文件转换为结构化Markdown后再进行分析。当用户要求解析竞品专利权利要求、要素分解、保护范围时触发。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produces litigation-grade case summaries for animal law disputes including cruelty/neglect prosecutions, ownership/custody, dangerous animal designations, veterinary malpractice, and service/assistance animal accommodations. Builds exhibit-cited factual timelines, maps evidence to statutory elements, evaluates expert evidence, and assesses remedies with jurisdiction-specific legal research. Use when summarizing animal law cases, analyzing animal cruelty charges, pet custody disputes, dangerous dog hearings, veterinary malpractice claims, or assistance animal accommodation matters. Also trigger for animal forfeiture, bite liability, wildlife possession, or animal-related court filings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manages intent — features, enhancements, bugs and the reasoning behind them — recorded as prose in the knowledge base with a lifecycle. Use when capturing new work, moving work through backlog, refinement or implementation, releasing or cancelling work, or asking what is pending, in flight, or no longer valid.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write technical documentation that matches the measured profile of professionally-written docs. Carries the craft rules derived from 114k words of pre-2022 documentation (SQLite, PostgreSQL, Python, Django, Rust, Go, Pro Git, nginx), the per-Diátaxis-type numeric targets, and the copywriting register for page leads. Use when drafting or rewriting any documentation prose, or when a page is factually right but reads as machine-written.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Oracle-bound spec-review check that every structured Rollout prerequisite binds to an enforcement-type acceptance criterion. A prerequisite whose `enforced-by` is missing, dangling, or points at a non-enforcement AC is a BLOCKER (hard-blocks implementation entry via the checker fan-out verdict); a prerequisite left in free prose is ADVISORY. Read-only. Runs in the spec-review fan-out before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dev-only check that a drafted spec for THIS baseline repo won't ship dev-tree references to consumer installs. Catches three failure modes — shipped SKILL.md prose that references paths under `src/`, `tests/`, `scripts/`, `obj/` as runtime invocations (in ```bash fences``` OR `inline backticks`, plus shipped `.mjs`/`.js`/`.sh`/`.py` helper-file imports); new Python helpers added under `.claude/skills/<slug>/` (shipped helpers must be `.sh` or `.mjs`/`.js` going forward); and imports of modules that aren't in `obj/template/.claude/manifest.json` (consumer won't have the file). The aggregate scanner (`scan-shipped-skills.mjs`) walks only baseline-owned skill dirs (via `owner: baseline` frontmatter) at top level — `references/` and other subdirs are documentation, not runtime. BLOCKER findings hard-block implementation entry; ADVISORY surfaces but doesn't block. Read-only — surfaces a punch list; maintainer edits the spec and re-runs until CLEAN.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bring documentation prose down to a high-school reading level without losing precision. Runs after the content is written and before humanizer. Targets grade 9 on four measures — sentence length, vocabulary, clause load and jargon density — and carries the rewriting moves that actually shift them.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.