How do I install the Development skill?

Run npx skillmds@latest add dmitryprg-ai/development 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. 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, adding, building, implementing new features, components, endpoints, pages, or modules. Also trigger when user asks to add functionality, create a form, implement a filter, build a new UI section, or add an API endpoint.

dmitryprg-ai Updated Sep 10, 2026

File contents

Feature Development

Build features methodically. Check first, build second.

Pre-Action (before writing any code)

1. Duplicate Check

Search semantically, grep, and file search. If similar functionality exists, extend it instead of creating a duplicate. Duplicates create maintenance burden — when the original changes, the copy becomes a silent source of bugs.

2. JTBD Analysis (for user-facing features)

Job Story: When [context], user wants [action], to get [result]

Three questions before coding:

What task is the user actually solving?
What is blocking them right now?
How will they know the job is done?

This prevents building features nobody uses because the feature solves the wrong problem.

3. Find Working Example

For UI: find a working pattern in the project first. Copy the pattern, then adapt. Inventing CSS class combinations from scratch leads to inconsistent UI and wasted debugging time.

4. Control File Size

Plan logic across multiple files before starting. Soft limits: routes 300 lines, services 400, components 200. Large files become hard to review and often hide multiple responsibilities.

Backend Pattern

module.types.ts -> module.repository.ts -> module.service.ts -> module.routes.ts

Types define the contract. Repository handles DB. Service contains business logic. Routes wire HTTP to services. This separation exists so changes to DB queries don't require touching HTTP handlers.

Frontend Pattern

App Router for pages (apps/web/app/)
Feature components (apps/web/features/)
Tailwind CSS v4 (no responsive prefixes like md:)
shadcn/ui components, KtCard wrapper

Common Pitfalls

UI patterns: Always find a working example in the project first. Don't guess CSS classes.
Types: Database bigint returns as JSON string. Always Number() in code.
External APIs: List/Enum fields may contain IDs, not text. Check field mapping.
Entry points: Use high-level orchestrator services (*SummaryService.syncDay()), not low-level methods.

Verification

0 linter errors
Tests pass (if tests exist)
JTBD job is fulfilled
All changed files opened and verified
If deploying: service restarted after build

---name: developmentdescription: Develop new features, functionality, and enhancements. Use when creating, adding, building, implementing new features, components, endpoints, pages, or modules. Also trigger when user asks to add functionality, create a form, implement a filter, build a new UI section, or add an API endpoint.---# Feature DevelopmentBuild features methodically. Check first, build second.## Pre-Action (before writing any code)### 1. Duplicate CheckSearch semantically, grep, and file search. If similar functionality exists, extend it instead of creating a duplicate. Duplicates create maintenance burden — when the original changes, the copy becomes a silent source of bugs.### 2. JTBD Analysis (for user-facing features)**Job Story:** When [context], user wants [action], to get [result]Three questions before coding:- What task is the user actually solving?- What is blocking them right now?- How will they know the job is done?This prevents building features nobody uses because the feature solves the wrong problem.### 3. Find Working ExampleFor UI: find a working pattern in the project first. Copy the pattern, then adapt. Inventing CSS class combinations from scratch leads to inconsistent UI and wasted debugging time.### 4. Control File SizePlan logic across multiple files before starting. Soft limits: routes 300 lines, services 400, components 200. Large files become hard to review and often hide multiple responsibilities.## Backend Pattern```module.types.ts -> module.repository.ts -> module.service.ts -> module.routes.ts```Types define the contract. Repository handles DB. Service contains business logic. Routes wire HTTP to services. This separation exists so changes to DB queries don't require touching HTTP handlers.## Frontend Pattern- App Router for pages (`apps/web/app/`)- Feature components (`apps/web/features/`)- Tailwind CSS v4 (no responsive prefixes like `md:`)- shadcn/ui components, KtCard wrapper## Common Pitfalls- **UI patterns**: Always find a working example in the project first. Don't guess CSS classes.- **Types**: Database bigint returns as JSON string. Always `Number()` in code.- **External APIs**: List/Enum fields may contain IDs, not text. Check field mapping.- **Entry points**: Use high-level orchestrator services (`*SummaryService.syncDay()`), not low-level methods.## Verification- 0 linter errors- Tests pass (if tests exist)- JTBD job is fulfilled- All changed files opened and verified- If deploying: service restarted after build

Frequently asked questions