Results for “notes”

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.

The English summary is being prepared. Showing the original description.

Knowledge base from NASA-STD-8719.14C (Process for Limiting Orbital Debris). Use for orbital-debris assessment planning, mission-related debris limits, explosion/passivation and collision risk, postmission disposal options, reentry casualty risk, and ODAR/EOMP governance. Covers STD-8719.14C (Approved 2021-11-05) synthesized notes only; does not replace NPR 8715.6 delivery timing, NASA-HDBK-8719.14 environment/modeling depth, or program-specific OSMA waivers.

The English summary is being prepared. Showing the original description.

Knowledge base from NASA-STD-7009B (Standard for Models and Simulations) with implementation depth from NASA-HDBK-7009B. Use for M&S criticality and programmatics, development evidence and capability assessment, verification/validation domains, uncertainty and sensitivity, use-phase results assessment, risk-informed decision reporting, and handbook life-cycle products. Covers STD-7009B (2024-03-05) + HDBK-7009B (2026-02-03) synthesized notes only; does not replace program-specific TA direction, NPR 7150.2 software requirements detail, or full PRA methodology.

The English summary is being prepared. Showing the original description.

Knowledge base from IS-GPS-200 Rev N (NAVSTAR GPS Space Segment / Navigation User Segment Interfaces). Use as a worked ICD/IS exemplar: what an interface specification is, DIST-A and IRN/CCB change control, interface definition vs identification, composite-signal criteria patterns, NAV data as payload families, and time/definition hygiene. Covers Rev N synthesized notes only; does not transcribe Apps II–IV bit fields or PRN/Gold-code tables, and does not replace faa-std-025 preparation rules.

The English summary is being prepared. Showing the original description.

Erfasst, ordnet und verdichtet bereitgestellte Notizen ohne Bindung an einen Speicherort oder eine Notiz-App.

The English summary is being prepared. Showing the original description.

Analyzes changes since last release and drafts them directly into the project's CHANGELOG.md. Use when users requests 'update the changelog' or 'prepare changelog release notes'

The English summary is being prepared. Showing the original description.

方針変更やキャンペーン再開時に、短期の判断・仮説をcapture / recall / triageする。長期記憶や日記には使わない。

The English summary is being prepared. Showing the original description.

実験やキャンペーンで次の判断を変える短期メモを capture / recall / triage する。方針変更やキャンペーン再開時に使い、単なる進捗・日記・過去経緯の検索には使わない。長期記憶は /ai-ltm、感想は /ai-diary。

The English summary is being prepared. Showing the original description.

Operational guide for integrating the NV oOS Complete purchase flow (vendor checkout API client) into standalone WordPress plugins — docs-hub 0.5.3 (stack added in PR #6963, shipped 0.5.2 → 0.5.3) and nvoos-content-graph 1.0.10 (live). Covers the vendor API contract (session/verify/health, nvoos-oos-complete product, 424/502 error passthrough), the five-class client stack (config, vendor client, license store, installer, REST controller), the purchase-modal JS/CSS port recipe (class-prefix rename, keep-the-JS-identical trick), wp.org commerce compliance (External Services disclosure, WPORG-REVIEW-COMMERCE-NOTES.md, js.stripe.com service exception), and the checkout test conventions (direct controller calls, pi_ fixture rules, zero-HTTP assertions). Use when adding the Get NV oOS Complete upsell/checkout to a plugin, porting the commerce stack to a new standalone plugin, extending the purchase flow, or debugging a checkout integration.

The English summary is being prepared. Showing the original description.

Manage encrypted vault storage for sensitive information — passwords, secure notes, payment cards, digital identities, and folder organization. Use when storing, retrieving, or organizing credentials, managing secrets, or working with encrypted data.

The English summary is being prepared. Showing the original description.

Automate recruiting and hiring workflows in Ashby -- manage candidates, jobs, applications, interviews, and notes through natural language commands.

The English summary is being prepared. Showing the original description.

Automate Attio CRM operations -- search records, query contacts and companies with advanced filters, manage notes, list attributes, and navigate your relationship data -- using natural language throug

The English summary is being prepared. Showing the original description.

Generate user-facing App Store release notes from git history since the last tag.

The English summary is being prepared. Showing the original description.

Use when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话

The English summary is being prepared. Showing the original description.

Use when the user asks to "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", or "is this update worth a relaunch"; produces a T+1→T+30 momentum plan — a launch-moment calendar (milestone / shipped-loop / badge moments only), announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only), a relaunch legitimacy call, spike-to-owned handoff briefs, and the next Tier-1 moment with launch-stacking spacing. Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner. 抗第二周断崖/changelog-as-GTM/relaunch/下一发布时刻

The English summary is being prepared. Showing the original description.

Use when the user asks to "map what our buyers believe", "capture the objections we keep hearing", or "find the switching forces that move the beachhead"; produces a belief map of the beachhead — held beliefs and mental models, the recurring objections and their reframes, and the JTBD four forces (push of the problem, pull of the new, anxiety of switching, habit of the present) — each item sourced from interviews or win-loss notes (User-provided) and labeled Measured / User-provided / Estimated, with any unverified quote or comparative claim marked "[needs source]" and routed to the claims candidates, never adjudicated here. Not for demographic or persona profiling — use audience-mapper; not for the positioning canvas — use positioning-truth-tracer. 受众信念/异议地图/切换四力/流失语言

The English summary is being prepared. Showing the original description.

Generate user-facing App Store release notes from git history since the last tag.

The English summary is being prepared. Showing the original description.

Turn post-publish notes into pipeline improvements. Use after a video ships, or when the user says "retro", "here is my feedback", or "wrap up this project".

The English summary is being prepared. Showing the original description.

Prepares mobile releases across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including separate Android/iOS artifacts from a shared KMP revision. Covers versions, signing, symbols, store readiness, rollout, release notes and CI/CD. Use for release audits, store submission, build pipelines or rollout planning.

The English summary is being prepared. Showing the original description.

Create a pull request from the current branch for pitwall, into the right base for this repo's two-tier flow — feature branches (`dev-<feature>`) target `dev`, and `dev` itself targets `master` as a release PR. Analyzes the new commits, drafts a PR title and a Summary/Test-plan body matching this repo's existing PR style, previews it for approval, then creates it via the `gh` CLI. A release PR into `master` additionally settles the version and writes the release notes file before the tag exists. Use whenever the user says "pr", "pull request", "open a pr", "create pr", "ship it", "merge into dev", "merge into master", "cut a release", "raise a pr", or anything about getting the current branch merged — even if they don't say the word "skill".

The English summary is being prepared. Showing the original description.

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

The English summary is being prepared. Showing the original description.

Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

Cuts the next minor release of Prisma Composer: bumps the root package.json version, propagates it to every workspace package in lockstep, and opens a PR titled "chore(release): v<next-version>". When a maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under dist-tag `latest`, plus a matching GitHub Release with auto-generated notes. Use when a maintainer asks to "cut the next minor", "bump to the next version", "open a release PR", or "prepare a publish PR".

The English summary is being prepared. Showing the original description.

Decide where to save any piece of information — monday.com, local file, daily notes, or MEMORY.md. Use this skill before saving anything to ensure the right destination. Prevents local clutter and ensures the owner can access all relevant content in monday.com.

The English summary is being prepared. Showing the original description.