「aces」の検索結果

Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.

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

Capture and visually inspect Qt GUI widgets using screenshots. Use when asked to verify GUI rendering, test widget appearance, check layouts, or visually inspect any PySide6/Qt component. Enables Claude to "see" Qt interfaces by capturing offscreen screenshots and analyzing them with vision.

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

Weekdays. Checks every project in the inventory from the outside, records one dated observation per project, then reads the production log surfaces since its own cursor and groups every error into a fingerprint so a hundred sightings are one incident. It appends the health ledgers, writes the health digest, and cards the incidents that clear the threshold. It changes nothing, deploys nothing, and never rotates a key.

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

Weekdays, heavy browser lane. Captures the dated raw material tomorrow's drafts are built from, out of the member's own shipped work, their own site and changelog, their own signed in saved searches, and the places their audience already is. Every line carries a source URL read this run, a date, a verbatim quote, and an expiry. It invents nothing, it is read only everywhere and totally read only on LinkedIn, and it sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekdays, heavy browser lane. Opens the member's own signed in profile, post, and notification surfaces for every platform in the channel plan, confirms that everything published since the last run is genuinely live, reads the counts attached to each post, captures every comment, mention, quote, reply, and inbound message into a queue the member answers by hand, and drafts a suggested reply for each one. Read only everywhere and totally read only on LinkedIn. It sends only where you released the channel, never replies, spends only where you released it, and never touches a credential.

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

Runs once by hand on the first day and once a month after that, light browser lane. On the first run it researches the business from its own published surfaces before asking anything, writes the strategy folder, creates the ledgers, seeds the opening cards, builds the single page dashboard, reconciles the schedule table, and registers the eight recurring jobs. On every monthly run it re-reads a month of the kit's own evidence, applies what changed, adds a tab for a channel that gained volume, rebuilds, and reconciles every registered job against the table. It holds every outbound action unless you released the channel, and it never enters a credential.

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

Runs once by hand on the first day and once a month after that, on the first weekday, light browser lane. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the pipeline, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed to the files it owns, and carries every member written setting across verbatim. It holds every outbound action unless you released the channel, and it never enters a credential.

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

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, reads the account structure once, writes the plan folder, seeds the board, creates the creative doctrine, builds the dashboard, and registers the recurring jobs. It asks about exactly two things, the monthly ceiling and the daily cap, because those are the two numbers that decide how much money can leave. On every monthly run it re reads the evidence, corrects what the ledgers prove wrong, and reconciles drift.

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

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces, reads the member's own already published posts, and builds the voice file from real samples rather than from an idea of a voice, then writes the plan, creates the proof inventory, seeds the opening slots, and registers the recurring jobs. On every monthly run it re reads the evidence the kit produced and rebuilds only what the evidence contradicts. It publishes only where you released the channel, never replies, spends only where you released it, and it never enters a credential.

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

Weekly, heavy browser lane, read only toward the world with no exception. Works the surfaces on its own watchlist through one contiguous browser phase, captures one dated observation per real change with a verbatim quote and the exact URL, refuses to report any change against a surface it has no baseline for, and writes one capped weekly page. It types nothing that changes anything, takes no action on LinkedIn ever, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekdays, conditional browser lane. Reads the ticket ledger and the account, billing, and usage surfaces the member named, and decides which paying customers are about to leave. Every flag is a dossier carrying the trip wires that fired, the exact evidence behind each one, that account's whole history, and one suggested save with its cost and the screen it happens on. It reads billing screens and touches no control on them: a refund, a credit, a plan change, and a cancellation are named and never made.

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

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the launch board, builds the tailored command center, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed, reconciles drift, and rebuilds. It holds every outbound action unless you released the channel, and it never enters a credential.

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

Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.

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

Use for authorized macOS and Mach-O reverse engineering including codesign, Objective-C/Swift recovery, endpoint security surfaces, and Apple platform malware analysis.

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

Use when an idea, task, or issue surfaces mid-session and the user wants it captured as a todo instead of doing it now. Infers the area, checks duplicates, and writes the todo file plus a STATE.md update.

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

Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone

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

Use when urgent work surfaces mid-milestone and must land between two planned phases without renumbering the roadmap. Inserts it as a decimal phase such as 72.1 after the phase the user names.

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

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

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

Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for — monitoring before anything blows up, see `15-social-listening-global`; diagnosing weak performance numbers, see `03-performance-eval-global`; the routine post-campaign review, see `63-campaign-retrospective-global`.

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

Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for "color theory."

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

Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a structured AskUserQuestion multi-option picker for user agency, and dispatches the chosen mode. Mode D (Atlas Fleet) is selectable only when detect_capabilities returns tier=premium (licensed atlas-launcher detected); otherwise it is a locked Atlas Pro teaser. Plan Mode is NOT used (spec section 13.5): AskUserQuestion is the sole user-agency mechanism. Declares HANDOFF complete so EXECUTE can follow.

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

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

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

Design or improve module interfaces using deep-module heuristics. Use when deciding where a seam belongs, reducing caller-facing complexity, improving testability or navigability, or comparing module designs.

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

Generate, derive, optimize, and diagnose structured AI image prompts for luminous cinematic Eastern xianxia environments under one inherited master canon with measurable divine scale, fixed five-layer space, 40–60% content-bearing breathing air, monumental Eastern architecture, railing-free edges, and coherent immortals and costume. Cover one-location scenic landmarks, immense inhabited celestial realms, cloud-borne palace cities, high-key Eastern sky-megastructure imagery, and the explicit `仙界大境原典` creative route. Use for Chinese fantasy scenery, places where immortals live, heavenly capitals, colossal celestial gates, architectural fragments above cloud seas, measurable divine scale, unusual framing, color and lighting direction, style-preserving variants, prompt rewrites, diagnosis, or direct image generation. Support 16:9, 21:9, 4:3, 3:2, 4:5, and 9:16; default to 16:9 for one prompt and never infer a nine-image series from a vertical ratio.

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