coordinate-agents
Drive another Sidecar-managed agent from a shell — discover targets, create the layout, start a provider, prompt and wait, read before sending keys, broadcast…
Writing and maintaining the Sidecar Docusaurus documentation site, including page structure, doc authoring, blog posts, styling, images, and deployment workflow. Use when writing documentation, updating the docs site, adding pages or blog posts, or working with Docusaurus
$ npx -y skills add marcus/sidecar --skill sidecar-website --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/sidecar-websiteContext preview
The summary Claude sees to decide when to auto-load this skill.
Writing and maintaining the Sidecar Docusaurus documentation site, including page structure, doc authoring, blog posts, styling, images, and deployment workflow. Use when writing documentation, updating the docs site, adding pages or blog posts, or working with Docusaurus
name: sidecar-website description: Writing and maintaining the Sidecar Docusaurus documentation site, including page structure, doc authoring, blog posts, styling, images, and deployment workflow. Use when writing documentation, updating the docs site, adding pages or blog posts, or working with Docusaurus configuration.
The documentation site lives in `website/`. It uses Docusaurus with Node.js >= 20.
cd website npm install # First time only npm start # Dev server at http://localhost:3000
website/ ├── docs/ # Markdown documentation pages ├── blog/ # Blog posts (date-prefixed markdown) │ ├── authors.yml # Blog author definitions │ └── tags.yml # Blog tag definitions ├── src/ │ ├── pages/ # Custom React pages (non-docs) │ │ ├── index.js # Front page (/) │ │ └── index.module.css │ ├── components/ # Reusable React components │ └── css/ │ └── custom.css # Global style overrides ├── static/ # Static assets (copied as-is to build) │ └── img/ # Images ├── docusaurus.config.js # Main site configuration ├── sidebars.js # Docs sidebar structure └── package.json
Add a Markdown file in `website/docs/` with YAML frontmatter:
--- sidebar_position: 2 title: My New Page --- # My New Page Content here. Supports **Markdown** and MDX.
**Frontmatter options**:
# Plugin Name One-line description.  ## Overview Brief explanation of UI layout and core purpose. ## Feature Section Description with keyboard shortcut table: | Key | Action | |-----|--------| | `s` | Stage file | | `d` | View diff | ## Navigation How to move around. ## Command Reference Complete shortcut list by context.
docs/ ├── intro.md ├── guides/ │ ├── _category_.json # Folder metadata │ ├── installation.md │ └── configuration.md
`_category_.json` controls folder appearance:
{
"label": "Guides",
"position": 2,
"collapsible": true,
"collapsed": false
}Auto-generates from `docs/` folder structure. To customize, edit `sidebars.js`:
const sidebars = {
tutorialSidebar: [
'intro',
{
type: 'category',
label: 'Guides',
items: ['guides/installation', 'guides/usage'],
},
],
};Docs support MDX (Markdown + JSX):
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; <Tabs> <TabItem value="npm">npm install</TabItem> <TabItem value="yarn">yarn add</TabItem> </Tabs>
The front page is at `website/src/pages/index.js` -- a React component using Docusaurus Layout and theming.
export default function Home() {
return (
<Layout title="Home" description="...">
<HomepageHeader />
<main className="container">
{/* Add content here */}
</main>
</Layout>
);
}Styling: `index.module.css` for page-specific, `src/css/custom.css` for global overrides.
**Website doc screenshots** (for pages in `website/docs/`):
**README / repo doc screenshots**:
**General website images** (logos, icons):
In JSX:
import screenshot from '@site/static/img/logo.png';
<img src={screenshot} alt="Logo" />Date-prefixed Markdown files in `blog/`:
--- slug: my-post title: Post Title authors: [default] tags: [announcement, release] --- Preview text shown in list. <!-- truncate --> Full content below the fold.
Never use emoji in site content, components, or documentation. Use Lucide icons instead.
The site uses Lucide icon font (CDN import in `docusaurus.config.js`).
<i className="icon-terminal" /> <i className="icon-check" /> <i className="icon-git-branch" />
Common icons: `icon-eye`, `icon-terminal`, `icon-rocket`, `icon-check`, `icon-copy`, `icon-external-link`, `icon-git-branch`, `icon-zap`, `icon-keyboard`, `icon-layers`, `icon-code`.
Browse all: https://lucide.dev/icons
cd website npm run build # Outputs to website/build/ npm run serve # Preview built site locally
Deploys automatically via GitHub Actions when changes to `website/` merge to `main`.
| Task | Steps | |------|-------| | Add docs section | Create folder in `website/docs/`, add `_category_.json`, add Mark
Always check if you are running in Sidecar: run sidecar agents for capabilities. You might never open your editor again. Status: Ready for daily use. Please report any issues you encounter. Documentation · Getting Started · Comprehensive List of Features
Drive another Sidecar-managed agent from a shell — discover targets, create the layout, start a provider, prompt and wait, read before sending keys, broadcast…
Create conversation adapters for importing AI chat history from different tools (Claude Code, Cursor, Warp, Codex, etc.). Covers the adapter.Adapter interface,…
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox,…
Create new sidecar plugins implementing the plugin.Plugin interface, rendering views with Bubble Tea, handling keyboard input via keymap contexts, and…
Create prompts for sidecar workspaces. Covers prompt structure (name, ticketMode, body), template variables (ticket with fallbacks), config file locations…
Create custom color themes for Sidecar, including base theme selection, color overrides, gradient borders, tab styles, per-project themes, community themes,…