Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
日本語の概要は準備中です。原文の説明を表示しています。
3,827 件 ・ 関連度順
概要と使いどころ
Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
日本語の概要は準備中です。原文の説明を表示しています。
Optimizes API performance through payload reduction, caching strategies, and compression techniques. Use when improving API response times, reducing bandwidth usage, or implementing efficient caching.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a user from an unclear idea to an actionable plan through the agent harness's native ask tool and clickable choices. Use when the user wants a guided requirements interview, step-by-step questions, help deciding what to build, or a button-led path from goals to scope, solution, and technology choices. Do not turn an ordinary implementation request or a single clarification into an interview.
日本語の概要は準備中です。原文の説明を表示しています。
Provider-neutral deep-research orchestration for brainstorming, technology choices, comparisons, and state-of-the-art surveys. The Research Lead makes scope and decision calls while native subagents scout, search, verify, synthesize, audit, write, and commit every research artifact.
日本語の概要は準備中です。原文の説明を表示しています。
Map the big picture around a topic or software repository by identifying its boundaries, layers, actors, components, relationships, flows, history, fault lines, and open questions, then explain how the pieces fit together and where to look next. Use when a user asks to understand a whole field, domain, technology, ecosystem, industry, codebase, architecture, unfamiliar repo, or phrases such as "give me the big picture", "map the landscape", "how does this all fit together?", "help me get oriented", or "what am I missing?"
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Condense rebuttal prose into fewer words without changing the original meaning. Use when a response block, paragraph, or selected passage is too long but all technical content, citations, and commitments must stay intact. Supports academic English.
日本語の概要は準備中です。原文の説明を表示しています。
Translate text between languages with cultural adaptation, terminology consistency, and support for multiple document types including technical docs, marketing copy, and UI strings. Use when the user requests translation or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize a webpage for search engines by analyzing on-page elements, improving technical performance, and implementing structured data for maximum visibility. Use when the user requests seo optimization or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize text using extractive, abstractive, hierarchical, and multi-document techniques, producing concise outputs at configurable detail levels. Use when the user requests summarization or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Rank an existing set of context chunks by relevance, diversity, freshness, and utility. Use when retrieval has already produced candidates that must be scored or reranked; use context-retrieval when the source corpus still needs to be searched.
日本語の概要は準備中です。原文の説明を表示しています。
Use when users want to practice or simulate Java, C++, Go, Golang, mixed-stack, or general backend technical interviews, including resume-based and job-description-based interview preparation.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Molecular Biologist. Use when a task calls for Molecular Biologist judgment. Reasons from central-dogma sequence flow, binding affinity (Kd/Km/kcat), gene regulation, and biological-versus-technical replicate structure through MIQE-compliant RT-qPCR, ddPCR, Western/flow/microscopy, CRISPR editing with rescue, and IWGAV antibody validation while treating off-target reagent effects, batch effects, mycoplasma and cell-line misidentification, and toxicity-driven artifacts as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Hydraulic Engineer. Use when a task calls for Hydraulic Engineer judgment. Reasons from Bernoulli–Darcy–Weisbach, Moody diagrams, HEC-RAS/EPANET modeling, and pump/system curves while treating transient water hammer, air entrainment, and roughness aging as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Fisheries Scientist. Use when a task calls for Fisheries Scientist judgment. Reasons from recruitment, growth, and natural and fishing mortality through state-space assessment models (SS3, SAM, JABBA), CPUE/GLM standardization, and reference points like F_MSY and B_lim under ICES and Magnuson-Stevens frameworks, while treating hyperstability, retrospective bias (Mohn's rho), unaccounted discard mortality, and misspecified M or selectivity as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Finite Element Analyst. Use when a task calls for Finite Element Analyst judgment. Reasons from discretization error, element technology, and constraint physics; runs mesh convergence and Richardson studies, Nastran/Abaqus/ANSYS workflows, RBE2/RBE3 and contact discipline, and ASME V&V 10 verification-before-validation reporting on governing QoIs.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Data Engineer. Use when a task calls for Data Engineer judgment. Reasons from idempotent ELT, medallion bronze/silver/gold, Kimball grain and SCD2, CDC/Debezium and watermark incremental loads, dbt/GX quality gates, Airflow/Dagster orchestration, Iceberg/Delta lakehouse MERGE, data contracts and freshness SLIs while treating silent join drops, duplicate amplification, schema drift, and green-DAG-wrong-numbers as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Computational Chemist. Use when a task calls for Computational Chemist judgment. Reasons from Kohn–Sham DFT, def2/D4 functional selection, and conformer ensembles through VASP/Gaussian/ORCA, AMBER/GROMACS MD, CREST/CENSO sampling, ONIOM/QM/MM electrostatic embedding, GMTKN55 validation, and SCF convergence escalation while treating B3LYP/6-31G*, BSSE, link-atom artifacts, and force-field mismatch as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Abusing Active Directory object ACLs (DACL/ownership) for privilege escalation and lateral movement (GenericAll, GenericWrite, WriteDACL, WriteOwner, AddMember, ForceChangePassword, and replication rights via DS-Replication-Get-Changes-All). Use when BloodHound CE shows an outbound control edge from a principal you own toward a higher-value object, and you want the exact bloodyAD/impacket command to weaponize that ACE, plus detection and remediation. DCSync is covered here strictly as a post-compromise technique, not a user entry path.
日本語の概要は準備中です。原文の説明を表示しています。
Active Directory Certificate Services (AD CS) escalation techniques ESC1 through ESC17, driven by hand with Certipy (ly4k). Use when the target runs a Certificate Authority and you want to find vulnerable certificate templates or CA misconfigurations, request a certificate that impersonates a privileged user, and know the exact certipy command, what each ESC actually checks, the Windows Event IDs that fire, and the remediation. ESC1 and ESC8 are the two you hit most in the field.
日本語の概要は準備中です。原文の説明を表示しています。
Author the research plan — fundamentals first, trade ideas last; Constitution Check evaluated twice; Deviation Register with mandatory Expiry; emits the four side artifacts (brief/entities/reproduce/contracts). Technical (market_data_stage: early) theses MUST emit the entities.md bars schema before implement (Q42).
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial verification of research theses — cross-run/cross-thesis contradiction via the entity index, pre-mortem (Klarman/Kahneman: assume the loss already happened, reverse the path), inversion (Munger: invert, always invert), and wrong_if falsifiability review. ≈50-finding cap sorted by severity; content-derived finding IDs; incremental scoping with three backstops; lifecycle hooks at pillar-complete / thesis-complete / pre-reduction.
日本語の概要は準備中です。原文の説明を表示しています。
Options trade execution, directional strategies long call covered call collar, spread strategies bull call bear put ratio ladder, volatility strategies straddle strangle strap strip, liquidity cost and implied volatility filters, integration with gold.technical_setups for options setup matching
日本語の概要は準備中です。原文の説明を表示しています。
Trade execution using price action setups, major trend reversal trading top and bottom, MTR failure continuation, strong bull and bear breakout trading, strong and weak channel trading strategies, trading range strategies, opening range swings, integration with gold.technical_setups for setup matching and execution planning
日本語の概要は準備中です。原文の説明を表示しています。