640건 · 관련도순
Maintain a collection of architecture decision record templates, examples, translations, and tool links. It explains which files to update for each contribution and how to review pull requests for completeness, consistent formatting, and relevant content.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Update Bifrost Helm charts, the packages used to configure deployments, while keeping settings, schemas, templates, and documentation aligned. Check the published release and group changes into the next unreleased version.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn product management notes or workshop material into a structured skill, or update an existing one. Follow a workflow covering duplicate checks, drafting, validation, catalog updates, and optional ZIP packaging for upload.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Draft structured RFCs, proposals for gathering feedback before a major decision. Organize background, weighted criteria, alternatives, costs, and a recommendation so stakeholders can compare choices and understand the reasons for the proposed direction.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a technical design document before implementation by answering questions about the problem, scope, architecture, risks, and delivery plan. The skill adjusts sections to project size and covers security, testing, monitoring, and recovery where relevant.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Choose how an AI team handles each task, from a direct coordinator answer to parallel work by several agents. Includes decision criteria, example requests, and a short assignment template for small tasks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Bring project Markdown documentation into line with code changes. Update factual references such as paths, versions, and counts, check consistency and document links, and reflect the documentation work in the pull request description.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Improve APM CLI commands, help text, setup flows, and error messages. The skill checks consistency with familiar developer tools and guides wording so users understand failures and know what action to take next.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a PipesHub GitHub release into a readable changelog with feature highlights, categorized changes, PR links, and author credits. The skill writes a detailed release file and updates the main changelog and release index.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize code and data projects into clear folders with documented workflows, data fields, dependencies, and changes. The skill guides new machine learning and data processing scripts, while preserving existing project structure during modifications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference, understand, how-to, troubleshooting, getting-started) plus the built-in skill description and README. If you just implemented a feature and need to update docs, this is the skill to use. Never manually edit website docs without cross-validating flags against Go source first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and terminology across a docs set — prefer it over editing documentation unaided. Covers reader and doc-type fit, second person and active voice, procedures, headings, lists and tables, code samples and placeholders, link text, notices, the word list, timeless docs, and accessibility. For code comments and naming, see clean-code. For marketing or landing-page copy, see storybrand-messaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
House style for user-facing documentation — voice, scope, structure, and what to leave out. Use this skill whenever writing, editing, or reviewing anything a user reads to learn how to use a tool — help center articles, getting-started guides, tutorials, feature docs, README usage sections, in-app help, release notes, or FAQ entries. Trigger it even when the request is phrased plainly — "document this feature", "write docs for X", "explain this to users", "write a README for this library", "turn these notes into a guide" — and even when no style guidelines are mentioned. Also use it to review existing docs for tone, bloat, or leaked implementation detail. Do not use it for internal engineering docs, architecture write-ups, RFCs, or code comments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write and edit project docs (README/markdown) as a glossary of principles, not a mirror of the code. Use when creating or revising a README; when a doc enumerates exact scenes, scenarios, helpers, class ids, file lists, or command/flag matrices the code already holds; when trimming narrative or changelog out of a doc; or when deduplicating overlapping docs and wiring a root doc to its sub-docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write or update READMEs, docs, repo instructions and handoff notes, checked against source. Use when: documenting something, writing a README or leaving a session handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit agent harness health: Claude/Codex agent parity, skill registry consistency, README.md sync, and protocol file wiring. Use when agents, skills, README.md, or development-protocol files move, split, or drift.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
用户要建立或修改设计系统时用：品牌的颜色、文字样式、间距与圆角 tokens，给智能体看的品牌手册 README，bundle 与预览，标志、图标与字体。在工作目录写一个设计系统目录（design-system.json 加 tokens.json、README.md、components/、assets/、fonts/），可以从代码仓库或设计工具里的真实来源整理；图片、视频与 PDF 导入设计系统的素材库，校验通过后线程里出现设计系统卡片，用户在功能区预览与编辑；做好的设计系统可以装进设计稿。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
House README standard: structure, badge row, tone, per-archetype templates, and verification gates for steipete/openclaw repos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflows. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write or update READMEs, docs, repo instructions and handoff notes, checked against source. Use when: documenting something, writing a README or leaving a session handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.