メニュー
Common rules for code development that apply across all project types (libraries, CLI tools, services, etc.). Covers development workflow, requirements clarity, bug-fix workflow, logging, coding style, testing discipline, version management, and commit conventions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Post-task checklist that runs after every agent task that makes essential changes to code, documentation, scripts, or configuration. Covers version bumping, release-notes update, and commit-text proposal. Applied automatically — the agent does not need to be asked.
REST API skill that provides naming conventions and best practices for REST API development.
Common rules for Angular code development. These guidelines apply to components, services, modules, dependency injection, and reactive patterns.
Common rules for TypeScript code development. These guidelines apply to interfaces, types, error handling, async patterns, dependency injection, and module structure.
TDD-based workflow for fixing bugs and defects. Use when investigating, reproducing, and resolving reported issues or unexpected behavior.
Workflow for implementing new features and processing issues. Use when adding new functionality, implementing requirements, or processing feature requests.
| name | common-development |
| description | Common rules for code development that apply across all project types (libraries, CLI tools, services, etc.). Covers development workflow, requirements clarity, bug-fix workflow, logging, coding style, testing discipline, version management, and commit conventions. |
| metadata | {"author":"vsirotin","version":"1.4"} |
site-map.yaml, read it to locate relevant files.After completing a task that makes essential changes, apply the post-task skill (version bump, release notes, commit text proposal).
All functions with many lines (e.g. more as 10 lines) or short, but very importanf functions must include logging by enty and before and after important steps (e.g. call to external service, important decision points, etc.). Logs should be informative and concise. In whole project should be use the same logging library and format.
Use best practices of the programming language, but maintain a common, consistent style across the entire project. Do not mix conventions within one codebase.
If a function uses data from environment variables or files, this must be mentioned in the function's documentation.
For testing rules including coverage expectations, naming conventions, organization, execution, and cleanup, see the dedicated testing skill. Use it when writing, organizing, or running unit tests.
If you see suddenly that you cannot solve some problem, stop the development and ask me.
If you try to fix the same bug too long (more than 20 iterations), stop the development and ask me.
For the full feature development workflow, see the dedicated feature-development skill. Use it when implementing new functionality, processing feature requests, or adding new features.
For TDD-based bug fixing, see the dedicated bug-fixing skill. Use it when investigating, reproducing, and resolving reported defects or unexpected behavior.