「reserve」の検索結果

Constant-product AMM bonding curve math for Pump token pricing — buy/sell quoting, fee-aware calculations, market cap computation, tiered fees, ceiling division, virtual vs real reserves, and edge-case handling.

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

반복되는 파라미터 그룹을 객체로 치환(IPO)하거나, 객체에서 꺼낸 값 대신 객체 자체를 전달(Preserve Whole Object). "파라미터 객체", "인자가 너무 많아", "start·end 대신 Range로", "/introduce-parameter-object" 요청 시 사용. 단, 결과 객체가 검증·연산을 가진 도메인 값이면 /discover-value-object가 적합. /introduce-parameter-object [commit-ref]로 호출.

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

Run one explicit escalation pass using the original glaze prompt words verbatim. Use when prompts say `/tw-glaze`, when the first answer feels merely adequate, or when you want the exact original rhetoric preserved while pushing for a materially stronger direction.

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

Compile up to five durable insights from the current conversation for possible addition to CLAUDE.md. Use before clearing context, when asked to remember lessons, or when the user wants project conventions and preferences preserved.

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

Run a second, harder escalation pass using the original glazer prompt words verbatim. Use when prompts say `/tw-glazer`, when a first escalation still feels incremental, or when you want the exact original rhetoric preserved while forcing a sharper replacement rather than more polish.

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

Signpost (not a knowledge pack) for the systems-engineering standards landscape — ISO/IEC/IEEE 15288, 24748, 29148, 42010, 15026, 24765; INCOSE SE Handbook & Vision 2035; OMG SysML; SAE/EIA 1001/649/748; ECSS space standards; NATO AAP-48; CMMI; NIST SP 800-160; and more. Contains NO source content: it lists each standard's designation, title, purpose, owning SDO, whether it's redistributable, and where to get it. Use when you need to identify or locate an SE standard — most are paywalled/all-rights-reserved and cannot be packaged, so this points you to the owner (and to the open packs where one exists).

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

Knowledge base from the NASA Cost Estimating Handbook (CEH) v4.0. Use for NASA's 12-step, three-part cost estimating process (Project Definition, Cost Methodology, Cost Estimate); the WBS, CADRe, and ONCE data backbone; estimating methodologies (analogy, parametric/CER, engineering build-up, EVM, Delphi); ground rules and assumptions, data normalization and inflation (BY/CY/RY); the point-estimate-to-S-curve cost-risk chain and Unallocated Future Expense (UFE) reserves; Joint Cost and Schedule Confidence Level (JCL) analysis via probabilistic cost-loaded schedules; decision-support analyses (sensitivity, trade studies, make/lease-vs-buy, affordability, CAIV); and economic analysis (discounting, NPV, OMB Circular A-94). The cost-estimating complement to NASA's SE and risk packs. Does NOT reproduce the handbook's tool-specific procedures, worked examples, or appendix-depth methods (it names the appendices), nor cover full DoD/GAO cost guides, schedule construction, or formal risk management beyond the cost interface.

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

Proposes tag and number structures for the new lines and instruments in a P&ID draft according to the project's numbering procedures, checks every tag extracted from the PFD against the quoted procedure format, and lists cross-section identifier mismatches and the registry checks a human must run. Never invents a numbering convention, never alters a PFD tag and never assigns a sequence number the procedure reserves for the registry. Use when the user asks to "run the tagging and numbering section", "check the tags against the numbering procedure", "propose the tag structure for the new lines and instruments" or "list the registry checks before validation" after the process safety flags. Do not use for validating the four sections, use validation-and-review-package instead; do not use for instrument content, use instrumentation-and-control-enrichment. Drafts for human review; never approves, authorises or signs off.

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

Build full-paper Chinese-English side-by-side, figure/table-aware, source-grounded Markdown readers for journal or conference papers from PDF, DOI, arXiv, publisher HTML, or pasted text. Use whenever the user asks to translate or read a paper, make 中英文对照/原文对照/全文翻译解读, extract figures or tables into the right positions, preserve figure/table placement near relevant prose, or keep exact source anchors for every block. This skill must not degrade into a summary-only output unless the user explicitly asks for a summary. Also trigger on general paper-reading and translation requests even without the word "Nature", such as reading/translating an academic paper, literature reading, understanding a paper, and Chinese phrasings like 读论文、精读论文、论文翻译、文献翻译、文献阅读、学术阅读、帮我读这篇文章、翻译这篇paper.

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

Handle UTF-8 and text encoding safely in WordPress plugins, especially on WP 6.9+ where wp_is_valid_utf8(), wp_scrub_utf8(), and noncharacter helpers replace older seems_utf8-style checks. Covers when to validate, scrub, reject, or preserve invalid bytes; wp_check_invalid_utf8 behavior; XML/JSON/feed/export boundaries; and avoiding data loss from premature replacement. Use when processing imported text, CSV, XML, feeds, email, REST payloads, AI prompts, logs, filenames, or external API data.

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

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

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

Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

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

Control risky structural change by proving a refactor is necessary and that behaviour, contracts, data, security boundaries, and operational properties can be preserved through a staged migration. Use whenever the user wants to refactor, restructure, clean up, modernise, extract, migrate, rewrite, or re-architect existing code, or asks whether they should. Prefer this over starting the refactor. DO NOT REFACTOR is a first-class outcome. Part of the audit suite; inherits the shared constitution while its own job is proving necessity and behavioural preservation.

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

Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.

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

Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits

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

Preserve the coding agent's explicit AAS skill selection as a validated stack and optional evidence.

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

Use when working with Cloudhealth — cloudHealth by VMware multi-cloud cost management and governance. Covers cost reporting, rightsizing recommendations, governance policies, budget tracking, reserved instance management, and compliance auditing. Use when analyzing cloud spend across providers, enforcing tagging policies, or tracking budgets.

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

Use when working with Aws Pricing — aWS pricing helper for cost queries. ALWAYS use get_aws_cost script for pricing questions. Use when: - User asks about AWS resource costs or pricing - User wants to compare pricing across regions - User needs spot, on-demand, or reserved pricing info Triggers: aws pricing, aws cost, how much does, ec2 price, rds cost, s3 pricing.

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

Use when working with Aws Cost Optimization — aWS native cost optimization using Compute Optimizer, Trusted Advisor cost checks, Savings Plan analysis, Cost Explorer, and resource rightsizing. Covers EC2 rightsizing, idle resource detection, Savings Plan and Reserved Instance recommendations, and cost anomaly detection. Use when optimizing AWS infrastructure costs with native AWS tools.

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

Install audited skills from a curated list or GitHub repo path into Codex or Claude Code after selecting the target host. Use when a user asks to list or install a skill, including from a private repo; preserve Codex system-skill boundaries and use an explicit Claude destination for Claude Code.

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

Recognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution

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

Expert en optimisation des coûts cloud (AWS cost, reserved instances, spot, rightsizing, FinOps)

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

Preserve and inventory scan archives while retaining capture variants, hashes, calibration, and frame provenance.

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

Build and review evidence tagged Blender architectural candidates, preserve unrelated scene content, and produce requested photographic materials, stills and portable model deliveries.

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