1,688 件 ・ 関連度順
概要と使いどころ
Complete community building, engagement, and monetization system. From zero to thriving community — launch strategy, member engagement loops, content programming, moderation frameworks, growth tactics, monetization models, and health metrics. Works for Discord, Slack, Telegram, Circle, forums, or any platform.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
日本語の概要は準備中です。原文の説明を表示しています。
Generates and delivers all outreach for OUTREACH_READY leads. Automated delivery via Chrome DevTools MCP -- email, LinkedIn, Instagram. Gig leads auto-applied on platform. No approval gates.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a weekly social media content calendar across platforms. Chains blog-researcher + linkedin-researcher + social-content-writer to produce 5-7 posts/week with posting schedule.
日本語の概要は準備中です。原文の説明を表示しています。
Generates video production plans including shot lists, scripts, B-roll suggestions, music mood, thumbnail concepts, and platform-specific specs for reels, YouTube, and video ads.
日本語の概要は準備中です。原文の説明を表示しています。
Generates detailed design briefs for social media creative assets. Covers image specs per platform, copy overlay text, color palette, and format specs for stories, carousels, singles, and reel covers.
日本語の概要は準備中です。原文の説明を表示しています。
Architects the encryption, codec/transport, and premium-feature layer of a group video-calling product, on top of an already-chosen SFU topology. Covers E2EE patterns (Zoom leader-fan-out, Signal pairwise-fan-out, MLS/TreeKEM as in Discord's DAVE, Telegram's ledger consensus), the SFrame (RFC 9605) + WebRTC Insertable Streams mechanism letting an SFU relay encrypted frames it can't read, codec/transport choice (AV1/VP9 SVC vs. simulcast, Opus, congestion control, Media-over-QUIC, WHIP/WHEP), and which "premium" features (virtual backgrounds, live captions, recording, breakout rooms, spatial audio) survive E2EE vs. structurally can't. Use when adding E2EE to an SFU-based call, choosing a 2026 codec/SVC strategy, or deciding which features to disable under E2EE mode. NOT for call topology/platform choice (see webrtc-adhoc-video-chat, which this composes with). NOT for one-way broadcast (see managed-video-streaming-pipeline). NOT for the DM/group-chat text backend (see realtime-messaging-backend-architecture).
日本語の概要は準備中です。原文の説明を表示しています。
Audit or design server-side indexes, directories, reputations, or aggregates that are DERIVED from traffic a platform witnesses (chain heads, run verdicts, heartbeats, publish activity) so that consent gates the derivation, not merely the read: no shadow index over non-consenting principals, post-consent-only evidence windows, retention bounds and delete-propagation into derived rows, activity-oracle threat modeling, and audit-logged ranking discretion. Use when building a capability directory / whois from witnessed activity, a reputation ledger from settled outcomes, vitals aggregation across tenants, or any "the yellow pages can't lie because they index signatures" feature. Keywords: shadow index, derived index, consent gates derivation, activity oracle, phone book not a log, delist propagation, ranking weight audit, k-anonymous aggregate, subpoena surface. NOT for the consent-screen UX and scope-ladder mechanics themselves (use local-first-tenancy-boundary), reputation scoring math and Sybil economics (use agent-identity-continuity-reputation), or discovery-layer architecture L1/L2/L3 (use agent-discovery-directories-guilds).
日本語の概要は準備中です。原文の説明を表示しています。