3.9천건 · 관련도순
Generate technical SEO assets: sitemap.xml (with sitemap index for large sites), robots.txt, per-entity schema markup (BreadcrumbList, AggregateRating), configurable internal link graph, and hreflang scaffold. Use when the user wants to add or update sitemap, robots, structured data, internal linking, or multilingual hreflang tags.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update TPP for engineer handoff when context is running low. Use when ending a session, running out of context, or switching to a different task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review or update stable, canonical, any-human, PMF, and adoption claims using adoption/canonicity governance packets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load when the user asks to create, find, update, assign, label, prioritize, transition, or organize ISLAMU Event issues/cycles/modules in Plane via MCP; not for local todo lists or implementation-plan markdown.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load when asked to create, update, re-baseline, or continue a repository-grounded implementation/technical/refactor plan and its `dev/active/<task>` plan/context/tasks files; not for a product PRD, informal advice, or reviewing an already-written plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using `asc apps wall submit`. Use when the user says "submit to wall of apps", "add my app to the wall", or "wall-of-apps".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Crystallize shared understanding into a reviewable spec, or update an existing one. Use when the problem needs a written specification, when assumptions or decisions have changed, or when the user says 'write a spec'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a feature or project area into frontier items and update `memory/PLAN.md`. Re-run to retire completed work, reorder priorities, or add new items.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Advisory checkpoint for deciding whether planning-document edits should be split into a separate planning branch/PR. Use only when the user explicitly asks where to commit `memory/SPEC.md` or `memory/PLAN.md` changes, mentions planning-doc merge conflicts, asks for a planning PR, or instructs you to prepare/submit one. Do not trigger for ordinary ln-* planning edits, one-line status updates, or routine canonical reconciliation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updated Sep 14, 2026 Python ProjectNeura / MIPCandy Sponsor Star 294 Code Issues Pull requests Build
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 GAO Cost Estimating and Assessment Guide (GAO-20-195G). Use for program cost estimating: the four characteristics of a reliable estimate (comprehensive, well documented, accurate, credible) and the 18 best practices; the 12-step cost estimating process (purpose, plan, technical baseline, WBS, ground rules and assumptions, data, point estimate, sensitivity, risk/uncertainty, document, present, update); estimating methods (analogy, parametric, engineering build-up, learning curves); Monte Carlo risk/uncertainty analysis, confidence levels and contingency; auditing and validating an estimate against the characteristics; earned value management (EIA-748, BCWS/BCWP/ACWP, CPI/SPI/TCPI, EAC, PMB, IBR); and specialized techniques (software cost estimating, learning curves, Analysis of Alternatives, WBS templates, the Green Book internal-control framework). This is the cost-estimating companion to the GAO Schedule and Technology Readiness Assessment guides. Does not cover schedule estimating/risk in depth (see the GAO Schedule Assessment Guide), agency-specific cost models, or the full text of referenced standards (EIA-748, MIL-STD-881D, the Green Book) — these are named, not reproduced.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evolutionary file renaming with wrapper files. Enables renames without hard breaks — references are organically updated through usage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evolutionary file renaming with wrapper files, plus the terse MOVED-stub standard for whole folder/file moves. Enables renames without hard breaks — references are organically updated through usage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files, and registry links.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quietly reuse and improve verified coding lessons across agents. Use for a nontrivial debugging or implementation problem where an earlier solution could help, when a Blaze offer or receipt appears, or when the user asks to inspect, install, update, contribute to, or link Blaze. Check applicability, verify locally, and close the lookup with an honest outcome and contribution disposition without adding routine user-visible narration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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'
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate social media announcements for Discord, Twitter/X, Facebook, and LinkedIn from the latest changelog entry. Use when user asks to 'create release announcement' or 'create social posts' or share changelog updates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Derive or update the auto mode `autoMode.environment` block from the event corpus — which repos, hosts, buckets, and CLIs your work actually touches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operate Jira Cloud via its REST v3 API — issues, projects, sprints, boards, comments, transitions, JQL search. Use when the user wants to triage, bulk-update, report on, or otherwise interact with Jira programmatically without the MCP server installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage n8n workflow automation via its public REST API — list/get/create/update workflows, activate/deactivate, inspect execution history, retry/stop executions, manage credentials, tags, variables, users, and projects. Works with self-hosted n8n and n8n Cloud. Use when the user wants programmatic access to their n8n instance without the n8n MCP installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read and write Notion pages, databases, and blocks via the public REST API — query a database with filters, create/update pages, append block content, search the workspace. Use when the user wants an agent to interact with their Notion workspace (e.g., a tasks or docs database) without the MCP server installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
明示されたディレクトリ内の独立した git clone を確認し、clean な fast-forward だけを適用する。マーケットプレース・プラグイン・Skillのupstream取込み確認に使う。Skill本文の編集・作成は skill-creator または instruction-refactor を使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.