← ClaudeAtlas

high-fidelity-source-portlisted

Use whenever someone wants a prototype, mockup, static HTML/CSS/JS demo, or simplified reimplementation to match a real reference codebase with high fidelity — "make this look/behave like the real app," "port this UI from the actual source," "align our prototype with the real product," "recreate this feature from the real component," or "the version I got before doesn't feel right." Trigger whenever the user has BOTH a simplified version of something AND a real source repo for it (open-source upstream clone, vendored dependency, competitor's open-sourced product, an earlier real version of their own app) and wants the simplified one to catch up in structure, copy, or logic. Push hard to use this when the user mentions "the real source" or "the actual repo," even without the word "port." Not for building from scratch with no reference, routine bug fixes with no second codebase involved, or cases with only screenshots and no source access.
skyhahalife-11/pm-skill-pack · ★ 0 · Web & Frontend · score 67
Install: claude install-skill skyhahalife-11/pm-skill-pack
# Porting a UI/feature from a real source codebase into a simplified target ## Why this skill exists When a real reference implementation exists, "make it look like the real thing" is not a design-taste problem — it's a research problem. The failure mode this skill exists to prevent is guessing: skimming a screenshot, half-reading a file, or inventing plausible-sounding copy and logic instead of reading the actual reference source end to end. Guessing produces something that is superficially similar but wrong in exactly the ways that make people say "this doesn't feel right" — wrong copy, wrong field order, wrong interaction model, invented logic where the original had precise rules. Reading the real source produces something that is *actually* the same, because it is grounded in it. The target codebase you're editing almost certainly also has its own history of half-finished, AI-assisted edits — functions that reference DOM elements that don't exist, buttons wired to nothing, two competing implementations of the same feature. Finding and being honest about these is as much a part of this skill as the porting itself. ## Workflow Work through these steps in order. Don't skip to writing code before step 2 is done — the temptation to start editing as soon as you've found "a" relevant file is exactly how superficial ports happen. ### 1. Locate the real component, don't guess the filename Reference codebases (especially app-router frameworks like Next.js, or any convention-