dev-skills
Enforces strict project, documentation, and coding standards to ensure code quality and project structure.
Install
mkdir -p .claude/skills/dev-skills && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15207" && unzip -o skill.zip -d .claude/skills/dev-skills && rm skill.zipInstalls to .claude/skills/dev-skills
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
devops rulerKey capabilities
- →Ensure all documentation is in the `docs` directory.
- →Prohibit emojis in documentation and code.
- →Ensure complete functional implementation of code.
- →Avoid duplicate functions by promoting code reuse.
- →Limit code files to a maximum of 500 lines.
- →Conduct multi-level analysis for user requirements, functional modules, and functions.
How it works
The skill enforces strict rules for documentation, code quality, file directory structure, and multi-level code analysis to ensure project consistency and completeness.
Inputs & outputs
When to use dev-skills
- →Standardizing file directory layouts
- →Ensuring multi-level functional code analysis
- →Reviewing code for completeness and compliance
About this skill
dev ruler
文档规范
为了项目文件结构清晰明了，所有的文档都必须全部统一放在docs目录下，同时文档中和代码中禁止出现任何emoji表情图标，这会让文档、代码不专业
代码规范
所有的代码必须要优雅的实现，确保功能代码的实现的完整性，不允许出现虚假的功能代码编写完成报告，比如用户要求的功能A没有实现，但是GPT在代码编写总结显示本次功能实现，这种错误的异常情况是绝对不允许的。所有代码文件的目录结构必须结构严谨，尽量避免重复编写用于实现同一个功能的函数，尽量做到函数复用，需要避免单个文件过大、过长导致后续难以定位问题、扩展优化，我们规定一个代码文件最多为500行。
文件目录规范
所有代码文件的命名都需要标准规范，比如测试类的代码文件必须以test_开头，项目的文件目录结构必须严谨，不允许出现定义好了功能目录但是没有使用该目录，同时为了保证目录的严谨性什么目录就只能存放什么功能的代码文件，比如定义这个目录为文档工具目录那么就只能在该目录写编写文档相关的python代码禁止在该目录下编写其他功能的代码
代码多级分析
在进行代码编写时，必须要进行多级分析，至少需要进行三级分析，第一层分析是对用户需求的整体分析，第二层分析是对每个功能模块的分析，第三层分析是对每个函数的分析，确保每个函数的功能实现都是符合用户需求的，同时在代码编写完成后需要进行代码的整体分析，确保代码的功能实现是完整的，避免出现功能缺失的情况
When not to use it
- →When the task does not involve code or documentation standards.
- →When the task is not about project structure or functional completeness.
- →When the task is not related to multi-level code analysis.
Limitations
- →All documentation must be in the `docs` directory.
- →Emojis are prohibited in documentation and code.
- →A code file can be a maximum of 500 lines.
How it compares
This skill mandates specific constraints on documentation location, emoji usage, code file size, and multi-level analysis, providing a rigid framework for project development.
Compared to similar skills
dev-skills side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dev-skills (this skill) | 0 | 6mo | No flags | Intermediate |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| python-code-style | 9 | 6mo | Review | Intermediate |
| cookbook-audit | 5 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
code-style-guide
OpenHands
Project coding standards and style guidelines. Always follow these conventions when writing or reviewing code.
fix-members-short-description
flet-dev
Use when asked to fix short descriptions of Python type members.
code-changelog
bear2u
AI가 만든 모든 코드 변경사항을 reviews 폴더에 기록하고 간단한 HTML 뷰어로 웹 브라우저에서 실시간 확인할 수 있습니다. 매 수정마다 문서가 생성되고 Python 서버로 즉시 확인 가능합니다.