'nle' 검색 결과

Manages AI model retention and machine unlearning requirements. Covers training data deletion verification, model versioning for compliance, machine unlearning techniques (SISA, gradient-based), and retraining triggers. Keywords: AI retention, machine unlearning, model versioning, training data deletion, retraining, storage limitation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan, review, and retire feature flags, switches that control feature availability. Includes tools to identify aging flags, generate phased release schedules, and check that documentation records ownership and emergency shutdown procedures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan a phased release for a new feature
• Identify old flags for cleanup
• Audit emergency shutdown documentation

Run individual or grouped traffic scenarios in CARLA, a driving simulator, and collect pass/fail reports or recordings. Check which scenarios match the current branch and map, and investigate runs that fail or show no movement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a CARLA setup with a lead-vehicle scenario
• Run all control-loss scenarios and collect pass/fail results
• Find scenarios available on the current map

Plan substantial DeepChat changes with a written design proposal and a clear implementation path. Record decisions, track progress, review the completed change, and select focused validation for features, complex bugs, or architecture updates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a substantial new feature
• Recording the diagnosis and fix for a complex bug
• Documenting architecture changes or migrations

Define a dataset's metadata profile — infer a Frictionless Table Schema from its data, add Data Package metadata (license, sources, keywords), and write it into datasets.json so the showcase renders a typed field table. Extend or customize via the L0-L3 profile ladder. Use when a registered dataset needs field types, constraints, or catalog metadata before publishing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Für Aktenlektüre: Fristennotiz und nächster Schritt: prüft Frist, Form, Zuständigkeit und Eilbedarf; Ergebnis: Fristen- und Risikoampel.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

独立开发者与微型 SaaS — 单人或极小团队 (≤3 人) 构建可持续订阅收入的软件产品商业, 有别于自由职业/咨询、企业级 SaaS 和开源维护: (a) 产品发现与验证 (自己的痒 vs 市场优先 Nugent/Walling; 着陆页冒烟测试; 先接 Stripe 再写代码; JTBD 访谈适配独立开发者场景; Reddit/HN/X/社区痛点挖掘; Mom Test 验证框架; 公开构建作为验证机制); (b) 独立开发者技术架构 (无聊技术论 McKinley; 单体优先; serverless vs VPS 在 ≤$100/月预算下的取舍; Rails/Django/Laravel/Next.js 等框架的出货速度选型; 托管服务优先于自建; Supabase/PlanetScale/Neon 数据库即服务; Clerk/Auth0 认证即服务; Stripe/Paddle/LemonSqueezy 支付; Vercel/Fly.io/Railway 部署; AI 辅助编码 Cursor/Copilot 作为力量倍增器); (c) 无营销团队的分发与增长 (SEO 作为微型 SaaS 护城河; Product Hunt 发布; AppSumo 终身授权利弊; 冷邮件; Twitter/X 公开构建; IndieHackers 社区分发; 集成市场 Shopify/WordPress/Zapier/Slack 应用目录; 联盟计划; 一人内容营销); (d) 定价与变现 (SaaS 定价心理学; freemium vs 免费试用 vs 纯付费; 按席位 vs 按用量 vs 固定费率; 年付折扣; 老用户保价; 微型 SaaS 流失率控制; MRR/ARR/LTV/CAC 在微型规模的含义; $10K MRR 里程碑心理学); (e) 独立创始人心智模型与生活设计 (default alive vs default dead Graham; 拉面盈利 Levels; 生活方式生意 vs 增长生意的光谱; 独立开发者倦怠预防; 时间管理与上下文切换成本; 地理套利与远程优先; 一次构建反复销售的资产思维; 社区作为支持网络 IndieHackers/WIP/MicroConf); (f) 法务与运营基础 (公司注册地选择 LLC/Ltd/GmbH 税效; Stripe Atlas vs Firstbase vs 本地律师; 服务条款与隐私政策; GDPR/CCPA 低成本合规; 知识产权基础; 首次雇人的承包商 vs 员工选择; 独立开发者会计 SaaS — Xero/QuickBooks; 多辖区税务义务)。中国独立开发者生态: 出海作为主导策略 (从中国构建面向全球市场的产品以避开国内竞争/监管); 即刻/V2EX/少数派作为社区枢纽; 微信小程序作为替代分发; 小报童/爱发电作为中文市场变现; 人民币定价心理学; 支付宝/微信支付集成; ICP 备案要求; 中国区 App Store 审核差异; 独立开发者周刊。诚实处理: 生存偏差 (每一个 Pieter Levels 背后是数千个从未达到 $1K MRR 的人), AI 对微型 SaaS 生态位的颠覆 (wrapper 产品脆弱), 独自构建的孤独与心理健康成本, 公开构建的表演性质 vs 真正透明, AppSumo 终身授权上瘾毁坏单位经济, 样板代码销售的伦理边界。不含: 企业级 SaaS (不同 GTM/销售/融资模型), 不含: 自由职业/咨询 (用时间换钱非建资产), 不含: 开源维护 (不同可持续性模型), 不含: 风投支持的创业 (不同增长期望), 不含: 无代码/低代码平台构建 (相邻但不同受众), 不含: 内容创作作为主业。 (Independent Developer and Micro-SaaS — the craft of single-person or tiny-team (≤3 people) software product businesses that generate sustainable recurring revenue without venture capital, distinct from freelancing/consulting, enterprise SaaS, and open-source maintainership: (a) product discovery and validation (scratching your own itch vs market-first Nugent/Walling; landing page smoke tests; Stripe checkout before code; Jobs-to-Be-Done interview adapted to solo context; Reddit/HN/X/community pain-point mining; idea validation frameworks Fitzpatrick Mom Test; build-in-public as validation mechanism); (b) technical architecture for solo operators (boring technology thesis Mckinley; monolith-first; serverless vs VPS tradeoffs for ≤$100/mo infra; framework selection for shipping speed — Rails/Django/Laravel/Next.js/Remix/SvelteKit; managed services over self-hosted whenever possible; database-as-a-service Supabase/PlanetScale/Neon/Turso; auth-as-a-service Clerk/Auth0/Supabase Auth; payment integration Stripe/Paddle/LemonSqueezy; deployment Vercel/Fly.io/Railway/Render; monorepo vs polyrepo for solo; AI-assisted coding Cursor/Copilot as force multiplier); (c) distribution and growth without a marketing team (SEO as moat for micro-SaaS Ahrefs-style content marketing on 1-person budget; Product Hunt launches; AppSumo lifetime deals tradeoffs; cold email outreach; Twitter/X building in public; IndieHackers community distribution; integration marketplaces Shopify/WordPress/Zapier/Slack app directories as channels; affiliate programs; content marketing at scale-of-one); (d) pricing and monetization (SaaS pricing psychology Patel/Campbell; freemium vs free trial vs paid-only; per-seat vs usage-based vs flat-rate; annual discount strategies; grandfathering existing customers; churn reduction for micro-SaaS — Baremetrics/ProfitWell/ChartMogul analytics; MRR/ARR/LTV/CAC at micro scale; the $10K MRR milestone psychology); (e) solo founder mental model and lifestyle design (default alive vs default dead Graham; ramen profitability Levels; lifestyle business vs growth business spectrum; burnout prevention for solo operators — no team to delegate to; time management and context-switching costs; geographic arbitrage and remote-first; the 'build once sell twice' asset mindset; community as support network IndieHackers/WIP/MicroConf); (f) legal and operational basics (incorporation LLC/Ltd/Gm

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Mathematical verification for physical calculations: unit tracking algebra (exponent maps), PhysicalQuantity pattern for compound units, SI/Imperial mixed-unit handling, Buckingham pi theorem for dimensionless groups, and common engineering dimensionless numbers. Activates for unit verification, dimensional consistency checks, scaling analysis, and calculation validation across all infrastructure domains.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use Tokenless for large files and noisy tool outputs before they enter context. Must be used when commands, Read output, diffs, logs, or search results are large.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Erstellt oder überarbeitet einen Skill FÜR DIESES ÖKOSYSTEM: delegiert die generische Interview-/Entwurfs-/Eval-Schleife an das offizielle skill-creator-Plugin (Anthropic, Apache-2.0), setzt aber zusätzlich die ellmos-Anforderungen durch, die das offizielle Plugin nicht kennt — Haus-Frontmatter (9 Felder), Kategorie/Sichtbarkeits-Regeln, anbieter-/nutzer-/ellmos-neutrale aber ellmos-sensitive Erkennung via grounding-seed, mitgelieferte config.json (inkl. Lernvertrag) + connections.json, Anbieter-/Vendor-Bewusstsein (State-of-the-Art-Alternativen inkl. eigener ellmos-Komponenten vorschlagen), einen Selbstaktualisierungs-Abschnitt UND einen wiederverwendbaren Lern-/Abdeckungs-Dateisatz (user-usecases.json, usecase-gaps.json, known-providers-and-abilities.json, gap-closing-analysis.json — an skill-creators evals.json und A2A/AgentSkill angelehnt, kein Parallelstandard). IMMER nutzen, wenn ein NEUER Skill für dieses System entstehen oder ein bestehender auf ellmos-Konformität nachgerüstet werden soll — auch bei "erstelle einen Skill", "bau mir einen Skill für X", "skill-creator nutzen", "neuen Skill anlegen", "diesen Skill ellmos-konform machen", "Lernvertrag/Verhaltenscodex für einen Skill anlegen", "Usecase-Abdeckung eines Skills prüfen". Für reines Skill-FINDEN/ROUTEN stattdessen skill-finder, für Landschafts-Audit skill-explorer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Meta-/Umbrella-Skill für die Familie „Projekt-/Pipeline-Aufbau & -Umbau". Kennt alle Skills für Anlegen, Aufnehmen, Umbauen und Analysieren von Projekten und Pipelines und leitet zum passenden weiter. Nutze diesen Skill, wenn unklar ist, ob etwas neu angelegt (Greenfield) oder umgebaut (Bestand) werden soll bzw. ob es um ein einzelnes Projekt oder eine ganze Pipeline geht. Auch auslösen bei „neues Projekt/Pipeline anlegen", „bestehendes umbauen", „Projekt aufnehmen", „Ordnerstruktur renovieren", „welcher Bootstrapper passt".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Austrian Impressum (legal notice) requirements for all company types. Covers ECG, UGB, GewO, MedienG, and Offenlegungspflicht for public media. Use when working with impressum, legal notice, imprint, austria, österreich, ECG, mediengesetz, offenlegung.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

OpenClaw에 전달한 자연어 요청을 Claude Code 같은 외부 코딩 에이전트로 연결합니다. ACP나 acpx로 작업을 시작하거나 이어가며 대화 맥락을 유지합니다.

• 스레드에서 Claude Code 시작
• 외부 에이전트의 기존 작업 계속
• acpx로 직접 지시 전달

모호한 기능 요청이나 영향이 큰 변경의 범위·전제·위험을 정리합니다. 기대 동작과 검증 방법을 명시한 인수 기준이나 인계 자료로 만듭니다.

• 모호한 기능 요청을 정리합니다
• 인증 변경과 데이터 이전 기준을 만듭니다
• 다른 에이전트나 팀에 구현을 인계합니다

Implement and review GSAP animations in Vue, Nuxt, Svelte, and SvelteKit. It explains when to start animations, how to limit element selection to one component, and how to clean up when that component is removed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding GSAP animations to Vue or Svelte
• Reviewing animation cleanup when components are removed
• Keeping animations scoped to one component

Build GSAP animations in React or Next.js with guidance on useGSAP, element references, and component boundaries. It covers cleanup when components update or disappear, plus keeping animation code out of server rendering.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding GSAP animations to React components
• Cleaning up animations when components are removed
• Keeping animations within the intended component

Inspect and test web pages through a browser automation command-line tool. Navigate, click, enter text, capture screenshots, and extract page details, with a focus on checking local OpenDesign previews and reviewing web app quality.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking local OpenDesign previews
• Testing clicks and text entry in web apps
• Capturing page or element screenshots

Coordinate multiple Orca workers by assigning tasks, exchanging threaded messages, and waiting for results or escalations. Use task dependency graphs and decision gates to supervise work that needs ongoing coordination across agents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Splitting work across multiple Orca workers
• Coordinating tasks with dependencies
• Waiting for worker results or escalations

Find recent earthquakes by date and minimum magnitude, then review their location, depth, and USGS source. World Monitor also provides a concern score combining magnitude, depth, and proximity to known nuclear test sites.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review recent earthquakes above a chosen magnitude
• Check earthquake locations and depths within a date range
• Inspect events near known nuclear test sites

Read local PDFs, scanned images, and Office documents for summaries, questions, and citations. Extract readable content, search indexed documents, and work through long files in sections while retaining precise page and block references.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reading scanned PDFs with optical character recognition
• Summarizing Office documents and answering questions
• Reading long documents a few pages at a time

Create a starter structure for a custom AI agent harness, the setup that supports agent execution. Choose a template and host, preview the plan, then explicitly confirm generation in a new directory outside the current project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a coding agent harness from a template
• Preparing starter setups for different agent hosts
• Previewing generated files' destination before writing

Review decorative images and icons to prevent unnecessary screen reader announcements. Check empty alt text, aria-hidden, and relevant keyboard behavior, then suggest fixes for concrete accessibility issues without flagging decorative assets solely because they exist.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking decorative images for unnecessary announcements
• Reviewing accessibility of SVGs and icons
• Checking shared decorative component patterns

Publishes oh-my-opencode through GitHub Actions, then checks package versions and release artifacts. Covers related packages, user-facing release summaries, and Discord announcements, reporting failures without starting code repairs during the release process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Publishing a patch, minor, or major release
• Releasing a specific prerelease version
• Checking related packages and platform binaries

Integrate GSAP animations into React and Next.js components using useGSAP, element references, and scoped selectors. The skill guides dependency updates, event callbacks, and cleanup when components unmount, while keeping animation code out of server rendering.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding GSAP animations to React components
• Restricting animations to elements within one component
• Cleaning up animations when components unmount