Results for “plain-language”

Explains bonds across financial, legal, and contractual contexts, covering bond investing, surety and performance bonds, bail bonds, and contract bond obligations in plain language.

Turns any folder of files into a navigable knowledge graph with community detection, producing interactive HTML, GraphRAG-ready JSON, and a plain-language report.

Distills the current conversation or a plain-language prompt into a production-ready, self-healing Claude Code skill with pre-flight checks, validation gates, self-review, and learnings capture.

Builds a navigable knowledge graph from any folder of files, with community detection, an audit trail, and outputs including interactive HTML, GraphRAG-ready JSON, and a plain-language report.

Produces neutral, section-pinned U.S. legislative bill summaries translating statutory language into plain terms with identifying data, provisions, fiscal impacts, and controversy. Use when summarizing bills, analyzing proposed legislation, preparing bill briefs, digesting committee reports or fiscal notes, or writing legislative updates.

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.

Technical writing proficiency covering clarity principles, audience analysis, information structure, editing techniques, and style enforcement. Use when writing or improving any technical content — docs, specs, guides, or explanations. Also trigger for 'technical writing', 'write clearly', 'simplify this', 'rewrite for clarity', 'plain language', 'writing style', or 'editing pass'.

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.

Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.

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

Performs a gap analysis between two artifacts (a current state and a desired state) and produces a plain-language, stakeholder-readable report indexed by stable gap IDs. Use when the user wants to compare, evaluate, audit, or reconcile one artifact against another. Does not investigate runtime bugs — use investigate. Does not assess module-level architecture — use architectural-analysis. Does not research open-ended options with no second artifact to compare against — use research.

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

Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.

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

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

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

Write user-facing copy following Sentry's brand guidelines, covering Plain Speech and Sentry Voice tones for UI text, documentation, and marketing content.

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.

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.

Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle, balanced (default), full, voice-match, anti-detector. Use when user says "humanize this", "make this sound human", "de-slop this", "rewrite without AI tone", "match my voice", "less robotic", or invokes /unslop. Also auto-triggers when text-quality is requested.

Conversational Pattern Restoration — Fix flat, robotic AI responses across any model and any personality. Restore YOUR natural conversational texture without triggering hype drift. Universal framework tested on 8+ models (Claude, GPT-4o, Grok, Gemini).

Extracts and formalizes domain terminology from a conversation into a consistent glossary saved to a local file.

Single entrypoint for taw-kit. User types `/taw <anything in VN or EN>` — this skill classifies the intent (BUILD / FIX / SHIP / MAINTAIN / ADVISOR) and loads the matching branch file to execute. Replaces the old one-command-per-task model (/taw-new, /taw-add, /taw-fix, /taw-deploy, /taw-security) with a single unified command. Supports dev workflows out of the box: test, upgrade, clean, perf, rollback, refactor, types, seed, review, stack-swap, status, and ADVISOR group (analyze, suggest, coverage, adversarial, scope-check) for opinionated review of existing code. User-visible strings match the user's input language (Vietnamese by default for VN users). Two modes: SAFE (default — clarify + approval, max 1 round-trip) and YOLO (skip gates, smart defaults — for demos/power users). YOLO triggers: prose contains `yolo`, `nhanh nha`, `lam luon`, `khoi hoi`, `auto`, or args start with `yolo`. Trigger phrases (EN + VN) — broad match so user can keep typing plain prose without re-invoking /taw every turn. Grouped by

Flamingo: A Visual Language Model for Few-Shot Learning

Plain-English translation layer for non-technical Copilot CLI users. Translates every approval prompt, error message, and technical output into clear, jargon-free English with color-coded risk indicators.

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".