「read」の検索結果

Gmail の未読を既読化する。「メールを既読にする」「メールの未読を既読」「メールを既読化」「Gmail 既読化」「Gmail の未読を消す」「メールを開封扱い」「メールを一括既読」などで起動。

Transform transcripts, conversations, or raw notes into shareable content — either multiple social posts OR a single long-form article. Learns style from user's published content. Handles transcripts of any length (tested up to 5500+ lines / 90+ min). Use when user: (1) provides transcript/conversation/recording and wants social content, (2) asks to "turn recording/notes into posts", (3) mentions generating content from recordings/notes, (4) needs multiple publishable pieces from single source, (5) asks to write an article from a transcript — e.g. "write an article/long-form", "organize into an article", "write up this session", "turn this talk into a blog post", "deep dive". Social mode outputs 2-15 ready-to-publish pieces. Article mode outputs a structured long-form piece (3000-10000+ chars) written section-by-section.

日本語の概要は準備中です。原文の説明を表示しています。

Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.

日本語の概要は準備中です。原文の説明を表示しています。

Patterns for scaling read-heavy Convex apps to millions of users. Use when optimizing bandwidth, reducing query costs, fixing slow queries, creating digest tables, replacing reactive subscriptions with one-shot fetches, adding compound indexes, debouncing writes, rate-controlling backfills, or running npx convex insights. Trigger when users mention "scale", "bandwidth", "performance", "optimize", "slow queries", "expensive queries", "digest table", "denormalize", or "thundering herd" in the context of Convex.

日本語の概要は準備中です。原文の説明を表示しています。

Use for pull-request, merge, version and release mechanics in the Syntropic137 repo, and for CI or release-pipeline failures. Trigger phrases include "open a PR", "submit my changes", "address the review comments", "Copilot left comments", "merge this PR", "push this nit straight to main", "CI is red", "the release gate failed", "smoke test broke", "why is this PR BLOCKED", "bump the version", "cut a release", "release v1.x", "write the release notes", "main -> release PR", "approve the release gate", "the release published a bad asset", "triage the open PRs", "PR backlog", "which PRs are ready to merge", "merge order", "DORA metrics", "deploy frequency", "lead time", "change failure rate", "time to restore", "why didn't the issue auto-close". Covers trunk-based `main`, the `release` branch, local gates (`just qa-ci`, `just preflight`), GitHub Actions gates, review and merge policy, and post-release verification. Do NOT use for deciding what to dispatch, running the orchestrator loop, or deciding when to deploy a beta or run a pit stop (see `orchestrating`); for whether a task belongs in a workspace or locally (see `dogfooding`); for using the `syn` CLI as an end user (see the syntropic137 plugin skills).

日本語の概要は準備中です。原文の説明を表示しています。

new step of mspec workflow — bootstrap a change directory and readme.md

日本語の概要は準備中です。原文の説明を表示しています。

Use when: ticket lifecycle, state transitions, ready for QA, changes requested, QA passed, role-based workflow policy, Developer to QA handoff, or relay routing across delivery agents.

日本語の概要は準備中です。原文の説明を表示しています。

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

日本語の概要は準備中です。原文の説明を表示しています。

Activate for any ticket that touches a Supabase RPC, edge function, or TypeScript client function in src/lib/. Ensures both caller and callee are verified before state:ready-for-qa.

日本語の概要は準備中です。原文の説明を表示しています。

Activate for any ticket that changes React components, user-facing flows, or UI state. Ensures all five observable UI states are verified before state:ready-for-qa.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: implement a scoped ticket, fix a bug, add tests, prepare a PR-ready code change, or reuse a standard builder workflow across software engineer agents.

日本語の概要は準備中です。原文の説明を表示しています。

Activate for any ticket that adds or changes a Supabase migration, environment variable, edge function deployment, or runtime configuration. Ensures infrastructure is live in the target QA environment before state:ready-for-qa.

日本語の概要は準備中です。原文の説明を表示しています。

Convergence loop that iteratively improves work until quality thresholds are met. Use when: (1) "refine this", "make this better", "iterate on this", (2) After /analyst gives a REVISE verdict, (3) Output quality is below 8/10, (4) "run the refinery loop on this". Reads analyst reviews from system/reviews/. Generates, scores, diagnoses, rewrites, re-scores. Stops when all dimensions >= 8/10 or diminishing returns detected. Outputs to system/refinery-log.md.

日本語の概要は準備中です。原文の説明を表示しています。

Senior engineering analyst for code review, plan review, and automation review. Use when: (1) "review this", "analyze the code", "check this plan", (2) After implementation to verify quality, (3) "is this good enough?", (4) Before marking a task complete, (5) Reviewing a blueprint from /architect, (6) Reviewing output from /refinery. Four-lens review: architecture, code quality, reliability, performance. Reads from system/blueprints/ and source code. Outputs to system/reviews/.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly review partner that compounds productivity gains over time. Use when: (1) "weekly review", "what did I accomplish this week?", "compound my gains", (2) End of work week to review progress, (3) "what patterns are emerging?", (4) "update the system map", (5) Feeling stuck and need to identify friction. Reads all system/ files to synthesize progress. Outputs to system/compounder/week-{date}.md. Feeds insights back to /audit.

日本語の概要は準備中です。原文の説明を表示しています。

Solution architect that creates implementation blueprints before building. Maps 2-3 approaches ranked by simplicity, creates phased build plans with rollback points, and checks dependencies. Use when you need to design a solution, create a blueprint, plan before building, or take a task from the audit and need an implementation plan. Part of the architect-system loop. Reads from system/audit-report.md. Outputs to system/blueprints/.

日本語の概要は準備中です。原文の説明を表示しています。

Solution architect that creates implementation blueprints before building. Use when: (1) "architect this", "design a solution", "blueprint for", (2) Taking a task from the audit report and need an implementation plan, (3) "how should I build this?", "plan before building", (4) Before any non-trivial implementation. Reads from system/audit-report.md. Outputs to system/blueprints/.

日本語の概要は準備中です。原文の説明を表示しています。

Productivity analyst that maps your workflow, scores tasks, and builds a prioritized automation plan. Use when: (1) "audit my workflow", "what should I automate?", "productivity review", (2) Starting a new project and need to identify high-leverage tasks, (3) Feeling overwhelmed and need to prioritize, (4) After /compounder surfaces new friction or patterns. Reads compounder insights when available. Outputs to system/audit-report.md.

日本語の概要は準備中です。原文の説明を表示しています。

Senior engineering analyst for code review, plan review, and automation review. Four-lens review covering architecture, code quality, reliability, and performance, each scored 1-10. Delivers APPROVE, REVISE, or REJECT verdicts. Use when you need a code review, plan review, quality check, or want to verify work before shipping. Part of the architect-system loop. Reads from system/blueprints/ and source code. Outputs to system/reviews/.

日本語の概要は準備中です。原文の説明を表示しています。

Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance checking, or App Store submission readiness.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.

日本語の概要は準備中です。原文の説明を表示しています。

Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and Workflow Builder integration. Focus on best practices for production-ready Slack apps. Use when: slack bot, slack app, bolt framework, block kit, slash command.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis, LiveKit for real-time infrastructure, and WebRTC fundamentals. Knows how to build low-latency, production-ready voice experiences. Use when: voice ai, voice agent, speech to text, text to speech, realtime voice.

日本語の概要は準備中です。原文の説明を表示しています。