sendbird-playground
Official@sendbird-playground
Facilitates codebase observability, IPC contract auditing, and design system implementation for Stave-based repository architectures.
Agent Skills by sendbird-playground
Showing 9 vetted skills indexed across 1 GitHub repositories.
sendbird-playgroundthe-high-signal-review
Analyze workspace diffs or pull requests and report validated issues with file:line references.
sendbird-playgroundthe-trace-execution-path
Trace request paths across Stave process boundaries from producer to consumer.
sendbird-playgroundstave-release
Automate versioned release PR creation for the Stave repository.
sendbird-playgroundthe-ipc-contract-audit
Audit IPC contract changes across TypeScript and Zod schemas.
sendbird-playgroundthe-explore-codebase
Guide step-by-step exploration of an unfamiliar codebase from architecture docs to entrypoints.
sendbird-playgroundthe-provider-runtime-symmetry
Validate Claude and Codex provider runtime parity after shared edits.
sendbird-playgroundlens-inspect
Inspect live web apps via MCP tools for DOM, console, and network data.
sendbird-playgroundstave-design-system
Apply the Stave desktop-first design system to UI surfaces using shadcn components and radix-vega preset.
sendbird-playgroundstave-worktree-pr-flow
Ship the current working state as a GitHub pull request using a worktree.
Frequently Asked Questions About sendbird-playground
FAQPage SchemaWhat specific technical tasks are enabled by these capabilities?▼
These capabilities enable granular codebase exploration, IPC contract auditing between TypeScript and Zod schemas, and runtime parity validation for Claude and Codex providers. Additionally, they support systematic UI surface updates using shadcn components and radix-vega presets, alongside streamlined GitHub pull request generation via worktrees.
Which engineering personas benefit from these technical capabilities?▼
Full-stack engineers, platform architects, and frontend developers working within the Stave ecosystem benefit most. These capabilities are designed for developers managing complex distributed process boundaries, maintaining strict schema contracts, or enforcing consistent design system standards across large-scale web applications.
What are the primary prerequisites for implementing these capabilities?▼
Implementation requires an existing Stave-based repository structure and a TypeScript-centric environment. Users must have established access to the target codebase and GitHub repository permissions to execute worktree-based pull requests and perform IPC contract audits across defined schema boundaries.