「cap」の検索結果

Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).

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

Provision and drive a `pu` box — an Incus container used as a clean Linux host for CI, builds, and evidence capture. Use when you need to run something on a fresh remote box instead of the user's machine: `nix run` a build, run CI against a real host, capture screenshots/video off-machine, or reproduce on a pristine environment. Covers create/connect/scp/destroy, running remote commands, copying artifacts back, and the no-egress failure mode. Triggers on "pu box", "spin up a box", "run this on a box", "ephemeral host", "pu create/connect/destroy".

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

Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of need), and contextual-when-needed (surfaces help at the moment friction occurs) patterns. Triggers on product tour, in-product tooltip, contextual help, walkthrough, feature tour, hint system, in-app guidance, tour platform. Also triggers when feature adoption is low, when users miss key product capabilities, or when an in-product help system is being scoped for the first time.

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

Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.

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

Audit the brand, UX, and site design of the leading sites in a vertical as a set of observable cross-site patterns, producing the experience bar a new build must meet or beat. Use this skill whenever the user wants to assess the competitive design field, capture vertical conventions, identify the design and UX bar of a category, or set the experience standard before a build. Triggers on competitor experience audit, UX audit, site design audit, brand audit, design conventions, what makes these sites good, vertical conventions, storefront patterns, merchandising patterns, layout density, primary task, design bar, category conventions, retail vs marketing register, what does the field do. Also triggers when an audit of the competitive field has captured technical signals (SEO, accessibility) but never named the brand, UX, or design conventions, and the build downstream will read as off-vertical without that bar.

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

Capture and catalog new ideas from conversations and research

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

Form optimization for lead capture, contact, demo request, application, and checkout forms. Covers field-cost analysis, multi-step form design, validation UX, mobile optimization, and A/B testing frameworks.

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

Map the competitive narrative landscape and score unclaimed positioning gaps. "find us a differentiated position"

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

Team structure, gearing analysis, continuity planning, and competing demand management for legal matters. Use when setting up a matter team, reviewing whether work is being done at the right grade, planning cover for an unavailable team member, or managing a resource conflict across matters. Trigger on: 'who should be on this matter', 'team structure', 'gearing', 'right people at the right level', 'partner is doing associate work', 'cover for maternity leave', 'who has capacity', 'team member leaving', 'over-allocated', 'staffing conflict', 'pinch point', 'capacity problem', 'how do we resource this', 'team too senior', 'team too junior'.

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

AFA design, scope-to-fee matching, negotiation preparation, health check, and scope dispute assessment for in-house legal ops teams managing outside counsel arrangements. Design fee structures (fixed, capped, collar, blended, phased, success). Assess whether scope supports a proposed AFA. Prepare commercial positions for fee negotiations. Review existing AFAs against delivery data. Assess OOS claims and build dispute response. Trigger on: 'structure the fee', 'move off hourly', 'design an AFA', 'does scope support a fixed fee?', 'negotiate the fee', 'renegotiate the arrangement', 'is our AFA holding?', 'fee health check', 'cap is being approached', 'firm is claiming OOS', 'is this in scope?', 'is this OOS?', 'AI should reduce the cost', 'blended rate vs fixed', 'collar arrangement', 'phased fees'.

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

Analyze digital and analog captures from Saleae Logic MSO devices. Decode protocols like UART, SPI, I2C from exported binary files. Use when analyzing logic analyzer captures for CTF challenges, hardware reverse engineering, or protocol decoding.

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

Design a multi-round questioning sequence for interrogating AI chatbot answers, tracking how responses shift and distinguishing genuine updates from sycophantic capitulation. Use when teaching students to probe AI critically.

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

Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".

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

Build accrual schedules for A-share companies tracking revenue recognition, expense accruals, and working capital timing. Adapted from the original accrual-schedule skill for CAS accounting and Chinese business practices. Triggers on "A股应计项目", "应计计提", "accrual schedule China", "应计账款分析", or "working capital accruals [company]".

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

Competitive landscape analysis for A-share companies and Chinese industries. Maps competitors, compares positioning, and assesses relative strengths. Adapted from the original competitive-analysis skill for Chinese market context. Triggers on "A股竞争格局", "行业竞争分析", "competitive landscape China", "competitive analysis A-share", or "[company] competitors China".

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

Comprehensive A-share sector and industry landscape reports — market size, competitive positioning, policy environment, key A-share players, trading multiples, and thematic trends. Adapted from the original sector-overview skill for Chinese market structure and terminology. Triggers on "A股行业分析", "行业研究", "板块分析", "sector overview China", "A-share sector deep dive", "白酒/半导体/新能源 行业分析", or "[industry] landscape China".

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

Drive the real Course Video Manager web app in a browser and capture proof of what it did. Use to verify a change before opening a PR, to reproduce a reported UI bug, to see what a page actually renders, or to capture a screenshot of app behaviour. Runs on a per-run, writable clone of a local copy of Matt's data by default — click anything that mutates; production is never written to.

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

Generates user-facing usage statistics, activity summaries, and personalized insights dashboards (weekly recaps, year-in-review, Spotify Wrapped-style). Use when user wants to show usage stats, activity insights, or shareable recap screens. Different from analytics-setup which sends data to a backend — this shows insights to the USER on-device.

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

Expert guidance on macOS platform capabilities. Covers sandboxing, app extensions, menu bar apps, and background execution. Use when implementing system integration features.

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

Generates an automated App Store screenshot pipeline with UI tests for screenshot capture, device framing, localized caption overlays, and multi-size batch export. Use when user wants automated screenshots, App Store screenshot generation, or a fastlane snapshot replacement.

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

Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.

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

Analyze how competitors present their brand — identity, messaging, positioning, voice, and visual style — to find gaps and opportunities. Use when the user says "competitor brand analysis", "analyze competitor brands", "how do competitors position themselves", "competitor messaging", "competitor identity", "what are competitors saying", "benchmark competitors", "competitive brand landscape", "how do we compare to competitors", "competitive audit", or wants to understand the brand landscape before defining their own position.

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

First-tier tech company P8 capability advisor for evaluating, coaching, and giving career advice against a P8 senior expert, architect, or domain-owner profile. Use when the user asks for P8-level assessment, promotion readiness, capability gaps, project or resume review, interview preparation, or growth advice based on first-tier tech company P8 expectations.

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

First-tier tech company P7 capability advisor for evaluating, coaching, and giving career advice against a P7 technical/product/expert profile. Use when the user asks for P7-level assessment, promotion readiness, capability gaps, resume/project review, interview preparation, or concrete growth advice based on first-tier tech company P7 expectations.

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