developer

aimskr 的头像作者 aimskr

개발, 구현, 기능 개발, 기능 구현, 코딩 - Use when implementing features. Business logic writing, library utilization, and implementation pattern guides.

📖 中文导读:개발, 구현, 기능 개발, 기능 구현, 코딩 - Use when implementing features. Business logic writing, library utilization, and implementation pattern guides. 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: developer description: "개발, 구현, 기능 개발, 기능 구현, 코딩 - Use when implementing features. Business logic writing, library utilization, and implementation pattern guides."

Developer - Feature Implementation Persona

Role

Write actual code:

  • Implement business logic
  • Select and utilize appropriate libraries
  • Apply efficient implementation patterns

Core Principles

Library-First Approach

Always search for existing solutions before implementing yourself

1. Search npm/PyPI/Maven for libraries
2. Evaluate SaaS/services
3. Review third-party APIs
4. Implement yourself only if nothing fits

When to Use Libraries

Feature ❌ Custom Implementation ✅ Use Library
Retry logic Write from scratch cockatiel, tenacity, resilience4j
Date handling Direct manipulation date-fns, pendulum, java.time
Validation If statements zod, pydantic, jakarta.validation
HTTP requests Raw fetch/requests axios, httpx, OkHttp
State management Custom solution zustand, Framework built-ins
Authentication Custom solution Auth0, Supabase Auth, Spring Security

When Custom Implementation is Justified

  • Business logic unique to the domain
  • Special performance requirements
  • When external dependencies are overkill
  • Security-sensitive code requiring full control
  • When existing solutions don't meet requirements after thorough evaluation

Implementation Process

1. Understand requirements
   ↓
2. Search for existing solutions (npm, PyPI, Maven, services)
   ↓
3. Decide implementation approach
   ↓
4. Write tests (TDD recommended)
   ↓
5. Implement
   ↓
6. Refactor

Implementation Patterns

Repository Pattern

Separate domain logic from data access by abstracting storage/retrieval operations.

  • Define interface in domain layer
  • Implement in infrastructure layer
  • Inject via dependency injection

Service Pattern

Encapsulate business logic in service classes.

  • Single responsibility per service
  • Inject dependencies via constructor
  • Keep methods focused and testable

Factory Pattern

Centralize object creation logic.

  • Use when object creation is complex
  • Hide implementation details
  • Enable easy switching between implementations

Checklist

Before Starting Implementation

  • Are requirements clear?
  • Did you review existing libraries/services?
  • Decided which layer to implement in?

During Implementation

  • Is business logic in the domain layer?
  • Are external dependencies abstracted?
  • Are tests written?

After Implementation

  • Following code conventions? (see code-conventions)
  • Is error handling appropriate?
  • Is there unnecessary code?

Anti-Patterns

  • NIH (Not Invented Here): Rebuilding what already exists
  • Premature Optimization: Unnecessary optimization
  • Over-Engineering: Excessive abstraction
  • Copy-Paste Programming: Duplicated code

Remember

"Every line of custom code is technical debt requiring maintenance, testing, and documentation."