How do I install the Development skill?

Run npx skillmds@latest add dmitryprg-ai/development-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Development safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Development?

dmitryprg-ai (@dmitryprg-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Development by dmitryprg-ai — Agent Skill

Name: Development
Rating: 4.666666666666667 (3 reviews)
Author: dmitryprg-ai

Development

Develop new features, functionality, and enhancements. Use when creating new features, adding functionality, building components, or when user says add, create, build, develop, implement. Includes Duplicate Check, JTBD Analysis, TDD approach, UI pattern reuse, and service restart verification.

dmitryprg-ai Updated Sep 22, 2026

File contents

Development Protocol

Pre-Action (MANDATORY before coding)

1. Duplicate Check

## DUPLICATE CHECK
**Target:** [what I'm creating]
**Search:** semantic/grep/file -> [found/not found]
**Decision:** CREATE NEW / EXTEND EXISTING / ASK USER

2. JTBD Analysis (for user-facing features)

## JTBD ANALYSIS
**Job Story:** When [context], user wants [action], to get [result] and [benefit]
**Questions:**
1. What task are they solving? -> [answer]
2. What's blocking them? -> [answer]
3. What change will help? -> [answer]

3. Find Working Example

For UI: find a working pattern in the project first. Copy the pattern, then adapt. Do NOT invent CSS classes without checking they work.

4. Control File Size

Plan logic across multiple files. Refer to standard-file-size-limits-agent.mdc rule.

Plan

## DEVELOPMENT PLAN
**Task:** [what to do]
**Expected Output:** [artifacts]
**Test Cases:** [input -> expected output]

Execute (TDD approach)

Follow the tdd-workflow skill for full TDD process (Red → Green → Refactor):

Fill test cases table BEFORE code (Phase 0)
Write failing tests (Phase 1 — RED)
Write minimal code to pass (Phase 2 — GREEN)
Refactor (Phase 3)
Restart affected services and verify

Verify

0 linter errors
Tests pass
JTBD: Job implemented, UI about benefits
Each file opened and verified
Services restarted if needed

Common Pitfalls

UI Components: Find working example in project first. Don't use CSS classes without checking they work.
Type Consistency: Database types may differ from JSON (bigint -> string). Check actual types.
Backend Modules: Follow pattern: types -> repository -> service -> routes
External APIs: List/Enum fields may contain IDs, not text. Need mapping.
Entry Points: Use high-level orchestrator services, not low-level methods.

Additional Resources

For prompt preparation methodology, see PREPARE-PROMPT.md.

---name: development-2description: Develop new features, functionality, and enhancements. Use when creating new features, adding functionality, building components, or when user says add, create, build, develop, implement. Includes Duplicate Check, JTBD Analysis, TDD approach, UI pattern reuse, and service restart verification.---# Development Protocol## Pre-Action (MANDATORY before coding)### 1. Duplicate Check```markdown## DUPLICATE CHECK**Target:** [what I'm creating]**Search:** semantic/grep/file -> [found/not found]**Decision:** CREATE NEW / EXTEND EXISTING / ASK USER```### 2. JTBD Analysis (for user-facing features)```markdown## JTBD ANALYSIS**Job Story:** When [context], user wants [action], to get [result] and [benefit]**Questions:**1. What task are they solving? -> [answer]2. What's blocking them? -> [answer]3. What change will help? -> [answer]```### 3. Find Working ExampleFor UI: find a working pattern in the project first. Copy the pattern, then adapt. Do NOT invent CSS classes without checking they work.### 4. Control File SizePlan logic across multiple files. Refer to `standard-file-size-limits-agent.mdc` rule.## Plan```markdown## DEVELOPMENT PLAN**Task:** [what to do]**Expected Output:** [artifacts]**Test Cases:** [input -> expected output]```## Execute (TDD approach)Follow the `tdd-workflow` skill for full TDD process (Red → Green → Refactor):1. Fill test cases table BEFORE code (Phase 0)2. Write failing tests (Phase 1 — RED)3. Write minimal code to pass (Phase 2 — GREEN)4. Refactor (Phase 3)5. Restart affected services and verify## Verify- [ ] 0 linter errors- [ ] Tests pass- [ ] JTBD: Job implemented, UI about benefits- [ ] Each file opened and verified- [ ] Services restarted if needed## Common Pitfalls- **UI Components**: Find working example in project first. Don't use CSS classes without checking they work.- **Type Consistency**: Database types may differ from JSON (bigint -> string). Check actual types.- **Backend Modules**: Follow pattern: types -> repository -> service -> routes- **External APIs**: List/Enum fields may contain IDs, not text. Need mapping.- **Entry Points**: Use high-level orchestrator services, not low-level methods.## Additional ResourcesFor prompt preparation methodology, see [PREPARE-PROMPT.md](references/PREPARE-PROMPT.md).

Frequently asked questions