메뉴
Contains well-defined rules for creating natural, accurate, and readable writing. Use this skill whenever authoring longer text, including reports, PR or CL descriptions, READMEs, system designs, analysis documents, or general documentation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Automates the triage of GitHub issues in the A2UI repository. Helps the oncall engineer by fetching untriaged issues, generating AI-suggested priorities, assignees, and responses, launching a local review dashboard, and bulk-applying approved decisions to GitHub. Use when tasked with triaging new GitHub issues or managing the repository backlog.
Step-by-step phased instructions for building new A2UI Core SDKs, Framework Adapters, and Inference SDKs from scratch in any client language.
Manage the evolution, merging, archiving, and cleanup of specifications and blueprints across the workspace.
Analytical navigation of A2UI Spec-Driven Development module and codebase blueprints.
Provides instructions on how to create a new language-agnostic A2UI Feature Blueprint, ensuring consistency and ease of cross-language implementation.
Provides instructions on implementing feature specs or module blueprint commit diffs in a specific codebase.
| name | natural-writing |
| description | Contains well-defined rules for creating natural, accurate, and readable writing. Use this skill whenever authoring longer text, including reports, PR or CL descriptions, READMEs, system designs, analysis documents, or general documentation. |
This document outlines strict rules to avoid common "AI-isms": stylistic and structural patterns that language models typically fall into. Follow these rules to produce content that is more understandable, and reads as natural, human-authored text.
Avoid words that are statistically overrepresented in AI text. Use simpler, more direct alternatives.
Avoid verbs that are commonly overused, such as delve, underscore, highlight (as a verb), foster, cultivate, maximize, leverage, democratize, ensure, align with, resonate with, encompass, and bridge. Also avoid adverbs like seamlessly and extensively.
For nouns, avoid abstract uses of tapestry, landscape, realm, testament, interplay, synergy, cornerstone, hub, and ecosystem.
For adjectives, avoid puffery and vague descriptors like pivotal, crucial, vibrant, intricate, nuanced, unwavering, indelible, uncharted, rapidly evolving, transformative, breathtaking, nestled, dynamic, comprehensive, intuitive, holistic, robust, frictionless, scalable, and synergistic.
Do not replace simple "is" or "are" verbs with flowery equivalents.
Do not use synonyms just to avoid repeating a subject's name (e.g., "the eponymous character," "the titular protagonist," "the celebrated author"). It is acceptable to repeat the name or use pronouns naturally.
Do not inflate the importance of a topic with vague praise. If a subject is important, the facts should demonstrate it without help.
Avoid phrases like "serves as a testament to," "marking a pivotal moment," "underscoring the importance of," "leaving an indelible mark," or "shaping the landscape."
Avoid attaching "dangling" present-participle phrases that offer vague commentary.
Delete clauses starting with "highlighting," "emphasizing," "reflecting," "showcasing," or "demonstrating" if they just restate the obvious or add fluff.
Maintain a neutral tone. Avoid "advertisement" words like boasts, features (as a verb), offers, premier, leading, state-of-the-art, committed to, and dedicated to.
Language models often end articles with a generic "Despite challenges... remains important" conclusion. Do not end with a summary paragraph starting with "Despite [X], [Subject] continues to..." or speculating on the future. End with the last fact.
Do not treat a descriptive article title (like a list or broad topic) as a proper noun in the first sentence.
Do not populate "See Also" sections with broad, generic terms. Links must be directly relevant and specific to the subject.
Avoid vague "weasel words" like "Experts argue," "Observers have noted," or "Several sources indicate" unless you cite specific people immediately. Do not claim a subject interacts with a "broader" history or trend unless a source explicitly says so.
Avoid sentences that structure a contrast unnecessarily.
Avoid listing exactly three adjectives or three noun phrases to sound "comprehensive."
Do not use "from X to Y" unless X and Y are endpoints of a logical scale (like time or size).
Use sentence case for headers (e.g., "Early life," not "Early Life"). Do not use title case in headers.
Do not use inline-header lists (such as * **Header:** Description...). Instead, use prose or simple lists.
Avoid excessive bolding of keywords, "key takeaways," or names in the body text, except for the first mention in the lead.
Do not use emojis (🚀, 🧠) or unusual bullets (#, -) in lists. Use standard bullets (*).
Avoid creating tables for simple information that easily fits in a sentence.
Ensure markup is context-appropriate; do not use Markdown (like ##) in formats that do not support it (like Wikitext) unless it is explicitly converted.
Use straight quotes (", ') and straight apostrophes ('). Do not use curly or smart quotes (“, ’).
Use em dashes sparingly, as language models often overuse them for emphasis. Prefer commas or parentheses instead.
Never generate a citation unless you are looking at the source. Do not invent URLs or DOIs. Do not assume a book exists or contains a specific fact without verification.
Avoid collaborative filler at the start of responses, such as "Certainly!", "Here is the information," or "I hope this helps." State the content directly.
Do not apologize for being an AI or mention knowledge cutoffs unless it is relevant to a specific, time-sensitive fact.
Do not preface responses with subject lines.
Keep edit summaries concise and informal, avoiding verbose paragraphs.
