'readme' 검색 결과

Document why software decisions were made, which alternatives were considered, and what trade-offs remain. Create architecture decision records, README guidance, API documentation, and changelogs that help future contributors and AI agents understand the project.

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

• Recording design decisions and rejected alternatives
• Documenting public API changes
• Updating README setup instructions

Create an animated diagram showing request flows, background jobs, or feature changes. The result is a single SVG image for README files, pull requests, issues, or blog posts, with support for light and dark themes.

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

• Explaining request and data flows
• Illustrating how a background job works
• Showing feature changes in a pull request

Review prose for repetitive wording, inflated language, and overly regular structure. Get an issues-only audit, a rewritten version, or targeted file edits that preserve the author's voice, existing facts, and protected quoted material.

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

• Reviewing a blog draft for machine-sounding prose
• Editing README files and release notes
• Getting style flags without rewriting

Create text diagrams with PlantUML for README files, emails, and terminal workflows. Convert diagram definitions into plain ASCII or Unicode box-drawing output to share interactions and relationships where image-based diagrams are unsuitable.

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

• Add text diagrams to README files
• Share sequence diagrams in emails
• View diagrams in a terminal

Compare documentation with actual code, configuration, and commands to find outdated instructions or missing information. Produce a read-only audit with evidence, severity levels, and specific guidance on which documents need updating.

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

• Check documentation after a pull request
• Compare README setup steps with current code
• Find mismatches in API and environment variable docs

Update the root README.md with entries for new or changed agent companies. Use when a new company has been added to the repo, when company details have changed (agents added/removed, skills added/removed), or when the user asks to refresh/sync the README. Triggers on: "update the readme", "add this company to the readme", "sync readme", "refresh readme", or after creating a new company with company-creator.

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

Use this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.

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

Compare README, specification, and product documents with recent git history to find outdated claims or missing features. Make small factual corrections, preserve the existing style, and prepare a pull request for review.

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

• Review documentation after a release
• Update documentation after major feature merges
• Correct outdated roadmap and support claims

Maintain a Chinese independent developer project list by reviewing comments, issues, and pull requests. Check duplicate URLs and submission eligibility, add projects to the appropriate README, merge contributions, and reply with the listing result.

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

• Review new project submissions
• Check duplicate product URLs
• Place projects in the appropriate list

Review and rewrite Chinese product announcements, articles, emails, and README text using eleven style checks. Identify repetitive phrasing, overloaded sentences, vague openings, and decorative language, then revise them into clearer statements suited to each type of writing.

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

• Revising formulaic Chinese product announcements
• Reviewing repetitive phrasing in Chinese articles
• Shortening overloaded sentences in Chinese emails

Create or edit Markdown with each prose paragraph on one source line, letting the viewer wrap the text automatically. Preserve meaningful line breaks in lists, code, and poetry while reducing unnecessary changes in file comparisons.

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

• Writing READMEs without fixed-width line wrapping
• Joining manually wrapped Markdown paragraphs
• Keeping Markdown changes easier to review

Turn a written diagram request into a JSON specification and render a blueprint-style SVG. Create system architectures, request flows, state machines, or neural network diagrams as files for documentation, READMEs, posts, and slides.

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

• Adding a system architecture diagram to a README
• Illustrating request flows or data pipelines
• Creating a state machine diagram

Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.

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

• Creating or updating technical documentation
• Reviewing README files and documentation changes
• Aligning agent instructions with contribution procedures

Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.

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

リポジトリの構造・技術スタック・機能一覧・セットアップ手順を動的に解析し、 包括的なドキュメントを自動生成するスキル。言語・フレームワーク問わず汎用的に動作する。 Use this skill whenever the user asks to: - Explain a repository / リポジトリの説明 / リポジトリの概要 - Generate a README / README生成 / README作成 - Understand project structure / プロジェクト構成を教えて / 構造を説明して - Learn how to run a project / 使い方を教えて / 動かし方 / セットアップ方法 - Get a repo overview / repo overview / explain this repo / what does this repo do - List features / 機能一覧 / このプロジェクトは何ができる？ - Onboard to a new codebase / コードベースのキャッチアップ / 新しいリポジトリに入った - "このリポジトリ何？" "プロジェクトの全体像" "how to run this project" - "コードの全体を把握したい" "ドキュメントを整備して" "技術スタックを知りたい" This skill is especially useful when joining a new project, onboarding team members, or when a repository lacks proper documentation. It works with ANY repository regardless of programming language, framework, or project type.

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

비공개 프로젝트를 공개용으로 복사하고 비밀 정보와 개인 정보의 제거·검증부터 README, 설치 절차, 라이선스 등 배포 파일 준비까지 진행합니다.

• 비공개 프로젝트의 공개 준비
• 비밀 정보와 개인 정보 잔존 여부 확인
• 사용자 설명과 설치 절차 정리

Compare release changes with project documentation, then update files such as README and CHANGELOG to reflect what shipped. The skill also checks architecture diagrams, maps missing documentation, and records remaining documentation work in the pull request.

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

• Updating project documentation after a release
• Checking architecture diagrams against shipped changes
• Polishing changelog entries and organizing TODOs

Set up a realtime evaluation folder with a suitable shared harness, the framework that runs evaluations. Prepare prompts, tool definitions, realistic starter data, and a README, then validate the setup with evaluation and test runs.

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

• Start a single-turn text-to-speech evaluation
• Set up evaluations using saved audio
• Build multi-turn simulations with mock tools

Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.

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

• Set up Python linting and formatting
• Define shared team coding conventions
• Review type hints and function documentation

Create technical documentation that people and AI can navigate by separating facts, context, known bugs, and uncertain claims. Convert existing Markdown to HADS, a structured documentation format, and check its required elements.

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

• Write API documentation for people and AI
• Convert an existing README to HADS
• Check document structure and block formatting

Keep project documentation aligned with recent code changes. Review commits since the last checkpoint, update affected guides and README files, and open a pull request for human review only when documentation needs correcting.

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

• Keeping documentation aligned with daily code changes
• Updating guides after API or configuration changes
• Catching up on documentation after missed sync runs

Match videos from 王二讲Agent to their scripts, then add Bilibili links and Douyin video IDs to the designated documentation files. Identify missing entries while preserving existing links and IDs.

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

• Add newly published Bilibili videos to the documentation
• Register Douyin video IDs for embedded players
• Check which scripts still lack video references

Prepares a project for open-source release by checking sensitive history, licensing, documentation, tests, and automated publishing. Helps identify gaps so people outside the project can build, use, and contribute to it.

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

• Preparing a private repository for public release
• Choosing and documenting a project license
• Improving README and contribution instructions

Use when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under `doc/` and key entry surfaces such as `README.md` (English default), `README.zh-CN.md`, `mcp/README.md`, and `mcp/README.zh-CN.md` during periodic maintenance or before preparing corrective PRs.

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