Project outline
Keep a short summary beside the selected file.
- Type
- Markdown document
- Updated
- Today
Your shortcut to everything.
product entry with public launcher and AI scenes.
⌘SpaceOpens Raycast when installed
One window, distinct commands
Select a public command family to inspect its particular structure.
Command window
No matching commands.
Recent files
Project outline.md
Planning notes.txt
Expression128 × 4
Result
Left half
Right half
Window placement is a labelled illustration.
Small actions, useful context
Each feature pairs one purpose with a concrete public structure.
Keep a note
A title, checklist and export affordance.
Find a command
A query, selection and result preview.
Share a starting point
A template, prerequisites and source link.
Show the work in context.
Text and media stay associated when the layout becomes a single column.
Explore a complete public flow.
Open the extension directoryA task, its context and its tools
The conversation is an authored public-demo reconstruction. Controls never run tools or a model.
Source-scale scene. On small screens choose the readable view to operate its controls.
Review newly reported bugs
Scripted exampleCheck the example bug reports and summarize their next steps.
The authored reports have three follow-ups. Review their context, choose an owner and confirm availability.
Checked new bugs in Linear3
Search example issues: New bug reports. Found three authored example reports. Status: complete.
Read issue context: Example project notes. Read the authored context for the example reports. Status: complete.
Check availability: Example schedule. Permission required in the real integration. Status: blocked.
Summarize the planning notes and identify the next action.
The sample notes point to three follow-ups. Review the outline, choose an owner and confirm the date.
Read project context3
Search notes: Planning notes. Found three local example notes. Status: complete.
Read document: Project outline. Read an authored example outline. Status: complete.
Check availability: Example schedule. Permission required in the real integration. Status: blocked.
Summarize the planning notes and identify the next action.
The sample notes point to three follow-ups. Review the outline, choose an owner and confirm the date.
Read project context3
Search notes: Planning notes. Found three local example notes. Status: complete.
Read document: Project outline. Read an authored example outline. Status: complete.
Check availability: Example schedule. Permission required in the real integration. Status: blocked.
- Schedule
- Gather context
- Review the result
Review the resultConnectors show a reading sequence. Automation remains a public illustration.
Models
Identity, capability and plan access.
Compare model structureProjects
Tasks remain grouped under their project.
Tools
Results stay inside the activity that produced them.
A small command can make a recurring task easier to start.
Keeping the context nearby makes the next step clearer.
Composition contract and public sources
product entry with public launcher and AI scenes. This authored implementation is distinct from original DOM/CSS replay. Automated presence, behavior and geometry are reported separately.
Family F-home; patterns hero, launcher, features, ai, testimonials.
Complete family contracts · Synthetic fixtures · Local schemas
Source capture IDs: CAP-capture--pages--home-1440, CAP-capture--pages--home-1440-lower, CAP-capture-more--pages--home-1440, CAP-capture-more--pages--home-1440-full, CAP-capture-more--pages--home-1440-lower, CAP-capture-more--pages--home-1920, CAP-capture-more--pages--home-390, CAP-capture-more--pages--home-768, CAP-capture-more--pages--home-homebrew-1440, CAP-capture-more--pages--home-mobile-menu-390, CAP-source-assets--pages--home-initial, CAP-source-assets--pages--home-mobile, CAP-source-assets--pages--home-mobile-initial, CAP-source-assets--pages--home-mobile-menu-open, CAP-source-assets--pages--home-scrolled.