domains / families / software-engineering / source-driven-development

source-driven-development

authentic

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.

When to use

• The user wants code that follows current best practices for a given framework
• Building boilerplate, starter code, or patterns that will be copied across a project
• The user explicitly asks for documented, verified, or "correct" implementation
• Implementing features where the framework's recommended approach matters (forms, routing, data fetching, state management, auth)
• Reviewing or improving code that uses framework-specific patterns
• Any time you are about to write framework-specific code from memory
• Correctness does not depend on a specific version (renaming variables, fixing typos, moving files)
• Pure logic that works the same across all versions (loops, conditionals, data structures)

When not to use

• Use this skill only when the task clearly matches its upstream source and local project context.
• Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
• Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Skill page

Source