「oop」の検索結果

Don't over-equip an agent with tools/MCP servers. More tools = more ways to fail and a higher cognitive load. Use when wiring tools or an agent underperforms.

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

Review SQL and ORM queries for correctness, safety, and performance before they ship.

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

Rebase, squash, or rewrite history without losing work or breaking shared branches. Use before any history rewrite.

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

Write the goal spec on disk before the agent acts, so it can't drift. Use before any multi-step task.

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

Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice.

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

Catch hardcoded secrets, keys, and tokens before they get committed. Use before any commit and on any file with credentials.

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

Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.

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

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

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

Use for ANY bug, test failure, crash, or unexpected behavior. Forces reproduce-then-isolate before proposing a fix. Stops the agent from guessing.

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

Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.

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

Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.

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

Security-review a diff against the OWASP Top 10. Use before merging anything that touches auth, input handling, queries, or external calls.

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

Reduce a change to the minimum that solves the problem. Use when code is over-engineered or a diff is bloated.

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

Get a PDF into the model without blowing the context window or losing structure. Native PDF beats OCR-then-text for most cases; extract-then-summarize beats native for very long docs.

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

Write a PR description a reviewer can approve fast. Use when opening any pull request.

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

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

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

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

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

Detect and interrupt the pattern where an agent confidently praises work it just produced instead of reviewing it critically. Same-context grading is not review — it's rationalization.

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

Cooperatively pause unfinished work in the current session, leave a precise continuation checkpoint, and resume from it when the user later says continue. Use only when the user explicitly requests this pause workflow. Do not use for crashes, app shutdown, new-session handoffs, or ordinary task summaries.

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

Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty. Use when iterating toward product/market fit, designing MVPs, deciding whether to pivot or persevere, setting up actionable metrics, or accelerating the Build-Measure-Learn loop. Triggers include 'how do we test this idea fast', 'what should our MVP look like', 'our metrics look good but we're not growing', 'should we pivot', 'we're building features no one uses', 'how do we measure validated learning', 'vanity metrics vs real metrics', 'how to do innovation accounting'. NOT for companies with proven product/market fit scaling a known playbook (use Crossing the Chasm), not for determining Market Type (use Four Steps), not for sales methodology (use SPIN Selling), not for pricing strategy (use Monetizing Innovation).

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

Cialdini's seven principles of compliance (the classic six — reciprocation, commitment-consistency, social proof, liking, authority, scarcity — plus Unity, added 2016) and Pre-Suasion. Use when crafting ethical persuasion (marketing, sales, negotiation), defending against manipulation, or designing systems that need cooperation. Includes replication-crisis caveats and known factual corrections (Bickman parking-meter numbers, Hofling modern replication, Drive Carefully condition disambiguation, Genovese myth).

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

Evidence-first development — surround the implementation with an executable spec and a gauntlet of constraints (tests, types, coverage, mutation) so line-by-line review becomes optional. Use when the user explicitly asks for high-assurance or evidence-first work ("reliable", "TDD", "prove it works", "I won't read the code"), or when the change touches high-stakes domains (money, auth, data loss, concurrency, public API). For routine changes where the user just wants normal tests, write good tests directly instead of invoking this loop.

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

RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes

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

Build a growth strategy with frameworks, metrics, and experimentation. Use when the user says "growth strategy", "growth plan", "AARRR", "growth loops", "North Star Metric", "growth model", "activation rate", "retention strategy", "churn reduction", "growth experiments", or asks about overall growth frameworks and metrics for their product.

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