「discipline」の検索結果

Design discipline-specific critical thinking tasks grounded in knowledge-contingent reasoning rather than generic skills. Use when embedding higher-order thinking into subject content.

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

Coder-agent working-file budget discipline: keep the editable working set (files you /add into writable context) under ~25k tokens, separate "read" from "edit", delegate breadth to a read-only repo-map, and drop files once edited. Use when an LLM coder-agent edits multiple files, when the working set must stay focused, or when the model starts editing the wrong file / missing targets because too much context dilutes attention. Search keywords: context window full, agent edits wrong file, too much context, /add /drop files, working file budget, context dilution, lost in the middle.

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

Shared discipline for every hunt-* skill: scope and authorization gating, the two-account rule, the confirmation gate that separates a real finding from a false positive, enumeration limits, stop conditions, marker discipline, wiki-first query and self-heal, FIND output, Deadends, and wiki distillation. ALWAYS LOADED alongside any hunt skill. Also trigger directly on "is this in scope", "is this a real bug", "how do I confirm this", "should I keep going", "how many IDs should I test", "what severity", "how do I report this", "I got someone else's data". Every hunt-* skill assumes this file; without it they run without their safety and quality layer.

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

Trading psychology, risk management discipline, position sizing psychology, drawdown management, behavioral bias mitigation, emotional discipline framework, loss aversion control

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

Design discipline-specific critical thinking tasks grounded in knowledge-contingent reasoning rather than generic skills. Use when embedding higher-order thinking into subject content.

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

Create a writing scaffold teaching the genre conventions specific to an academic discipline. Use when students write lab reports, historical essays, or other discipline-specific text types.

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

🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns. 🇨🇳 B2B SaaS 增长 — PLG vs SLG 决策手册 — 诊断你的瓶颈是分发、定价还是 PMF。按 ACV 和销售周期选 PLG/SLG，$0 → $10M ARR 的 5 阶段路径，NRR 纪律，联盟与渠道打法，Enterprise 分层。提炼自 HeyGen、Deel、Vercel、Supabase、Snowflake。 🇯🇵 B2B SaaS グロース — PLG vs SLG プレイブック — 課題が流通・価格・PMFのどれかを診断。ACVとセールスサイクルでPLG/SLG選定、$0→$10M ARRの5段階パス、NRR規律、アフィリエイト＆チャネル。 🇰🇷 B2B SaaS 성장 — PLG vs SLG 플레이북 — 병목이 유통·가격·PMF 중 무엇인지 진단. ACV와 세일즈 사이클로 PLG/SLG 선택, $0 → $10M ARR 5단계 경로, NRR 규율, 제휴 & 채널. Triggers: "B2B growth" | "B2B SaaS" | "PLG" | "SLG" | "product-led growth" | "sales-led growth" | "PLG or SLG" | "SaaS pricing" | "ARR growth" | "NRR" | "go to market" | "enterprise sales" | "affiliate" | "PMF" | "B2B 增长" | "PLG 还是 SLG" | "SaaS 定价" | "渠道合作" | "PLG/SLG 선택"

The discipline of keeping a field notebook — words, pictures, numbers, metadata, and questions captured during sustained outdoor observation. Covers the Laws notebook method, the sit-spot practice, phenology recording, sketch-first-name-later discipline, and the long-term research value of accumulated journals. Use when the task is to teach or structure ongoing field observation rather than answer a one-shot identification.

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

Martial arts as body discipline — the shared pedagogical structure across striking, grappling, and weapon arts (stance, distance, timing, ukemi, live partner work, graded ranking, and the ethical container the best schools enforce). Covers karate, judo, jiu-jitsu (Brazilian and traditional Japanese), aikido, kendo/kenjutsu, boxing, muay Thai, and wrestling at enough depth that an agent can place a user into a reasonable first-month practice and recognize the safety failures that matter most. Leans on Moshé Feldenkrais's judo background and Yang Jwing-Ming's martial scholarship for the internal-to-external bridge. Use for any query about beginning a martial art, training injury patterns, graded progression, or the ethics of combat training.

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

Orchestrator discipline plugin documentation index. Load when needing to read about orchestration patterns, delegation rules, or context window management.

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

Use when Odylith Discipline pressure behavior, zero-credit hard laws, host/lane parity, or benchmark-proved learning-spine contracts need validation.

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

Use when Odylith Discipline pressure behavior, host/lane parity, or credit-safe benchmark proof needs validation.

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

Bulletproof agent operating protocol. 15 failure-prevention rules distilled from 120+ real sessions and 10 agent definitions. Covers fabrication, constraint tracking, verification, scoping, retry discipline, and communication. Load before any task to prevent the most common agent failure modes.

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

Use when preparing or writing any committable deliverable (phase closeout, status report, skill file, wave spec, README section, summary document, CHANGELOG entry, or any markdown file declaring completion or pass/fail status). Applies before the write happens, not after. Without this discipline, agents ship 60% deliverables and declare closure prematurely.

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

PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.

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

Design and implement systematic checklists that reduce errors by 30-50% in complex, high-stakes domains (medicine, aviation, construction, finance). NOT for simple tasks or when comprehensive instruction is needed.

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

Conditional discipline for projects hosted on a git forge (GitHub, GitLab, Forgejo, …): branch↔PR mapping, self-contained PR prose, review-on-forge, merge consent, and the forge audit. Trigger when: - Opening, updating, reviewing, or merging a pull/merge request. - A campaign's integration branch is ready to surface on a forge. - Auditing forge-side presence at merge-consent or campaign CLOSE. - Prompt contains: /forge, pull request, PR body, merge request, forge discipline, PR review, stacked PR.

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

Knowledge base from the FAA Systems Engineering Manual (SEM) v1.0.1. Use for civil-agency systems engineering as the FAA practices it inside the Acquisition Management System (AMS) and the National Airspace System (NAS): the five-phase AMS lifecycle and its decision points; operational concept development and implementation-free functional analysis (ConOps, FFBD/N², CMLs); requirements analysis and architectural design synthesis (PRS→MRS, the PRD ratchet pPRD→iPRD→fPRD, RAM, ISEF/DoDAF views, CPRs); the seven technical management disciplines (Integrated Technical Management/SEMP, Interface Management/IRD-ICD, Risk-Issue-Opportunity, Configuration Management, SE Information Management, Decision Analysis, Verification & Validation); and the specialty disciplines (RMA via Service Threads/STLSC, Life Cycle Engineering, E3/Spectrum, Human Factors, Information Security via the NIST RMF, System Safety via the SMS, and Hazardous Materials/Environmental/EOSH). Scope limits: this is FAA-specific guidance, not policy — it is a tailorable menu that points outward to companion handbooks (FAA-HDBK-006A for RMA, the SMS Manual, the NIST 800-series) rather than restating generic SE theory; it is thin on detailed cost estimating, contracting/FAR law, software-development methodology, named anti-pattern catalogues, and any non-FAA or non-civil-aviation lifecycle. Source has no page numbers in the extracted text (~360 pp.).

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

Prepares a DRAFT management-of-change intake record from a change description (email, meeting note, marked-up drawing or request form): what changes from what to what and where, the identifiers named, the candidate affected documents matched against the register, the disciplines to consult with the reason for each, and the numbered questions reviewers must answer, with UNKNOWN wherever the description is silent. Prepares the record only: never approves, classifies the change, decides replacement in kind or makes any hazard or safety judgement. Use when the user asks to "raise an MoC for this", "prepare the change request intake", "which documents does this change touch", "who needs to review this change" or "draft the MoC form from this email". Do not use for tracking who owes information to whom across disciplines, use interface-register-builder instead. Drafts for human review; never approves, authorises or signs off.

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

Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导

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

Operating discipline distilled from Claude Fable 5 for sessions and subagents on weaker models (Opus 4.x, Sonnet 5/4.x, Haiku 4.5) doing agentic coding. Load it at the START of any non-trivial task when not running on Fable 5: debugging, refactoring, changes across 2+ files, or unfamiliar code; and instruct a subagent on Opus/Sonnet/Haiku to read this skill with a non-trivial assignment. Triggers include "think like Fable", "fable-mode", "turn on discipline", "work carefully", dispatching a subagent on a weaker model, and repeated mistakes or rework in the session. NOT needed for trivial edits (rename, typo, one-liner) or purely conversational answers.

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

Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 5-stage recon pipeline (seed discovery, asset expansion, enrichment, exposure analysis, reporting), asset-graph discipline with 29 asset types, severity rubric (CRITICAL/HIGH/MEDIUM/LOW/INFO), confidence upgrade workflows, time budgeting, asset-level triage rules, scale-based tactics, identity-fabric mapping (Entra/Okta/ADFS/Google/SAML/M365 Teams+SharePoint+OAuth), API and auth-map methodology, JavaScript deep analysis, mobile attack surface, cloud attack surface, breach×identity correlation, detectability tagging, detection-aware probing (back-off, persona rotation), read-only validator discipline, WAF/CDN bypass + origin discovery, vulnerability prioritization (CVE/EPSS/KEV), phishing infrastructure planning + pretext development, bug bounty submission templates, client deliverable templates with risk translation, threat-actor investigation (incl. RU/CN pivots), cryptocurrency tracing,...

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

Design and implement systematic checklists that reduce errors by 30-50% in complex, high-stakes domains (medicine, aviation, construction, finance). NOT for simple tasks or when comprehensive instruction is needed.

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

Discipline an AI agent needs to work an issue/task tracker (Jira, Linear, GitHub Issues) as the shared source of truth: pull the right next item instead of inventing work, search before creating to avoid duplicates, write actionable items with checkable acceptance criteria, keep status transitions honest, and link work to items via branches/PRs/commits so progress is legible. Use when an agent picks up tracker work, files a new issue, updates status, or closes an item. NOT for authoring the PR itself (use agent-pr-authoring), roadmap-level planning and prioritization (use legible-roadmap-with-sidequests), or the mechanics of multiple agents coordinating on the same codebase (use multi-agent-coordination).

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