72 件 ・ 関連度順
概要と使いどころ
Writes Symfony PHP — DI container, bundles, Doctrine, Messenger, Security voters, console commands. For Laravel / Eloquent / Artisan use `laravel`. For framework-free PHP use `php-coder`.
日本語の概要は準備中です。原文の説明を表示しています。
Use for deep Symfony project analysis: kernel/bootstrap, container wiring, routing/request flow, Doctrine, security, Messenger, and Symfony-specific failure patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Writes Laravel PHP — Eloquent, Artisan controllers, FormRequests, jobs, events, policies, providers. For Symfony / Doctrine use `symfony-workflow`. For framework-free PHP use `php-coder`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding what earns a page — the page, action and info classes stated provider-neutrally, and the rule that a page without an owner, a runbook and a first diagnostic step is malformed.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Probabilistic Risk Assessment Procedures Guide (NASA/SP-2011-3421, 2nd ed.). Use for quantitative PRA of aerospace and safety-critical systems: the risk triplet and scenario logic stack (MLD, ESD, event trees, fault trees, minimal cut sets), Bayesian data collection and parameter estimation, aleatory/epistemic uncertainty modeling and common-cause failure (Alpha Factor, beta-factor, CCBE), human reliability analysis (THERP, CREAM, NARA, SPAR-H), context-based software risk (CSRM), physics-based and structural/phenomenological models (stress-strength, limit states, FORM/SORM, NASGRO, range safety), uncertainty propagation and importance measures (F-V, RAW, Birnbaum, DIM), and launch-abort modeling with worked PRA examples. This is the QUANTITATIVE engine beneath NASA's risk doctrine — for the qualitative RIDM/CRM decision framework use the nasa-risk pack. Thin on programme management, organisational risk governance, and non-aerospace regulatory contexts; aerospace-focused and anchored to the 2011 second edition.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. Use when working with Eloquent, Doctrine, Composer, Psalm, ReactPHP, or any PHP API development.
日本語の概要は準備中です。原文の説明を表示しています。
Trial protocol for teaching AI Matrx an expert's knowledge until the platform breaks, fixing it. Use when asked to run an expertise trial, distil a person/creator/recent video into a Masterwork, or test the capture product. NOT for a known-missing feature (use build-sub-feature).
日本語の概要は準備中です。原文の説明を表示しています。
Doctrine for fixing TypeScript errors against generated types (database.types.ts, api-types.ts). Use when fixing tsc or type-check failures or a type-errors batch, writing supabase .rpc()/.from() calls or DB shape guards, errors mention Json/unknown/Database, or you are tempted to cast or suppress.
日本語の概要は準備中です。原文の説明を表示しています。
Real tests around a big code change: written first, proven to fail on a planted break, run by a fresh agent in the live product before and after. Use when told to use safety-net, or before a change wide enough that one agent cannot see every way it breaks. NOT for one test (forcing-function-tests).
日本語の概要は準備中です。原文の説明を表示しています。
Audit-and-fix method for one user setting area across every repo. Use when a setting seems ignored, duplicated or confusing, on 'audit the X settings' or 'why doesn't my X setting apply', or as a lane of the settings sweep. NOT for adding a new setting (use build-sub-feature).
日本語の概要は準備中です。原文の説明を表示しています。
Retired pointer for Next.js SSR doctrine. Use when something references nextjs-ssr-architecture; read the ssr-zero-layout-shift skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Collapsing every copy of one kind of thing (tables, UIs, utilities, hooks, APIs, renderers) into a single canonical one. Use when asked to unify, merge, converge, or 'make one X used everywhere', or before migrating callers onto a new canonical piece. NOT for docs (use docs).
日本語の概要は準備中です。原文の説明を表示しています。
Pre-commitment attack on a plan by an agent that did not write it. Use when presenting a feature-deep-dive plan, assigning vision-to-fleet briefs, moving a register to build mode, ratifying a scope list, or coding a new contract or table. NOT for built work or DONE reports (use subagent-dispatch).
日本語の概要は準備中です。原文の説明を表示しています。
SSR-first Next.js App Router doctrine with zero layout shift. Use when creating a page or data-fetching UI, fixing CLS, layout shift, or hydration mismatches, placing 'use client', Suspense, or skeleton boundaries, awaiting params/searchParams/cookies, adding server-only guards or cache() dedup, or choosing Route Handlers vs Server Actions.
日本語の概要は準備中です。原文の説明を表示しています。
Doctrine for all Supabase realtime: postgres_changes, broadcast, presence. Use before writing a `.channel(`/useChannel subscription, echo suppression, reconnect logic, an autosave loop beside realtime, or replacing polling with live updates, or when the tab freezes, messages duplicate, or a subscription delivers nothing.
日本語の概要は準備中です。原文の説明を表示しています。
The watch-fix-rerun method for making an existing platform agent or automated process efficient and correct: baseline its ledger, run one unit yourself, fix the class behind every wasted call, rerun, record. Use when asked to improve, optimize, watch, or 'make efficient' an agent, a sandbox session, a sync job, or any recurring automated process.
日本語の概要は準備中です。原文の説明を表示しています。
The interview primitive for putting open decisions to an owner. Use on 'grill me', 'stress-test this', or 'what do you need from me before you build this', and whenever a plan, scope, spec, vision, or question ledger needs owner rulings. NOT for steps only a human can perform (use a guided session).
日本語の概要は準備中です。原文の説明を表示しています。
The bar every automated test or guard must clear: green only when the real system works. Use when writing, fixing, or reviewing a test, mock, stub, fixture, snapshot, or self-test; adding a regression test for a bug; or about to call work done because tests pass.
日本語の概要は準備中です。原文の説明を表示しています。
The doctrine for turning a vision into a finished, verified, deployed system with near-zero owner involvement. Use when launching, coordinating, resuming, or working any large build, module, campaign, or multi-agent project, or when writing its launch prompt.
日本語の概要は準備中です。原文の説明を表示しています。
[00] TnR ABSOLUTE RIGOR — Systemic Verification Doctrine. Forced cognitive exertion for high-stakes investigations. Mandates absolute deconstruction, mathematical proof chains, and ≥95% derived certainty. Zero-tolerance for heuristics or sentiment-based reasoning. Shortcuts are defined as intentional hallucinations.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim L2 pack. Bundles: All six L1 packs. Primary framework: Behavioral Moat Framing Doctrine (ADR-007).
日本語の概要は準備中です。原文の説明を表示しています。
Verify every visual-evidence artifact (screenshot/GIF/recording) attached to a PR carries a provenance manifest binding it to real daemon-backed truth — daemon port, run id, transcript head hash, agent node id, commit, and an honest real/fixture/mock source label — and that operator-control-panel PRs cover the required set of proof states. Use when gating a PR's proof artifacts before merge, auditing whether a "LIVE" visual claim is backed by a real daemon run versus a reused or fixture-backed mock, or defining the required state-coverage set for a control-panel change. NOT for the capture technique itself — headless Playwright, `screencapture -x -l`, non-interruptive capture (use port-daddy-agent-skill's visual-evidence doctrine), designing the receipt body schema an artifact attaches to (use agent-work-receipt-designer), or the broader dogfood/Potemkin product-quality bar (use multi-agent-authoring-product-bar).
日本語の概要は準備中です。原文の説明を表示しています。