Discourse Graphs
Official@discoursegraphs
Tools and ecosystem for collaborative knowledge synthesis.
Agent Skills by Discourse Graphs
Showing 9 vetted skills indexed across 1 GitHub repositories.
DiscourseGraphsshadcn
Automate shadcn/ui component installation and design system configuration.
DiscourseGraphsnext-best-practices
Validates Next.js App Router migrations and flags deprecated Pages Router patterns.
DiscourseGraphscreate-obsidian-release
Automate Discourse Graphs Obsidian plugin releases with GitHub pull request data.
DiscourseGraphsreact-best-practices
Review React and Next.js codebases for performance and best practices.
DiscourseGraphsroam-playwright-session
Initialize persistent Playwright browser sessions for Roam Research extension testing.
DiscourseGraphsturborepo
Orchestrates build tasks and dependency graphs for JavaScript and TypeScript monorepos.
DiscourseGraphsroam-load-extension
Build, deploy, and verify local Roam Research extensions in Playwright.
DiscourseGraphsupdate-user-docs
Analyze git diffs and pull request metadata to synchronize user-facing documentation.
DiscourseGraphsvercel-functions
Configure and optimize Vercel serverless and edge functions for production.
Frequently Asked Questions About Discourse Graphs
FAQPage SchemaWhat specific engineering tasks does Discourse Graphs support?▼
Discourse Graphs enables validation of React codebases, orchestration of monorepo build dependencies, and management of plugin release cycles. It specifically targets the synchronization of documentation from git metadata and the configuration of serverless edge environments for production-grade web applications.
Which technical personas benefit most from these capabilities?▼
Frontend engineers, monorepo maintainers, and extension developers working within the Obsidian or Roam Research ecosystems benefit most. These capabilities are designed for developers managing complex React-based architectures who require rigorous validation of migration patterns and streamlined deployment cycles for browser-based plugins.
What are the primary prerequisites for implementing these capabilities?▼
Implementation requires an existing React or Next.js codebase, a Turborepo-managed monorepo structure, and access to GitHub for pull request metadata. For extension testing, a local environment configured with Playwright is necessary to initialize persistent browser sessions and verify local plugin builds.