Community생산성 & 협업github.com

addyosmani/증분-구현

변경 사항을 증분 방식으로 전달합니다. 여러 파일에 걸친 기능 또는 변경 사항을 구현할 때, 한 번에 많은 코드를 작성하려고 할 때, 또는 작업이 한 번에 처리하기에 너무 크다고 느껴질 때 사용하세요.

증분-구현란 무엇인가요?

이 스킬은 개발자와 AI 에이전트가 대규모 코드 변경을 더 작고 관리 가능한 증분 단계로 분할하여 구현하도록 안내합니다. '한 번에 모든 것을 구현'하는 일반적인 함정을 방지하여 오류 위험을 줄이고, 검토 가능성을 높이며, 전체 개발 프로세스를 더 원활하게 만듭니다. 이 스킬은 기능 구현, 리팩토링, 버그 수정 등 여러 파일에 걸친 모든 종류의 변경 사항에 유용합니다. 기본 원칙은 각 증분 단계가 독립적으로 테스트 가능하고 검토 가능해야 하며, 전체 솔루션의 진행을 향해 점진적으로 구축되어야 한다는 것입니다. 이 스킬은 Claude Code, Cursor, Codex, GitHub Copilot을 포함한 모든 주요 AI 코딩 에이전트 플랫폼에서 사용할 수 있습니다. SKILL.md 문서에 설명된 대로 에이전트는 먼저 현재 구현 상태를 평가하여 증분이 완료된 부분을 결정하고, 각 단계에서 구현할 다음 논리적 증분을 식별하며, 해당 증분을 구현하기 위한 구체적이고 실행 가능한 계획을 수립하고, 테스트를 구현한 다음 증분 자체를 구현하고, 다음 증분으로 진행할 준비가 되었는지 확인합니다. 이 접근 방식은 '로드맵'을 기반으로 작업을 더 작은 단계로 나누는 데 탁월하여 복잡한 코딩 작업을 안내합니다.

지원 대상~Claude Code~Codex CLI~Cursor
Part ofAgent Workflows
npx skills add https://github.com/addyosmani/agent-skills/tree/main/skills/incremental-implementation

Installed? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

문서

addyosani/증분-구현

변경 사항을 증분 방식으로 전달합니다. 여러 파일에 걸친 기능 또는 변경 사항을 구현할 때, 한 번에 많은 코드를 작성하려고 할 때, 또는 작업이 한 번에 처리하기에 너무 크다고 느껴질 때 사용하세요.

작동 방식

이 스킬은 대규모 변경 사항을 더 작고 관리 가능한 증분 단계로 분할합니다. 각 증분 단계는:

  • 독립적으로 테스트 가능해야 함
  • 독립적으로 검토 가능해야 함
  • 전체 솔루션의 진행을 향해 점진적으로 구축되어야 함

사용 지침

에이전트는 다음을 수행해야 합니다:

  1. 현재 상태 평가: 이미 어떤 증분이 완료되었는지 결정합니다 (git log, 커밋 기록 확인, 또는 현재 코드베이스 상태 확인).
  2. 다음 증분 식별: 아직 완료되지 않은 변경 사항 목록에서 가장 작은 논리적 다음 단계는 무엇입니까?
  3. 계획: 각 증분 단계를 구현하기 위한 구체적이고 실행 가능한 계획을 수립합니다. 어떤 파일을 수정해야 합니까? 테스트는 어떻게 됩니까?
  4. 구현: 증분 단계를 구현합니다.
    • 증분을 위한 테스트 구현
    • 증분 자체 구현
  5. 진행 상황 확인: 모든 테스트가 통과하도록 보장하고, 리팩토링이 필요한지 확인하며, 다음 증분으로 진행할 준비가 되었는지 확인합니다.

예시

# 예시: 대규모 기능을 증분으로 구현
# 증분 1: 데이터 모델 및 스키마
# 증분 2: 저장소 계층
# 증분 3: 서비스 계층
# 증분 4: API 엔드포인트
# 증분 5: 프론트엔드 통합

지원 플랫폼

  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • 기타 AI 코딩 에이전트

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

addyosmani/agent-skills

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

addyosmani/agent-skills

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

addyosmani/agent-skills

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

addyosmani/browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

addyosmani/ci-cd-and-automation

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

addyosmani/code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

addyosmani/code-simplification

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

addyosmani/constraint-driven-development

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

addyosmani/debugging-and-error-recovery

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

addyosmani/deprecation-and-migration

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

addyosmani/documentation-and-adrs

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

addyosmani/doubt-driven-development

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

addyosmani/git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

addyosmani/idea-refine

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

addyosmani/interview-me

Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.

addyosmani/observability-and-instrumentation

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

addyosmani/performance-optimization

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

addyosmani/planning-and-task-breakdown

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

addyosmani/security-and-hardening

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

addyosmani/source-driven-development

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

관련 스킬

steipete/gemini

Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.

community

steipete/gh-issues

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

community

steipete/skill-creator

Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.

community

steipete/clawhub

Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.

community

steipete/coding-agent

Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.

community

steipete/mcporter

List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.

community
← More 생산성 & 협업 skills