1,799 件 ・ 関連度順
概要と使いどころ
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any CodexAI task; load this baseline before routing, editing, or claiming work is done.
日本語の概要は準備中です。原文の説明を表示しています。
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
日本語の概要は準備中です。原文の説明を表示しています。
Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
日本語の概要は準備中です。原文の説明を表示しています。
Master Anthropic's prompt engineering techniques to generate new prompts or improve existing ones using best practices for Claude AI models.
日本語の概要は準備中です。原文の説明を表示しています。
Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze the NTFS Master File Table ($MFT) to recover metadata and content of deleted files by examining MFT record entries, $LogFile, $UsnJrnl, and MFT slack space using MFTECmd, analyzeMFT, and X-Ways Forensics.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes bootkit and advanced rootkit malware that infects the Master Boot Record (MBR), Volume Boot Record (VBR), or UEFI firmware to gain persistence below the operating system. Covers boot sector analysis, UEFI module inspection, and anti-rootkit detection techniques. Activates for requests involving bootkit analysis, MBR malware investigation, UEFI persistence analysis, or pre-OS malware detection.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Lean Six Sigma consulting skill supporting all belt levels (White Belt to Master Black Belt). Use this skill for DMAIC/DMADV project execution, Lean waste elimination (VSM, 8 Wastes/DOWNTIME, 5S), statistical analysis (process capability Cp/Cpk, control charts, hypothesis testing), and Six Sigma training/education. Triggers include "improve process", "reduce defects", "sigma level", "DMAIC project", "value stream mapping", "Kaizen", "process capability", "control chart", "root cause analysis", "5 Whys", "Fishbone diagram", "FMEA", "DOE", or requests involving process improvement methodologies.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks about "Hyprland configuration", "hyprland.lua", "hyprland.conf", "Hyprland Lua config", "hyprctl", "Hyprland keybinds", "Hyprland window rules", "Hyprland monitors", "Hyprland dispatchers", "Hyprland animations", "Hyprland workspaces", "Hyprland IPC", "Hyprland plugins", "hyprlock", "hypridle", "hyprpaper", "hyprcursor", "hyprpicker", "hyprsunset", "xdg-desktop-portal-hyprland", "Hyprland on NixOS", "Hyprland Home Manager", "Hyprland layouts", "Hyprland dwindle", "Hyprland master layout", "Hyprland FAQ", "Hyprland performance", "Hyprland Nvidia", "Hyprland screen sharing", "Hyprland special workspace", "Hyprland smart gaps", "Hyprland multi-monitor", "Hyprland tearing", or any topic related to configuring, troubleshooting, or extending the Hyprland Wayland compositor and its ecosystem tools.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the GAO Schedule Assessment Guide (GAO-16-89G, 2015). Use for building, assessing, or auditing a program's integrated master schedule (IMS): the ten best practices of a reliable schedule (capture, sequence, resource, duration, traceability, valid critical path, reasonable total float, schedule risk analysis, updating, baseline), the four characteristics (comprehensive, well-constructed, credible, controlled), critical path method arithmetic (forward/backward pass, total float), schedule risk analysis (Monte Carlo, contingency), statusing and baseline control, and the Appendix II audit triad. Scheduling/time-management oriented: it is the authority on schedule reliability, but it is NOT a cost-estimating guide, a full SE process model, an agile guide, or a risk-management framework — see sibling packs (gao-cost, dau-se-guidebook, nasa-schedule, nasa-risk) for those.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from MIL-HDBK-61B, the DoD Configuration Management (CM) guidance handbook (7 April 2020, cataloged with Change 1, 2025). Use for defense CM across the acquisition and sustainment life cycle: the five CM functions (planning, identification, control/change management, status accounting, verification & audit), the three configuration baselines (FBL/ABL/PBL) and FCD→ACD→PCD documentation, configuration items (CIs/HWCI/CSCI), change instruments (ECP/NOR/RFV), the CCB and Class I/II classification, CDCA/AA authority, FCA/PCA audits, data management and data rights (CDRL/DID, DFARS rights ladder, master/authoritative source), and tailoring CM by phase (EIA-649-1 R/T/NR matrix, Appendix C templates), plus digital-era CM (digital twin, viewpoints, MOSA). NOTE: 61B is advisory guidance that adopts and points to the SAE EIA-649 / EIA-649-1 / GEIA-HB-649 suite for the authoritative CM requirements — this pack names and describes that suite but does not reproduce its copyrighted requirement text. Thin on: the EIA-649 requirement clauses themselves, form-level detail (DD-form field instructions, full DID content), and non-DoD/commercial CM frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Digital Engineering Acquisition Framework Handbook (NASA-HDBK-1004). Use for acquiring digital/model-based data under contract: the Data Requirements Description (DRD) instrument and the Appendix A DRD suite (TDP, MBx, CDMP, CSA, CR, FCA/PCA, SDT, EMDAL, REF, MRI); the Data Type 1-5 control scale; SOW/RFP/Cost-Volume contract language and data rights (FAR/DFARS, Table 3 license categories); the Requirements Exchange Format (REF/ReqIF, UUID schema) and Master Records Index; model-based data definition (MBSE, CAD/PMI, M&S credibility, BOM, release-state mapping, PLM); digital data collaboration, the four owned architectures, and interoperability standards (MIL-STD-31000, STEP/ISO 10303, ASME Y14); the four MBE interoperability use cases; and MBE Plan development. Scope is the acquisition and contracting side of digital engineering. Does not reproduce ISO/STEP/ASME/MIL-STD/SAE standard text, and the companion NASA-HDBK-1009A carries the deeper digital-engineering practitioner detail this handbook defers to.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Abbruchbedingung für autonome Loops: So weit wie möglich selbständig weiterarbeiten UND einen Loop erst beenden, wenn belegt ist, dass keine autonom ausführbare Aufgabe mehr vorliegt. Der bloße Eindruck "nichts mehr zu tun" reicht NICHT — er löst eine vierstufige Prüfkette aus (think/decide, _CONTROL/_DECISIONS, Gardener/USMC, decision-avatar/BYUM), die zuerst neue Aufgaben GEWINNEN muss, bevor der Loop enden darf. Jeder Kettenschritt meldet found/empty/unavailable statt eines binären Ergebnisses — "exhausted" gilt nur, wenn ALLE Quellen tatsächlich befragbar waren; ist mindestens eine Quelle unavailable, meldet der Skill "blind" statt "exhausted" und behauptet nichts Ungeprüftes. Nutze diesen Skill bei /work-autonomous, /waafap, "arbeite autonom weiter bis nichts mehr zu tun ist", als Goal-Bedingung innerhalb eines /loop, oder wenn geprüft werden soll, ob wirklich keine autonome Arbeit mehr übrig ist, bevor ein Loop/eine Session beendet wird.
日本語の概要は準備中です。原文の説明を表示しています。
Reißverschluss-Verfahren (englisch: zipper merge) für sehr konfliktreiche Merges: Wenn zwei divergente Branches oder ein PR und sein Zielbranch BEIDE wertvolle, unvereinbar erscheinende Änderungen tragen, wird nicht pauschal eine Seite gewählt, sondern Abschnitt für Abschnitt verglichen, per Entscheidungstabelle (Nimm/Warum) die jeweils bessere Version übernommen, abschnittsweise committet und erst am Ende gepusht. Letzte Eskalationsstufe: Rebuild statt Merge — nur die Absicht/Funktionalität des Branches übernehmen und auf dem aktuellen Stand neu bauen. Nutzen bei: "Merge-Konflikt", "divergente Branches", "main vs. master", "konfliktreicher PR", "zipper merge", "Reißverschluss", "beide Seiten haben Recht", "PR ist zu alt zum Mergen".
日本語の概要は準備中です。原文の説明を表示しています。
Einmaliger Tasksolver+Writer+Maintainer-Durchlauf fuer den Projektordner, in dem die Session gerade sowieso gearbeitet hat (inkl. Unterordner) — kein systemweiter Sweep. Loest offene triviale/autonome Register-Punkte, aktualisiert Dokumentation auf den gemessenen Ist-Stand (im Projekt UND in der Root der Pipeline, in der das Projekt liegt) und raeumt Strays/Temp- Dateien nach dem Papierkorb-Prinzip weg. Nutze diesen Skill bei /tidy-up, "raeum das Projekt auf", "mach hier sauber bevor wir weitermachen", am Ende einer Arbeitssitzung an einem Projekt, oder als faellige autonome Aufgabe innerhalb von /work-autonomous + /goal.
日本語の概要は準備中です。原文の説明を表示しています。
Sweeps a SharePoint library listing (an export or a listing the agent can reach, with file name, link, review-date column and owner column) for documents past their review date and returns a dated DRAFT review sweep report (Overdue, Due soon, No review date, Summary) plus one ready-to-paste reminder per document owner for the user to send. Never changes metadata, sends a message or invents a document, date or owner. Use when the user asks to "find the documents past their review date", "run the review sweep on the policies library", "which documents are overdue for review", "audit the review dates in this library export" or "draft reminders to owners about stale documents". Do not use for duplicate, conflict and ownership checks across knowledge files, use knowledge-base-hygiene-review instead; for gaps in an engineering deliverables register, use master-document-register-check. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a document transmittal (header, one line per document with revision and purpose of issue, distribution with action required, blank acknowledgement block) from a document list and the project's transmittal template, with UNKNOWN for anything not stated and questions for document control. Never assigns a transmittal number, changes a revision or marks anything issued. Use when the user asks to "draft a transmittal for these documents", "fill in the issue sheet" or "prepare the document issue note". Do not use for checking a register or deliverables list, use master-document-register-check instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
日本語の概要は準備中です。原文の説明を表示しています。
Master software architect specializing in modern architecture
日本語の概要は準備中です。原文の説明を表示しています。