connector-required
Skill2 starsChanged 13 days agoMITView on GitHub
Conventions for Patio web UI (web/src) pages that need an AI connector to do anything, such as Chats and Scheduled tasks. Use when building or changing any AI feature page, form, or empty state that picks a connector (chat, scheduled task, agent, automation, prompt runner), so users with no connectors get pointed to Connections › AI instead of an empty picker.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibilitySkill
- dropdown-buttonSkill
- frontend-designSkill
- golang-patternsSkill
- golang-testingSkill
- icon-buttonSkill
- list-viewSkill
- releaseSkill
- searchable-dropdownSkill
- seoSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Edit form for an existing item whose connector is gone: keep the form so the user can still read, disable, or delete the item, show …
- Distinctive: line 33
No new copy of the sentence.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Connector required
Every AI feature runs through a connector (Claude Code, Codex, Copilot, opencode, or Local AI). Users with zero connectors can't do anything on these pages, so the page should say why and give them one click to fix it, instead of showing an empty select or a disabled button with no explanation.
Reference: ConnectorRequired in web/src/Connectors.tsx, used by web/src/Chats.tsx and web/src/ScheduledTasks.tsx.
The component
import { ConnectorRequired } from "./Connectors";
<ConnectorRequired then="create a scheduled task" />It renders a complete .panel skill-empty card: the connector icon mark, <h2>No connectors yet</h2>, the shared sentence "Add a connector first (Claude Code, Codex, Copilot, opencode, or Local AI), then <then>.", and a Go to Connectors button that navigates to /ai/connectors (the AI tab of the Connections page). Pass then as a lowercase verb phrase for what the page does. Don't wrap it in another panel, and don't copy the card, sentence, or button into a page; if the look or wording changes, it should change in one place.
Where it goes
Load connectors with api.get<Connector[]>("/api/connectors") and keep the state undefined until loaded, then check connectors?.length === 0. This avoids flashing the message before the request returns.
- List page with no connectors: show
ConnectorRequiredin place of the normal empty state. Hide the page's primary "New<thing>" buttons, since creating one would fail anyway. Existing items still list below. - Main empty area (like Chats with no chat open): show
ConnectorRequiredin place of the whole empty-area section. - Create form with no connectors: show only
ConnectorRequiredand skip the form. - Edit form for an existing item whose connector is gone: keep the form so the user can still read, disable, or delete the item, show
ConnectorRequiredabove it, and keep Save disabled until a connector is picked.
Checklist
- No new copy of the sentence; use the component.
- Message appears only after connectors finish loading.
- The Go to Connectors button is a real
<button>reachable by keyboard. - Plain
var(--border)panels, no colored accent stripes (AGENTS.md). - Verify with
pnpm --dir web build.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

