← ClaudeAtlas

prior-art-searchlisted

Mandatory pre-implementation research skill. Search GitHub, official documentation, package registries, and existing battle-tested implementations before writing new features, rules files, skills, or architecture. Enforces the Adopt-Extend-Compose-Build hierarchy and delegates heavy search loops to subagents to prevent main-thread context bloat. Use before any non-trivial feature, skill, config, or library choice — and whenever an existing approach fails or survives only on a workaround and 'keep the status quo' is tempting — not for bug fixes, refactors, or mechanical changes.
yjhqwer/yjh-discipline · ★ 1 · Code & Development · score 69
Install: claude install-skill yjhqwer/yjh-discipline
# Prior Art Search (Search Before Building) **The best code and configurations are the ones already battle-tested by the global community.** Before designing architecture, writing non-trivial features, creating skills, or synthesizing configurations (rules files, CI/CD, Docker), search for existing solutions first. Do not invent from imagination. **Settling counts as building.** When the current approach fails, breaks something else, or survives only through manual workarounds, run this skill before recommending the user keep the status quo. "No better method exists" is a conclusion only a completed search can earn — most such conclusions come from incomplete searches. Present "do nothing" alongside the realistic alternatives and justify it with the same evidence as any other verdict. --- ## 1. The Decision Hierarchy: Adopt → Extend → Compose → Build Assess all candidates through this strict precedence ladder: 1. **Adopt (Direct Reuse)** - If an official template, high-starred repository, or standard library solves the problem, use it directly. - Do not re-implement existing standards. 2. **Extend (Adapt & Specialize)** - If a proven solution covers ~80% of the requirements, adapt only the remaining 20% for local constraints. - Credit the reference pattern and document the adaptation delta. 3. **Compose (Combine Small Pieces)** - If 2–3 small, maintained packages together cover the requirements better than one heavy dependency, combine them. 4. **Build (