「sem」の検索結果

Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.

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

Build and release pipeline for the Pump SDK — tsup TypeScript builds, Cargo release profiles, semantic release with commitizen, npm publishing, linting, Makefile targets, Vercel deployment, and MCP server distribution.

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

Use when designing, implementing, reviewing, debugging, testing, profiling, or porting concurrent, parallel, distributed, high-performance, network dataplane, kernel-bypass, or real-time software, including locks, semaphores, monitors, MPI, CSP rendezvous, DPDK, VPP, eBPF, XDP, AF_XDP, SR-IOV, RSS, RoCEv2/RDMA, RMS/EDF, priority inversion, and environment selection from silicon to edge.

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

Find the canonical Rosetta Stone attribute that best matches a fuzzy description, semantic phrase, or required schema shape. Searches the catalog with pagination, describes the shortlist in one batched call, ranks candidates by name + shape match, and returns the canonical attribute ID plus close alternatives. Use when: "find the X attribute", "what's the graph-edge attribute ID", "look up the email Rosetta Stone attribute", "search the attribute catalog for Y", "which attribute has SOURCE_ID + TARGET_ID + IS_DIRECTED". (narrative-common)

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

Load for EF Core entities/configurations, semantic value persistence, portable constraints, DbContext/query filters, repositories/specifications, migrations, model snapshots, transactions, or seeded lookup tables; use query-optimization specifically for N+1 or slow SQL diagnosis.

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

Load for global UI-system changes involving CSS `@layer`, primitive/semantic/component tokens, themes, reusable MudBlazor wrappers, or design-token governance; not for one component's isolated CSS.

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

Create Beamer-style academic PPTX presentations using python-pptx. Produces publication-quality .pptx files with navy-blue Metropolis theme (16:9, frame title bars, progress bar) for conference talks, job market presentations, and seminar slides. Called by /present command.

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

Knowledge base from the NIST/SEMATECH e-Handbook of Statistical Methods (NIST HB 151) — the practical statistics reference for engineering, metrology, and quality. Use for: exploratory data analysis and the four univariate assumptions (4-plot); measurement process characterization including bias/precision, calibration designs, gauge R&R, and ISO/GUM uncertainty budgets; production process characterization (stability vs. capability); process modeling and regression (LS/WLS/NLS/LOESS); design of experiments (screening, fractional/factorial, response-surface, Taguchi); statistical process control (Shewhart/CUSUM/EWMA charts, capability indices, acceptance sampling); product/process comparisons (hypothesis tests and confidence intervals for 1/2/3+ groups, ANOVA, multiple comparisons); and reliability (lifetime & repair-rate models, accelerated testing, reliability growth). Scope limits: this is applied frequentist statistics for measurement and quality — it does NOT reproduce the per-distribution formula galleries, worked case studies, datasets, plot images, or Dataplot/R code of the original web Handbook (those are described, not copied); it is thin on modern machine learning, Bayesian methods beyond conjugate reliability priors, time-series/forecasting, and Bayesian experimental design.

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

Knowledge base from the NIST Framework for Cyber-Physical Systems (SP 1500-201/202/203, v1.0, 2017). Use for engineering and analyzing cyber-physical systems (CPS) and IoT: the CPS Framework's aspect × facet grid (nine aspects of concern examined through conceptualization, realization, and assurance facets), cross-property trustworthiness risk management (safety/security/privacy/reliability/resilience together), data interoperability (syntactical/semantic/contextual, canonical models, identifiers, provenance), the timing aspect (time-interval classes, time domains, time-aware networking) and secure/resilient time (GNSS jamming/spoofing, PTP/NTP attacks, holdover, the clock-error model and Allan/MTIE metrics), plus the use-case requirements method. Bridges IT and OT under a clock. Scope limits: a 2017 living/draft document, thin on post-2017 standards and on detailed control catalogs; it names but does not reproduce ISO/IEC/IEEE 42010 and 15288 process text or permission-licensed third-party figures.

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

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 FAA AMS Lifecycle V&V Guidelines (verification and validation), Version 3.0, dated April 2017. Use for applying verification and validation across the FAA Acquisition Management System (AMS) lifecycle: the verify-vs-validate distinction (built right vs. right thing), the work-product/component/product tiers, the nine V&V planning elements, the four method catalogs (Appendix C), decision-point-gated V&V (SASP, CRD, Investment Analysis, Solution Implementation, In-Service Management), the Appendix B document checklists (PRD/APB/ISPD/PMP), and the DT/OT/IOA test triad. Scope limits: this is an FAA acquisition-V&V doctrine, NOT a general SE process model, requirements-engineering manual, or test-design textbook. It borrows its core V&V definitions from CMMI v1.2 (SEI, paraphrased) and presumes the surrounding AMS lifecycle (see the FAA SEM pack); its phase tables are policy snapshots as of April 2017 and it is thin on detailed test methods, tool specifics, and anything outside FAA acquisition governance.

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

Activación conductual para la depresión: romper el círculo vicioso, registro de actividades, planificación semanal y actividades basadas en valores.

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

Ordner und Dateiablagen semantisch aufräumen: lokale Regeln und vorhandene Taxonomie erkennen, Dateien inhaltlich zuordnen, zusammengehörige Sets erhalten, klare Vorgänger-/Nachfolgerreihen und Logs archivieren, gemischte gültige und überholte Inhalte per Cut-and-Clue trennen und Löschkandidaten reversibel in einen Prüf-Papierkorb legen. Nutze diesen Skill bei „Ordner aufräumen“, „Dateien sinnvoll einsortieren“, „alte Versionen archivieren“, „Logdateien bereinigen“, „veraltete und gültige Inhalte trennen“ oder wenn beim Aufräumen Geheimnisdateien beziehungsweise Geheimnisse in einer Cloud-Ablage auffallen. Er funktioniert anbieter- und nutzerneutral allein; erkannte kompatible Module oder Dateidienste werden nur als optionale Beschleuniger genutzt. Für bereits vollständig definierte wiederkehrende Sammelregeln stattdessen eine regelbasierte Datei-Automation, für den Umbau einer ganzen Projektarchitektur einen Pipeline-/Projekt-Optimizer verwenden.

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

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrase -- including German ones such as "grill mich", "grill mich zu diesem Plan" or "zerpflück meinen Plan im Grill-Modus". Entry point for the /grill-me command; can also be invoked directly.

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

A relentless interview to sharpen a plan or design. Use when the user says "grill me", "grill mich", "grill mich zu diesem Plan", or explicitly invokes /grill-me. Does NOT fire on generic "review this", "poke holes", "stress-test", "devil's advocate" or "critique" phrasing -- for reviewing an already-written artifact (code, PR, paper) use code-review, 3agenten-review, 7phasen-review or caveman-review instead; grill-me interrogates a still-open plan or idea before it is built.

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

Extrahiert aus einem Chatverlauf (aktuelle Session oder Transkript-Dateien) einen wiederverwendbaren Skill — oder verbessert einen sehr ähnlichen existierenden Skill, statt ein Duplikat zu erzeugen. Nutze diesen Skill bei „mach daraus einen Skill", „das sollten wir als Skill festhalten", „extrahiere Skills aus diesem/alten Chatverläufen", „diese Arbeitsweise wiederverwendbar machen", oder bei `/skill-extract`. Deckt auch Bulk-Läufe über viele alte Transkripte ab (mit Datenreduktion über Subagenten). Für wiederkehrende AUTOMATISIERUNGEN (Cron/Schedule/Loop) stattdessen den Schwester-Skill workflow-extract nutzen.

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

KI-gestuetzte Textproduktion in drei Teilskills: Allgemeine Texte (Blogpost, Social, Newsletter, Copy, E-Mail, Bericht), narrative Storys (Skript, Kurzgeschichte, RPG, Weltenbau) und PR-Kommunikation (Pressemitteilung, Positionspapier) mit lokalem LaTeX-PDF-Compiler. Kein externer Dienst zwingend erforderlich.

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

Baut und betreibt ein anbieterneutrales Self-Care-Kernset für geplante LLM-Aufgaben und Desktop-App-Automationen. Ergänzt deterministisches Policy-Linting, Lock- und Modell-Governance, semantische Prompt-Prüfung, konsistente Mehrflächen-Updates, Mini-Checks und Regeldatei-Hygiene. Nutzen, wenn ein Agent seinen nativen Scheduler entdecken oder eine bestehende Automations-Flotte mit Rollback, Readback und Löschschutz kontinuierlich verbessern soll. Löst aus bei automation self-care, Scheduler-Task-Pflege, Desktop-App-Automations-Wartung, Automations-Flotten-Audit, selbstheilende Zeitpläne, core-set-textautomations, basic-text-automations, textbased-automation-core, textbased-automation-drivers, textbased-governance-automations oder textbased-desktopapp-automations.

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

Reads one export transaction, order or shipment description and returns a DRAFT export review pack: parties to screen with a screening checklist, an item classification worksheet, a red-flag review, licence-determination questions and open items. Use when the user asks to "prepare the export review for this order", "pre-check this shipment for export control", "who do we need to screen on this deal", "build the classification worksheet for this item" or "assemble the trade-compliance file for this technology transfer". Do not use for vendor security or due-diligence screening of a supplier's questionnaire answers; use vendor-risk-screening-brief instead. Never classifies, screens, clears, decides licence need or releases a shipment; trade compliance does. Drafts for human review; never approves, authorises or signs off.

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

Maps every proposed P&ID object from an accepted enrichment draft to the generic family, catalogue class and required attributes the project's intelligent P&ID authoring tool would need, as a readiness table with UNKNOWN wherever the project catalogue extract is not provided, plus connectivity readiness per line and a numbered list of import blockers. Mapping only: it never writes to the tool, never produces an import file and never claims a class exists in the catalogue. Use when the user asks to "build the readiness map", "show how far the draft is from a sandbox import", "list what would block the import", "map the objects to the tool catalogue" or "check attribute readiness against the catalogue extract" after gate G3. Do not use for validating the discipline sections or assembling the review package, use validation-and-review-package instead. Drafts for human review; never approves, authorises or signs off.

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

Assembles a DRAFT capital expenditure request pack from the requester's inputs: business need, options including do nothing, costs exactly as provided, benefits as stated, risks, assumptions, budget status and the approvals route read from the organisation's own delegation of authority, with UNKNOWN for every missing figure, date or name. Use when the user asks to "prepare a capex request", "draft the business case for this equipment", "fill in the capital request form", "structure this investment proposal" or "what approvals does this spend need". Do not use for a board or committee decision paper, use board-paper-skeleton instead; for an IT change approval, use change-request-pack; to pressure-test a finished business case, use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

AI-first web search via Exa — semantic/neural ranking, category-scoped results, fresh content retrieval, and one-shot answer synthesis with citations. Use when the user needs current web information better ranked than general web search, or a grounded answer with sources.

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

Refresh WhatsApp text into an Obsidian vault (data layer, dashboard, group labels, contact notes). Text only, never downloads media, and pulls the recent window the live companion bridge exposes rather than a full multi-year archive. Semi-automatic by design: it drives the live bridge and needs the phone nearby. Triggers: "/whatsapp-sync", "pull whatsapp".

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

Assemble a full multi-tier content episode from a milestone session's hot context and publish it out of band, ahead of the nightly schedule: teasers go to chats right after one approval, the rest follow by topology. Triggers: "/wow", "this is a milestone", "this session is great, tell everyone".

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