**fix: resolve duplicate SkipToContent component #72**

[Awointa]

Summary

Removes the misplaced SkipToContent organism and consolidates all imports to the correct atoms version. A skip link is an indivisible UI primitive — it belongs in components/atoms/ per Atomic Design principles. The duplicate was causing import confusion with no functional benefit.

Changes

Deleted

• components/organisms/skip-to-content.tsx — removed the violating duplicate

Updated

• app/layout.tsx — import path updated to point to components/atoms/skip-to-content.tsx
• Any other files importing the organism version — all updated to the atoms path

Verified

• SkipToContent component retains focus-visible styles for keyboard accessibility

Validation

• Tabbing into the page surfaces the "Skip to main content" link
• Activating the link moves focus to #main-content
• No duplicate component files remain in the codebase
• pnpm build passes locally
• Screen recording attached — skip link visible, functional, and keyboard accessible

Screen Recording

📎 (attach .mp4, .mov, .gif, or Loom/YouTube link here)

Checklist

• Branched from and rebased against latest main
• No .md files or AI tool folders committed
• All commits follow Conventional Commits spec
• Each commit builds and passes lint independently
• pnpm build passes — confirmed locally before pushing

---

Closes #72

[drips-wave]

@Awointa Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[pragmaticAweds]

Hi @Awointa

Please record a video of your implementation, and what you did for review.

Secondly, the CI did not pass.