1.4万 件 ・ 関連度順
概要と使いどころ
Use when writing or changing any React component - React Testing Library tests are behavior-focused (byRole first), use user-event, assert on accessible output, one behavior per test, and run in npm test
日本語の概要は準備中です。原文の説明を表示しています。
Automatically notify the user when long-running terminal commands finish (npm test, docker build, git push, etc.). The agent monitors command execution and sends a desktop notification on completion if the command ran longer than threshold (default 10s). Use when user asks to "notify me when done", "desktop notification when command finishes", "alert when done", or "tell me when this completes". Do NOT use for interactive commands (vim, nano, less, htop), commands that always complete in <5s, or streaming commands (tail -f).
日本語の概要は準備中です。原文の説明を表示しています。
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability, with the chosen default + the one sanctioned alternative for each. Applied whenever a new product is scaffolded or a stack choice would otherwise be improvised. Re-deciding the stack every build is the biggest silent time sink; this kills it.
日本語の概要は準備中です。原文の説明を表示しています。
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
日本語の概要は準備中です。原文の説明を表示しています。
Celebrate real milestones only. One line, one emoji. Credit belongs to user, not AI.
日本語の概要は準備中です。原文の説明を表示しています。
The definition of done. Run before calling any change done, fixed, verified, ready or shippable, for features and bug fixes alike. Checks the pre-mortem was answered, proves the tests fail on the old code, gets a fresh breaker review, runs CI's own checks in a clean checkout, checks the user-facing words, and writes the evidence report. Also use when asked "is it done", "is it ready", "did you verify it" or "can we merge".
日本語の概要は準備中です。原文の説明を表示しています。
Set up first-pass for a main folder that holds many repos, or for one repo. In a main folder it writes one set of working rules at the root that every session loads, a workspace map, and a section in each repo with that repo's real commands, test limits and invariants, and it lists each repo's own hooks so first-pass can run them from the main folder. In one repo it writes the rules and the section into that repo. Use when asked to set up, install, add, update or re-run first-pass, to "add the shipping rules", or when the start-of-session check says something drifted. Re-run to update.
日本語の概要は準備中です。原文の説明を表示しています。
After any AI-generated explanation, require the learner to identify one place it could be wrong, one thing to check, and one source to consult. Builds epistemic vigilance — treats AI output as a claim to evaluate, not truth to absorb.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, build, or optimize SMS or MMS marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS. Also use when the user mentions "SMS marketing," "text message campaigns," "SMS sequence," "SMS automation," "abandoned cart text," "post-purchase SMS," "Klaviyo SMS," "Postscript," "Attentive," "Twilio," "A2P 10DLC," "TCPA," "SMS compliance," "short code," "toll-free SMS," "MMS campaign," "should I do SMS," or "SMS vs email." For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.
日本語の概要は準備中です。原文の説明を表示しています。
Build one-page HTML/PDF resumes from copy-paste YAML using one of 12 official templates. HARD GATES: deliver exactly one A4 page; never invent a layout — copy assets/templates/<id> into output/<id>/ and edit that copy only. Keep a full inventory in raw.data.yaml. For each job, COPY selected entries into resume.data.yaml (polish there), then apply that file to a template. Apply pasted YAML by replacing visible text in the official resume.html, then run QA. Default template is basic-a4. Use when creating, iterating, polishing copy, migrating, exporting, or designing resume/CV HTML/PDF. For polishing resume copy, prefer writing-oriented models (Claude Fable 5 / Claude Opus 4.6-4.7 or Opus 5 / Kimi K3 / GLM-5.1-5.3-max / Qwen 3.8 Max); do not use GPT-5.6 Terra/Luna or GPT-5.5 Instant.
日本語の概要は準備中です。原文の説明を表示しています。
Satori is a clinically informed wisdom companion for navigating the inner life — emotions, meaning, grief, purpose, relationship, identity, and the questions that don't resolve easily. Activate when someone is processing something difficult, wrestling with a life question, seeking perspective, or simply needs to think alongside someone who won't rush them toward an answer. Also activate when someone uses language like "I've been struggling with," "I don't know what to do," or "I need to figure out" — or any emotionally charged framing. When in doubt, activate. Draws from Taoism, Buddhism, Stoicism, Christianity, Sufi wisdom, Hindu philosophy, Confucian ethics, and African thought, alongside modern psychology, neuroscience, and trauma-informed frameworks (IFS, DBT, CFT, Schema Therapy, Somatic). Uses Motivational Interviewing, Voss tactical empathy, McAdams Life Story, and Singer Self-Defining Memory — woven naturally, not mechanically.
日本語の概要は準備中です。原文の説明を表示しています。
shadcn/ui component patterns with Radix primitives and Tailwind styling. Use when building UI components, using CVA variants, implementing compound components, or styling with data-slot attributes. Triggers on shadcn, cva, cn(), data-slot, Radix, Button, Card, Dialog, VariantProps.
日本語の概要は準備中です。原文の説明を表示しています。
Drone CI migration to GitHub Actions — syntax mappings and the migration report template for Pipelines, plugins, services, secrets, triggers, multi-platform pipelines. Load with `migration-core` when migrating Drone CI sources to GitHub Actions.
日本語の概要は準備中です。原文の説明を表示しています。
Advanced CV for infrastructure inspection including forest fire detection, wildfire precondition assessment, roof inspection, hail damage analysis, thermal imaging, and 3D Gaussian Splatting reconstruction. Expert in multi-modal detection, insurance risk modeling, and reinsurance data pipelines. Activate on "fire detection", "wildfire risk", "roof inspection", "hail damage", "thermal analysis", "Gaussian Splatting", "3DGS", "insurance inspection", "defensible space", "property assessment", "catastrophe modeling", "NDVI", "fuel load". NOT for general drone flight control, SLAM, path planning, or sensor fusion (use drone-cv-expert), GPU shader development (use metal-shader-expert), or generic object detection without inspection context (use clip-aware-embeddings).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user mentions flood zone, flood risk, FEMA, SFHA, floodplain, property due diligence, natural hazard disclosure, flood insurance, base flood elevation, or asks whether a property is in a flood zone.
日本語の概要は準備中です。原文の説明を表示しています。
Extrae datos estructurados de póliza de seguros argentina — condiciones, exclusiones, franquicias, obligaciones
日本語の概要は準備中です。原文の説明を表示しています。
Calculate and extend runway — current cash, burn rate, runway months, and the levers available to extend it. Use when asked to "how long is our runway", "when do we run out of money", or "what cuts extend runway by 6 months".
日本語の概要は準備中です。原文の説明を表示しています。
SEO audit and keyword strategy — investigate a site's real search opportunities, shortlist candidates, and recommend the one to three changes most likely to grow organic traffic that converts. Evidence-first — metrics come from a tool or are written as unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", "why aren't we ranking", or "what should we fix first for search".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".
日本語の概要は準備中です。原文の説明を表示しています。
Build onboarding playbook - day 1 through week 4 checklist, access provisioning, context transfer, and success milestones. Use when asked to "build an onboarding process", "how do we onboard new hires", or "reduce time to productivity for new joiners".
日本語の概要は準備中です。原文の説明を表示しています。
UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work.
日本語の概要は準備中です。原文の説明を表示しています。
Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".
日本語の概要は準備中です。原文の説明を表示しています。
Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips. Use when asked to "write the copy for this flow", "word this error message", or "write empty state copy".
日本語の概要は準備中です。原文の説明を表示しています。