「spr」の検索結果

Für Chronologie Strafverfahren: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Chronologie mit Beleg- und Widerspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Schaltet sich ein, wenn in Aktenaufbereiter Strafrecht ein juristisches Arbeitsprodukt tragfähig begründet werden muss; verbindet konkrete Aktenfundstellen mit Tatbestandsmerkmal, Beweislast, stärkster Gegenposition und Rechtsfolge.

日本語の概要は準備中です。原文の説明を表示しています。

Für Beziehungen: Zahlen, Schwellenwerte und Berechnung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Chronologie mit Beleg- und Widerspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Für Aktenaufbereiter: Erstprüfung, Rollenklärung und Mandatsziel: routet Rolle, Frist, Unterlagen und Fachschritt; Ergebnis: Tatbestands- oder Anspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Für Chronologie: Compliance-Dokumentation und Aktenvermerk: ordnet Akte, Belege und Lücken; Ergebnis: Chronologie mit Beleg- und Widerspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Für Norm Live Check Gesetze im Internet: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Tatbestands- oder Anspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Für Non Solicitation: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Tatbestands- oder Anspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Schaltet sich ein, wenn in Agb Recht Prüfer ein juristisches Arbeitsprodukt tragfähig begründet werden muss; verbindet konkrete Aktenfundstellen mit Tatbestandsmerkmal, Beweislast, stärkster Gegenposition und Rechtsfolge.

日本語の概要は準備中です。原文の説明を表示しています。

Bestimmt nach Nichteinbeziehung oder Unwirksamkeit einer AGB-Klausel den verbleibenden Vertrag. Prüft Teilbarkeit, salvatorische Regelung und Lückenfüllung; ersetzt weder Anspruchsberechnung noch Rückabwicklung oder Prozessführung.

日本語の概要は準備中です。原文の説明を表示しています。

Für AGB Prüfung Kaltstart: routet Rolle, Frist, Unterlagen und Fachschritt; Ergebnis: Tatbestands- oder Anspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Für AGB und 242 BGB Eingriffsnorm: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Tatbestands- oder Anspruchsmatrix.

日本語の概要は準備中です。原文の説明を表示しています。

Writing screenplays in the style of Ozu Yasujiro and Noda Kogo (小津安二郎・野田高梧) — distilled from six complete screenplays (晚春 Late Spring, 麦秋 Early Summer, 东京物语 Tokyo Story, 浮草 Floating Weeds, 秋日和 Late Autumn, 秋刀鱼之味 An Autumn Afternoon). Covers the "family member leaves" master plot, off-screen events / on-screen reactions, lie-driven plots, minimal-syllable confessions, go-between characters, faceless suitors, pillow-shot scene breaks, echoing objects, mirror characters, children's subplots as metaphor, displaced quarrels, the single-monologue rule, diminishing endings, Ozu's script format and stage-direction vocabulary. Use when the user wants to write a quiet family drama, a 小津风 / 侘寂 / 日常系 script, a story about marrying off a daughter, aging parents, or wants dialogue that says less and means more.

日本語の概要は準備中です。原文の説明を表示しています。

From an idea to a sellable series design; series engine / franchise, story pattern, character webs that keep generating conflict, pilot types, and the documents that sell them (剧集引擎/franchise/故事模式/人物网/试播集类型/剧集圣经/跳板/提案). Merged from Rabkin's four-element franchise and story landmines, Landau's tacit contract and pitch recipe, Oberg's series types and bible specs, Douglas's franchise-plus-springboard and bible tiers, Goldberg & Rabkin's 100-episode test, Blum's concept/presentation/bible ladder, Miller's ten-component treatment, Calvisi's Compelling Crisis, Smith's series format, plus engines read off Sopranos, Fleabag and Succession. Use when turning an idea into a series, testing whether a premise has legs, choosing premise vs typical-episode pilot, designing a sustainable character web, writing a logline, pitch document, bible or treatment, picking a series type, adapting IP into a series, or diagnosing a project that feels "more like a movie than a series".

日本語の概要は準備中です。原文の説明を表示しています。

Add a Jev-powered decision and release gate after an office assistant generates a report, proposal, spreadsheet, document, or slide deck. Use for claim-to-evidence checks, narrow requirement decisions, risk triage, and human-review routing; do not use it to generate the deliverable or claim that Jev browsed or verified a URL.

日本語の概要は準備中です。原文の説明を表示しています。

Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.

日本語の概要は準備中です。原文の説明を表示しています。

Create or assess an evidence-grounded, falsifiable outcome hypothesis: a testable prediction of what measurable business result will change, for whom, by when, and how leading and lagging indicators will prove or disprove it. Use when framing measurable outcomes, turning an MVP, POC, feature, or technical initiative into a beneficiary result, defining targets and indicators, or judging whether evidence is strong enough to invest. Also applies to business outcome hypotheses, value hypotheses, and outcome statements.

日本語の概要は準備中です。原文の説明を表示しています。

Read-only backlog planning for Azure DevOps, GitHub, and Jira. Use to discover, triage, sprint-plan, or resume without mutating a tracker.

日本語の概要は準備中です。原文の説明を表示しています。

Routes any game-development request to the right specialized skill(s): it detects the engine (Godot, Unity, Unreal, Bevy, Phaser, PixiJS, three.js, LÖVE, pygame, Roblox) and the task, then reads the chosen skill before acting. Use to make a game or to decide which skill applies — for players, levels, enemies, shaders, art direction, sprites, tiles, textures, 3D assets, UI/UX, cameras, game feel, physics, input, audio, saving, multiplayer, AI, dialogue, procedural generation, or performance, for genres (platformer, roguelike, RPG, FPS, tower-defense, card game, visual novel, survival-crafting, puzzle), and for shipping (game jam, Steam, itch). Start here when unsure which gamedev skill to use.

日本語の概要は準備中です。原文の説明を表示しています。

Use Phaser 4 Arcade Physics: enable the world, give sprites bodies, set velocity/acceleration/gravity, and resolve collisions with colliders, overlaps, groups, and world bounds. Use when a Phaser game needs movement or collisions — when the user mentions Arcade Physics, this.physics, setVelocity, collider, overlap, gravity, onFloor, or a platformer/top-down controller. For game config, scenes, and the loader use phaser-core.

日本語の概要は準備中です。原文の説明を表示しています。

Build a first-person shooter: move+mouse-look controller, hitscan or projectile shooting, weapons, health, and enemy AI. Use for an FPS, or tuning aim feel, time-to-kill, recoil, or spread.

日本語の概要は準備中です。原文の説明を表示しています。

Animate in Godot 4.7 three ways: AnimationPlayer for keyframed clips (incl. call and signal tracks), AnimationTree with state machines and blend spaces for character animation, and Tween for short procedural/UI tweens via create_tween(). Use when working with AnimationPlayer/AnimationTree nodes in a .tscn, blending character states, sprite-sheet animation, or code-driven Tweens.

日本語の概要は準備中です。原文の説明を表示しています。

Plan, generate, source, normalize, and validate cohesive visual game assets. Use for art direction, style bibles, sprites, tilesets, backgrounds, UI art, icons, textures, concept art, or 3D asset briefs.

日本語の概要は準備中です。原文の説明を表示しています。

Routes docs: Word/PDF/PPTX/saved HTML→Markdown; MD/Word→PDF; create Word; PDF HTML/translate; Excel/xlsm/macOS; photo/signed scans; Mermaid; DOCX review; post-change docs. Reads one bundled Daymade specialist. New slide decks use deck-creator when installed; generic PDF reading/editing and spreadsheet analysis stay with their own Skills. Retired ppt-creator stays manual-only.

日本語の概要は準備中です。原文の説明を表示しています。

Consolidates redundant documentation while preserving all valuable content; keeps a doc set truthful after things change. Modes: (1) POST-CHANGE GOVERNANCE — when code, scripts, config, env vars, ports, paths, deployment, auth, tests, or a documented procedure changed; also "which docs are now wrong", "check docs for inconsistencies", "过时的命令/路径", "文档同步". Use it even when the user mentions only the change and never the docs — updating them is part of the change, not optional cleanup. (2) CONSOLIDATION — "clean up docs", "documentation bloat", "reduce documentation sprawl", "consolidate documentation", "too many doc files", "merge redundant docs", "merge these docs", "文档太多/太乱", multiple files covering the same topic, or documentation exceeding 500 lines across multiple files on similar topics. Finds stale copies of a fact changed in only one place, values that should never have been persisted (counts, totals, "N items", restated summaries), rival definitions that drift apart, and orphaned cross-references.

日本語の概要は準備中です。原文の説明を表示しています。