القائمة
Workflow for implementing new features and processing issues. Use when adding new functionality, implementing requirements, or processing feature requests.
التثبيت باستخدام 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.
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.
| name | feature-development |
| description | Workflow for implementing new features and processing issues. Use when adding new functionality, implementing requirements, or processing feature requests. |
| metadata | {"author":"vsirotin","version":"1.0"} |
Note: This skill is based on common-development. Read the origin document first for complete development rules.
When implementing a new feature or processing a feature request, always follow this order:
Design interfaces — Develop interfaces or empty classes with function signatures to decide on the API. Within the same sub-project this can be interfaces in the used programming language (e.g. TypeScript). Between sub-projects it can be interfaces in the corresponding sub-protocol (e.g. OpenAPI specification).
Write tests first — Develop tests of all types according to sub-project requirements. All projects with code require unit tests; in some cases also behaviour and integration tests. Tests must be developed before or alongside the implementation of production code.
Implement production code — Develop the production code following the designed interfaces.
Run tests to confirm they pass — Execute the full test suite. Small adjustments to implementation or tests may be needed to align details, but reducing the number of tests or skipping them is an exception and should be done only after careful consideration of the consequences.
Report the result — Document the outcome.
These rules from common-development also apply:
