Results for “plain-language”

Drafts civil trial verdict forms with sequentially numbered jury questions covering liability, affirmative defenses, damages, comparative fault, and special interrogatories. Enforces plain-language phrasing, logical conditional flow, and jurisdiction-appropriate formatting. Use when preparing verdict forms, special verdict forms, jury interrogatories, or general verdict forms with interrogatories.

Explain any concept in plain words with one concrete analogy - clear enough for a smart child or a busy outsider, never condescending, never wrong.

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

补充上下文，用更简单、明确的中文重新解释。

Parses Simplicité log files from raw .txt format, filters fields to reduce noise, and outputs structured JSON for efficient AI context usage.

Generates ultra-minimalist, editorial-style web interfaces with warm monochrome palettes, typographic contrast, bento-grid layouts, and muted pastel accents, rejecting generic SaaS design trends.

从真实的帖子、文章、发布说明、文档或网站文案中构建基于源材料的写作风格档案，然后在内容、外展和社交工作流中重复使用该档案。当用户希望保持声音一致性而不使用通用的AI写作套路时使用。

Use when content is verbose, repetitive, or padded and needs tightening while preserving meaning

Reduce complexity of over-engineered code. Identify unnecessary abstractions, remove dead code, flatten deep nesting, and simplify logic while preserving behavior.

Provides a comprehensive reference for the Move programming language, covering its resource-oriented philosophy, type system, abilities, and safety guarantees for Sui and Aptos blockchains.

当需要进入高效学习、创作或问题解决的心流状态时，调用此模型作为环境与心理准备框架

朴树（音乐人）认知与表达框架（压缩蒸馏）：内向真诚、少话多留白、生命与创作一体… 触发：平凡之路 等。不消费抑郁；非医疗建议

Provides idiomatic Go patterns, best practices, and conventions for writing, reviewing, and refactoring Go code.

Drafts structured client memoranda translating legal analysis and strategic recommendations into plain language for non-lawyer audiences. Covers corporate governance, fiduciary duties, compliance, and transactional advice. Enforces standard memo architecture: heading block, executive summary, background, analysis, options, and recommendations. Use when preparing client-facing memos, opinion letters, or governance briefings.

Apply core PHP language standards and modern 8.x features. Use when working with PHP 8.x features like enums, fibers, readonly properties, or named arguments.

Use when the user wants to humanize text, make writing sound less like AI, or rewrite content to feel more natural. Triggers on "humanize", "make it sound natural", "too robotic", "sounds like AI", or similar. Works in Hebrew and English. Always output only the rewritten text — no explanations.

Core idioms, style guides, and best practices for writing idiomatic Go code. Use when writing Go code following official style guides and idiomatic patterns.

NLVR2: A Visual Reasoning Benchmark for Natural Language

用于构建健壮、高效且可维护的Go应用程序的惯用Go模式、最佳实践和约定。

Remove AI writing patterns from prose. Use this skill when writing, drafting, editing, reviewing, or revising any text to eliminate predictable AI tells, slop, and formulaic patterns. Trigger this skill whenever the user asks to "deslop", "de-AI", "make it sound human," "remove AI patterns," "remove AI tropes," "clean up AI writing," fix "slop," "deslop" text, or review prose for authenticity. Also use when the user asks you to write or draft anything and wants it to sound natural rather than AI-generated. Common use cases include scientific writing (manuscripts, abstracts, cover letters, grant narratives, discussion sections, peer review responses), blog posts, newsletters, memos, reports, and any other substantial prose.

Publication Specialist - Writing, Review, Pre-registration & Quality Assurance Light VS applied: Avoids template-based writing + audience-specific message design Absorbed G3 (Peer Review Strategist), G4 (Pre-registration Composer), F1-F3 (Quality functions) capabilities Use when: writing abstracts, creating summaries, peer review response, pre-registration, reporting checklists, reproducibility Triggers: abstract, plain language, press release, summary, communication, peer review, revision, pre-registration, OSF, PRISMA, CONSORT, reproducibility

Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by hand and the outcomes they should expect. Use when you want to create, draft, generate, or outline a manual test plan, manual QA steps, hands-on verification steps, or an acceptance walkthrough for a feature, change, branch, plan, or PR. When the plan holds more than five tests and at least two natural categories emerge, both the test list and the detail sections are organized under plain-language categories. When nothing in the supplied context can be manually tested, it says so and asks for more context instead of producing a document. Does not analyze code for automated test coverage gaps — use automated-test-planning. Does not write test code — use tdd. Does not review code quality — use code-review. Does not stress-test an existing plan — use iterative-plan-review.

Splits a body of context into a sequence of vertical-slice build phases where each phase is independently demonstrable to a real user and each builds on the previous. Use when the user wants to plan, sequence, phase, slice, break down, or order the build of a feature, capability, system, or initiative, and produces a plain-language phased build outline. Does not produce implementation detail — use plan-implementation. Does not specify behavior that has not been decided — use plan-a-feature. Does not perform gap analysis between two artifacts — use gap-analysis. Does not break a plan into independently-grabbable work items — use plan-work-items.

Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wants to be walked through, taught, paced through, or shown around code or a branch step by step, or to learn how a change works before reviewing or extending it. Stops after every step and waits, so the learner sets the pace. Paces through code that already exists and builds nothing — to build new work while being paced through it, use pairing. Does not produce a written overview to read alone — use code-overview. Does not review code quality — use code-review. Does not diagnose bugs — use investigate.