One home for your agent’s MCP tools and skills. Roster learns from local outcomes, while you stay in control.
Your tools, skills, and local learning. Connected.
The MCP client you use.
Client setupThe local tool routerTransparent by default
Your command-backed servers.
Tool connections
Understand why the checkout button is disabled
Lineup draftedSelect a starter to look inside. Your agent makes this choice.
Playwright/toolSee what the checkout exposes to the browser before guessing at a fix.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
Page: Checkout Heading “Your order” Textbox “Email address” Button “Pay now” [disabled] Text “Enter an email to continue”
GitHub/toolLocate the checkout component and its submit handler in the example repository.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
src/checkout/CheckoutForm.tsx export function CheckoutForm() src/checkout/useCheckout.ts export function useCheckout() src/checkout/CheckoutForm.test.tsx requires an email before payment
Inspect the actual condition behind the disabled button, without changing the file.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
const canSubmit = email.trim().length > 0;
<button
disabled={!canSubmit}
onClick={submitOrder}
>
Pay now
</button>
Linear/toolRead the reported behavior before deciding whether the disabled state is a defect.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
SHOP-24 Explain the disabled payment button The button is disabled until an email is entered. The message is easy to miss on small screens. Status: Triage No resolution recorded.
Get a repeatable method for investigating the checkout. Your agent decides how to follow it.
Returns instructions and resource paths. No scripts run.
Ask for this play to see what your agent receives.
1. Reproduce the reported behavior. 2. Read the relevant code and tests. 3. Separate observation from assumption. 4. Propose a small change. 5. Verify only what the checks establish.
debug-workflow/references/checklist.mdFind likely implementation and test files without loading the whole repository.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
/example/shop/src/checkout/CheckoutForm.tsx /example/shop/src/checkout/CheckoutForm.test.tsx /example/shop/src/checkout/useCheckout.ts
Check the existing rationale for requiring an email before submitting payment.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
Checkout decision Require an email before submitting payment. Show a visible explanation beside the button. This is stored context, not a fresh verification.
Start from the observed behavior, trace the handler, then identify the right regression test.
Returns instructions and resource paths. No scripts run.
Ask for this play to see what your agent receives.
1. Find the UI entry point. 2. Follow the event handler. 3. Read its validation conditions. 4. Locate the test covering that behavior. 5. Report source locations and open questions.
trace-a-change/references/source-map.mdUnderstand the project's conventions before asking a tool to make changes.
Returns instructions and resource paths. No scripts run.
Ask for this play to see what your agent receives.
Use the existing component patterns. Keep changes inside the requested scope. Add a regression test for changed behavior. Run the project's checks before review. Describe anything you could not verify.
project-guide/references/conventions.mdproject-guide/references/testing.mdGitHub/toolGet instructions from the repository itself, rather than inferring its workflow.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
Contributing to Shop Keep UI changes small and testable. Preserve keyboard and screen-reader behavior. Use the package manager declared by this repo. Open a review with the checks you actually ran.
Prepare a clear verification plan. Receiving a checklist does not run those checks.
Returns instructions and resource paths. No scripts run.
Ask for this play to see what your agent receives.
Confirm the requested behavior. Review the complete diff. Check keyboard access and narrow screens. Run the relevant tests. Report results without inventing coverage.
review-checklist/references/review.mdFind the project's boundaries before choosing where a change should live.
A curated fixture, not a connection to your tools.
Try the example to see what this tool returns.
src/
checkout/
CheckoutForm.tsx
CheckoutForm.test.tsx
useCheckout.ts
components/
styles/Call class and latency stay local. Raw prompts, arguments, and results are not stored in the outcome log.
Illustrative MCP arguments using Roster’s real contract. A draft returns compact cards; the agent chooses a call. No visitor tools or configs are accessed.
This is five mode, explicitly enabled. Transparent passthrough is Roster’s default. Five mode returns up to five candidates by default; K is configurable from 1 to 10. The lineups and example outputs are illustrative, not measured rankings.
Transparent by default. Draft a starting five when you choose.
Download Roster and discover your setup. Your client files stay untouched.
Node 22.17+ (22.x) or 24.2+. No global install or model download required.
“Help me set up Roster. Start local, preserve my configuration, and let me choose what changes.”
Checks release availability. Asks before config changes.
Sync backs up first. Use eject to restore your configuration.
Open source. Local state. Telemetry off by default.
Built with AI assistance. Human-review and release gates remain explicit.