Community생산성 & 협업github.com

addyosmani/source-driven-development

모든 구현 결정을 공식 문서에 근거합니다. 권위 있는 출처를 인용한 코드로 오래된 패턴 없이 작업하려는 경우 사용합니다. 정확성이 중요한 프레임워크나 라이브러리로 빌드할 때 사용합니다.

source-driven-development란 무엇인가요?

이 스킬은 공식 문서를 기반으로 모든 구현 결정을 내리는 '소스 기반 개발(Source-Driven Development)' 방법론을 구현합니다. 개발자가 프레임워크나 라이브러리를 사용할 때 오래된 패턴이나 잘못된 관행을 따르지 않고, 공식 출처에서 인용된 권위 있는 코드를 생성하도록 안내합니다. Claude Code, Cursor, Codex 등 다양한 AI 에이전트 플랫폼에서 사용 가능하며, SKILL.md 문서에 따라 공식 문서를 참조하고 출처를 명시하며 최신 모범 사례를 적용합니다. 이 스킬은 정확성과 신뢰성이 중요한 프로젝트에 특히 유용하며, 개발자가 베스트 프랙티스에 기반한 결정을 내릴 수 있도록 돕습니다.

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

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

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

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

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

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

문서

source-driven-development은(는) 무엇을 하나요?

모든 구현 결정을 공식 문서에 근거합니다. 권위 있는 출처를 인용한 코드로 오래된 패턴 없이 작업하려는 경우 사용합니다. 정확성이 중요한 프레임워크나 라이브러리로 빌드할 때 사용합니다.

소개

이 스킬은 소스 기반 개발(Source-Driven Development) 방법론을 적용합니다. 즉, 사용하는 모든 프레임워크, 라이브러리 또는 API에 대해 최신 공식 문서를 참조하여 코드를 생성합니다. 추측이나 구식 블로그 게시물에 의존하지 않습니다.

작동 방식

  1. 작업 분석: 현재 작업 중인 구현 작업을 분석합니다.
  2. 출처 확인: 관련 공식 문서(예: Python Docs, MDN, React 공식 문서, FastAPI 문서 등)를 식별합니다.
  3. 정보 추출: 정확한 API 사용법, 모범 사례, 주의 사항을 문서에서 직접 추출합니다.
  4. 코드 생성: 추출한 정보를 바탕으로 올바른 패턴을 사용하여 코드를 생성합니다.
  5. 출처 인용: 생성된 코드에 주석이나 마크다운을 덧붙여 권위 있는 출처를 명시합니다.

사용 예시

# 출처: https://fastapi.tiangolo.com/tutorial/body/#request-body
from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class Item(BaseModel):
    name: str
    price: float

@app.post("/items/")
async def create_item(item: Item):
    return item

지원 플랫폼

  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • 기타 AI 지원 개발 환경

요구 사항

  • 활성 인터넷 연결 (공식 문서 접근을 위해)
  • 작업 중인 프레임워크/라이브러리에 대한 기본 지식

라이선스

MIT

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/incremental-implementation

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

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.

관련 스킬

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