5,057 件 ・ 関連度順
概要と使いどころ
Checks Next.js Server Actions ('use server') for missing authentication/authorization before mutations, missing input validation, and untrusted client-supplied IDs — treating each action as a public HTTP endpoint.
日本語の概要は準備中です。原文の説明を表示しています。
Detects domain terms drifting between code identifiers and the established ubiquitous language (same concept under different names, or different concepts sharing a name).
日本語の概要は準備中です。原文の説明を表示しています。
Turn brand context and a social brief into platform-aware copy, storyboard, reference frames, and video drafts without publishing them.
日本語の概要は準備中です。原文の説明を表示しています。
Establish durable project context, asset roles, delivery constraints, and approval state for repeatable video work.
日本語の概要は準備中です。原文の説明を表示しています。
Build a music-led video sequence by planning beats, creating or accepting an audio track, animating ordered visuals, and assembling a reviewable draft.
日本語の概要は準備中です。原文の説明を表示しています。
Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
日本語の概要は準備中です。原文の説明を表示しています。
Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition.
日本語の概要は準備中です。原文の説明を表示しています。
Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
日本語の概要は準備中です。原文の説明を表示しています。
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
日本語の概要は準備中です。原文の説明を表示しています。
Turn post-publish notes into pipeline improvements. Use after a video ships, or when the user says "retro", "here is my feedback", or "wrap up this project".
日本語の概要は準備中です。原文の説明を表示しています。
Run a comprehensive health check on a single Estuary task by combining catalog status, data flow stats, recent errors, and publication history. Use when diagnosing a task that seems broken, slow, or stuck. Use when user says "is my task healthy", "something seems wrong", "check my capture", "check my materialization", "why is data not flowing", "task health check", "diagnose my task", or "what's wrong with my pipeline".
日本語の概要は準備中です。原文の説明を表示しています。
Implements type-safe reactive SQL persistence in Flutter using Drift v2.32 (formerly Moor) built on SQLite with automatic code generation. Activates when defining table schemas with Drift DSL, writing type-safe join or subquery operations, handling schema migrations with MigrationStrategy, using reactive watch() streams for live UI updates, implementing ACID transactions, defining foreign key constraints or cascade deletes, enabling WAL mode for write performance, troubleshooting generated .g.dart type mismatches, migrating from sqflite or sqlite3 v2 to v3, using DAOs for query separation, or building offline-first apps requiring strong relational data integrity and compile-time SQL verification.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect, debug, and inject custom code into a running Steam client — desktop (macOS, Linux, Windows) or Steam Deck over the network — through its Chromium Embedded Framework (CEF) Chrome DevTools Protocol endpoint. Use when developing Steam UI plugins, mods, themes, or integrations — injecting CSS/JS to try a change, locating webpack modules and obfuscated class names, reading React or SteamUIStore state, inspecting Big Picture / Quick Access Menu windows, screenshotting what actually rendered, streaming console logs, or diagnosing runtime errors in Steam's UI. The same commands run against either device, or both at once. Injection is per-session and for development only. Not for building a plugin loader or making changes persist across restarts, Steamworks game SDK work, game development, or scraping the public Steam web store.
日本語の概要は準備中です。原文の説明を表示しています。
META Stock Price Activity: Meta stock was up 0.37% at $718.30 at the time of publication Tuesday, ac
日本語の概要は準備中です。原文の説明を表示しています。
Write operator-facing and public documentation plans for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for runbooks, rehearsal checklists, show-day checklists, EN/PT docs updates, demo scripts, safety wording, and follow-up documentation revisions.
日本語の概要は準備中です。原文の説明を表示しています。
Idea to published-ready content: brief, script, render routed through the Creator Extension content-studio skill (Hyperframes or Remotion), then a social pack. Use for "make a reel", "idea to video", "content from this idea", "script and render a clip".
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce verification evidence with explicit limits. Use when the user wants to ship, deploy, go live, launch, publish, or put their app online, or asks to wire up env vars, webhooks, auth settings (signup, email confirmation, password policy), a real signup → confirmation email → login journey, password recovery, account isolation between two users, auth redirects, email DNS or a custom domain.
日本語の概要は準備中です。原文の説明を表示しています。
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
日本語の概要は準備中です。原文の説明を表示しています。
Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.
日本語の概要は準備中です。原文の説明を表示しています。
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
日本語の概要は準備中です。原文の説明を表示しています。
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
日本語の概要は準備中です。原文の説明を表示しています。