1,868 件 ・ 関連度順
概要と使いどころ
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
日本語の概要は準備中です。原文の説明を表示しています。
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
日本語の概要は準備中です。原文の説明を表示しています。
Web and App implementation guide for Aurora UI. Trigger when user wants gradient glows, color blobs, and atmospheric lighting effects.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Generate professional AI product photography and commercial images. Models: FLUX, Imagen 3, Grok, Seedream for product shots, lifestyle images, mockups. Capabilities: studio lighting, lifestyle scenes, packaging, e-commerce photos. Use for: e-commerce, Amazon listings, Shopify, marketing, ...
日本語の概要は準備中です。原文の説明を表示しています。
Control Philips Hue lights and scenes via the OpenHue CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Review a product requirement, PRD, brief, or meeting note before design or development; expose missing decisions, contradictions, edge cases, dependencies, and validation gaps without inventing business rules.
日本語の概要は準備中です。原文の説明を表示しています。
Track and correlate events across multiple timezones with automatic conversion. Use when analyzing distributed system incidents, coordinating cross-regional operations, or creating time-normalized reports from logs/events spanning PST/CST/EST/JST or other timezones. Handles daylight saving transitions automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Correlate events across multiple log files from different sources, systems, or time periods. Build unified timelines, identify causal relationships between events, and highlight anomalies that span multiple data sources. Supports timezone normalization and gap detection. Use when analyzing logs from multiple systems (frontend, backend, database, infrastructure), investigating distributed system failures, or building event timelines across services. Triggers: "correlate these logs", "build timeline from multiple logs", "cross-system analysis", "find related events across logs", "multi-source log analysis", "distributed trace analysis"
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a local codebase and infer the architecture it is actually using, including repo kind, best-fit dominant architecture, directly evidenced coexisting patterns, major subsystem exceptions, confidence, docs-vs-code drift, and repo-fit hints for downstream agents. Use when prompts ask what architecture a repo uses, whether it is really hexagonal or just layered, what subtle patterns shape a repo or slice, how a target slice fits a hybrid monorepo, whether documented architecture matches implementation, or when `/tw-tk` needs a repo-dialect preflight before making a minimal change.
日本語の概要は準備中です。原文の説明を表示しています。
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Uses the chrome-devtools-axi CLI for browser automation, accessibility-tree snapshots, console and network inspection, screenshots, Lighthouse audits, and performance traces. Use when interacting with Chrome from the shell, especially when the user mentions chrome-devtools-axi, AX snapshots, browser debugging, or DevTools automation from the command line.
日本語の概要は準備中です。原文の説明を表示しています。
Lightweight triage for the ln-* skill set. Use when unsure which ln skill to use next, starting work on something new, or when the user asks for guidance on their development process.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesized reference notes from three US Government vehicle-safety sources: NHTSA Cybersecurity Best Practices for the Safety of Modern Vehicles (updated 2022, final), NHTSA Automated Driving Systems 2.0: A Vision for Safety (2017), and a 16-section selection of 49 CFR Part 571 (FMVSS) pinned at eCFR versioner date 2025-01-01. Use for voluntary vehicle cybersecurity practices, the ADS 2.0 twelve priority safety design elements, and FMVSS occupant protection, brakes/stability/lighting, and fuel/EV integrity requirements. Not ISO 26262, not ASPICE, not ISO/SAE 21434, not UNECE R155/R156, not SAE J3016, and not the full Part 571; the FMVSS material is a selection of vehicle-level minimum performance standards, not a process standard.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the OUSD(R&E) guidebook Implementing a MOSA in DoD Programs (Feb 2025). Use for the Modular Open Systems Approach as a DoD acquisition + design discipline: the statutory/regulatory basis (10 U.S.C. 4401–4403, FY2017/FY2021 NDAA, DFARS), the five OUSD(R&E) pillars, the plan→modularize→identify→define→standardize interface lifecycle, technical levers (WBS/MIL-STD-881F taxonomy, standards profiling, API-first software, COTS/cybersecurity), MOSA assessment metrics and tools (PART/OAAT/KOSS/SEAM/MAUT), technology-change and DMSMS management, roadmaps, MOSA across the six AAF pathways, and contracting/IP/data-rights mechanics. SCOPE LIMITS: this is U.S. DoD weapon-system acquisition policy, not a general open-architecture or interface-standards reference — it names standards (FACE, OMS, DISR) without reproducing them, is light on detailed engineering of any specific standard, and does not cover the underlying SE processes (use dau-se-guidebook / nasa-npr-7123) or general systems-engineering theory (use sebok).
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NASA NPR 7123.1D — Systems Engineering Processes and Requirements. Use for the 17 common SE processes (SE Engine), life-cycle reviews and entrance/success criteria, SEMP structure and content, ETA roles and tailoring/customizing rules, Technology Readiness Levels (TRL 1–9), SE work product maturity terminology, contracted project oversight, and MOE/MOP/TPM measurement frameworks. Does not cover NASA programme financial management, human spaceflight medical standards, or software engineering requirements in depth (see NPR 7150.2 for the latter).
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2). Use for NASA's systems-engineering process model — the SE Engine and 17 common technical processes, the program/project life cycle (Pre-Phase A through F), Key Decision Points and technical reviews (MCR/SRR/PDR/CDR/…), stakeholder expectations, technical requirements, design solution, product verification and validation, and crosscutting technical management (planning, risk, configuration, interfaces, data, assessment, decision analysis). Strong for aerospace/spaceflight project SE and lifecycle gating; NASA-specific terminology (KDPs, NPR 7123.1).
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Schedule Management Handbook (2024 edition, Revision 2). Use for program/project schedule management of aerospace and large engineering efforts: the five sub-functions (Planning, Development, Assessment & Analysis, Maintenance & Control, Documentation & Communication); the Integrated Master Schedule (IMS) and the WBS/OBS/CBS breakdown structures; the Schedule Management Plan (SMP) and Basis of Estimate (BoE); Critical Path Method, logic, durations, float and margin; tiered schedule assessment (Requirements/Health/Basis checks, the Shock Test) and the Dimensions of Schedule Reliability; Schedule Risk Analysis (SRA), Integrated Cost-Schedule Risk Analysis (ICSRA), Monte Carlo, correlation, merge bias, and the Joint Confidence Level (JCL); baselining, replan vs. rebaseline, EVM schedule metrics (SPI, BEI, CEI, HMI, Earned Schedule, CPLI), and status/progress/forecast reporting. This is NASA's scheduling doctrine grounded in NPR 7120.5 and the GAO Schedule Assessment Guide. Thin on the underlying mechanics of CPM, statistics, and EVM (it points to companion handbooks); aerospace/space-flight-centric; anchored to the 2024 second edition.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Fault Management Handbook (NASA-HDBK-1002, Draft 2, April 2012). Use for the systems-engineering discipline of designing what a system does when it fails — the fault/failure/anomaly vocabulary, the five FM strategies (two prevention strategies — design-time fault avoidance and operational failure avoidance — plus three tolerance strategies — failure masking, failure recovery, and goal change), the six FM process activities across NASA mission phases Pre-A to E, response-latency-versus-time-to-criticality (TTC) design trades, fault/failure containment regions and FEPPs, the four redundancy approaches, top-down FM requirements development, FM verification vs. validation, the seven dedicated FM milestone reviews (FMCR/FMARR/FMPDR/FMCDR/FMTRR/FMLRR/FMCERR), FM organizational structure, and mined NASA Lessons Learned. Space-mission oriented (flight/ground/operations); spacecraft examples throughout. IMPORTANT: built from an UNAPPROVED DRAFT — several sections (detailed architecture building blocks, the Assessment & Analysis guidance, and Operations & Maintenance) are placeholders in the source and are thin here. Thin on detailed FDIR algorithms, terrestrial/IT fault management, and any approved-standard terminology that may have changed since Draft 2.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32). Use for writing requirements for real-time, embedded control systems — the avionics/medical slant — via the Handbook's eleven recommended practices: system overview and boundary (monitored/controlled variables), operational concepts (use cases), environmental assumptions, change-tolerant functional architecture (dependency diagrams), safety-driven architecture revision (FHA/PSSA/fault tree), system modes, detailed behavior and performance requirements (ideal value + tolerance + latency), the four-variable model bridge to software requirements (MON/CON/NAT/REQ, IN'/REQ'/OUT', DO-178B mapping), subsystem allocation, and rationale. Carries the Isolette Thermostat and Flight Control System worked examples. Slanted toward control systems with sensors and actuators; thin on information-system / enterprise / agile requirements, on requirements-management tooling, and on the formal-methods internals of SCR/RSML/SpecTRM (it names them, does not re-teach them). Does not reproduce the IEEE/DO-178B/ARP standards it cites.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from MIL-HDBK-516C (Airworthiness Certification Criteria). Use for DoD air-system airworthiness planning: tailoring a certification basis, systems engineering criteria, and domain clusters for structures, flight technology, propulsion/installation, avionics/electrical/E3/diagnostics, computer systems/software, and crew systems (including applicable UAS control-station elements). Qualitative guidance handbook — not raw contractual requirements. Does not replace service airworthiness authority policy, civil FAA certification rules as authorities, or detailed JSSG/MIL performance specs.
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
日本語の概要は準備中です。原文の説明を表示しています。
Compares one clause (liability, termination, confidentiality or any other) across several contracts, templates or successive versions and returns a DRAFT comparison table: verbatim clause text per document, the clause split into elements with every difference from the baseline highlighted and categorised, and neutral questions for counsel. Never says which wording is better or enforceable. Use when the user asks to "compare the liability caps across these five supplier contracts", "line up the termination clause in these three drafts", "show how the confidentiality clause changed between versions", "contrast this clause with our template" or "benchmark the indemnity wording across our customer agreements". Do not use for a whole-contract review, use contract-review-pack instead; for screening one NDA against standard positions, use nda-triage. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Transform a supplied photo into an editorial collage where a realistic foreground gradually continues as fine drawing and light pigment on paper. Use for 实景渐绘拼贴、摄影与建筑线描融合、photo-to-sketch travel posters. Keeps a photographic anchor rather than converting the whole image into an illustration.
日本語の概要は準備中です。原文の説明を表示しています。