Skills
Teach it how you work.
- Keep conventions and tooling with the project
- Package repeatable work as named skills
- Reuse the process you refined last time
projects/atlas golub/workspace16.15%
❯/review-navigation-labels
Reviewed for 3.2s
◆Editsrc/navigation/NavLink.tsx
41export function NavLink({label, current}: Props) {
42 return (
43 <a className="nav-link">
43 <a className="nav-link" aria-current={current}>
44 {label}
45 </a>
46 );
47}
48
49export default NavLink;
Navigation now announces the current page and keeps its readable label.
❯ /review-interface❯ /check-accessibility❯ /capture-responsive-views
❯golub-build · skills
Plan
Agree on the approach before editing.
- Map the work before changing files
- Adjust the sequence and resolve open details
- Connect each step to a change you can review
projects/atlas golub/workspace16.15%
❯Plan a shared sign-in link flow.
Reviewed for 3.2s
plan.md×
1Outcome
2Let members sign in with a short-lived email link.
3Implementation
4• Store a hashed, single-use token.
5• Validate the link and open the session.
6• Test expiration and repeated use.
[a]approve[c]comment[q]close
✓ Plan approved · Ready for the next step
❯ /review-interface❯ /check-accessibility❯ /capture-responsive-views
❯golub-build · plan
Plugins
Connect the tools that fit your project.
- Bundle useful skills and integrations
- Make team workflows available in the workspace
- Add browser, data, and development connections
projects/atlas golub/workspace16.15%
❯Enable browser-review for this workspace.
Reviewed for 3.2s
HooksPluginsMarketplaceSkillsMCP Servers
/ Type to searchWorkspace ⌄
›team-tools(project)[install]
›browser-review(workspace)[install]
›git-workflow(workspace)[install]
›code-quality(workspace)[installed]
◆browser-review · ready
✓/review-interface
✓/check-accessibility
✓/capture-responsive-views
❯ /review-interface❯ /check-accessibility❯ /capture-responsive-views
❯golub-build · plugins
Q&A
Resolve the unknowns before they become rework.
- Surface missing requirements early
- Choose the architecture and design together
- Keep those decisions in the implementation plan
projects/atlas golub/workspace16.15%
❯Sketch a workspace activity view.
Reviewed for 3.2s
A few details before we start[3]
How should the workspace feel?
1Quiet and spaciousSimple panels with room for the work
2Colorful and livelyUse color to make activity easy to scan
3Dense and practicalKeep frequently used controls close together
4Follow our brandUse the design guidance in this project
[1/3] ↑/↓ navigate · ←/→ questionEnter: select
What foundation should we use?
1AstroPages and focused interactive components
2ReactStateful views across the application
3VueReusable views with shared application state
4Keep our current toolsBuild on the dependencies already here
[2/3] ↑/↓ navigate · ←/→ questionEnter: select
Which view would be useful first?
1Today’s workAssigned items and decisions awaiting review
2Recent activityA timeline of updates and completed work
3Team workloadTasks grouped by owner and status
4Workspace setupManage access and connected services
[3/3] ↑/↓ navigate · ←/→ questionEnter: select
✓ Direction captured · Updating the plan
❯ /review-interface❯ /check-accessibility❯ /capture-responsive-views
❯golub-build · ask
Subagents
Give focused investigations their own room.
- Delegate independent questions in parallel
- Keep research context separate for each task
- Gather the results before choosing the next edit
projects/atlas golub/workspace16.15%
exploreTrace report submissionexplore · golub-build
exploreCheck worker deploymentexplore · golub-build
exploreRead queue utilitiesexplore · golub-build
exploreInspect report generationexplore · golub-build
exploreReview retry behaviorexplore · golub-build
exploreMeasure database waitsexplore · golub-build
❯Investigate delays in the report queue.
Reviewed for 3.2s
│Review the last releaseexplore · golub-build[Working]
│Measure queue waiting timeexplore · golub-build[Working]
│Inspect report queriesgeneral · golub-build[Working]
│Check worker concurrencygeneral · golub-build[Working]
Four focused checks are ready to compare.
Queue waits increased after the worker limit changed. The report queries are stable; review the concurrency setting first.
❯ /review-interface❯ /check-accessibility❯ /capture-responsive-views
❯golub-build · subagents
projects/atlas golub/workspace16.15%
A clearer path through the code
Describe what you want to change. Build is being designed to help turn that intent into a plan, working code, and a result you can inspect.
A workspace for the whole change
The planned toolkit brings project context, implementation, and verification into the same workflow.
Plan mode
Decide the route before the first edit
Subagents
Separate agents for independent questions
Skills
Save a working method and call it again
Hooks
Run routines at the right points in the work
MCP servers
Bring external tools into the workspace
AGENTS.md
Let repository instructions guide the work
Memory
Carry useful decisions into later sessions
Code search
Locate the code behind a feature or issue
Multi-file edits
Make related edits across several files
Git integration
Inspect diffs and prepare versioned changes
Deep reasoning
Reason through the harder parts of a task
Web search
Consult documentation while you work
Terminal execution
Run commands and examine their results
Headless workflows
Use the agent in automated development jobs
Code review
Examine a change before accepting it
Sandboxed execution
Use boundaries appropriate to the task
Background tasks
Follow work that continues in the background
Theming
Adjust the workspace to your preferences
What would you build with it?
Golub Build is in development. Share the workflows you’d like us to support.
❯Talk to us about BuildComing soon.
