Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
中文简介正在准备中。当前显示原文说明。
Generate a README.md for the current project by analyzing the codebase structure, package files, and existing documentation. Use when asked to write a README, create documentation, or document the project.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Check for language and framework indicators in this order:
package.json — Node.js / JavaScript / TypeScript projectpyproject.toml or setup.py — Python projectgo.mod — Go projectCargo.toml — Rust projectbuild.gradle or pom.xml — Java / Kotlin project*.gemspec or Gemfile — Ruby projectRead whichever file is found to extract the project name, version, description, and dependencies.
Based on the project type, read the main entry point:
main field in package.json, or look for src/index.ts, src/index.js, index.ts, index.js__main__.py, the module directory, or the entry point in pyproject.tomlmain.go or cmd/<name>/main.gosrc/main.rs or src/lib.rsRead the first 80 lines to understand what the project does.
Run ls -1 at the project root and at the src/ (or equivalent) directory if it exists. Note top-level directories that give structure clues (cli/, api/, lib/, tests/, docs/, examples/).
Produce a README.md with the following sections in this order. Include a section only if there is real content for it — do not leave placeholder text in any section except Badges.
# Project Name
One sentence describing what the project does and who it is for.
## Badges
<!-- Add badges here: build status, coverage, version, license -->
## Installation
Commands to install the project. Use the package manager detected in step 1.
## Usage
The minimal example to get something working. Show a command or code snippet.
If the project has a CLI, show the most common command.
If it is a library, show an import and a basic function call.
## Configuration
If the project has configuration options (environment variables, config files, flags),
list the important ones with their defaults and descriptions.
## Contributing
Brief instructions: how to set up a dev environment, how to run tests, how to submit a change.
## License
State the license. Read the LICENSE file if present to confirm.
After writing the README, tell the user which sections have placeholder content (Badges) and which sections they should review for accuracy (Usage examples especially benefit from human review).
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
中文简介正在准备中。当前显示原文说明。
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
中文简介正在准备中。当前显示原文说明。
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
中文简介正在准备中。当前显示原文说明。
Create a git branch named after a GitHub issue.
中文简介正在准备中。当前显示原文说明。
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
中文简介正在准备中。当前显示原文说明。
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
中文简介正在准备中。当前显示原文说明。