Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
Use when building UI, components, motion icons, loaders, or visual design. In BDB projects, routes to the BDB component and motion-icon library (npm @hybridlabor-api/ui-motion-library, shadcn namespace @bdb) as the first source before third-party registries or building from scratch. Outside BDB projects, the same lookup order applies with the original sources listed in the bdb-ui-library repository docs.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
BDB component and motion-icon library. In BDB projects it is the first source for UI building blocks, before anything is built from scratch. Outside BDB projects the same lookup order applies, using the original sources listed in the bdb-ui-library repository docs.
registry.json (items) and llms.txt (install, item table, conventions) from the library repo or the installed package (@hybridlabor-api/ui-motion-library; in the BDB workspace: ~/dev/bdb-dev/bdb-ui-library/). If an @bdb item fits, install it, do not rebuild it. Install: npx shadcn@latest add @bdb/{name} (registry in the consumer's components.json; template: templates/components.json).components.json order, only for items whose endpoint was verified (see the source list in the bdb-ui-library repository docs). Install via registry. Currently @magicui (marquee verified) and @watermelon. Skip @aceternity (401) and @cultui (404) until an endpoint is verified.@spaceui, @componentry, Skiper UI, 21st.dev, React Aria, Tremor, Hairline, Kojima; listed in the bdb-ui-library repository docs): documentation and inspiration links only. Never install from them without a verified endpoint, never copy code.npx shadcn@latest add @bdb/knob (namespace @bdb)npm install @hybridlabor-api/ui-motion-libraryregistry/knob.json in the library repoNew items must meet the intake checklist (repo README): DTCG-tokens-only styling, dark/light via tokens.css, prefers-reduced-motion guard, a11y primitives (Base UI/Radix), evidence screenshot (scripts/evidence.mjs), scripts/registry-validate.mjs exit 0.
Style references: observe yes, copy code no; always write code fresh. Componentry is MIT (reference). Space UI (@spaceui) has no verified licence or endpoint (see the bdb-ui-library repository docs). ui-experiments is NO-REDISTRIBUTION (strict).
~/dev/bdb-dev/bdb-ui-library/registry.jsonREADME.mdNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
The English summary is being prepared. Showing the original description.
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
The English summary is being prepared. Showing the original description.
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
The English summary is being prepared. Showing the original description.
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
The English summary is being prepared. Showing the original description.
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
The English summary is being prepared. Showing the original description.