# Make room to focus

Board: https://swipefile.design/board/make-room-to-focus/
References: 3

Use this board as design direction for my project. Review the references below, identify useful layout, typography, color, and interaction patterns, then adapt them to my brief. Cite the original references you use.

Use these references for design principles. Follow the project brief and use original branding, content, and imagery. Captures document a particular date; they do not verify current product behavior.

## 1. Keybr — Typing practice

Source website: https://www.keybr.com/
Swipefile reference: https://swipefile.design/ref/keybr-practice/
Screenshot: https://swipefile.design/_astro/full.C41g1_8b.webp
Captured: 2026-09-04 | Scope: viewport | Type: app | Style: Education & Learning

A typing practice screen pairs a drill with progress indicators and lesson navigation.

Useful for: Show progress in the context of the exercise while keeping the exercise itself central.
- surface: Typing practice
- nav: Practice, profile, settings, and learning destinations form a compact vertical menu.
- layout: Practice text sits below small performance and key-progress indicators, with destinations on the side.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: A warm pale workspace with dark typing text and restrained progress accents.
- typography: Use spacious practice text and smaller progress labels that do not compete with it.
- pattern: Show progress in the context of the exercise while keeping the exercise itself central.
- states: Initial public practice screen after dismissing the welcome tour; no account was used.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

### Design adaptation prompt

~~~text
# Design reference: Keybr — Typing practice
Source: https://www.keybr.com/
Swipefile reference: https://swipefile.design/ref/keybr-practice/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Typing practice
- nav: Practice, profile, settings, and learning destinations form a compact vertical menu.
- layout: Practice text sits below small performance and key-progress indicators, with destinations on the side.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: A warm pale workspace with dark typing text and restrained progress accents.
- typography: Use spacious practice text and smaller progress labels that do not compete with it.
- pattern: Show progress in the context of the exercise while keeping the exercise itself central.
- states: Initial public practice screen after dismissing the welcome tour; no account was used.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Show progress in the context of the exercise while keeping the exercise itself central.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.
~~~

## 2. Pomofocus — Focus timer

Source website: https://pomofocus.io/
Swipefile reference: https://swipefile.design/ref/pomofocus-timer/
Screenshot: https://swipefile.design/_astro/full.DYEVw5fH.webp
Captured: 2026-09-04 | Scope: viewport | Type: app | Style: Productivity

A focus timer gives one large countdown priority over modes, settings, and task planning.

Useful for: Center the current task and defer planning details until they are needed.
- surface: Focus timer
- nav: Session and break tabs sit above the countdown; report and settings actions stay in the header.
- layout: A centered timer panel sits above a compact task area on a single-color page.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: Warm red surfaces with white timer text and a pale primary start action.
- typography: Make the countdown the strongest element, with secondary labels and actions substantially smaller.
- pattern: Center the current task and defer planning details until they are needed.
- states: The initial 25-minute session with an empty task list; the timer has not been started.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

### Design adaptation prompt

~~~text
# Design reference: Pomofocus — Focus timer
Source: https://pomofocus.io/
Swipefile reference: https://swipefile.design/ref/pomofocus-timer/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Focus timer
- nav: Session and break tabs sit above the countdown; report and settings actions stay in the header.
- layout: A centered timer panel sits above a compact task area on a single-color page.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: Warm red surfaces with white timer text and a pale primary start action.
- typography: Make the countdown the strongest element, with secondary labels and actions substantially smaller.
- pattern: Center the current task and defer planning details until they are needed.
- states: The initial 25-minute session with an empty task list; the timer has not been started.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Center the current task and defer planning details until they are needed.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.
~~~

## 3. Music for Programming — Listening workspace

Source website: https://musicforprogramming.net/latest/
Swipefile reference: https://swipefile.design/ref/music-programming/
Screenshot: https://swipefile.design/_astro/full.GUk3OB9_.webp
Captured: 2026-09-04 | Scope: viewport | Type: app | Style: Media & Content

A listening interface borrows the structure of a code document to organize an episode and its archive.

Useful for: Keep the current item and the wider archive visible without turning the archive into large cards.
- surface: Listening workspace
- nav: Episode links form a persistent right-side list while playback controls stay beside the current episode.
- layout: A broad episode column with credits and controls sits between supporting context and a narrow numbered archive.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: Black background, gray monospaced text, and syntax-like green and violet accents.
- typography: Use consistent monospaced spacing and clear column widths to organize dense credits and lists.
- pattern: Keep the current item and the wider archive visible without turning the archive into large cards.
- states: Public episode page in its unplayed state; no audio was started.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

### Design adaptation prompt

~~~text
# Design reference: Music for Programming — Listening workspace
Source: https://musicforprogramming.net/latest/
Swipefile reference: https://swipefile.design/ref/music-programming/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Listening workspace
- nav: Episode links form a persistent right-side list while playback controls stay beside the current episode.
- layout: A broad episode column with credits and controls sits between supporting context and a narrow numbered archive.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: Black background, gray monospaced text, and syntax-like green and violet accents.
- typography: Use consistent monospaced spacing and clear column widths to organize dense credits and lists.
- pattern: Keep the current item and the wider archive visible without turning the archive into large cards.
- states: Public episode page in its unplayed state; no audio was started.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Keep the current item and the wider archive visible without turning the archive into large cards.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.
~~~

View board: https://swipefile.design/board/make-room-to-focus/
Swipefile: https://swipefile.design/