source-driven-development

Grounds Android implementation decisions in official documentation with cited sources.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill source-driven-development-22teikk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/22Teikk/22Teikk-Agent-Skills-Hub/tree/main/core/skills/source-driven-development
Command: npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill source-driven-development-22teikk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents often write Android code from stale training data, producing deprecated APIs, hallucinated signatures, and outdated patterns that fail to compile or crash at runtime. This Skill forces every Android-specific decision to be verified against official documentation before implementation. ## Core Features & Use Cases - Stack Detection: Reads libs.versions.toml, build.gradle.kts, and settings.gradle.kts to identify exact Kotlin, Compose, Hilt, and Retrofit versions before writing code. - Source Hierarchy Enforcement: Fetches only authoritative sources (developer.android.com, kotlinlang.org) and rejects Stack Overflow, blogs, or training-data memory as citations. - Conflict Surfacing: When existing project code contradicts current docs (e.g., startActivityForResult vs. registerForActivityResult), it presents both options to the user instead of silently choosing. - Use Case: You ask the agent to add image picking to your Compose app. It detects your Activity library version, fetches the Activity Result API guide, implements registerForActivityResult with ActivityResultContracts, and cites the official URL in code comments. ## Quick Start Ask the agent to implement an Android feature using the source-driven-development skill so every API choice is verified against official documentation and cited.

Frequently Asked Questions about source-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop AI agents from using deprecated Android APIs?▼

Require the agent to verify every Android API against official documentation before implementing. This Skill detects your library versions from Gradle files, fetches the current docs, and replaces deprecated calls like startActivityForResult with modern equivalents such as registerForActivityResult.

How to make AI-generated Android code cite official documentation?▼

The Skill enforces a citation step where every Android or Jetpack pattern includes a source URL, both in code comments and in conversation. Only official sources like developer.android.com and kotlinlang.org are accepted; Stack Overflow and blog posts are rejected as primary citations.

Does this work with Jetpack Compose and Kotlin version catalogs?▼

Yes. The first step reads libs.versions.toml, build.gradle.kts, and settings.gradle.kts to detect exact versions of Kotlin, Compose, Hilt, and other dependencies. If versions are missing or ambiguous, the agent asks the user instead of guessing.

What happens when official docs conflict with existing project code?▼

The agent surfaces the conflict explicitly instead of silently choosing. It presents both options, such as using the modern documented API versus matching the existing codebase pattern, and asks the user which approach to take.

When should I not use documentation-driven development?▼

Skip it when correctness does not depend on a specific version, such as renaming variables, fixing typos, or moving files. Pure logic like loops, standard collections, and math that behaves identically across versions also does not need doc verification.