「dr」の検索結果

This skill should be used when the user asks to "create a template", "テンプレート作成", "書式を登録", "XLSXをテンプレート化", "テンプレート登録", "この書式を登録して", "テンプレートを追加", or wants to register a new court document template from an XLSX file.

This skill should be used when the user asks to "proofread", "校正", "誤字脱字チェック", "表記揺れ", "typo check", "文書チェック", "法律文書の確認", "この書面チェックして", "おかしいところない？", "文章確認して", "間違いがないか確認", "書面の確認", or wants to review a Japanese legal document for writing errors. Do NOT trigger for translation, summarization, or content generation requests.

This skill should be used when the user asks to "search a law", "法令検索", "条文を見せて", "法律を調べて", "○○法 第○条", "条文参照", "法令を確認", "何条に書いてある", or wants to look up Japanese law articles from the e-Gov API.

This skill should be used when the user asks to "calculate iryubun", "遺留分侵害額", "遺留分", "遺留分侵害額請求", "遺贈", "生前贈与の遺留分算入", or wants deterministic computation of reserved-portion infringement under 民法 1042-1048.

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

This skill should be used when the user asks to "recalculate debt", "利息制限法で引き直し", "引き直し計算", "過払金", "過払い金", "サラ金", "貸金業者との取引履歴から引き直し", or wants deterministic recalculation of loan transactions under the Interest Rate Restriction Act.

Full lifecycle expense reimbursement: single invoice intake and staging, batch aggregation to generate reimbursement drafts, approval workflow, ledger and dashboard. Trigger when user mentions reimbursement, expenses, invoices, travel reimbursement, approval workflow, or needs to organize / verify / approve expense records. Also applies when user needs to enter invoices, view reimbursement dashboards, ledgers, or compliance checks.

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

MUST USE whenever the user wants to automate a real desktop or sandbox - clicking, typing, scrolling, screenshotting, running an OS shell command, or handing a high-level 'open browser and do X' task to an autonomous computer-use agent. Wraps the trycua/cua Python toolkit via its `cua` CLI - pynput-based, cross-platform (macOS / Linux / Windows). NO custom tools are registered; you call `cua` through pi's built-in bash and read screenshots back through the Read tool. Triggers: cua, computer use, computer-use, GUI automation, screenshot the desktop, click on the screen, type into the active app, scroll the page, control my computer, drive my browser, sandbox, docker sandbox, QEMU sandbox, Lume sandbox, ComputerAgent, cua do, cua sandbox, 컴퓨터 자동화, 스크린샷 찍어, 내 컴퓨터 조작, 브라우저 열어서, 샌드박스, 화면 자동화, 마우스로 클릭, 키보드 타이핑, computer use 위임, 자동으로 클릭, 자율 에이전트로 처리.

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

Create and wire Replica prototype controls. Use when asked to add or change dropdowns, sliders, input fields, toggles or action buttons that configure variants, scenarios, visible UI, app state or data sources, even without canvas terminology. Covers declarations, typed bindings, defaults, conditions, resets and actions. Product UI form fields and filters alone belong to create-prototype.

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

Use when drafting a bug or defect ticket, reviewing one someone else wrote, or deciding whether a reported problem is ready to file. Keeps what the reporter actually saw separate from what the agent later found out, so a reader can tell which lines are testimony and which are collected proof. Trigger phrases: 'file a bug', 'write up this defect', 'triage this report', 'is this ticket ready to file', 'what did the reporter actually see'.

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

GLTF pipeline: production-level GLB conversion, draco/meshopt, lazy load. Use when implementing, reviewing or testing gltf pipeline for React, Vite, Next.js or Perfect_AI projects.

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

Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.

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

Use when acting as the orchestrator agent that drives Syntropic137 - running the dogfood loop, deciding what to dispatch next, landing agent PRs, deploying a beta, triaging failed executions, or keeping the scratchpad, paper cuts and retrospectives current. Trigger phrases include "orchestrator tick", "keep the loop running", "what should we dispatch next", "land these PRs", "why are PRs stacking up", "deploy the next beta", "pit stop", "the run failed, what now", "write the retro", "is the system helping", "scale quality", "learning loop for the orchestrator". Do NOT use for deciding whether one task belongs in a workspace or locally (see `dogfooding`), for turning one incident into an eval case (see `learning-loop`), for designing a workflow A/B experiment (see `workflow-experimentation`), or for release-branch and version-bump mechanics (see `devops`).

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

Use for pull-request, merge, version and release mechanics in the Syntropic137 repo, and for CI or release-pipeline failures. Trigger phrases include "open a PR", "submit my changes", "address the review comments", "Copilot left comments", "merge this PR", "push this nit straight to main", "CI is red", "the release gate failed", "smoke test broke", "why is this PR BLOCKED", "bump the version", "cut a release", "release v1.x", "write the release notes", "main -> release PR", "approve the release gate", "the release published a bad asset", "triage the open PRs", "PR backlog", "which PRs are ready to merge", "merge order", "DORA metrics", "deploy frequency", "lead time", "change failure rate", "time to restore", "why didn't the issue auto-close". Covers trunk-based `main`, the `release` branch, local gates (`just qa-ci`, `just preflight`), GitHub Actions gates, review and merge policy, and post-release verification. Do NOT use for deciding what to dispatch, running the orchestrator loop, or deciding when to deploy a beta or run a pit stop (see `orchestrating`); for whether a task belongs in a workspace or locally (see `dogfooding`); for using the `syn` CLI as an end user (see the syntropic137 plugin skills).

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

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

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

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

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

Use when: assumptions audit, audit assumptions, check for hidden assumptions, plan/ticket has ambiguous scope edges, pre-flight before finalizing a ticket, unstated assumptions, or 'what am I assuming'. Surfaces unstated assumptions, ambiguous scope edges, and untested preconditions in a finished plan/ticket/ADR before it is handed to Builder. Optional pass — Architect judges when to apply it; not a mandatory gate on every ticket.

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

Use when: architecture mode, architect this, ADR, C4, PlantUML, system boundary, design decision, PRD gap, high ambiguity, multiple technical approaches, security architecture, data architecture, integration risk, implementability gap, story ticket, or epic ticket.

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

Universal guardrails loaded by every agent. Defines Verify Before Reporting (VBR), Write-Ahead Log (WAL), and the security baseline. Always-on, role-independent.

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

Use when: Good night Team, EOD, Wrapping up, or end-of-day consolidation. Archives session context, promotes durable patterns, and compacts live agent memory files for the next session.

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

Context-survival and proactive-iteration extensions. Always-on. Covers Working Buffer Protocol, Compaction Recovery, Relentless Resourcefulness, and Self-Improvement Guardrails.

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

One-question-at-a-time design interrogation. Use when: 'grill me', 'interrogate this', 'one question at a time', 'brainstorm', 'let's brainstorm', 'let's discuss', 'lets discuss', 'discuss', 'walk me through', or design review start. Produces ADRs and glossary as decisions settle. Use for unsettled designs; for settled designs go straight to architecture-mode. When the design is unsettled and also has high ambiguity, several technical approaches, or security/data risk, load architecture-mode alongside.

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

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

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

Productivity analyst that maps your workflow, scores tasks by time cost and energy drain, and builds a prioritized 4-week automation plan. Use when you want to audit your workflow, figure out what to automate, do a productivity review, identify high-leverage tasks, feel overwhelmed and need to prioritize, or after the compounder surfaces new friction. Part of the architect-system loop. Outputs to system/audit-report.md.

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

Create a new App Store Connect app record via browser automation. Use when there is no public API for app creation and you need an agent to drive the New App form.

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