fec-source-driven-development
Installation
SKILL.md
Source driven development
Purpose
Prioritize the use of in-project facts, official documentation, and current version behavior in front-end implementation, review, and architecture decisions, and avoid relying on outdated experience or unverified assumptions.
Procedure
-
Determine whether it is necessary to check the source
- Source checking is required when new versions of frameworks, routing, rendering modes, caches, build tools, browser APIs, package publishing formats, authentication protocols, or public interfaces are involved.
- When it comes to project commitments, read the README, configuration, templates, existing implementations, testing and migration records of this warehouse first.
- Use the project's existing schema as a source of truth when simply stabilizing the language syntax or significantly partial refactoring.
-
Collect authoritative materials
- Preferred official documentation, specifications, source code, release notes, migration guide, type definitions and in-project testing.
- Third-party articles can only be used as clues and cannot be used as the final basis.
- Record package name, version, document date or page title for rapidly changing libraries.
- When a user asks to answer a question from a local knowledge base, project repository or
knowledge/directory, perform local knowledge retrieval first and do not use network search to fill in the facts.