scoop-ui-refactor
Project-specific UI refactor workflow for the Scoop news platform in /home/bender/classwork/Thesis. Use when updating Scoop frontend layouts, globe UX, research workspace, and brand docs while preserving all features and enforcing a no-emoji policy across UI, logs, and docs.
Best use case
scoop-ui-refactor is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Project-specific UI refactor workflow for the Scoop news platform in /home/bender/classwork/Thesis. Use when updating Scoop frontend layouts, globe UX, research workspace, and brand docs while preserving all features and enforcing a no-emoji policy across UI, logs, and docs.
Project-specific UI refactor workflow for the Scoop news platform in /home/bender/classwork/Thesis. Use when updating Scoop frontend layouts, globe UX, research workspace, and brand docs while preserving all features and enforcing a no-emoji policy across UI, logs, and docs.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "scoop-ui-refactor" skill to help with this workflow task. Context: Project-specific UI refactor workflow for the Scoop news platform in /home/bender/classwork/Thesis. Use when updating Scoop frontend layouts, globe UX, research workspace, and brand docs while preserving all features and enforcing a no-emoji policy across UI, logs, and docs.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scoop-ui-refactor/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scoop-ui-refactor Compares
| Feature / Agent | scoop-ui-refactor | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Project-specific UI refactor workflow for the Scoop news platform in /home/bender/classwork/Thesis. Use when updating Scoop frontend layouts, globe UX, research workspace, and brand docs while preserving all features and enforcing a no-emoji policy across UI, logs, and docs.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Scoop UI Refactor ## Scope - Project root: `/home/bender/classwork/Thesis` - Frontend: `frontend/app` and `frontend/components` ## Required outcomes - Preserve all existing features (view modes, filters, research, modals). - Increase density and reduce empty vertical space. - Make globe selection flow clear and usable. - Have grid view have snap scroll. - Keep feed snap-scroll while preserving global header visibility. - Remove emojis from UI, logs, and docs. ## Workflow 1) Review primary surfaces - `frontend/app/page.tsx` (home layout) - `frontend/components/globe-view.tsx` and `frontend/components/interactive-globe.tsx` - `frontend/app/search/page.tsx` (research UI) - `frontend/app/globals.css` (theme tokens) 2) Home layout refactor - Compress the lead story into title + summary + action row. - Move big narrative blocks into a compact summary card. - Convert long "Contact" sections into short action rows. - Keep view mode controls and filters visible and separated. 3) Globe view UX - Add a clear country focus header. - Show source count and top sources for the selected country. - Keep a clear "reset" action visible. - Remove all country flag emojis and any emoji usage. 4) Research workspace - Use a top query bar. - Add Brief and Flow modes (Flow shows reasoning steps in sequence). - Move history or chat list into a sidebar. - Ensure research visuals are distinct from the main feed styling. 5) No-emoji enforcement - Use ripgrep to find emoji usage and remove it. - Replace emoji with icons or labels. - Apply to UI strings, logs, and docs. 6) Feed view snap-scroll (TikTok style) - Use full-viewport sections (`h-screen`, `snap-start`) within a scroll container that has `snap-y snap-mandatory scroll-smooth`. - Keep the global header visible by only calling `event.preventDefault()` on wheel/touch when a snap transition actually occurs; allow default scrolling when at the first/last item. - Track `activeIndex` and an `isAnimating` guard; call `scrollIntoView` for the next/previous section and clear the guard after a short timeout. - Support wheel, touch (deltaY threshold), and arrow keys; debounce small deltas to avoid accidental snaps. - Retain modals, bookmarks, likes, and favorites behavior; do not regress existing feed actions. ## Checks - Confirm view modes still switch correctly. - Confirm modals and source filters still work. - Confirm research results still render with embedded sources. - Confirm feed snap-scroll still works on wheel, touch, and arrow keys, and that the header remains accessible at top-level scroll. ## Recent context - Snap-scroll feed clips lower content if sections are fixed to `h-screen` without accounting for surrounding layout; prefer a flex parent (`flex-1 h-full min-h-0`) and per-section `h-full min-h-full snap-start` inside the scroll container so each article uses the available viewport height without hiding titles. - Lint currently fails with pre-existing warnings/errors across the frontend (unused vars, hook ordering, explicit `any`); fixes are pending and not related to snap-scroll layout.
Related Skills
dry-refactoring
Guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use when user asks to eliminate code duplication, refactor repetitive code, apply DRY principle, or mentions code smells like copy-paste, magic numbers, or repeated logic. Implements a 4-step workflow from identifying repetition to verified refactoring.
code-refactoring
Simplify and refactor code while preserving behavior, improving clarity, and reducing complexity. Use when simplifying complex code, removing duplication, or applying design patterns. Handles Extract Method, DRY principle, SOLID principles, behavior validation, and refactoring patterns.
agent-md-refactor
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
tdd-workflows-tdd-refactor
Use when working with tdd workflows tdd refactor
codebase-cleanup-refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
code-refactoring-tech-debt
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
code-refactoring-refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
code-refactoring-context-restore
Use when working with code refactoring context restore
component-refactoring
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
swiftui-view-refactor
Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.
refactor-assistant
Automated code refactoring suggestions and implementation.
refactor-code
コードリファクタリングスキル(DRY原則適用、複雑度削減、パフォーマンス最適化、デグレーション防止)