「ept」の検索結果

Provides multi-school trading Q&A, chart/OHLCV analysis, annotation, and fresh-market workflows covering ICT/SMC, ChanLun, Wyckoff, Price Action, Order Flow, VSA, and Elliott Wave. Use for trading concepts; capability-discovery questions about available analysis lenses, Schools, models, modes, or data sources; attached charts; pasted OHLCV; chart annotation; or asset-plus-timeframe requests across crypto, stocks, or forex. Defaults unselected market analysis to strict ICT/SMC, honors explicit School/source selectors, and fails closed when no native analyzer exists. Phase 1 comparison is Q&A-only; fetch fresh Mobius Quant API data only after the capability gate.

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

Cents-per-point (cpp) valuations across major loyalty programs from four publications. Floor/ceiling rules for deciding if a redemption is good or exceptional.

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

Search Sutochno.ru (СУТОЧНО.РУ), a Russian short-term apartment-rental platform where you book directly from owners and pay in rubles (Mir card / bank transfer). Best for Russian-speaking travellers booking stays in Georgia / the CIS, where Airbnb and Booking have withdrawn or do not accept Russian cards. Sutochno is NOT behind a bot wall — it ships on the toolkit standard patchright-docker base but runs the bundled chromium headless with no Akamai sensor to defeat. Trigger phrases include search Sutochno, суточно, Russian apartment rental, ruble payment, Mir card, Tbilisi apartment, Batumi apartment, Georgia CIS rental.

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

Step 2 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the visualization plan from outline.json — render plots and conceptual diagrams from experimental_log.md and idea.md, optionally refine via VLM critique loop, and produce context-aware captions. Runs in parallel with the literature-review-agent. TRIGGER when the orchestrator delegates Step 2 or when the user asks to "generate the figures for my paper" or "render the plots from this experiment log".

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

Use when a HyperFrames composition needs seek-safe 2D/3D keyframes, GSAP timelines, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

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

Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a website (/product-launch-video — promo or tour). Unclear → /hyperframes.

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

Use after a phase's code is written, or when the user asks to review changed files for bugs, security issues, or quality. Spawns the gsd-code-reviewer agent at quick, standard, or deep depth and writes the phase REVIEW.md.

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

Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and other visual explanations.

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

Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers queries against the corpus, lints the graph for health, and audits in-context human feedback filed from Obsidian or the local web viewer. Use when (1) scaffolding a new knowledge base for any research topic, (2) ingesting articles/papers/PDFs/web pages into raw/, (3) compiling or restructuring wiki articles from existing raw material, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links / orphan pages / coverage gaps / audit shape, (6) processing human feedback from the audit/ directory and applying corrections. Not for general note-taking, daily journals, or non-wiki Obsidian use.

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

Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.

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

Monthly on the last weekday, light browser lane. Re-tests every theme and every severity rule against a month of real ticket evidence and rewrites strategy/themes.md wherever the evidence disagrees with the assumption. It merges two themes the evidence shows are one, splits a theme whose tickets have two different answers, retires a theme with no volume, creates a theme for a cluster that kept landing unclassified, and rewrites a severity rule wherever the outcomes contradict it. Theme ids are never reused and never renumbered. It holds every outbound action unless you released the channel, and it never touches a credential.

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

Monthly, on the last weekday, file work only, no browser at all. Folds the decision ledger, scores this Employee's own judgement against the metric files that measured it rather than against its own predictions, appends one outcome line per closed decision, retires a move proposed three times and never accepted, and rewrites the priorities where the evidence disagrees with them. It refuses to publish a calibration figure on too few closed decisions, changes nothing outside its own folder, proposes nothing to anybody, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekly, heavy browser lane, read only toward the world with no exception. Works the surfaces on its own watchlist through one contiguous browser phase, captures one dated observation per real change with a verbatim quote and the exact URL, refuses to report any change against a surface it has no baseline for, and writes one capped weekly page. It types nothing that changes anything, takes no action on LinkedIn ever, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Desktop application UI patterns for product owners. Load when designing native or cross-platform desktop applications, writing desktop-specific acceptance criteria, or evaluating panel layouts and keyboard workflows.

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

Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.

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

Terminal UI and CLI design patterns for product owners. Load when designing command-line tools, interactive terminal applications, or writing CLI-specific acceptance criteria.

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

Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.

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

Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.

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

Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.

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

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

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

Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.

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

BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation

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

Dung khi da co MOT master design va can ra du kich thuoc cho tat ca kenh — bang kich thuoc chuan 2025-2026 cho feed, story, reel, cover, placement ads; 3 cach xu ly scale-crop, re-compose, rebuild; quy tac safe zone va cach dat ten file. Kich hoat khi user nhac 'resize asset', 'du kich thuoc', 'adapt kich thuoc', 'bang kich thuoc chuan', 'safe zone', 'anh bi cat mat chu tren story', 'mot anh dang duoc may cho'. Khong dung cho — thiet ke moi tu concept thi dung skill 42-brief-hinh-anh; asset gap khi campaign dang chay thi dung skill 48-quick-visual-brief; liet ke toan bo asset cua campaign thi dung skill 41-campaign-asset-list.

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

Dung khi can brief mot ANH TINH cho designer hoac photographer — banner, thumbnail, poster, anh feed: muc tieu visual, concept va mood, bo cuc, copy overlay, mau va font lay tu brand guideline, kich thuoc theo kenh, tieu chi duyet. Kich hoat khi user nhac 'brief anh', 'brief banner', 'brief thumbnail', 'brief visual', 'dat designer lam anh', 'ta lai anh muon lam sao', 'designer hoi lai hoai'. Khong dung cho — chua co cau overlay / slogan hai lop thi dung skill 74-copy-hai-lop truoc; chuoi nhieu slide thi dung skill 43-brief-carousel; huong dan thao tac tren Canva thi dung skill 45-brief-canva; can asset gap trong ngay khi campaign dang chay thi dung skill 48-quick-visual-brief; tu gen anh bang AI thi dung skill 30-thiet-ke-master.

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