「discipline」の検索結果

Discipline for the seam between two SDKs (or two sides of one contract) that the same hand writes. The failure mode: "we own both sides" produces dirty contracts no foreign reviewer would accept. The exercise: pretend the other side is FFI, IPC, or a network protocol you cannot rewrite. Spawn an adversarial subagent profiled as the producer's maintainer; negotiate the change as a feature request, not a PR. Companion to $sdk-design. Language-agnostic — applies to a TS package + its consumer, a Rust crate + its WASM binding, two services sharing a wire format, or any other boundary the same author writes both ends of.

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

Rewrite and optimize existing blog posts for Google SEO (May 2026 Core Update, March 2026 core/spam context, June 2026 spam context, E-E-A-T) and AI citation visibility as one SEO discipline. Full rewrite for both Google rankings AND AI citations. For AI-citation-only audit (no Google work), use blog-geo instead. Replaces fabricated statistics with sourced data, applies answer-first formatting, adds Pixabay/Unsplash images, generates built-in SVG charts, validates Article-priority schema, performs AI content detection, adds citation capsules and information gain markers, and updates freshness signals. Works with any blog format (MDX, markdown, HTML). Use when user says "rewrite blog", "optimize blog", "update blog", "improve blog", "fix blog", "refresh blog post", "blog optimization".

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

Rewrite and optimize existing blog posts for Google SEO (May 2026 Core Update, E-E-A-T) and AI citation visibility as one SEO discipline. For AI-citation-only audit (no Google work), use blog-geo instead. Replaces fabricated statistics with sourced data, applies answer-first formatting, adds images, generates SVG charts, and updates freshness signals. Works with any blog format (MDX, markdown, HTML). Use when user says "rewrite blog", "optimize blog", "update blog", "improve blog", "fix blog".

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

Full-lifecycle blog engine with 31 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents. Routes user requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW framework prompts, topic-cluster execution, and multilingual publishing. Optimized for Google rankings around the May 2026 Core Update, E-E-A-T, and AI citations as one SEO discipline. Supports any platform (WordPress, Next.js MDX, Hugo, Ghost, Astro, Jekyll, 11ty, Gatsby, HTML). Use when user says "blog", "write a blog", "blog post", "blog strategy", "content brief", "editorial calendar", "blog audit", "blog optimization", "topic cluster", "multilingual blog", "FLOW framework", or any /blog subcommand. Sub-skill descriptions cover narrower triggers.

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

Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a cluster, work out why VMs are slow when the hosts look idle, clean up sprawl, set snapshot and template policy, or decide what stays virtualized and what moves to cloud.

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

Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.

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

Converts an audited medical research gap into a complete, structured, gap-traceable study design. Always use this skill whenever a user already has one or more candidate research gaps and wants to transform them into an executable biomedical research plan rather than re-run broad topic ideation. Covers six gap-to-design patterns (evidence-completion, mechanism-resolution, cell-state/context-mapping, translation-bridge, causality-upgrade, population/stage-specific) and always outputs one recommended primary protocol, a gap-to-design dependency map, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path, and verified design-support literature rules. Never fabricate references. Preserve claim-evidence discipline and do not replace a topic-specific gap with a generic workflow.

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

Refines broad, vague, or aspirational biomedical research objectives into clear, bounded, measurable, executable, and downstream-ready study objective statements. Always use this skill when a user has a general aim such as “explore a mechanism,” “study prognosis,” “investigate biomarkers,” or “look at treatment response,” but the objective is still too broad, non-operational, or too ambiguous to support protocol framing, design selection, analysis planning, or hypothesis design. Never assume that polished wording alone means the objective is actionable. Focus first on objective type, missing operational elements, scope discipline, and downstream-ready formulation.

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

Assesses whether study results are trustworthy by auditing design integrity, sample structure, statistical handling, bias control, validation chain, and claim discipline. It identifies where results are robust, fragile, overfit, under-validated, or overclaimed. Always separate reported findings from reliability judgment. Never fabricate references, PMIDs, DOIs, trial identifiers, study features, or validation claims.

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

Designs primary aims, secondary aims, and testable hypotheses from broad biomedical research ideas. Use this skill when a user needs to convert a loose study idea into a tighter protocol-framing structure with clear aim hierarchy, hypothesis discipline, and separation between hypothesis-driven and exploratory components. Always keep aims answerable, non-overlapping, and aligned to the intended evidence type and study scope.

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

Ranks papers by evidence family, methodological quality tier, validation depth, and claim discipline; assigns anchor, context-setting, mechanistic support, or caution citation roles; prevents prestige-based or design-label-based ranking errors.

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

Builds background-gap-objective logic for biomedical manuscript introductions with clear study positioning and disciplined narrative structure.

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

Writes the full Introduction section of a biomedical manuscript based on an approved or sufficiently clear study logic, while preserving evidence boundaries and introduction discipline.

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

Organizes biomedical figures, analyses, and result blocks into a clear Results section structure with disciplined narrative ordering and evidence-aware presentation.

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

Use when evaluating crypto charts through an Hsaka-style technical lens: market structure, trend, invalidation, leverage discipline, and narrative-aware timing.

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

Use when evaluating trend-following trades, pivotal-point breakouts, pyramiding, stop discipline, or whether a liquid market is acting right in a Jesse Livermore style.

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

Use when evaluating Ed Seykota-style systematic trend following: mechanical rules, long-term trend capture, small losses, position sizing, whipsaw tolerance, and emotional discipline.

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

Use when evaluating growth stocks through O'Neil CAN SLIM: earnings acceleration, relative strength, institutional demand, market direction, base quality, and breakout discipline.

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

Use when evaluating Paul Tudor Jones-style macro trend trades: major turning points, trend confirmation, risk control, stop discipline, liquidity, and not losing big.

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

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

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

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

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

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

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

Final completion discipline including summary generation, plan document updates, and confirmation that all success criteria from the original plan are satisfied.

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

Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.

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