source-driven-development
Verify behavior and APIs against official documentation and source of truth before implementing or advising. Use when working with libraries, frameworks, cloud services, or any external system where assumptions are dangerous.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- source-driven-development
- description
- Verify behavior and APIs against official documentation and source of truth before implementing or advising. Use when working with libraries, frameworks, cloud services, or any external system where assumptions are dangerous.
03 SKILL.md 正文
Source-Driven Development
Overview
LLMs can hallucinate APIs and best practices. When accuracy matters, go to the source.
When to Use
- Using a library or framework feature you are not 100% certain about
- Cloud provider APIs, SDKs, or configuration
- Security-sensitive or version-sensitive behavior
- When previous assumptions have proven wrong
Process
- Identify the authoritative source (official docs, source code, RFCs, etc.)
- Check the version that is actually in use
- Confirm the exact API, options, and behavior
- Only then implement or recommend
Principles
- Prefer primary sources over blog posts or Stack Overflow
- Note version differences explicitly
- When docs are ambiguous, say so
Verification
- Claims about external systems are backed by checked sources
- Version compatibility is considered
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.